12:00:53 <kkeithley> #startmeeting Gluster community weekly meeting
12:00:53 <zodbot> Meeting started Wed Apr  6 12:00:53 2016 UTC.  The chair is kkeithley. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:00:53 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
12:00:53 <zodbot> The meeting name has been set to 'gluster_community_weekly_meeting'
12:01:14 <kkeithley> probably going to have a light turnout today.
12:01:38 <kkeithley> roll call.  (we'll wait a few minutes to see who turns up)
12:01:45 * skoduri is here
12:01:53 <post-factum> o/
12:02:27 * Saravanakmr is here
12:02:35 <kkeithley> while we're waiting...  who had birthdays in March?
12:03:06 <post-factum> september
12:03:16 * poornimag is here
12:03:51 <kkeithley> yeah, the BLR office has one "party" for everyone's bday the previous month. I think that was today.
12:04:30 <kkeithley> anyway, let's get started
12:04:47 * atinm joins
12:04:53 <kkeithley> first action, who wants to host next week?
12:04:59 * rjoseph_ is little late
12:05:17 <kkeithley> #topic who wants to host next week?
12:05:33 <kkeithley> don't all raise your hands at once.
12:05:54 <kkeithley> okay, we'll come back to it later.
12:06:21 <kkeithley> #topic Last Week's AIs
12:07:16 * ndevos arrived too _o/
12:07:18 <kkeithley> first is mine, sanity checker tools in the codebase.  Actually we have clang analyze support being added to gerrit/jenkins
12:07:25 * anoopcs is here
12:07:46 <kkeithley> That's a good start. I'm going to take the AI off the list
12:08:00 <kkeithley> next: kshlm & csim to set up faux/pseudo user email for gerrit, bugzilla, github
12:08:47 <kkeithley> I don't see csim here, and kshlm is away
12:09:01 <kkeithley> next: msvbhat to announce DiSTAF HOWTO on mailing lists
12:09:09 <kkeithley> anyone see that? Or know about it?
12:09:16 <ndevos> I think he did that
12:09:37 <kkeithley> and the related: msvbhat to add links to DiSTAF on the dev workflow page.
12:09:41 <ndevos> #link http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/14728
12:10:27 <kkeithley> looks like yes to both then?
12:10:46 <ndevos> yes, although I can not find the additions to the developers workflow that quickly
12:11:04 <kkeithley> wasn't that one of the links in the email?
12:11:52 <ndevos> no, that points to the docs in the distaf repo
12:11:55 <kkeithley> er no
12:12:09 <ndevos> there was an update to the developer workflow page on readthedocs
12:12:25 <kkeithley> so a yes and a maybe ?
12:12:44 <kkeithley> I'll leave the second AI open for next week
12:12:44 <ndevos> #link http://gluster.readthedocs.org/en/latest/Developer-guide/Development-Workflow/#commit-policy
12:12:56 <ndevos> there is a topic "test cases" just below that link
12:13:25 <ndevos> so, can be marked as "done"
12:13:43 <kkeithley> okay, both are done then.
12:14:05 <kkeithley> next: jdarcy to share his notes from his Bangalore discussions with the community
12:14:27 <jdarcy> Note done.  People finally seem to be getting out of customer-escalation hell, so I think I'll try to restart this.
12:14:43 <kkeithley> okay, I'll roll this over to next week
12:14:54 <kkeithley> next: jdarcy to follow up on 3.6-maintainer situation
12:15:17 <jdarcy> Also not done.  Haven't been in the office to see the current maintainer since last week.
12:15:30 <kkeithley> okay
12:15:40 <kkeithley> next: ndevos to send out 3.5.9 announcement
12:16:04 <ndevos> ah! I knew I forgot something :-/
12:16:23 <kkeithley> and: ndevos to update events page re: Incontro DevOps
12:16:24 <ndevos> I'll try to do that today or tomorrow
12:16:43 <ndevos> wait, that's a new one? but yes, need to do that
12:17:31 <kkeithley> okay, moving on
12:17:41 <kkeithley> #topic GlusterFS 3.7
12:18:11 <kkeithley> have all the 3.7.10 bugs and the tracker been closed?
12:18:12 <ndevos> kshlm was thinking to release 3.7.11 today
12:18:29 <kkeithley> #info kshlm was thinking to release 3.7.11 today
12:18:39 <ndevos> no, 3.7.10 bugs were supposed to get closed when the release is announced, and due to a bug that was not done
12:19:09 <ndevos> we're trying to keep users away from 3.7.10, and close all 3.7.10 bugs when 3.7.11 is ready
12:19:19 <ndevos> at least, that is my understanding
12:19:29 <post-factum> eh, I've already started 3.7.10 testing...
12:19:53 <ndevos> post-factum: as long as you do not use snapshots, it should be OK
12:19:56 <kkeithley> I don't know how we can keep people from updating to 3.7.10 given that the packages are out there.
12:20:23 <post-factum> ndevos: I don't use them, but still have some questions
12:20:24 <ndevos> kkeithley: well, not announcing the release and not pushing them to repos is one way that should prevent at least some troubles for users
12:20:37 <atinm> kkeithley, even if they do release note (updated) has the work around for that
12:21:13 <atinm> so honestly I am not that worried now..
12:21:13 <ndevos> atinm: ah, but not merged yet?
12:21:36 <kkeithley> indeed, these are all true statements. Anyone know if kshlm is on track to release 3.7.11 today, or is tomorrow more likely? Or when actually?
12:21:38 * ndevos worries that we break installations from users that just blindly update their STABLE release
12:21:58 <atinm> ndevos, its merged, http://review.gluster.org/#/c/13886/
12:22:07 <ndevos> kshlm mentioned he wanted to do it after todays meeting...
12:22:36 <kkeithley> I guess that's as good as we're likely to get. We'll just wait and see.
12:22:38 <ndevos> atinm: ah, my bad, 3.7.10 sorting comes after 3.7.1 :)
12:22:45 <ndevos> #link https://github.com/gluster/glusterfs/blob/release-3.7/doc/release-notes/3.7.10.md
12:22:46 <post-factum> :D
12:23:08 <kkeithley> anything else about 3.7?
12:23:17 <post-factum> skoduri: still no luck with all rpc fixes?
12:24:20 <kkeithley> nothing, okay, moving on
12:24:25 <kkeithley> #topic GlusterFS 3.6
12:24:40 <kkeithley> anything?
12:25:24 <ndevos> ... no raghu?
12:25:37 <kkeithley> one thing of note, apparently the Debian 3.6.9-1 dpkgs have borked dependencies. I'm respinning.
12:26:14 <kkeithley> Any reason to think we're not on track for a release on the 20th?
12:26:18 <skoduri> post-factum, there is only one pending which is waiting on reviews in master branch..rest all merged
12:26:34 <post-factum> skoduri: thanks!
12:26:36 <ndevos> I have not heard of any issues, the 20th is still a while out
12:26:51 <ndevos> not sure if anyone sent backports to 3.6 either...
12:27:10 <ndevos> #info bugs fixed in master/3.7 should also get their backports to 3.6 and 3.5
12:27:27 <kkeithley> okay, no news is good news I guess.
12:28:05 <kkeithley> yes, that should happen as a matter of routine IMO.
12:28:17 <kkeithley> moving on then
12:28:22 <kkeithley> #topic GlusterFS 3.5
12:28:46 <ndevos> no changes planned for the next release
12:28:55 <ndevos> and I still need to announce 3.5.10
12:29:11 <ndevos> the 10th of April will not see a 3.5 release
12:29:25 <ndevos> instead, we'll give our users a 3.7 update this week ;-)
12:29:26 <kkeithley> 3.5.10?
12:29:30 <kkeithley> you mean 3.5.9
12:29:36 <ndevos> oh, yes, 3.5.9
12:29:46 <ndevos> numbers--
12:29:47 <glusterbot> ndevos: numbers's karma is now -1
12:30:31 <ndevos> #info 3.5.9 might be the last release that we see in the 3.5 series, once 3.8 is released it will be EOL
12:30:44 <kkeithley> #info no 3.5 release planned for 10 April.  (due to lack of any backports or bug fixes on the branch.)
12:31:02 <kkeithley> noted
12:31:15 <kkeithley> and speaking of 3.8
12:31:19 <kkeithley> #topic GlusterFS 3.8
12:31:35 <ndevos> there have been more updates on the roadmap
12:31:43 <ndevos> #link https://www.gluster.org/community/roadmap/3.8/
12:31:55 <ndevos> some features are now in the "at risk" category
12:32:20 <ndevos> #info we still need 3.8 feature owners to update the text for their features on the roadmap
12:32:48 <kkeithley> when is the drop dead date?
12:33:01 <kkeithley> besides May/June?
12:33:13 <kkeithley> anything more specific yet?
12:33:16 <ndevos> end of April is code-freeze and branching of release-3.8
12:33:27 <post-factum> very soon
12:33:44 <kkeithley> code freeze or feature freeze?
12:33:45 <ndevos> after branching, we'll clean up the roadmap a little, and move features that didnt make it to "next release"
12:34:12 <ndevos> well, branching, and after that only stability fixes are allowed in release-3.8
12:34:43 <ndevos> unstable features will be disabled/removed so that 3.8 has a fixed feature set for its lifetime
12:35:08 <kkeithley> sounds good. Anything else on 3.8?
12:35:18 <ndevos> actually, the schedule for 3.8 is on the roadmap too
12:35:46 <ndevos> nothing more from my side
12:36:06 <kkeithley> If 3.8 doesn't ship 'til June, then 3.5 is on life support for at least 60 more days.
12:36:25 <kkeithley> anyway... next topic
12:36:31 <kkeithley> #topic GlusterFS 4.0
12:37:05 <kkeithley> jdarcy: ^^^
12:37:05 <ndevos> jdarcy, atinm ?
12:37:11 <atinm> sure
12:37:21 <jdarcy> Nothing for me.
12:37:41 <atinm> From GD2.0 we have couple of patches merged now, one is proxy etcd and the other is single node txn framework
12:38:16 <atinm> jdarcy, I believe Avra also sent a patch to rename NSR to Journal based replication (JBR)
12:38:27 <jdarcy> Yes, there is that.
12:38:32 <atinm> I don't have any updates from DHT2 team
12:38:42 <kkeithley> that's a better name.
12:38:43 <ndevos> atinm: can you remind me where the GD2.0 patches are reviewed?
12:38:44 <jdarcy> I know Shyam has been flat-out on other stuff.
12:39:13 <atinm> ndevos, https://github.com/gluster/glusterd2
12:39:33 <ndevos> jdarcy: oh, reminder! could you make sure that all changes related to JBR and so on are attached to a JBR tracker bug?
12:39:46 <ndevos> atinm: oh, right, no Gerrit for that?
12:39:56 <atinm> ndevos, not yet :)
12:40:03 <jdarcy> ndevos: OK.  I assume one needs to be created, then?
12:40:30 <ndevos> jdarcy: I thought there was a NSR tracker bug already and that can be renamed, but maybe not?
12:40:50 <atinm> do we really have feature specific tracker bug for 4.0?
12:41:01 <ndevos> jdarcy: bug 1158654 seems to be one
12:41:02 <glusterbot> Bug https://bugzilla.redhat.com:443/show_bug.cgi?id=1158654 medium, unspecified, ---, bugs, NEW , [FEAT] New Style Replication (NSR)
12:41:04 <atinm> I thought we just have a 4.0 tracker
12:41:25 <atinm> :-/ my bad
12:41:26 <ndevos> atinm: each feature should have its own tracker, how can we else group patches per feature?
12:41:32 <jdarcy> ndevos: OK, I'll rename that.
12:41:32 <kkeithley> I guess we should have bugzilla components jbr and glusterd2 before too long?  Any other new components we want?
12:41:41 <atinm> DHT2
12:42:11 <kkeithley> atinm: noted
12:42:11 <ndevos> kkeithley: probably also SELinux, richacl, ...
12:42:15 <jdarcy> They're all new codebases, so I'd say yeah, they should have components too.
12:42:50 <kkeithley> #info new bugzilla components needed:  jbr, dht2, SELinux, richacl, glusterd2
12:43:06 <kkeithley> ping me on IRC or send an email if any others are needed
12:43:23 <kkeithley> anything else for 4.0?
12:43:28 <jdarcy> Are SELinux and richacl big enough to get their own components, or would they more logically be parts of components that already exist.
12:43:46 <jdarcy> For precedent, we don't split every performance/* translator into its own component.
12:43:53 <ndevos> I think richacl should bre seperate, SELinux maybe not
12:44:25 <ndevos> but it helps to have a component per xlator, it helps the triaging when new bugs are filed
12:44:38 <atinm> I agree with ndevos
12:44:39 * ndevos has email filters for different components
12:44:42 <jdarcy> Actually it looks like we sort of do.  Huh.
12:45:18 <jdarcy> So I withdraw my question/objection/whatever it was.
12:45:24 <ndevos> #info developers and maintainers should be triaging bugs for their components and use https://github.com/gluster/glusterdocs/blob/master/Developer-guide/Bugzilla%20Notifications.md
12:45:52 * atinm wonders how does ndevos find the links so fast :)
12:46:03 <ndevos> atinm: firefox history!
12:46:04 <kkeithley> he's magic
12:46:31 <atinm> hats off!
12:46:32 <kkeithley> okay, any more 4.0?
12:46:40 <atinm> I am done kkeithley
12:47:31 <kkeithley> #topic meeting chair for next week?
12:47:45 <ndevos> you're doing a great job, kkeithley!
12:48:05 <ndevos> same time as today?
12:48:11 <jdarcy> I thought of volunteering and then not showing up, so nobody would ever try to draft me again.
12:48:31 <kkeithley> yes, same time every week AFAIK
12:49:05 <ndevos> I really wonder where the other maintainers are...
12:51:30 <post-factum> recovering from march birthdays celebration?
12:51:40 <atinm> post-factum, :)
12:52:52 <kkeithley> okay, well, if nobody volunteers, someone is going to get volunteered. Look for the special prize email in your inbox in the next couple of days.
12:53:12 <kkeithley> #topic Open Floor
12:53:14 <post-factum> #link http://random.org/
12:54:03 <kkeithley> any other topics or news?
12:54:29 <kkeithley> going once?
12:54:32 * ndevos thinks hard...
12:54:46 <kkeithley> going twice
12:54:49 * ndevos ... nopw
12:55:07 <kkeithley> #topic recurring topics
12:55:16 <kkeithley> If you're attending any event/conference please add the event and yourselves to Gluster attendance of events: https://public.pad.fsfe.org/p/gluster-events
12:55:22 <kkeithley> Put (even minor) interesting topics on https://public.pad.fsfe.org/p/gluster-weekly-news
12:55:29 <kkeithley> Use the following etherpad for backport requests  https://public.pad.fsfe.org/p/gluster-backport-requests
12:55:35 <kkeithley> anything else
12:55:37 <kkeithley> ?
12:55:52 <post-factum> thx for hosting, kkeithley
12:56:03 <kkeithley> if nothing else, do I have a motion to adjorn (sp?)
12:56:05 <kkeithley> adjurn
12:56:15 <kkeithley> adjourn
12:56:31 <kkeithley> spelling is over-rated
12:57:08 <kkeithley> wow, tough audience. I can't even get a motion to adjourn
12:57:36 <kkeithley> meeting adjourned
12:57:38 <kkeithley> #endmeeting