Thursday, 2015-01-29

*** david-lyle is now known as david-lyle_afk00:28
*** johnthetubaguy is now known as zz_johnthetubagu01:04
*** mestery has quit IRC05:15
*** mestery has joined #openstack-relmgr-office05:16
*** eglynn-pto has quit IRC08:21
*** mestery has quit IRC08:29
*** mestery has joined #openstack-relmgr-office08:31
*** eglynn-pto has joined #openstack-relmgr-office08:46
*** eglynn-pto has quit IRC09:01
SergeyLukjanovttx, hi, if you have 5 mins, I have a question re backports to stable branch11:03
ttxSergeyLukjanov: sure11:03
ttxask away11:03
SergeyLukjanovttx, thx11:03
SergeyLukjanovttx, so, I'd like to add several folks to sahara stable maint team, is it on my own, or should I discuss changes to the team with stable branch CPL?11:04
SergeyLukjanovttx, that's because we'd like to merge fixes for a bunch of critical user-facing bugs in 2014.2.211:05
ttxSergeyLukjanov: you suggest a list, we send them a brief email pointing them to the Stable Branch policy, they confirm that they read and understand it, and off they go11:06
SergeyLukjanovttx, ack, thx11:06
SergeyLukjanovttx, email with [stable][sahara] tags to -dev will be ok?11:07
ttxyes11:07
SergeyLukjanovttx, thx11:10
*** eglynn-pto has joined #openstack-relmgr-office12:01
*** eglynn-officeafk is now known as eglynn-lunch12:15
*** eglynn-pto has quit IRC12:20
*** eglynn-lunch is now known as eglynn-office13:17
*** eglynn-office is now known as eglynn-officeafk13:40
*** eglynn-pto has joined #openstack-relmgr-office13:54
*** eglynn-pto has quit IRC14:03
*** eglynn-pto has joined #openstack-relmgr-office14:19
*** eglynn-pto is now known as eglynn14:59
*** bswartz has joined #openstack-relmgr-office15:59
ttxredrobot: ready when you are15:59
redroboto/15:59
ttx#startmeeting incub_sync15:59
openstackMeeting started Thu Jan 29 15:59:49 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.15:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:59
openstackThe meeting name has been set to 'incub_sync'15:59
ttx#topic Barbican15:59
ttx#link https://launchpad.net/barbican/+milestone/kilo-216:00
ttxI see one incomplete BP on the docket16:00
ttxcertificate-order-api16:00
ttxIs that likely to get completed by the milestone next week ?16:00
redrobotyes, it's very close to being done.  I think the last CR is in review right now, so I feel pretty confident it will land16:00
ttxok, moving to "needs code review" then16:01
ttxWe'll tag sometimes between Tue and Thu next week, ideally16:01
ttxAny other thing you'd like to include in the tag ?16:01
ttxand that we should track status of ?16:02
ttx(feature or bugfix)16:02
redrobotI will probably add any fixes that land before next week, but nothing critical that I can think of16:02
ttxok. Ping me when you're happy, worst case scenario we'll tag during the sync next week16:03
redrobotsounds good16:03
ttxany question on that ?16:03
redrobotYeah, we accidentally introduced some bad dependencies with a new client release16:03
redrobotas I understand it the client was pinned to <3.0.2 in stable/juno16:04
ttxredrobot: yeah, I saw that thread... not sure I understand the issue exactly16:04
ttxwhat was the nesw release version ? What did it introduce ?16:04
redrobotI think it was an oslo.something that pulled in an incompatible dependency.16:05
redrobotwe have a bot syncing requirements for us, but we didn't have a stable branches job in our gate, so we didn't notice it16:05
ttxI thinkn that's the issue with having stable branches before you have stability :)16:05
redrobotwe have the job now, but I'm still not clear on how to backport fixes so that they can be used in juno?16:06
redrobotshould I create a stable/juno branch in the client at 3.0.1 (the last juno-compatible release) and then cherrypick for 3.0.1.x releases?16:06
ttxwell, in theory we don't do that (stable branches for clients) so that the recent client acvtually workd with the supported release16:07
ttxbut then here we don't really have a "supported release"16:07
ttxredrobot: we should discuss that on #openstack-dev and try to get a few others in the discussion16:08
redrobotttx ok, will do.  thanks.16:08
ttxwould you be around in 23 min once I'm done with the syncs ?16:08
ttxI'd like to be around to continue that discussion, but I'm stuck16:08
redrobotyeah, I should be.  just ping me to get my attention.16:08
ttxok will do16:09
ttxredrobot: was that your only topic ?16:09
redrobotttx yep, I'm good.16:09
ttxok, brb16:09
ttxbswartz: around?16:09
bswartzttx: yes!16:09
ttx#topic Manila16:09
bswartzalthough I'm in a cinder meetup with 20 people o_O16:10
ttx#topic https://launchpad.net/manila/+milestone/kilo-216:10
ttxerr16:10
ttx#topic Manila16:10
ttx#link https://launchpad.net/manila/+milestone/kilo-216:10
ttxbswartz: act natural16:10
bswartzyes16:10
ttxthat page shows 10 more blueprints to complete16:10
bswartzso we reviewed the BPs and nearly all of them are in good shape16:10
ttxare you confident they can all make it ?16:11
bswartzI've made threats to the various developers to get their stuff fixed16:11
bswartzhonestly I expect 1 or 2 not to make it but I don't know which16:11
bswartzso I'm giving them all a chance16:11
bswartzit's possible to get them all merged16:11
ttxOK -- as we get closer to the milestone window (Tuesday-Thursday next week), it would be good to to push back to kilo-3 what will miss the window16:11
bswartzthe bugs are a different story16:11
ttxyeah, the unassigned ones are unlikely to get fixes in the time we have left16:12
bswartzyeah I gave some of them a deadline to at least rebase and patch jenkins by tomorrow16:12
ttxthe ideal would be to keep only the milestone blockers on the page16:12
bswartzanyone than can't do that will get pushed, so we can focus on good reviews16:12
ttxstarting Tuesday16:12
bswartzyes16:13
ttxand not be too greedy so that we can actually tag within the window16:13
ttx:)16:13
bswartzwell most of the bugs are netapp related and netapp is going to triage them and see if any need to stay in k216:13
ttxthen a quick ping when all is green and I can tag16:13
ttxack16:13
ttxbut generally, good progress16:13
bswartzI think we're on the same page -- by Tuesday anything nonessential should be pushed out16:14
ttxI'll let you trim down that buglist16:14
ttxany question on the process ?16:14
bswartzwhen is the ideal time to tag the milestone frm your perspective?16:14
bswartzWednesday night? Thursday morning16:14
bswartz?16:14
ttxbswartz: wednesday.. morning for you16:15
ttxafternoon for me16:15
bswartzokay we'll shoot for that and I'll tell you if we're going to be late16:15
ttxTuesday and Thursday are usually busier16:15
ttxbswartz: cool, that works16:15
ttxthat's all I had16:15
bswartzthanks ttx16:15
bswartzsame here16:15
ttxcool, have a good week and meetup16:16
bswartzI'll get back to this meetup and cracking the whip on manila devs16:16
ttxflaper87: ready when you are16:16
flaper87ttx: here16:17
ttx#topic Zaqar16:17
ttx#link https://launchpad.net/zaqar/+milestone/kilo-216:17
ttxThat looks still very much work in progress...16:17
flaper87yeah, I'm giving some of those a couple of more days before pushing them back to k-316:18
ttxAre any of those open BPs actually just waiting on review on code fully posted ?16:18
ttx(i.e. should be Need code review status)16:18
flaper87I'm confident few of those bps will be fully implemented16:18
flaper87ah damn, why do I always forget there's a Need core review status?16:18
flaper87T_T16:18
flaper87yeah, most of them are up for review16:18
flaper87there're 2 that need follow-up patches16:19
ttxWe use it to represent "all code posted, wtf are the reviewers doing" state16:19
ttxalso works for "I gave -1 wtf is the author doing"16:19
flaper87hahahaha16:19
ttxbasically the final stages16:19
flaper87yeah, that makes sense16:19
flaper87I'll update those bps16:19
flaper87ttx: question: Is it "legal" to remove the "Incubated" lable from zaqar in the docs page?16:20
ttxWe use Good progress / Slo progress more to represent "I'm in the middle of a 12-patch long patchseries"16:20
flaper87(and everywhere it's being used)16:20
ttxflaper87: it's consistent with https://review.openstack.org/#/c/145740/14/reference/projects.yaml16:21
ttxscroll down to line 35516:21
flaper87w00000t16:21
flaper87:D16:21
ttxbut that's not approved yet16:21
* flaper87 will throw a zaqar party at FOSDEM16:21
ttxI think that's the sense of history though16:22
flaper87yeah, I'll wait for that patch to land then16:22
ttxdirection of history16:22
ttxprobably better16:22
ttxThat's the change where we erase "incubation" from the collective history16:22
flaper87ok, other than that. I've no further questions16:22
flaper87nice, looking forward to the beginning of the tagging craziness16:23
ttxalright, update your status, ping me when you have a "won't get much more in anyway" SHA16:23
flaper87will do16:23
ttxideally between Tue and Thu next week16:23
ttxgreat, thx16:23
ttxflaper87: oh, and push back bugs as well, not just BPs16:24
ttxKiall: ready when you are16:24
Kiallttx: heya16:26
ttx#topic Designate16:26
ttx#link https://launchpad.net/designate/+milestone/kilo-216:26
ttx2 open BPs16:26
ttxhow likely is taht to be completed by the milestoen window next week ?16:26
KiallYes, Agent has merged - there's a followup commit pending before complete16:26
Kialland the 2nd one has code waiting to me to submit16:26
Kiallso - likely to close both out.16:27
ttxso still on track16:27
ttxOn the bugs side, you might want to trim the list to milestone blockers16:27
KiallYes - many of the still open bugs will likely get pushed to k316:27
ttxand push back most unassigned ones unless you can get someone on them now16:27
ttxThen when you're happy and that page is all green, you can send me a SHA16:27
ttxhopefully between Tue and Thu16:28
KiallYea, I asked people to push anything that won't land in our meeting last night, nothings changed yet though ;)16:28
ttxsame old process16:28
KiallSounds good16:28
ttxyeah, cats!16:28
Kiall:D16:28
ttxok, that's about all I had, you look in good shape16:28
ttxany question on your side ?16:29
Kiallcan't help myself..16:29
Kiall    _,,/|16:29
Kiall    \o o'16:29
Kiall    =_~_=16:29
Kiall    /   \ (\16:29
Kiall   (////_)//16:29
Kiall   ~~~16:29
KiallNope, same old process as you said :)16:29
ttxthat's a single cat. It's when there are thousands that it gets tricky.16:29
KiallI'll do the bug list myself tonight if nobody else get's to it first16:29
ttxalright16:29
ttxhave a good end of week16:29
KiallSame to you..16:29
ttxI'll try to be at Graham's presentation at FOSDEM16:29
KiallI'm technically presenting at that too ;)16:30
ttxtechnically ? Or really ?16:30
KiallBut - It's so short, I might leave it to Graham16:30
ttxok, but you'll be around?16:30
KiallYes - I fly out friday :)16:30
ttxok, see you there then!16:30
KiallI'll keep and eye out for you :)16:30
ttx#endmeeting16:30
openstackMeeting ended Thu Jan 29 16:30:57 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/incub_sync/2015/incub_sync.2015-01-29-15.59.html16:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/incub_sync/2015/incub_sync.2015-01-29-15.59.txt16:31
openstackLog:            http://eavesdrop.openstack.org/meetings/incub_sync/2015/incub_sync.2015-01-29-15.59.log.html16:31
*** david-lyle_afk is now known as david-lyle16:49
*** bswartz has quit IRC17:30
*** ff has joined #openstack-relmgr-office18:11
*** eglynn has quit IRC18:25
*** eglynn has joined #openstack-relmgr-office18:50
*** mikal_ has joined #openstack-relmgr-office19:55
*** mikal has quit IRC19:56
*** ff has quit IRC22:15
*** asalkeld has joined #openstack-relmgr-office22:20
*** eglynn has quit IRC23:16

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!