Thursday, 2015-04-02

*** thingee has quit IRC03:38
*** asalkeld has left #openstack-relmgr-office04:08
*** zz_johnthetubagu is now known as johnthetubaguy08:35
*** johnthetubaguy is now known as zz_johnthetubagu10:54
Kiallttx: HP email server hosting my account seems foo-bar'd, trying to lookup the new sync-up time.. Have it handy?12:16
ttxKiall: sure12:17
ttxhttps://wiki.openstack.org/wiki/Release_Cycle_Management/1:1_Syncs#Incubated_projects_.28Thursdays.2912:17
ttx15:30 UTC Kiall Mac Innes (Designate)12:17
KiallPerfect, thanks :)12:18
*** zz_johnthetubagu is now known as johnthetubaguy12:35
ttxKiall: err.. actually that's not up to date12:40
ttxlet me fix12:40
Kialllol :)12:41
ttxok updated12:41
ttx15:20 UTC Kiall Mac Innes (Designate)12:41
ttxsorry about that12:41
KiallNo problem!12:42
ttxnikhil_k: around?14:23
*** bswartz has joined #openstack-relmgr-office14:46
* bswartz looks around to see if anyone's here14:50
bswartzttx: ping14:52
bswartzare we using the new meeting times this week, or does that start next week?14:52
ttxno, starting today14:53
ttx#startmeeting incub_sync14:53
openstackMeeting started Thu Apr  2 14:53:13 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.14:53
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:53
ttx#topic Manila14:53
openstackThe meeting name has been set to 'incub_sync'14:53
bswartzI have a hard stop at 1500UTC14:53
ttxbswartz: yes, let's do it quick14:53
ttxhttps://launchpad.net/manila/+milestone/kilo-rc114:53
ttxStill have one feature freeze exception running ?14:53
ttxWould be good to close it asap so that you can focus on RC bugfixing14:54
bswartzyes, we granted 2 actually14:54
ttxoh, would be nice to add the other one to the LP page14:54
bswartzone of the bugs looked like a feature so we put it through the FFE process14:54
ttxok14:54
bswartzit's a bug in LP14:54
bswartzhttps://bugs.launchpad.net/bugs/143717614:54
openstackLaunchpad bug 1437176 in Manila "glusterfs_native: Unable to create shares using newly available GlusterFS volumes without restarting manila share service" [Medium,In progress] - Assigned to Csaba Henk (chenk)14:54
bswartzso what you see there is accurate14:54
ttx#info second FFE for https://bugs.launchpad.net/bugs/143717614:55
bswartzeverything is ready to merge today with the exception of 2 bugs14:55
ttxbswartz: feel like both are close to final merging ?14:55
ttxok14:55
ttxSo you might just be able to issue a RC1 at the end of next week14:55
bswartzI'm going to try to figure out if we can push the RC a few days to get those bugs in too14:55
ttxthen you can work on Liberty and if you spot a critical issue we can backport it (and a few others) and do a RC2, etc14:55
bswartzif something is going to take more than a few days we may go ahead with RC114:56
ttxI don't have a set date for RC114:56
bswartzyeah -- I was hoping for today but we didn't meet that goal14:56
ttxbasically you need to be hhappy enough with it to stamp it as "releasable for all I know"14:56
ttxno point in tagging RC1 if you know you have bugs you don't want to final-release with and ask for a RC2 the minute after14:57
bswartzokay14:57
bswartzin that case the RC will definitely be delayed a few more days14:57
ttxyou have to believe (at the moment of tagging) that this is good enough14:57
bswartzso do you tag RCs or do I?14:57
ttxthe trick is more to lower your standards of "good enough" based on time :)14:57
ttxI do them because you need to create branches at the same time14:58
ttxalthough I can walk you through the scripts if you want to run them yourself14:58
bswartzshould I just come grab you when the last critical bug merges?14:58
ttxyes, when the RC1 page is all green, ping me14:58
bswartzit will most likely be Monday-Wednesday14:58
ttxwon't be around on Monday. Tuesady+ is fine14:58
bswartzok14:58
bswartzextra time for us then14:59
ttxi'll let you jump on your next meeting14:59
bswartz:-)14:59
ttxdon't hesitate to reach out to me if you have questions14:59
bswartzthanks14:59
ttxbswartz: have a good day!14:59
ttxredrobot: ready when you are14:59
redrobotttx o/14:59
ttx#topic Barbican14:59
ttxhttps://launchpad.net/barbican/+milestone/kilo-rc115:00
ttxI see one FFE left15:00
ttxis that the last one ?15:00
redrobotyeah, that's the only outstanding one15:00
ttxAlso the bug list is suspiciously empty15:00
redrobotindeed.  I have to triage some bugs to see what is needed for RC115:00
ttxI suspect you didn't run through all the bug list and target release-critical stuff yet ?15:00
redroboti'll be doing that today15:00
ttxawesome15:00
ttxideally we would tag RC1 sometime next week, although I don't mind if you can't meet that date15:01
ttxHow far is that last FFE from merging ?15:01
redrobotawesome... I was thinking Thursday next week, but I do want to beat up on the FFE once it lands15:02
ttxack15:02
redrobotwe had a google hangout yesterday to iron out the last of the issues15:02
redrobotjust waiting on a new patch from the feedback15:02
ttxwe kind of need to issue the RC1, if only to trigger testing from an array of people15:02
ttxbut that should be done when you're reasonably confident it's not utterly broken15:02
ttxotherwise it's counterproductive15:03
redrobotagreed.  I'll aim for Thursday and let you know if anything comes up in our next 1:115:03
ttxok, that is all I had15:04
redrobotttx cool, see you next week15:04
ttxcheers!15:04
ttxflaper87: ready when you are15:05
flaper87ttx: ready15:05
ttx#topic Zaqar15:05
ttxhttps://launchpad.net/zaqar/+milestone/kilo-rc115:05
ttxSame as Barbican...15:05
ttxOne FFE up and bug list suspiciously empty15:06
ttxIs taht the last FFE for Zqar ?15:06
flaper87The FFE is on review and it's ready. Some nits to address before it can land15:06
flaper87Re the bug list, the remaining bugs were not high prio so I moved them15:06
ttxok, once that's done it would be great to scrub trhe bug list and see what you must fix before tagging15:06
flaper87to focus on reviews and that outstanding FFE15:06
flaper87ttx: yes sir, consider it done!15:07
ttxif you're bug-free then we could just tag once that FFE is in :)15:07
flaper87ttx: roger, I'll work on getting that patch in and scrub the bug list15:07
ttxalright, don't have much to add15:07
* flaper87 neither15:07
flaper87:D15:07
ttxyou know where I am if you need me15:07
flaper87quickest meeting ever15:07
flaper87:D15:07
ttxKiall: ping me when around15:08
nikhil_kttx: hi15:08
nikhil_k(was in glance meeting)15:08
nikhil_k(weekly one)15:08
ttxnikhil_k: ohai15:08
nikhil_ko/15:08
ttxso CIS merged15:09
ttxand I guess we should defer Artifact repo (it's still on the list)15:09
ttxtrying to see if those patches he stil asked for are in now15:09
nikhil_kttx: I think they are15:10
nikhil_kttx: I asked him to create a new spec with more details of what merged and what did not15:10
ttxyes, all merged15:10
ttxok, deferring15:11
ttxnikhil_k: so now you need to come up with a clean list of blockers for RC1 (if any)15:11
ttxthen we'll burn down that list (either by fixing the bugs, or removing them from the critical path)15:12
ttxand when we're empty, tag15:12
ttxnikhil_k: but all that process relies on a clean buglist15:12
Kiallttx: on my way back from lunch - will be 8 (or more likely 10 mins)15:12
ttxKiall: perfect15:12
ttxnikhil_k: did you go through the bug list yet ?15:13
nikhil_kttx: yes, I did15:13
ttxoh, cool. So the list is actually up to date. Sounds like you could hit the RC1 tag sometimes next week15:13
nikhil_khttps://launchpad.net/glance/+milestone/kilo-rc115:14
nikhil_kyes, I think we need to remove this from RC115:14
nikhil_khttps://bugs.launchpad.net/bugs/141730415:14
openstackLaunchpad bug 1417304 in Glance "Upload/Import image continues consuming glance host cpu/memory/network/disk resources even after the image is deleted" [Undecided,Incomplete]15:14
nikhil_kand this one is merge:15:14
nikhil_khttps://bugs.launchpad.net/bugs/127669415:14
openstackLaunchpad bug 1276694 in neutron "Openstack services should support SIGHUP signal" [Wishlist,In progress] - Assigned to Elena Ezhova (eezhova)15:14
nikhil_kanother related is in kilo-rc-potential15:14
nikhil_kbasically, we're on track15:14
ttxok, you can clean them up15:14
ttxagree that "incomplete" bugs should not be targeted to RC115:15
nikhil_kI asked the authors to, if they dont' today I will15:15
ttxalright15:15
ttxsounds like you have stuff under control15:15
ttxquestions ?15:15
nikhil_kttx: do we have a wiki for RC restrictions?15:15
ttxwhat do you mean by RC restrictions ? Feature freeze ?15:15
ttxUsually the whole dance is explained at https://wiki.openstack.org/wiki/ReleaseCycle15:16
ttxlet me know if it's missing something15:17
nikhil_kah, I was looking for more control on reviews15:17
nikhil_kand to let everyone know where to stop giving +2A15:17
nikhil_kThat seems okay and I think people will have to use their common sense15:18
ttxyeah, we don't really prevent them from shoting themselves in the foot15:18
nikhil_kgotcha15:19
ttxnikhil_k: that's all I had. Questions on your side ?15:20
nikhil_kNothing from me15:20
nikhil_kThanks!15:20
ttxalright then, have a great end of week, talk to you Tuesday15:20
nikhil_kHave a nice one, yourself!15:20
nikhil_kttyl15:20
Kiallhey ttx - back at my desk...15:20
ttx#topic Designate15:21
Kiall(and only 13 seconds late ;))15:21
ttxhttps://launchpad.net/designate/+milestone/kilo-rc115:21
ttxPerfect timing, had to talk to Nikhil anyway15:21
ttxI see one unprioritized BP left15:21
KiallOkay - 3 the in-progress bugs have reviews up, 1 in gate, 2 just got some minor reviews.15:21
* ttx removes the invalid one15:22
ttxHow far is stable-v2 from merging ?15:22
ttx(if that's something you want to merge)15:22
KiallThe last BP - Mark V2 stable - is waiting on a decision as to if we can call V2 stable - The actual change is a 1 liner, we're reviewing the API and thinking through future use cases to make sure we don't shoot ourselves in the foot15:23
KiallI'm hopeing we can have a go/no go before the weekend is out.15:23
ttxok, so it's a last minute thing15:23
ttx#info stable-v2 is a placeholder for the decision on marking v2 stable or not15:23
KiallYea, exactly..15:24
ttxok, you seem to have stuff under control15:24
ttxand to be on track to hit RC1 in a reasonable timeframe15:24
ttxI don't think I have questions. Do you ?15:24
KiallYea, things are shaping up nicely :) I'll likely give you a sha1 for rc1 early next week15:24
ttxcool, thx!15:26
Kiall1 - we'll probably have an rc2.. we just don't know what specific issues yet15:26
ttxright -- it's fine to have a RC2 over a new unknown issue15:26
KiallHP designate folks getting into a room the week of the 12th to try break things..15:26
Kialland I'm confident we'll find a bunch ;)15:26
ttxthat's the goal, rc1 usually triggers testing15:26
KiallCool, that's it so :)15:26
ttxit's the "will be the release unless you can find a critical bug in it"15:26
ttxalrightn have a great end of week!15:27
KiallSame to you15:27
ttx#endmeeting15:27
openstackMeeting ended Thu Apr  2 15:27:22 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:27
openstackMinutes:        http://eavesdrop.openstack.org/meetings/incub_sync/2015/incub_sync.2015-04-02-14.53.html15:27
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/incub_sync/2015/incub_sync.2015-04-02-14.53.txt15:27
openstackLog:            http://eavesdrop.openstack.org/meetings/incub_sync/2015/incub_sync.2015-04-02-14.53.log.html15:27
*** SlickNik has left #openstack-relmgr-office16:28
*** bswartz has quit IRC17:01
david-lylettx, any chance you're still around?17:02
*** russellb has quit IRC17:55
*** johnthetubaguy is now known as zz_johnthetubagu17:56
*** russellb has joined #openstack-relmgr-office17:58
*** russellb has quit IRC18:15
*** russellb has joined #openstack-relmgr-office18:19
*** russellb has quit IRC18:42
*** russellb has joined #openstack-relmgr-office18:47
*** ttx has quit IRC21:35
*** morganfainberg has quit IRC21:37
*** morganfainberg has joined #openstack-relmgr-office21:37
*** ttx has joined #openstack-relmgr-office21:39

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