12:30:25 #startmeeting releaseteam 12:30:26 Meeting started Mon Sep 14 12:30:25 2015 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:30:27 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 12:30:30 The meeting name has been set to 'releaseteam' 12:30:46 Agenda @ https://wiki.openstack.org/wiki/Release_Cycle_Management#Agenda 12:31:00 #topic Liberty release coordination 12:31:14 I actually refactored a number of etherpads into a single plan at: 12:31:23 #link https://etherpad.openstack.org/p/liberty-final-release 12:31:34 so we are at R-4 12:31:56 nice 12:31:59 On the requirements side, we should have completed the work on constraint bumping 12:32:10 not sure where we stand on that 12:32:25 I suspect it's linked to the libraries stuff 12:32:35 i.e. can't bump until we did the last relkeases 12:32:37 yeah, I think we have a couple of other libraries to release 12:32:53 I'll put in bold where we are late 12:32:55 troveclient, glanceclient 12:33:04 All oslo libs are done now ? 12:33:21 ("done" as in we can branch from the last release) 12:33:28 ttx: yes 12:33:41 * dhellmann types slower than dimsum__ this morning 12:33:54 :) 12:34:07 i am still in the weekend mode too dhellmann :) 12:34:27 I add bold to the steps we need to complete this week 12:34:54 So we should cut stable branches for Oslo, make the last client rteleases and constraint bumps, thyen branch the client libs too 12:35:02 ok 12:35:07 sounds good! 12:35:13 I type fast but don't stop to correct my typos 12:35:20 I'll start working on the releases as soon as the crew is here and working in the basement 12:35:30 OK, on the cycle-with-milestones front... 12:35:43 dimsum__: do you have permissions to create branches, or should I go ahead and do those? 12:35:51 we need to engage with the various project teams and check that they purged their FFEs 12:35:58 dhellmann: i don't have permissions 12:35:59 and that they are making progress toward their RC1s 12:37:01 We also need to get them to converge on constraints (i.e. import the requirement bot proposed changes) once we have all the libs nailed 12:37:14 ttx: by purge you mean that the rc milestone is accurate, not empty, right? 12:37:56 by purge I mean, they should no longer have FFEs by now 12:38:07 they should have completed the associated features 12:38:26 ack 12:38:30 so nothing open 12:39:33 OK, I un-bolded the things that are blocked 12:39:45 Let's put names on each of those bold lines 12:40:38 Cool, once you're done with libs we can work on the bump/converge constraints R-4 tasks 12:40:53 dhellmann: when do you expect to complete the libs releases ? Tomorrow ? 12:40:59 I'll send email announcing the need for final client releases and that we'll create the branches later in the week 12:41:08 there are just 2 up for review now, and I can do the releases today 12:41:08 ok 12:41:32 OK, questions on that plan ? 12:41:35 Things missing ? 12:41:38 I could start branching oslo and the clients we've done recently today/tomorrow 12:41:53 I think it's clear 12:42:06 right, then we can work on clast contrainst bump and start merging the resulting updates at the end of the week 12:42:25 I may have skipped an important step, so if you think of anything let me know 12:42:55 One interesting thing I notices with -intermediary things is that there is no real moment when do merge the translations 12:43:04 to* 12:43:32 If you follow johnthetubaguy's StringFreeze approach, we do have to do a RC2 to merge the translations, one week after RC1 12:43:34 translations can be patch releases, no? 12:43:41 which is basically what we did in the past 12:43:49 dhellmann: yes 12:44:03 it's just that the process doesn't enforce those at all (in fact we never did that for Swift) 12:44:27 there is a RC release, and most of the time it's the final, no "translations merge point release" after that 12:44:42 yeah 12:44:51 we should talk to the translation team about that and see what we can do 12:45:07 just food for thoughts, how to integrate translations in the "intermediary" model. 12:45:45 RC2 for translation is the approach we did in horizon. 12:46:15 right, it's what we do for every "milestone-based" project 12:46:21 intermediary model has not discussed in i18n team either. 12:46:41 *been discussed 12:46:42 ok, moving on 12:46:51 #topic Publicize docs.o.o/releases 12:47:00 dhellmann: I think it's ready to get some publicity now 12:47:16 ok, I'll send email about that today 12:47:17 since that will be our main way of associating numbers with cycles 12:47:20 -dev or -announce? 12:47:37 Hmm... -announce maybe 12:47:46 most devs know how to read tags 12:47:55 k 12:48:08 We can point to it at the cross-project meeting 12:48:20 sounds good 12:48:31 questions on that topic ? 12:48:53 if you have anything in particular you want in that message, let me know, otherwise I'll write something up on my own 12:50:00 dhellmann: nothing special -- something like "with the new model it's more difficult to find which version maps to what cycle, so we provided a translation table (website) and YAML data (repo)" 12:50:15 that's more or less what I was going to say 12:50:18 you can point to my blogpost about new versioning 12:50:30 for those who missed that epidsode 12:50:48 http://ttx.re/new-versioning.html 12:50:50 ++ 12:51:16 #topic Release model tags mass approval 12:51:47 hmm, looks for link 12:51:50 * dhellmann hopes this means his list of open reviews is going to shrink soon 12:52:05 https://review.openstack.org/#/q/project:openstack/governance+topic:%255Erelease-tags/.*,n,z 12:52:29 let's see if we can approve a bunch now 12:52:36 I see 2 with -1 12:52:43 dhellmann: how much more time do you have in the meeting ? 12:52:49 we can do taht one off-meeting 12:52:55 on-channel 12:52:56 ttx: just a couple of minutes, yeah, can we do that in a bit? 12:53:00 sure 12:53:09 #info will do in-channel 12:53:19 #topic PTL candidacy 12:53:37 dhellmann: Wanted to ask you if you would be interested in a PTL rotation 12:54:04 I'll give that some serious thought. 12:54:53 I don't expect that to change a lot either way, since we are acting like equals, but if you're interested, let me know and we can set up some healthy rotation there 12:54:58 we talked about it a bit early on, and I think as long as you're around to help with schedule, it's probably something I could take on for a cycle as we push out the remaining process changes, but I need to check that HP doesn't have other stuff they need me to look at, too 12:55:17 sure, just let me know 12:55:23 I do agree it would be good to establish that we can rotate the position 12:55:40 Just saying I'm not stuck on the throne :) 12:55:41 I suppose I would need to propose myself, so I'll let you know in a day or two :-) 12:55:47 ack 12:56:06 The remaining points on the agenda are more forward-looking 12:56:12 * jokke_ hands over the vaseline ;) 12:56:21 #topic stable/liberty point releases plan 12:56:58 My question here is whether there is anything we need to do before release / design summit on that front 12:57:14 did we settle on doing those on-demand? 12:58:21 I don't think we officially settled on that. We just said that would be plan B unless we can come up with something better 12:58:33 ok 12:58:51 we might just need to get the interested parties in a room to hash it out, then 12:58:58 I have to run, the workers are here 12:59:00 So yeah, we might want to give that Mitaka plan a bit more publicity 12:59:02 ok 12:59:04 ttyl 12:59:07 #endmeeting