14:06:46 <dhellmann> #startmeeting releaseteam
14:06:47 <openstack> Meeting started Fri Mar  4 14:06:46 2016 UTC and is due to finish in 60 minutes.  The chair is dhellmann. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:06:48 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:06:50 <openstack> The meeting name has been set to 'releaseteam'
14:07:10 <dhellmann> courtesy ping: ttx, dims, lifeless
14:07:16 <ttx> o/
14:07:29 <dhellmann> #link our agenda is under R-5 on https://etherpad.openstack.org/p/mitaka-relmgt-plan
14:07:45 <ttx> that etherpad is starting to be so huge it's pretty slow
14:08:09 <dhellmann> yeah, I've started seeing letters inserted in the wrong order when I type, too. Next cycle we probably want to split the calendar into a few pages
14:08:17 <dhellmann> maybe one per milestone
14:08:20 <dims> o/ partially here
14:08:26 <dhellmann> anyhow, let's start
14:08:31 <dhellmann> #topic m3 deadline
14:08:41 <ttx> So we have 3 misses
14:08:45 <dhellmann> thanks, ttx, for putting together the list of projects that haven't done releases
14:08:48 <ttx> On managed one (barbican)
14:09:01 <ttx> and trove-dashboard
14:09:15 <ttx> In the official list, Astara missed the date again
14:09:17 <dhellmann> I wonder if trove-dashboard was merged into horizon? amrith, david-lyle?
14:09:27 <dhellmann> I've pinged adam_g about that, but I think he's west coast
14:09:42 <ttx> dhellmann: about barbican, you noted that they were just waiting for a late patch
14:09:58 <ttx> I haven't sent the m3 email announcement yet
14:10:01 <dhellmann> yeah, I didn't get a patch id
14:10:05 <dhellmann> I'll ping redrobot
14:10:12 <ttx> so we could squeeze it in
14:10:40 <ttx> adam_g: what about Astara ?
14:10:48 <ttx> ok
14:11:33 <ttx> dhellmann: are you fine adding barbican and trove-dashboard if we can get them in the next hours ?
14:11:33 <dhellmann> since astara isn't managed, I think it's safe to announce m3 without them, even if we let them slip a tag in later today
14:11:44 <ttx> sure
14:12:02 <dhellmann> I'd like to get both barbican and trove-dashboard in though, assuming amrith actually wants a trove-dashboard release
14:12:07 <amrith> hello
14:12:10 <ttx> ack
14:12:23 <dhellmann> I need to come up with a better way to track who's keeping up with the schedule next cycle. A checklist of deliverables.
14:12:29 <amrith> dhellmann, trove-dashboard should be released, yes.
14:12:40 <amrith> I wasn't sure whether it is treated as a 'client library'
14:12:50 <amrith> and the understanding we had was that horizon would get it
14:12:52 <ttx> no, it's treated as an extra thing
14:13:01 <ttx> same deadlines as trove itself
14:13:10 <dhellmann> if follows cycle-with-milestones, so we need a 0b3 tag
14:13:10 <amrith> well, extra thing with its own release or extra thing that horizon will get?
14:13:23 <ttx> most projects release the -ui extensions at the same time as the main thing
14:13:23 <amrith> ok, a b3 tag shall be produced ;)
14:13:25 <dhellmann> amrith : according to http://governance.openstack.org/reference/projects/trove.html the trove team manages it
14:13:43 <amrith> dhellmann, ok, I'll make a b3 tag.
14:13:46 <ttx> amrith: thx
14:13:48 <dhellmann> amrith : great, thanks!
14:13:56 <amrith> what's the convention re: the version numbering? Same as trove I assume?
14:14:08 <ttx> amrith: well...
14:14:10 <amrith> when they are to be release together (same time)
14:14:14 <ttx> the issue is it's been using it's own
14:14:17 <dhellmann> amrith : it doesn't have to be
14:14:25 <ttx> https://review.openstack.org/#/c/288339/
14:14:34 <dhellmann> I see 6.0.0.0b2 there now
14:14:47 <amrith> yikes
14:15:02 <amrith> that's 'interesting'.
14:15:05 <ttx> amrith: you might want to post a follw-up patch to https://review.openstack.org/#/c/288339/
14:15:09 <dhellmann> though that's probably an old one
14:15:27 <ttx> dhellmann: no, it's the m2 one
14:15:32 <amrith> well, that's about 4h old. I think ttx just posted that this AM
14:15:42 <dhellmann> ah, yeah, I see that's a new patch now
14:15:52 <ttx> yes, it's just documenting the existing patch
14:15:55 <ttx> tag
14:16:03 <dhellmann> got it
14:16:23 <amrith> how badly would the wheels come off if I sent up a 5.0.0.0b3?
14:16:34 <dhellmann> very badly, you can't go backwards
14:16:45 <amrith> seems to make sense that Trove 5.0.0.0b3 goes with trove-dashboard 5.0.0.0b3, no?
14:17:04 * amrith channels my inner Trump
14:17:12 <ttx> yes, but things would be very unhappy
14:17:22 <amrith> ok, so going backwards is out.
14:17:25 <ttx> like they would continue to use 6.0.0.0b2 anyway
14:17:35 <dhellmann> your users would come and find you and do unpleasant things to you for breaking their upgrades
14:17:35 <amrith> so it may be too late to catch this bus
14:17:56 <ttx> I'd say do a 6.0.0.0b3
14:18:00 <dhellmann> right
14:18:01 <ttx> and maybe align next cycle
14:18:02 <amrith> and at a later time, maybe trove has to skip release 6 and go straight to 7 in lock step with dashboard.
14:18:05 <amrith> ok, sounds good.
14:18:12 <ttx> i.e. go from 6 to 8
14:18:13 <dhellmann> you can fix them next cycle by jumping trove to 7
14:18:16 <ttx> err
14:18:18 <ttx> 5 to 7
14:18:20 <amrith> yup
14:18:20 <ttx> right
14:18:37 <amrith> ok, I'll send up a trove-dashboard 6.0.0.0.0b3
14:18:40 <ttx> dhellmann: maybe we can fast-approve https://review.openstack.org/#/c/288339/
14:18:45 <amrith> sorry, I'll figure the right number of 0's.
14:18:45 <ttx> so that amrith posts his on top
14:18:53 <dhellmann> done
14:18:58 <amrith> you want me to dep on 288339?
14:19:09 <amrith> or just wait for you to merge
14:19:12 <ttx> amrith: should be in master really soon.
14:19:14 <amrith> and then submit
14:19:17 <amrith> ok, thanks
14:19:18 <dhellmann> amrith : give it a few minutes to merge, those jobs don't take long
14:19:21 <amrith> will do it
14:19:27 <ttx> amrith: thx
14:19:33 <dhellmann> amrith : thanks
14:19:33 <ttx> next
14:19:42 <ttx> python-brick-cinderclient-ext
14:19:56 <ttx> missed lib freezae
14:20:10 <ttx> not used anywhere so smcginnis wanted to do a release next week
14:20:22 <ttx> At this stage I wonder if it's not simpler to make a first release in newton
14:20:33 <dhellmann> there's a 0.1.0 tag, when was that from?
14:20:34 <ttx> since it won't be used before
14:20:40 <ttx> hmm
14:20:44 <dhellmann> yeah, I just tagged that yesterday
14:20:46 <dhellmann> it might have been late
14:20:49 <ttx> oh
14:21:00 <dhellmann> 15:12 -0500
14:21:18 <ttx> I see it now. Ignore me
14:21:35 <ttx> Next
14:21:41 <dhellmann> ok, then cloudkitty
14:21:48 <ttx> python-cloudkittyclient needed for client lib  deadline today
14:21:58 <dhellmann> is that project active?
14:22:02 <ttx> sheeprine told me he would push a tag request now
14:22:17 <dhellmann> ok
14:22:38 <ttx> so it should be there anytime now, just doing a few last-minute tests
14:22:39 <dhellmann> how about the server-side projects?
14:22:50 <ttx> So that's the next topic
14:23:02 <ttx> Things that do intermediary releases but haven't yet
14:23:24 <ttx> cloudkitty, cloudkitty-dashboard: sheeprine promised me one in the next 10 days
14:23:36 <ttx> ironic-ui: do you have news
14:23:53 <dhellmann> jroll : what's the plan for ironic-ui?
14:23:58 * dhellmann has no news
14:24:10 <ttx> Last one I caught this morning was sahara-tests, no idea what plans SergeyLukjanov has for this
14:24:27 <ttx> we should keep a close eye on those next week
14:24:34 <ttx> and nag
14:24:42 <dhellmann> yeah
14:24:50 <ttx> I spotted a number of other issues while I went through my lists this morning
14:25:08 <ttx> I opened reviews for the first 3
14:25:29 * dhellmann waits for gerrit to reload the review dashboard
14:25:31 <ttx> The 4th is in progress, except angdraug hasn't +1ed my review so it's stuck
14:25:45 <ttx> The last 5 I want to discuss now
14:25:53 <ttx> - Missing entry for tacker 0.1.0 (tacker, tacker-horizon, python-tackerclient)
14:26:12 <ttx> I suspect we want to include that in the mitaka page ? Even if recent ?
14:26:16 <dhellmann> I don't see that, did it merge already?
14:26:28 <dhellmann> yeah, probably
14:26:45 <ttx> so we need to file a releases yaml for it
14:26:48 <ttx> I'll do that
14:27:06 <dhellmann> ah, ok, I thought you were saying you'd already done so, sorry I see now
14:27:15 <ttx> - pbr is release:independent but appears in mitaka deliverables
14:27:29 <ttx> so this is a mismatch but I have no idea what would be correct
14:27:46 <dhellmann> hmm, yeah.
14:27:47 <ttx> I'll let you sort that one out and file the fix
14:28:03 <ttx> - tempest is cycle-with-intermediary but hasn't done a "release"
14:28:08 <dhellmann> we don't do stable branches, but it seems important to indicate which version of pbr we need
14:28:10 <ttx> tempest is another odd one
14:28:17 <dhellmann> yeah
14:28:37 <amrith> ttx, dhellmann ... shouldn't dashboard projects also feature in requirements/upper-constraints/global-constraints? How else do we tie a particular dashboard version to a 'release'?
14:28:47 <dhellmann> there are some old stable branches, but I don't think mtreinish is using stable branches for tempest any more so maybe we should make it release:independent
14:29:01 <ttx> amrith: install docs I suspect
14:29:12 <amrith> ouch
14:29:13 <dhellmann> amrith : if nothing actually depends on it, the install guide and the releases.openstack.org page will do it
14:29:17 <ttx> - Other dashboards should not be considered "libraries"
14:29:42 <amrith> how then do we manage dependencies?
14:29:58 <ttx> So we have a bit of inconsistency where some -ui or -dashboard or -horizon project are type:library, some are packed with deliverables, and some don't have type
14:30:18 <dhellmann> ttx: that may indicate that we need another type: tag?
14:30:25 <ttx> My current take on them is that they should either be packed with deliverables or not use type: for the moment
14:30:41 <ttx> dhellmann: maybe, in the mean time I'd like to move those from library to other
14:30:51 <dhellmann> ttx: ++
14:30:55 <ttx> murano-dashboard, monasca-ui
14:31:02 <ttx> astara-horizon
14:31:18 <ttx> I think that is all
14:31:29 <ttx> the others are already there
14:31:39 <ttx> That will make it clearer that the deadline don't apply to them
14:31:39 <amrith> ok, I guess that's an independent conversation. I see your change merged, I'll push up 6.0.0.0b3 in a couple of minutes
14:32:01 <ttx> dhellmann: ok, will propose the fix for that too
14:33:14 <ttx> finall last one
14:33:17 <ttx> training-labs is release:cycle-with-milestones
14:33:20 <amrith> amrith proposed openstack/releases: Release 6.0.0.0b3 of trove-dashboard  https://review.openstack.org/288481
14:33:24 <ttx> which is kinda very weird
14:33:38 <ttx> given it didn't tag anything yet
14:33:53 <dhellmann> I don't even know what training-labs is, I'll check with loquacities
14:34:18 <ttx> Alright. All covered
14:34:55 <dhellmann> I really thought we'd straightened out the release model tags already. This is more mismatches than I expected.
14:35:19 <ttx> dhellmann: people keep doing weird things
14:35:19 <dhellmann> ready to move on to requirements?
14:35:20 <kzaitsev_mb> tried to read throught the conversation, but couldnt find the answer — is there anything wrong with murano-dashboard currently?
14:35:42 <ttx> kzaitsev_mb: not really. I'll remove the type:library tag from it since it's a horizon plugin
14:35:48 <dhellmann> kzaitsev_mb : we may want to change some tags, but that's it
14:36:06 <kzaitsev_mb> oh, got it =) you were talking about different type of tags =)
14:36:18 <dhellmann> yeah, governance tags :-)
14:36:29 * dims back on now
14:36:32 <dhellmann> #topic freezing requirements
14:36:37 <dhellmann> dims: just in time
14:36:40 <dims> :)
14:36:53 <dhellmann> I have a list there in the etherpad of a bunch of the patches I think we want to land for requirements.
14:37:06 <dhellmann> I think we *don't* want to land *any* others, including any future auto-generated constraints updates
14:37:12 <dhellmann> does that match what your expectations are?
14:38:12 <dims> yes, no more merges either to g-r or constraints.
14:38:16 <ttx> It looks sane but I'll admit I haven't looked at the whole list
14:38:32 <dims> anything we release today should be updated in upper constraints though
14:39:41 <dims> dhellmann : agree?
14:40:03 <dhellmann> dims : good point, we had one or two more client releases on that list from earlier
14:40:11 <dhellmann> I'll add those to the etherpad as they come in
14:40:17 <dims> dhellmann : cool
14:41:36 <dims> dhellmann : i am debating a oslo.cache update to match the dogpile.cache bump. as projects don't define dogpile directly and rely on oslo.cache to pull that in
14:41:39 <dhellmann> ok, we can make adjustments if we find the need
14:41:47 <dhellmann> dims : is that a new minimum?
14:41:59 <dims> dogpile.cache is a new minimum. yes
14:42:05 <dhellmann> yeah, I agree, it would be good to have that set with oslo.cache
14:42:33 <dhellmann> do we want to raise the minimum for oslo.cache, then?
14:42:37 <dims> ok. i'll spend some time today poking at list_oslo_unreleased_changes
14:42:45 <dims> dhellmann : yes, otherwise it would not work
14:43:24 <dhellmann> makes sense
14:44:00 <dhellmann> the etherpad is starting to slow down a lot, I may go ahead and create a new one for finalizing the release
14:44:03 <dims> that's the only one i had, will raise red flags if i see anything else
14:44:08 <dhellmann> if so, I'll stick a link in this one
14:44:13 <dims> thanks
14:44:16 <dhellmann> thanks
14:44:21 <dhellmann> #topic lib stable branches
14:44:30 <dhellmann> we've scheduled this for early next week
14:44:45 <dhellmann> dims, you wanted to try to do some oslo releases earlier?
14:44:49 <dhellmann> sorry, branches
14:45:09 <dhellmann> I think you'd want to leave oslo.cache out, since we're planning another requirements update there
14:45:28 <dhellmann> ttx: do you see any reason to wait until monday?
14:45:29 <dims> so can we just create the branches so folks can work on master say middle of next week
14:45:52 <dhellmann> so do you want to wait?
14:45:57 <ttx> dhellmann: breaking things on Friday is a bad idea ?
14:46:08 <dhellmann> ttx: very true
14:46:12 <dims> dhellmann : we don't have to do it today. just figuring out if we could do it and if there are any obstacles
14:46:19 <dhellmann> dims : ah, I see
14:46:42 <dims> so i can tell the team on monday in the oslo team meeting
14:47:05 <dims> ttx : +1 :)
14:47:20 <jroll> dhellmann: I'm told ironic-ui should have something this week, I have yet to find out how true this is
14:47:22 <dhellmann> we always cut a branch from a release, so you can go ahead and let them work with the understanding that if they commit features we'll have to set up the branch and backport bug fixes
14:47:31 <dhellmann> jroll : today's the day :-)
14:47:43 <jroll> mhm
14:47:43 <dhellmann> jroll : if there's someone else I should talk to, let me know?
14:47:50 <dims> dhellmann : cool. will pass that along
14:47:55 <jroll> dhellmann: betherly is leading that
14:48:03 <dhellmann> jroll : ack, I'll ping her
14:48:04 <jroll> I just poked her in ironic channel
14:48:25 <dhellmann> k
14:48:33 <betherly> hi jroll dhellmann
14:49:08 <dhellmann> hi, betherly, we were hoping to get an idea of when ironic-ui would be ready for a release or milestone tag?
14:49:28 <betherly> trying to get through review process. made a whole ton of changes this am to meet reviewer requests so waiting on the +2s before it can merge
14:49:57 <betherly> have pinged krotscheck to see if he can +2 things today
14:50:32 <ttx> dhellmann: looking at the tacker 0.1.0 tag it seems to be pretty empty and we shouldn't probably consider it a mitaka release.
14:50:49 <ttx> so I'll move tacker to the "ping for an intermediary release" section
14:50:50 <dhellmann> betherly : ok, it's marked as using the cycle-with-intermediary model, which means we'd like to have a release soon that we can use to fall back on if there are issues with any point releases between now and final
14:50:56 <dhellmann> ttx: sounds good
14:51:26 <dhellmann> betherly : basically, something *close* to final, with the expectation that you might have bug fixes but not features to land before actual final
14:51:40 <dhellmann> or there may be no changes needed, and we could use that version as final
14:52:08 <betherly> dhellmann: i will do my best to get it up there today for sure i will keep both you and jroll in the loop
14:52:23 <dhellmann> betherly : thanks! drop by #openstack-release if you have questions or updates
14:52:39 <betherly> will do thanks dhellmann!
14:52:47 <dhellmann> #topic open discussion
14:52:48 <ttx> dhellmann: means we shoudl probably ask for a python-tackerclient release ~todayish
14:53:12 <dhellmann> ttx: noted
14:54:17 <dhellmann> I've started filling in https://etherpad.openstack.org/p/newton-relmgt-plan by adding some of the incomplete action items from this cycle
14:54:49 <dhellmann> we can review those when we get closer to the end of the cycle and are ready to start doing planning
14:55:22 <ttx> dhellmann: would be good to get an idea of what lifeless managed to implement of his mitaka plan for constraints, so that we know what to defer to newton
14:55:31 <dhellmann> ttx: do you have a draft of the announcement email ready?
14:55:37 <ttx> dhellmann: not yet
14:55:46 <dhellmann> ttx; yeah,  I need to confer with him
14:56:35 <dhellmann> ttx: did you see my note about the FFE for ironic-lib under R-4?
14:57:09 <dhellmann> they have a FFE, but it's a lib, so they'll need to update the minimum requirement next week
14:57:32 <dhellmann> should we make the deadline tuesday?
14:57:48 <dhellmann> I think only ironic-python-agent will actually need to have that min updated
14:58:12 <ttx> if only ironic-python-agent is affected... they can have the whole week
14:58:24 <ttx> we'll have others as RC bugs are discovered in libs
14:58:34 <dhellmann> good point
14:58:50 <dhellmann> ok, anything else? we're about out of time
14:58:56 <ttx> nope
14:59:12 <ttx> FOr newton we should work on automating the verification I did manually this morning
14:59:21 <dhellmann> yeah, definitely
14:59:28 <ttx> i.e. governance/releases mismatches, and missing releases
14:59:31 <dhellmann> it would be nice to have some sort of dashboard
14:59:37 <ttx> ++
14:59:43 <dhellmann> something to think about
14:59:54 <ttx> also releases/git mismatches, like missing tags
15:00:09 <dhellmann> yes, good point
15:00:24 <dhellmann> we have some scripts for importing git tags, but they tend to produce messy results
15:00:32 <dhellmann> ok, we're out of time and should give up the channel
15:00:33 <dhellmann> thanks!
15:00:36 <dhellmann> #endmeeting