15:02:09 <JustinClift> #startmeeting Weekly GlusterFS Community Meeting
15:02:09 <zodbot> Meeting started Wed Jun 11 15:02:09 2014 UTC.  The chair is JustinClift. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:09 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:02:17 <JustinClift> k, who's here? :)
15:02:18 * kkeithley is here
15:02:22 * hagarth too
15:02:27 * JoeJulian is
15:02:32 * ndevos is here, after all
15:02:36 * xavih is here
15:02:50 * Eco_ is here as well
15:03:03 <JustinClift> Cool. :)  Lets start
15:03:05 * hchiramm_ is here
15:03:14 <JustinClift> #topic Agenda items from last week
15:03:24 <JustinClift> "hagarth to send an email to professor in ihep.ac.cn"
15:03:28 <JustinClift> Punted to next week
15:03:29 * raghug is here
15:03:35 <JustinClift> "pranithk to add information about EasyFix to the existing Developer page"
15:03:38 <JustinClift> pranithk: ?
15:03:59 <pranithk> JustinClift: Sorry Didn't get time this week will do it on Friday :-(
15:04:09 <JustinClift> np.  Punted to next week.
15:04:18 <JustinClift> "JustinClift to ask Eco when new site is targetted for roll out"
15:04:42 <JustinClift> Done.  Eco has provided (extensive) task list, but we still need to figure out good target date
15:04:46 <Eco_> JustinClift, DV set a push goal for two weeks, i need to work with you and misc on some of the technical details
15:05:20 <JustinClift> Sure.  If it's Ruby, I'll point you at misc for that.  I don't know Ruby and have no (anti) interest in learning it. ;)
15:05:24 <Eco_> the most daunting tasks at this point are how to get the live feeds (blog, forge, bugs) to work into the static framework
15:05:26 <JustinClift> But other stuff, sure
15:05:28 * lalatenduM_ is here
15:05:56 <JustinClift> Eco_: I think it'll just need triggering of static rebuild when new content comes in.  We'll discuss later
15:06:05 <Eco_> sounds good
15:06:08 <JustinClift> "hagarth to work with the team for adding a web page on details of prominent community members"
15:06:13 <JustinClift> In progress
15:06:35 <JustinClift> hagarth: We did have a Community Member volunteer to help us yesterday with stuff
15:06:47 <hchiramm_> Eco_, can we have a "News" tab as well ?
15:06:52 <JustinClift> It was part of the conversation around the GlusterFS Consultants page.
15:07:29 <Eco_> hchiramm_, the blog post is where most of that would go, is there a need for a seperate news feed as well?
15:07:29 <JustinClift> hagarth: Rodrigo Gonzalez
15:08:00 <JustinClift> hagarth: We could ask him to look on the Net for any substantial users we don't know about, and to help prepare the list of prominent members
15:08:10 <JustinClift> hagarth: It's reasonably likely there are places we don't know about yet
15:08:20 <Eco_> between that, the bugs feed and the forge feed i think thats all the news about Gluster there is?
15:08:28 <hchiramm_> may be about gluster releases and events ? Eco_ ..
15:08:59 <JustinClift> #action JustinClift or hagarth to ask Rodrigo Gonzalez if he'd like to assist with the prominent users page
15:09:09 <JustinClift> hagarth1: Ahhh
15:09:25 <Eco_> hchiramm_, we will look into it if there is a need, most likely we will just add those items to one of the existing entries but no reason not to consider a news feed as well
15:09:28 <JustinClift> hagarth: Here now?
15:09:38 <hagarth> JustinClift: yes
15:09:45 <hchiramm_> Eco_, thanks..
15:09:53 <JustinClift> k.  We're just covering "hagarth to work with the team for adding a web page on details of prominent community members"
15:10:00 <JustinClift> hagarth: We did have a Community Member volunteer to help us yesterday with stuff
15:10:07 <JustinClift> hagarth: Rodrigo Gonzalez
15:10:12 <JustinClift> hagarth: We could ask him to look on the Net for any substantial users we don't know about, and to help prepare the list of prominent members
15:10:16 <JustinClift> hagarth: It's reasonably likely there are places we don't know about yet
15:10:28 <JustinClift> hagarth: So I did this: #action JustinClift or hagarth to ask Rodrigo Gonzalez if he'd like to assist with the prominent users page
15:10:34 <hagarth> JustinClift: ok, cool
15:10:44 <JustinClift> Cool.  Anything else for that item?
15:11:33 <JustinClift> k, guess not.  Moving on
15:11:35 <JustinClift> "JustinClift to start the discussion on gluster-infra about updating links on the main gluster.org website. re 3.5.x links in template & the new Prominent Gluster Users page"
15:11:47 * JustinClift completely forgot about that.  Moved to next week
15:11:56 <JustinClift> #action JustinClift to start the discussion on gluster-infra about updating links on the main gluster.org website. re 3.5.x links in template & the new Prominent Gluster Users page
15:12:13 <JustinClift> "JustinClift to report back if Eco will do the Who Wrote GlusterFS 3.5 page"
15:12:34 <JustinClift> Eco's looking into it.  Sample output from git-dm here: http://fpaste.org/108945/
15:12:36 <glusterbot> Title: #108945 Fedora Project Pastebin (at fpaste.org)
15:12:59 <Eco_> DV also showed me ohloh.net last night
15:13:13 <Eco_> http://www.ohloh.net/p/glusterfs/contributors/summary
15:13:46 <JustinClift> Ahh.
15:13:57 * JustinClift hasn't looked into the Ohloh contributors page
15:14:06 <JustinClift> Wonder how it matches up...
15:14:22 <kshlm> There's github as well, https://github.com/gluster/glusterfs/graphs/contributors
15:14:23 <glusterbot> Title: Contributors to gluster/glusterfs · GitHub (at github.com)
15:14:46 <JustinClift> Eco_: That git-dm output looks useful.  That could definitely be good info source for the Who Wrote GlusterFS 3.5 page.
15:14:53 <JustinClift> Just needs to be padded out and commentary added.
15:15:05 <ndevos> stats for 3.5.0 to 3.5.1 can be gathered with: ./extras/who-wrote-glusterfs/who-wrote-glusterfs.sh v3.5.0...v3.5.1beta2
15:15:05 <JustinClift> kshlm: Good thinking. :)
15:15:15 <Eco_> potentially all three
15:15:20 <JustinClift> Yep
15:15:47 <JustinClift> Eco_: So, you're good to get this Who Wrote GlusterFS 3.5 page done too?
15:16:21 <Eco_> JustinClift, with trepidation, yes  ;)  will need your help sorting out a few of the bits if you dont mind but once i have the data writing the article is simple
15:16:37 <JustinClift> Eco: Cool. :)
15:17:03 <JustinClift> #action Eco_ will create the Who Wrote GlusterFS 3.5 blog post/page
15:17:10 <JustinClift> Eco_: ETA?
15:17:14 <Eco_> this will have to wait until after the site release though since that is my main focus given the short time frame
15:17:26 <JustinClift> Sure
15:17:34 <JustinClift> Clear priority :)
15:17:35 <Eco_> say three weeks, two weeks for site launch one week to write article
15:17:42 <JustinClift> Works for me
15:17:48 <JustinClift> k, next item
15:17:57 <JustinClift> "JustinClift to get the Westford lab mac mini doing nightly GlusterFS build tests happening (cron). Failure emails to gluster-devel I guess"
15:18:05 <JustinClift> Didn't even start this.  Moving it to next week
15:18:07 <JustinClift> :/
15:18:16 <JustinClift> #action JustinClift to get the Westford lab mac mini doing nightly GlusterFS build tests happening (cron). Failure emails to gluster-devel I guess
15:18:19 <Eco_> those mac minis are very old
15:18:30 <JoeJulian> G4?
15:18:36 <Eco_> and you will need to get the latest jaguar or whatever cat name mac uses now
15:18:37 <JustinClift> Eco_: The one I'm thinking of is um... 2011 or 2012
15:18:39 <Eco_> no, core 2
15:18:55 <kkeithley> Mavericks is a cat ?
15:18:56 <Eco_> 2011 i think i ordered them
15:19:12 <Eco_> kkeithley, shows how much i keep up with apple products ;)
15:19:20 <JustinClift> 2011 is still withing support for everything
15:19:33 <JustinClift> They should be fine (with appropriate ram upgrade)
15:19:34 <Eco_> yeah just the OS needs to be updated from what is on them
15:19:46 <Eco_> ram should be 2G so would be good to have more
15:19:47 <JustinClift> Eco_: Hmmm, when you say "them"... I'm only aware of one
15:19:53 <JustinClift> Are there more?
15:19:58 * johnmark listens in
15:19:59 <Eco_> there were three all told
15:20:03 <kkeithley> yeah, Mavericks needs more than 2GB
15:20:11 <Eco_> i have one so there should be two left
15:20:25 <JustinClift> Interesting.  Let's look into this
15:20:39 <Eco_> if not, one may have fallen off a truck at some point during all the moving but that is my recollection
15:20:45 <JustinClift> #action JustinClift to look into the "other Mac Mini's" we might have lying around
15:20:51 <JustinClift> Eco_: Sure
15:20:53 <johnmark> JustinClift: is the bitergia dashboard interesting?
15:20:57 <johnmark> it pulls from the same repo
15:21:05 <JustinClift> johnmark: For Mac Mini?
15:21:17 <JustinClift> Ahhh.
15:21:20 <johnmark> heh :)
15:21:21 * pranithk happy to see johnmark :-)
15:21:21 <JustinClift> Different topic
15:21:26 <johnmark> sorry, was looking backwards
15:21:26 <Eco_> to get the stats on where the other mac mini is  ;)
15:21:30 <johnmark> lol
15:21:35 <johnmark> Eco_: precisely
15:21:38 <johnmark> pranithk: howdy :)
15:22:13 <JustinClift> johnmark: Um, guessing you mean for the leaderbaord thing?  Yeah, it'll be useful source for the mailing list leaderboard.  That's likely all though.
15:22:23 <JustinClift> Anyway, this should prob be in "Other Agenda Items" ;)
15:22:26 <johnmark> JustinClift: ok
15:22:36 <johnmark> don't mind me :)
15:22:42 <JustinClift> ;)
15:23:07 <JustinClift> Eco_ kkeithley: Are either of you near Westford?
15:23:13 <Eco_> not in the slightest
15:23:25 <Eco_> 6000 km or so
15:23:27 * JustinClift is thinking "who could install ram upgrade in the Mac Mini?"
15:23:29 <JustinClift> k
15:23:45 <JustinClift> We'll come to that some other time then :)
15:23:48 <hagarth> JustinClift: kkeithley will be there next week
15:23:51 <kkeithley> I'm flying home in about 8 hours
15:24:07 <JustinClift> Cool, good to know
15:24:18 <johnmark> kkeithley: woohoo
15:24:19 <JustinClift> kkeithley will be the ram installer then most likely ;)
15:24:26 <JustinClift> Anyway, moving on...
15:24:29 <johnmark> JustinClift: can we talk about Gluster++
15:24:32 <johnmark> ?
15:24:42 <JustinClift> Now?
15:24:50 <johnmark> JustinClift: not necessarily
15:24:57 <johnmark> JustinClift: just at some point
15:24:58 <kkeithley> is that the rewrite in C++?
15:25:00 <JustinClift> Can you wait until the end of the meeting?
15:25:02 <johnmark> lol
15:25:03 <kkeithley> Or in Apple Swift?
15:25:06 <johnmark> JustinClift: yes. geez...
15:25:15 <JustinClift> We have an agenda. ;)
15:25:24 <JustinClift> "kkeithley_ to release 3.4.4"
15:25:24 <johnmark> JustinClift: goodie! ok, then
15:25:34 <JustinClift> Done.  Thanks Kaleb. :)
15:25:47 <JustinClift> We should get blog item on the website about it
15:25:56 <pranithk> guys what will we do about the crash seen by Joe? shall we release one more?
15:25:56 * JustinClift looked quickly, didn't see one
15:26:17 <pranithk> by Joe I mean JoeJulian of course
15:26:30 <JustinClift> If there are crashes with 3.4.4, then I'm inclined to make a 3.4.5 when a patch becomes available
15:26:41 <hagarth> JustinClift: I have already backported the patch
15:26:43 <pranithk> JustinClift: I already gave +1 on the patch.
15:26:50 <JustinClift> Cool
15:27:03 <JustinClift> How bad is the crash, and should we release 3.4.5 immediately?
15:27:07 <lalatenduM_> hagarth, yeah saw that, nice :)
15:27:18 <hagarth> JustinClift: the crash is present in all of 3.4.x
15:27:23 <pranithk> JoeJulian: what do you say?
15:27:36 <hagarth> but it would be nice to release 3.4.5 soon for more reasons than one
15:27:38 <JoeJulian> I think it's pretty severe, so yeah, release the patch.
15:27:39 <JustinClift> hagarth: How confident are we that this patch doesn't break things?
15:27:42 <lalatenduM_> just to make sure we are talking abt the same bug https://bugzilla.redhat.com/show_bug.cgi?id=1022510
15:27:44 <glusterbot> Bug 1022510: urgent, urgent, ---, rgowdapp, NEW , GlusterFS client crashes during add-brick and rebalance
15:27:48 <JoeJulian> I'll be testing it in staging tomorrow.
15:27:50 <hagarth> I like a release which has n.n+1.n+2 ;)
15:27:56 <JustinClift> eg should we just do 3.4.5 today, or do we beta it first?
15:27:59 <pranithk> hagarth: hehe
15:28:04 <JoeJulian> Beta it.
15:28:09 <hagarth> JustinClift: I am sure there will be no side effects
15:28:09 <JustinClift> k, lets do that
15:28:15 <pranithk> JustinClift: let Joe confirm it and then we can do the release
15:28:15 <JoeJulian> I'll test it and add my comments.
15:28:26 <johnmark> JoeJulian: thanks
15:28:44 <JustinClift> k, can we push out a 3.4.5 beta1 tarball today/tonight?
15:28:57 <JustinClift> Which JoeJulian can do the testing of tomorrow
15:29:14 <JustinClift> And we'll push out 3.4.5 release after that, depending upon test result?
15:29:29 <JustinClift> Feasible approach?
15:29:29 <kkeithley> ugh, you guys are making me crazy
15:29:42 <JoeJulian> Didn't take much effort, that.
15:29:47 <johnmark> kkeithley: what are you worried about? you'll be on a plance
15:29:49 <hagarth> JustinClift: let us leave it to kkeithley to determine the schedule
15:29:51 <kkeithley> would a 3.4.4-2 with the patch?
15:30:00 <JustinClift> kkeithley: Sure
15:30:07 <JustinClift> You're our 3.4.4 guy :)
15:30:12 <JustinClift> 3.4.x guy
15:30:16 <JustinClift> (brain-o)
15:30:18 <pranithk> kkeithley: Didn't you teach humble/lala about releasing rpms?
15:30:33 <JoeJulian> ... the worst part is, I'm stuck using debs.
15:30:42 <lalatenduM_> pranithk, yup :)
15:30:43 <kkeithley> yes, but building rpms isn't the same as doing a 3.4.x release though
15:30:58 <pranithk> kkeithley: hmm...
15:31:13 <lalatenduM_> pranithk, once the tar ball is available we can build rpms out os it
15:31:15 <JustinClift> Heh, sounds like you need to educate them on the "doing a release" then too
15:31:17 <ndevos> kkeithley: btw, do you do release notes for 3.4.x?
15:31:19 <lalatenduM_> s/os/of/
15:31:24 <pranithk> JustinClift: +1
15:31:35 <kkeithley> I'm just saying, if the patch is super critical, we can spin rpms with a patch while 3.4.5 is baking
15:31:47 <johnmark> kkeithley: right, hence the -2
15:31:51 <lalatenduM_> kkeithley+1
15:32:01 <kkeithley> there was a -2 somewhere?
15:32:06 <JustinClift> kkeithley: Sounds like a plan to me
15:32:10 <kkeithley> oh, sorry, it's late
15:32:11 <johnmark> kkeithley: sigh... 3.4.4-2
15:32:13 <JustinClift> kkeithley: He's meaning the -2 in 3.4.4-2
15:32:15 <johnmark> or something
15:32:15 <kkeithley> yes
15:32:18 <kkeithley> got it
15:32:27 <JustinClift> k, lets do that
15:32:47 <JustinClift> JoeJulian: If the test results tomorrow with patch are good
15:32:52 <JustinClift> Then kkeithley can make 3.4.4-2
15:32:56 <lalatenduM_> JoeJulian, I believe you would need rpms for CentOS 6 right?
15:33:02 <kkeithley> but first we have to finish building 3.4.4-1 rpms for download.gluster.org
15:33:11 <pranithk> lalatenduM_: I guess debs
15:33:13 <JoeJulian> lalatenduM_: No, debs. :(
15:33:32 * JustinClift is now confused
15:33:33 <lalatenduM_> ohh, who make debs then?
15:33:33 <JoeJulian> I'm working with semiosis to figure out how that's done.
15:33:42 <JustinClift> Ahh
15:33:56 <lalatenduM_> JoeJulian, I thought you use rpm based distro
15:34:06 <lalatenduM_> when did you move to debs
15:34:07 <lalatenduM_> ?
15:34:08 <kkeithley> Humble can finish 3.4.4-1 rpm building while I'm flying
15:34:22 <JustinClift> k.  So we need semiosis to create suitable deb's-with-patch first, which you can then test with
15:34:27 <JustinClift> Oh, lets do it this way:
15:34:34 <JoeJulian> lalatenduM_: I did up until 10 days ago when I changed jobs.
15:34:44 <JustinClift> a) JoeJulian will test the patch when he gets the suitable debs
15:35:08 <lalatenduM_> JoeJulian, congratulations for the new job :)
15:35:15 <JustinClift> b) We'll spin 3.4.4-2 rpms when patch is confirmed good
15:35:22 <JustinClift> (or not, if the results fail)
15:35:35 <JoeJulian> Makes sense to me.
15:35:40 <JustinClift> And the patch will be in 3.4.5, whenever that comes out
15:35:56 <JustinClift> (which will therefore go into every other binary type then based on 3.4.5)
15:36:01 <JustinClift> k
15:36:26 <JustinClift> #action JoeJulian to test extra patch on top of 3.4.4 and report success/failure
15:36:49 <JustinClift> #action kkeithley to release 3.4.4-2 (with the extra patch) if JoeJulian's testing succeeds
15:37:00 <JustinClift> k, next item
15:37:02 <kkeithley> agreed
15:37:11 <JustinClift> "ndevos to release 3.5.1 beta2 when the required patches are merged"
15:37:20 <JustinClift> Done.
15:37:35 <JustinClift> RPMS turned up in the repos today too
15:37:47 <ndevos> thanks Humble (and lalatenduM_ and kkeithley?)
15:37:57 <hagarth> yay! thanks everyone for that!
15:38:04 * JustinClift I did a blog post about it 1 min before this meeting started (super simple one), asking for testers
15:38:05 <hchiramm_> ndevos, np!! kkeithley++
15:38:06 <kkeithley> Humble, I only watched and cheered him on
15:38:15 <hchiramm_> kkeithley, :)
15:38:17 <lalatenduM_> kkeithley, ++ :_)
15:38:21 <hagarth> JustinClift: re-tweeted ;)
15:38:27 <JustinClift> hagarth: Tx :)
15:38:51 <ndevos> #link http://www.gluster.org/2014/06/glusterfs-3-5-1-beta2-ready-for-testing/
15:38:55 <JustinClift> "JustinClift and hagarth to discuss website schedule tomorrow/friday, after progress report from Eco"
15:39:27 <JustinClift> Done.  Discussed during meeting about team prioritisation and stuff on Tue.
15:39:35 <JustinClift> "kshlm to report on forge alternatives"
15:39:39 <JustinClift> kshlm: ?
15:40:12 <kshlm> Nope. I'm trying to get my 3.6 deliverables done.
15:40:26 <johnmark> ok. we need to take this on reather urgently
15:40:43 <JustinClift> k.  Do we have someone else who can investigate it?
15:41:14 <hagarth> johnmark: by when do we need a read out?
15:41:54 <kshlm> I had formed a list of the alternatives though. Someone can continue from there, https://gist.github.com/kshlm/fd884ae1df1e9b982252
15:41:55 <glusterbot> Title: What should be done for GlusterForge? (at gist.github.com)
15:41:55 <johnmark> hagarth: well, because the forge is key to Gluster++, which I wanted to roll out this month, I was hoping we would have stuff identified pretty soon
15:42:02 <johnmark> kshlm: thanks
15:42:19 <hagarth> kshlm: cool, we could take it up from there
15:42:21 <johnmark> I can take it on, and that will be my parting gift to the community :)
15:42:26 <kshlm> johnmark, what is gluster++ ?
15:42:33 <hagarth> johnmark: we will never let you go ;)
15:42:43 <johnmark> hagarth: just when I think I'm out...
15:42:44 <johnmark> heh
15:42:44 <JustinClift> kshlm: It's the last item for the Agenda
15:42:52 <Eco_> johnmark, lol
15:42:57 <kshlm> oh. didn't see that.
15:43:13 <johnmark> JustinClift: now?
15:43:14 <JustinClift> k, we need to figure out what we're going to do with it
15:43:18 <JustinClift> Hmmm, not yet
15:43:21 <johnmark> o
15:43:23 <johnmark> k
15:43:42 <JustinClift> #action JustinClift to look into Gitorious alternatives
15:43:44 <JustinClift> Fuck it
15:43:46 <JustinClift> ;)
15:43:49 <johnmark> ha
15:43:59 * JustinClift always makes the recorded meeting minutes interesting
15:44:02 <johnmark> JustinClift: ok, let's discuss later - just you and me, man
15:44:18 <JustinClift> "kkeithley_ to give JustinClift the details of where the FreeBSD port code lives"
15:44:22 <JoeJulian> All the cool people use gitlab
15:44:24 <JustinClift> Done
15:45:01 <JustinClift> "JustinClift to canvas for people to pick up the FreeBSD port code and get it merged/working with master"
15:45:20 <JustinClift> kkeithley just gave me the info.  Will get it done this week
15:45:29 <JustinClift> #action JustinClift to canvas for people to pick up the FreeBSD port code and get it merged/working with master
15:45:41 <JustinClift> "hagarth to email gluster-users and gluster-devel with the details of the new Port Maintainers"
15:45:48 <JustinClift> To be done this week
15:45:55 <JustinClift> #action hagarth to email gluster-users and gluster-devel with the details of the new Port Maintainers
15:46:03 <JustinClift> "hagarth to email gluster-devel, reminding them that 3.6.0 feature freeze is in 2 weeks"
15:46:09 <JustinClift> Done: http://supercolony.gluster.org/pipermail/gluster-devel/2014-June/041032.html
15:46:10 <glusterbot> Title: [Gluster-devel] 3.6.0 feature freeze - reminder (at supercolony.gluster.org)
15:46:16 <JustinClift> "ndevos to check with pranithk and raghug whether the fixes for the gfid memory leaks are ready for 3.5.2"
15:46:19 <JustinClift> ndevos: ?
15:46:37 <ndevos> not sure where that came from?
15:46:59 <ndevos> maybe thats pranithk's?
15:47:02 <pranithk> ndevos: :-) It was there
15:47:10 <pranithk> ndevos: You merged raghug's patch
15:47:15 <johnmark> busted!
15:47:28 <semiosis> :O
15:47:36 <pranithk> ndevos: My patch is still under review :-)
15:47:39 * Eco_ spit takes
15:47:42 <JustinClift> ndevos: http://meetbot.fedoraproject.org/gluster-meeting/2014-06-04/gluster-meeting.2014-06-04-15.02.log.html
15:47:44 <glusterbot> Title: #gluster-meeting log (at meetbot.fedoraproject.org)
15:47:49 <JustinClift> At 16:00:10
15:47:56 <JustinClift> So, scroll back up a bit
15:48:28 <ndevos> pranithk: any patches missing to have that fixed?
15:48:29 <pranithk> ndevos: I think raghug's patch was the critical one IMO
15:48:39 <JustinClift> pranithk: So, this still needs review for 3.5.1 beta <next> ?
15:48:59 <JustinClift> ... sounds like a beta3 will be needed
15:49:03 <ndevos> and, well, 3.5.2 will have some time, if 3.5.1beta2 is ok
15:49:17 <ndevos> JustinClift: I dont think we can fix all bugs in 3.5.1 :)
15:49:25 <pranithk> ndevos: +1
15:49:30 <JustinClift> Heh
15:49:34 * JustinClift pulls a sad face
15:49:48 <JustinClift> k, it's a 3.5.2 targeted patch then?
15:49:50 <pranithk> JustinClift: :-) I have 3 more patches I wanted to propse for the release
15:50:01 <JustinClift> pranithk: For 3.5.1 beta3, or for 3.5.2 ?
15:50:02 <pranithk> JustinClift: I think we will release 3.5.2 pretty soon
15:50:07 <JustinClift> Sure
15:50:16 <ndevos> pranithk: only very major issues can make it in 3.5.1, everything else gets pushed to 3.5.2
15:50:22 <JustinClift> k, np
15:50:42 <pranithk> ndevos: I feel they are major but we can't delay the release IMO
15:50:47 <JustinClift> So, what do do about this item... mark it as done I guess?
15:50:55 <pranithk> JustinClift: Yes I guess
15:51:06 <raghug> pranithk: what are those patches?
15:51:12 <raghug> are they related to gfid-access?
15:51:18 <pranithk> raghug: http://review.gluster.org/8015
15:51:19 <glusterbot> Title: Gerrit Code Review (at review.gluster.org)
15:51:28 <ndevos> pranithk: okay, sounds good, patch proposal for release-3.5 is open, I'm just merging only the critical ones, if any at all
15:51:44 <ndevos> after 3.5.1 has been released, any sane patch can get in again
15:51:47 <pranithk> raghug: http://review.gluster.org/7981
15:51:48 <glusterbot> Title: Gerrit Code Review (at review.gluster.org)
15:52:00 <pranithk> raghug: The gfid-access leak patch...
15:52:12 <pranithk> raghug: I am waiting on kotresh's patch to be merged
15:52:17 <kkeithley> Can we let 3.5.1beta2 bake for a bit? I don't like rushing the release just because ndevos is going on holiday.
15:52:21 <raghug> ok
15:52:29 <pranithk> JustinClift: I think we will have to get the patch reported by Tom also into 3.5.2 :-(
15:52:36 <JustinClift> kkeithley: Apparently there are pretty critical bug fixes in it
15:52:39 <pranithk> JustinClift: s/Patch/bug
15:52:55 <JustinClift> pranithk: Yeah, that makes sense to me
15:53:06 <ndevos> kkeithley: there was only one real issue with 3.5.1beta1, not sure how long we want to test beta2
15:53:29 <JustinClift> kkeithley: So we want to get 3.5.1beta2 confirmed good/bad asap, so we can release 3.5.1 with the critical fixes
15:54:06 <JustinClift> k, anyway, I think we're good for this item
15:54:09 <johnmark> kkeithley: also, we don't get much backing of our betas anyway. not sure how much good extra time will do
15:54:12 <johnmark> tbh
15:54:25 <johnmark> er s/backing/baking
15:54:40 <JustinClift> johnmark: We do get some testing off-list
15:54:48 <pranithk> johnmark: I think Justin did a fabulous job this time to get good beta testing done. I wanna thank him for that!
15:54:50 <johnmark> JustinClift: good ot know
15:54:56 <johnmark> pranithk: nice!
15:55:01 <johnmark> JustinClift: you get a gold star
15:55:04 <JustinClift> pranithk: np.
15:55:18 <JustinClift> pranithk: We can likely do better, with a bit more co-ordination
15:55:26 <johnmark> JustinClift: that's awesome
15:55:29 * johnmark is happy
15:55:33 <JustinClift> We didn't really make use of social media nor reach out as well as we could have
15:55:34 <pranithk> JustinClift: yes. Over time it should improve :-)
15:55:36 <hagarth> JustinClift: yeah, there's a lot more we can do
15:55:37 <JustinClift> But, we'll get it
15:56:19 <johnmark> ok, next
15:56:24 * johnmark has to leave soon
15:56:34 <JustinClift> #action JustinClift to think through then wiki-ise what steps we should do for getting more thorough beta testing, and draw up likely list of candidates to ping directly
15:56:39 <JustinClift> k
15:56:48 <JustinClift> johnmark: k, do the Gluster++ thing now
15:56:51 <johnmark> woohoo
15:57:10 <johnmark> ok, so the reason that the forge decision is so important, is because we're taking a "best of forge" approach to do a software bundle
15:57:33 <JustinClift> Cool
15:57:41 <JustinClift> Who's the lead for it?
15:57:43 <johnmark> including packaging of things like puppet-gluster, pmux, xavih's xlator
15:57:45 <johnmark> etc.
15:57:59 <johnmark> JustinClift: right now, no one. I guess you could call me the biz guy for this
15:58:04 <JustinClift> Cool
15:58:11 <johnmark> but we need individual project owners to take up packaging for their stuff
15:58:27 <johnmark> my understaning is that purpleidea is packaging his puppet stuff
15:58:30 <johnmark> so that should be ok
15:58:47 <johnmark> not sure who would package pmux or the disperse xlator
15:58:54 <johnmark> or anythign else that's valuable
15:59:05 <johnmark> JustinClift: there's also glusterflow, whihc would be pretty interesting
15:59:32 <johnmark> anyway, the idea is to present the packaged goods in some way to show that it's abou tmore than just glusterfs
15:59:32 <xavih> johnmark: disperse xlator is currently in review to add it to master branch
15:59:48 <JustinClift> johnmark: Hmmm, I haven't had time to touch it in ages.  Gerald Sternagl did some work on it recently, but it's still very alpha level
15:59:51 <johnmark> xavih: ok, good. but it won't appear in an extual release branch until 3.6 right?
16:00:04 <johnmark> JustinClift: that's fine, as long as it's labeled as such
16:00:04 <xavih> johnmark: yes
16:00:10 <JustinClift> Makes sense
16:00:14 <JustinClift> Cool.
16:00:26 <johnmark> xavih: so this would give users the opportunity to use it in conjunction with the 3.5 releases
16:00:28 <ndevos> I've packaged some projects, maybe that helps?
16:00:29 <ndevos> http://copr.fedoraproject.org/coprs/devos/gluster-addons/
16:00:30 <glusterbot> Title: devos/gluster-addons Copr (at copr.fedoraproject.org)
16:00:31 <JustinClift> What's the plan/approach to make it happen then?
16:00:36 <johnmark> ndevos: cool!
16:00:36 <JustinClift> ndevos: Cool
16:00:46 <johnmark> JustinClift: sounds like ndevos has partially shown the way
16:00:49 <lalatenduM_> ndevos, cool
16:01:04 <JustinClift> ndevos == unintentional lead ;)
16:01:33 <ndevos> JustinClift: well, mostly for my own needs :D
16:01:34 <johnmark> lol
16:01:43 <johnmark> ndevos: wouldyou be able to add in a couple more packages?
16:01:51 <JustinClift> johnmark: Do you have the list of what you want?
16:01:51 <johnmark> ndevos: because that's a pretty good base to start with
16:02:04 <johnmark> JustinClift: yes, what I just provided - puppet-gluster, pmux, disperse xlator
16:02:18 <johnmark> JustinClift: plus some of the projects ndevos just listed
16:02:28 <johnmark> JustinClift: and glusterflow :)
16:02:35 * hagarth will be dropping off now, so long folks
16:02:40 <johnmark> hagarth: thanks :)
16:02:43 <JustinClift> hagarth: Thanks :)
16:02:45 <ndevos> cya hagarth
16:02:49 <johnmark> so...
16:03:08 <JustinClift> johnmark: Are you ok to bring it up on gluster-devel, so it can be worked out there?
16:03:16 <johnmark> JustinClift: +1
16:03:18 <JustinClift> We're at meeting end time
16:03:21 <johnmark> yup
16:03:24 <johnmark> I'll do that
16:03:24 <JustinClift> Cool
16:03:29 <johnmark> ndevos: and I'll ping you separately
16:03:42 <ndevos> johnmark: adding packages can be easy, but depends on how the project
16:03:44 <JustinClift> #action JohnMark to initiate conversation about Gluster++ on gluster-devel
16:03:49 <ndevos> -how
16:04:06 <JustinClift> #action pranithk to add information about EasyFix to the existing Developer page
16:05:00 <JustinClift> We're at meeting end
16:05:04 <JustinClift> But two quick status updates
16:05:15 * JustinClift has pretty much gotten the Rackspace slaves functional finally
16:05:22 <JustinClift> Doing some final testing and adjustment now
16:05:47 <JustinClift> 3 slaves online. They're not reporting pass/failure back to Gerrit yet, until I see them pass consistently
16:05:51 <JustinClift> (hopefully next few hours)
16:06:07 <semiosis> JoeJulian & anyone else with questions/concerns about deb packaging should contact me in #gluster i'll be around all day.
16:06:11 <JustinClift> Once they do I'll enable them to report pass/failure to Gerrit, then we can schedule shed loads of stuff onto them
16:06:20 <JustinClift> semiosis: Cool :)
16:06:34 <JustinClift> And the GlusterFS leaderboard thing, is still a work in progress (barely started)
16:06:47 <JustinClift> Still mucking around with Gerrit REST API queries
16:07:04 <JustinClift> But, it should help us get incentives in place for the behaviours we want
16:07:24 <JustinClift> eg patch reviews prioritised, etc
16:07:28 <JustinClift> Anyway, that's it from me
16:07:31 <JustinClift> #endmeeting