12:05:42 #startmeeting 12:05:43 Meeting started Wed Jul 1 12:05:42 2015 UTC. The chair is kkeithley. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:05:43 Useful Commands: #action #agreed #halp #info #idea #link #topic. 12:05:48 rollcall 12:05:55 * RaSTar is here 12:05:56 * poornimag is here 12:06:07 * obnox waves 12:06:08 wohoo! kkeithley is our host :D 12:06:14 * kshlm o/ 12:06:25 * raghu is here 12:06:25 * rjoseph is here 12:06:33 agenda at https://public.pad.fsfe.org/p/gluster-community-meetings 12:06:35 * overclk is here 12:07:00 * gd is here 12:07:13 #topic action items from last week 12:07:23 JustinClift to demo the new Forge this week 12:07:42 thunder and lightning going on. Hope we don't lose power 12:08:09 Justin's last day at Red Hat was yesterday, so that's probably a not going to happen 12:08:23 did anyone get a hand-off from Justin on that? 12:08:41 * kkeithley guesses not 12:08:57 no, I thought he wanted to finish that before leaving... 12:09:24 maybe misc or csim knows more about it? 12:09:43 right. I'll take an action to check with his management to see what kind of hand-off we got 12:09:58 #action kkeithley to check on new Forge hand-off from JustinClift 12:10:19 next, hchiramm to updpate about packaging emails 12:10:49 is hchiramm here? I did see email from him indicating we have a couple packaging volunteers 12:11:25 or hchiramm_home 12:11:36 okay 12:11:44 next, tigert summarize options for integrating a calendar on the website, call for feedback. 12:12:46 I think tigert is on holidays 12:13:03 okay, nothing there, next is hagarth will start with planned roadmaps for all gluster.next releases [TBD - will do so by next week] 12:13:28 then csim/misc to pickup the requesting of public IPs and those kind of things for our new servers 12:13:48 that is for the Jenkins slaves 12:14:10 I think you spoke to KB about using something in the CentOS infra? 12:14:26 maybe that is an option too, care to share? :) 12:15:15 okay. yes, that's correct. hagarth and I both spoke to kb. We are allowed to use the CentOS jenkins infra. misc/csim has what he needs to know to start running jobs there. 12:16:27 N.B. that CentOS isn't generally hosting Jenkins for "just anyone." We are being allowed to use it because we're members of the CentOS Storage SIG. If it weren't for that it would require CentOS board approval. 12:16:53 hmm, sounds as if its still the same bottleneck :-/ 12:17:12 Anyway, they have a veryh high powered server and the VMs are there, we just need to start using them. 12:18:00 They have a fat pipe to the internet and to storage, so they're supposed to be pretty fast. And we don't have to pay for using them, like we do for the rackspace VMs 12:18:19 okay, sounds like a plan, but we need to get access somehow, someone needs to do some initial work to prepare the environment for our tests 12:18:20 I suspect it's in our best interest to start using them 12:19:05 misc+csim is quite busy from what I understand, is there someone else that can and want to help out with this? 12:19:41 anyone who wants to help can ping me and I'll send the details 12:20:07 any other questions about Jenkins infra? 12:20:16 questions or comments? 12:20:17 #info volunteers more than welcome to help out with the Jenkins infrastructure provided by the CentOS people 12:20:55 I really think we need to fix up gerrit first. 12:21:12 +1 12:21:13 Getting more jenkins slaves, will only hammer gerrit more. 12:21:39 not more jenkins slave, replacesments for the rackspace ones 12:21:56 ... move that 's' a little around 12:22:50 gerrit is supposed to move to the new server we have, but that is waiting for public IP addresses.... 12:22:55 well, eventually we can have as many as we want, but I'm hearing that gerrit needs some work 12:23:10 I still have problems with gerrit, pages fail to load.. 12:23:15 With the new beefy servers and the CentOS infra, we're sure to get more slaves. Gerrit needs work. 12:23:18 It seems like something related to javascript on this version of gerrit 12:23:37 can we move to 2.11 and try? 12:24:04 Let's take this discussion later, and continue with the meeting for now. 12:24:06 * ndevos isnt a Gerrit admin and has no aspiration to become one 12:24:23 indeed 12:24:41 next is hagarth should remove the meeting invite request, which is done 12:24:50 then raghu to announce 3.6.4beta2 in the mailing list (post RPM build) 12:24:57 * hchiramm : sorry for being late. reg# packaging , yes, we have volunteers. I will start a thread soon explaining the next action plan 12:25:21 3.6.4beta2 rpms are on download.gluster.org. I have not seen an announcement though. Did I miss it? 12:25:24 3.6.4beta2 rpms are ready .. I think raghu will be announcing it soon.. 12:25:51 kkeithley: I have not yet announced it. I am preparing the release-notes and you can expect the announcement EOD today 12:26:09 #info raghu will announce 3.6.4beta2 12:26:19 #info raghu will announce 3.6.4beta2 today 12:26:31 next is ndevos to release 3.5.5 before end of June 12:26:42 missed it! Do we have a new ETA? 12:26:50 its still june, right? 12:27:14 I hoped to do it last weekend, but there is still a little work needed on one patch 12:27:23 I'm trying to get it done this week 12:27:45 I think it's July where I am 12:28:10 It might still be June in Hawaii though 12:28:12 * ndevos had an additional second, but would have liked an additional week 12:28:23 ndevos :) 12:28:25 ;-) 12:29:32 So by Friday (3 July)? 12:29:43 lets try! 12:30:15 #info ndevos will release 3.5.5 by 3 July (which is a holiday in the U.S.) 12:31:08 next is hagarth to push 4.0 roadmap on the site - [TBD, will do so by next week] 12:31:14 so not done 12:31:30 #action hagarth to push 4.0 roadmap on the site by 10 July 12:31:42 then overclk to put up feature page for lockdep 12:31:53 kkeithley, not done 12:32:05 soon? 12:32:12 kkeithley, target for next meeting please (along with other details in -devel ML) 12:32:17 okay 12:32:37 #info overclk to put up feature page for lockdep by 10 July and on -devel mailing list 12:33:05 then krishnan_p to send out email on devel list about improving our epoll solution 12:33:11 I don't remember seeing that. 12:33:53 kkeithley, not ready yet. I haven't gotten around working on that. 12:34:03 kkeithley, I will aim for 10 July too. 12:34:40 #info krishnan_p to send out email on devel list about improving our epoll solution by 10 July 12:34:44 okay, thanks 12:34:51 okay, next 12:34:57 #topic GlusterFS 3.7 12:35:34 Atin, anything to report? An ETA for 3.7.3 perhaps? 12:36:14 kkeithley, I think lot of patches came in after 3.7.2 12:36:18 kkeithley, what do you mean by "improving our epoll solution"? 12:36:35 kkeithley, so we do have a strong reason for releasing 3.7.3 12:36:45 kkeithley, probably in another couple of week's time? 12:37:12 kkeithley, I don't think we have any major issue reported by the community on 3.7.2 12:37:29 kkeithley, so we can wait for another couple of weeks 12:37:46 bene2, https://public.pad.fsfe.org/p/glusterfs-epoll attempts to list a few of those. 12:37:46 yeah, I think so too, atinm 12:37:59 so mid-July? 17 July or 24 July? 12:38:24 24th, earliest? 12:38:36 unless someone hits a real issue? 12:38:48 ndevos, sounds good 12:39:07 so more like late July? 12:39:27 yeah, something like that, no fixed date :) 12:39:35 #info 3.7.3 ETA late July. 12:39:43 yeah, I'm not trying to carve it in stone. ;-) 12:40:11 bene2: don't know, KP can say more about it off-line perhaps. 12:40:22 anything else about 3.7? 12:40:35 going once 12:40:41 going twice? 12:40:46 next 12:40:52 #topic GlusterFS 3.6 12:41:19 so 3.6.4beta2 is out. How long are we going to let that soak before GA? 12:41:33 A couple of weeks? 12:42:16 raghu: ? 12:42:28 1 more week 12:42:50 next week (max end of next week) 12:43:12 so both 3.6.4 and 3.5.5 will land around the same time then. 12:43:32 stable releases ftw! 12:43:51 ndevos: you're not planning on doing any betas? 12:44:04 no, nobody reports back on betas 12:44:07 save that for the next topic 12:44:09 right 12:44:31 #info 3.6.4 GA next week. 12:44:45 anything else for 3.6? 12:45:19 hearing nothing, next is 12:45:24 #topic GlusterFS 3.5 12:45:43 now? no, nobody reports back on betas 12:45:53 right, so 12:46:00 #info 3.5.5 GA next week 12:46:07 correct? 12:46:16 yeah, or this week(end) 12:46:22 anything else about 3.5? 12:46:32 * ndevos did not hear anything 12:46:44 okay, next 12:46:52 #topic GlusterFS 4.0 12:47:05 anyone have anything they want to say about it? 12:47:44 guess not 12:47:53 #topic Open Floor 12:48:17 Anyone? 12:50:07 one, I'd like to shift focus to more unit tests and less on regression tests? 12:50:27 And I'd like to get developers to stop using "inline" 12:50:49 +1 for stop using inline 12:51:24 as in the C keyword? 12:51:32 yeah, the inlines are biting us where gcc-5.x is used 12:51:50 yes, the C language 12:51:52 k 12:52:41 by unit tests you mean cmockery? 12:52:52 s/cmockery/cmocka/ 12:52:57 actually we've switched to cmocka 12:52:57 ok 12:54:01 well, I've put those thoughts out there. I don't expect we're going to make/take any decisions on them today 12:54:30 +1 to more unit tests 12:54:44 we need some guidance on when to add unit tests, and more examples of how to write them to get ideas 12:55:31 who would like to start with a chapter in the developers docs and explain why/how to do it? 12:55:49 I was hoping that we'd get some of our interns to write some, but the idea of unit tests is that the developer who writes the code also writes the unit tests that go with it. 12:56:15 unit tests done correctly anyway 12:56:25 yes, they should be part of the patch that gets submitted, just like regression tests 12:56:45 yes..I will try to get some initial doc done. It would be good to have a buddy though. 12:57:21 RaSTar: I'm sure you can reach out to Andreas Schneider if you have questions about cmocka 12:57:48 ndevos: Just checked now that is by Andreas :) 12:57:54 would be happy to approach him 12:58:10 that would be great. thanks 12:58:18 RaSTar: yeah, he helped with the migration from cmockery2 to cmocka, and wont hesitate to look into gluster sources :) 12:58:19 but learning a new library/tool is more fun if not alone 12:58:35 okay, we're up to the end of the hour. Any last might thoughts? short ones? 12:58:50 yeah, propose a roster/schedule for hosting the weekly meeting (all maintainers should participate) 12:59:23 we have many maintainers now, and all of them should be visibly active in our community 12:59:41 it is expected that all of them will be hosting this meeting every now and then 12:59:46 +1 for a roster of meeting hosts 13:00:28 anyone that wants to put a schedule together, or has an idea how to create such a schedule? 13:00:42 RaSTar, well am okay to pitch in ... but please spare with my abrupt absence if any mainly because of :) 13:01:37 okay, motion to adjourn? 13:01:47 or are there any more topics? 13:02:10 * ndevos does not have a topic 13:02:20 going once 13:02:28 going twice 13:02:39 #endmeeting