13:01:04 #startmeeting releaseteam 13:01:05 Meeting started Mon Jun 15 13:01:04 2015 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:01:06 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:01:08 The meeting name has been set to 'releaseteam' 13:01:18 o/ 13:01:26 Back to ful speed this week 13:01:32 we have liberty-1 next week 13:01:42 so we might need to complete a few things before then 13:01:55 courtesy ping for dims and lifeless as library release team members 13:02:06 ack 13:02:10 \o/ 13:02:14 #topic Things to do before liberty-1 13:02:31 So for liberty-1 we'll need... 13:02:41 - the script to retrieve completed blueprints 13:03:18 - potentially the new preversioning (to tag X.Y.0b1) 13:03:24 what else... 13:04:01 I have a todo to make a list of what those versions should be 13:04:40 dhellmann: Currently still hesitating to switch all tp 12 or all to .0.0 13:05:17 If we opt for I would pick the number of integrated releases they have been here to simplify 13:05:39 yeah, I was going to go through and count those for all of the projects, unless you already have a list like that somewhere? 13:05:57 actually: https://review.openstack.org/191228 13:05:59 I don't have such list, but there is a "since" in the integrated-reelase tag that carries the info 13:06:11 oh, right, forgot about that :-) 13:06:19 as official as it gets 13:06:32 that will make it easier 13:07:22 dhellmann: you think we have still time to carry that through before next week ? I think it would be better to not issue any 2015.2.0 tag 13:07:33 but we still can if needed 13:08:10 I'll make the list today 13:08:16 I guess we should make it the top discussion at tomorrow's cross-project meeting 13:08:24 to have closure on it 13:08:42 you've convinced me we don't want to use 12 for everyone, so in my mind that is decided 13:08:56 also preemptively engaging with most PTLs might be a good idea 13:09:32 that's a good idea -- we're expecting them for office hours tomorrow, right? 13:09:52 tomorrow's office hours is still pretty much opt-in 13:10:00 but we can actively ping them before meeting 13:10:18 ok, how about if I send an email with the proposed versions? 13:10:27 heh, that's what I was writing 13:10:52 then I can ping the EU/EMEA/APAC-based ones in Tuesday morning 13:10:58 during my office hours 13:11:11 and you can ping some of the others during yours 13:11:11 ok, I'll start working on that after we're done with the meeting 13:11:21 than we do a catch-all during the cross-project meeting 13:11:38 and start pushing the resulting patches wednesday, in time for next week tags 13:12:01 I'll take ownership of the Launchpad scripts side 13:12:16 I can do the patches to update the pre-version values 13:12:25 #action dhellmann to calculate and post proposed version numbers to ML 13:12:39 #action shellmann and ttx to reach out to PTLs during office hours about next version 13:12:42 arh 13:13:04 #action ttx to write the new blueprint-grabbing script 13:13:38 dhellmann: are we going to release python-.*client(s) as well? 13:13:54 dims: I don't think so 13:13:58 no? 13:14:03 we do have quite a backlog 13:14:14 I mean, it's unrelated 13:14:16 maybe after the milestone? 13:14:20 ok 13:14:35 Alright, anything else in the "must be completed before next week" bucket ? 13:14:54 (adding new server versioning discussion to cross-project meeting agenda) 13:15:10 Looks like I'll chair that meeting 13:16:42 OK, moving on 13:16:43 I can't think of anything else that has to be done by next week 13:16:54 #topic Recentralize library release management 13:17:05 This was also added to tomorrow's cross-project meeting agenda 13:17:26 the patch is up to set the acls, but I haven't asked the infra team to prioritize it yet 13:17:37 There doesn't seem to be much objection so far, but I suspect most PTLs missed it 13:17:49 I think one more round of publicity would be good, so maybe we can target that change for wed, after we've discussed it again 13:17:53 so with the discussion up tomorrow that will be a good heads-up 13:18:13 so far the only comment was to point out a client lib I missed in the original draft of the patch 13:19:04 I have the infra spec to review on my TODO list 13:19:09 as well as the release-tools reviews 13:19:27 ttx: there are some changes to the release scripts up for review still, can you put those on your priority review list, too? that will make it easier for dims and lifeless to use the same version I'm using 13:19:32 heh 13:20:35 :) ++ 13:20:45 Anything more on that topic ? 13:21:31 I haven't decided how proactive I want to be with releases 13:21:44 for oslo I scanned the unreleased changes weekly to decide when we needed releases 13:21:48 At this point I think we can wait and see 13:21:52 we could do the same with the other libs, or -- yeah 13:22:05 as the process gets more streamlined and we have more people to handle it, we can start being proactive 13:22:09 one step at a time :) 13:22:29 * dhellmann takes a deep breath 13:22:33 dhellmann: ttx: i am running ./list_oslo_unreleased_changes.sh and putting it in front of the team in monday meeting 13:22:43 (oslo meeting) 13:23:16 dims: sounds good 13:23:22 ok; moving on 13:23:51 #topic New PTL/RelMgt coordination 13:24:23 We are left with building reusable checklists 13:24:43 I think we can figure it out as we go during next week 13:24:54 I'll have an etherpad ready during my end of the office hours 13:24:59 with the points to cover 13:25:23 by the time it comes to your side of the office hours it should already have a few critical steps to cover 13:25:29 k 13:26:10 Oh, about releasing in general -- do we want to more officially repurpose openstack-announce for all the announcements ? 13:26:30 i.e. push there instead of dev with Reply-To set to dev 13:26:58 I'm still waffling about that. I see the benefit, though. 13:27:11 and communicate to -dev and openstack@lists.o.o that we won't cover annoucnements there anymore so they should subscribe to low-traffic announce) 13:27:30 currently we do server release announces to -announce and openstack@ 13:27:49 ok, I guess we should be consistent with the libraries, then, too 13:28:21 and lib announce to -dev only 13:28:36 I think making them all post to -announce is a good middle way 13:28:42 yes, that sounds good 13:28:43 with reply to set to -dev for libs 13:28:52 we should announce the change on the other lists 13:28:58 Yep, I'll take that on 13:29:14 #action ttx to announce convergence to -announce for all release announcements 13:29:27 though we could wait for the library release takeover 13:29:30 #action dhellmann update release note sending script to send to -announce list instead of -dev 13:29:49 bah I'll find the rigth wording 13:30:07 I need to take 5 min to get my youngest daughter off school apparently 13:30:20 Feel free to cover another topic, like onboarding of new release team memebrs 13:30:24 I'll brb 13:31:09 dims: once we have all of the tools merged, I was planning to rely on you to deal with the oslo releases. That will let me concentrate on all of the clients and non-oslo libs. 13:31:47 and we'll have lifeless to help as well, of course 13:32:23 dhellmann: sounds good. if i can shadow you to take notes at least one more time, i'll feel comfortable 13:32:52 sure, we can work through the next batch of releases together 13:33:09 you may also want to take a look at the spec for starting to automate some of this: https://review.openstack.org/#/c/191193/ 13:33:23 very much a WIP 13:34:30 ack starred it for later 13:36:16 ok, back, sorry about that 13:36:25 np 13:36:35 dims: this one may be interesting, too: https://review.openstack.org/#/c/189858/2/release_many.sh,cm 13:37:03 I think we have a clear plan for the coming week 13:37:25 Let's pass on the release modeling (buckets) thing for this week until we are past l1 13:38:12 k 13:38:18 #topic Open discussion 13:38:40 pabelanger, dims: we kind of track work using https://etherpad.openstack.org/p/liberty-release-mgmt 13:39:00 I added a new "Onboarding new release team members" section 13:39:18 ack 13:39:27 bookmarked 13:40:15 dhellmann: see anything else we should discuss/coordinate for this week ? 13:40:48 dhellmann: I'll chair the cross-project meeting tomorrow, but rely on you to introduce our two topics ? 13:40:50 I just (re)noticed the comment about making release management opt-in -- did we mean that to apply to the libs, too? I wonder if my ACL changes includes more projects than it should 13:40:55 ttx: sure 13:41:22 dhellmann: that's a good question 13:41:41 maybe we should align with the project teams we "cover" 13:42:00 I basically updated everything currently under openstack/ that looked like a library 13:42:09 https://review.openstack.org/#/c/189856/ 13:42:13 i.e. 5.1.2.1.1 and 5.1.2.1.2 13:42:38 excluding things like magnum or magnetodb which we don't handle the server part of yet ? 13:43:19 that seems weird to handle the libs of a project team we don't manage the main product of 13:43:19 yes, I left them out 13:43:48 that way we could actually apply the "managed" tag at the project team layer 13:43:55 yeah, I'm still concerned with bad versioning practices, but as you say, "one step at a time" 13:44:13 yeah 13:44:29 which I think makes more sense 13:44:46 speaking of tags, I'm going to propose one to indicate that a repo contains a library rather than a server project, so we can have tools that look at all of the library project repos 13:45:21 dhellmann: you prefer a "lib" tag than a "server"/"mainthing" tag ? 13:45:31 I agree that sidesteps the naming problem gracefully 13:45:40 but that will result in more lines 13:45:58 we could have both/all of those, but it seems easier to say "show me a list tagged with X" than "show me a list not tagged with Y" 13:47:18 hmm, yeah, also some things will likely fall in-between 13:47:35 so we could have a "service" and a "library" one 13:47:59 should those be "release:X" or use some other prefix? 13:48:22 type:service and type:library? 13:48:47 On one hand they are generally useful so type: would be more appropriate 13:49:08 on the other release:* will generate less questions (those are the tags driven by this team) 13:49:27 maybe try type: and we can retreat to release:* if people complain 13:49:31 ok 13:50:02 type: service will be super useful to sort the grain from the chaff 13:50:23 (in, say, the project navigation website) 13:50:34 true 13:50:59 and that lets "everything else" (like, say, zuul) be undetermined 13:51:16 service means an openstack service as presented by the keystone catalog 13:51:24 imho 13:51:53 yes, that's how I was thinking of it, too 13:52:43 ok, added a few notes under the "buckets" section 13:53:46 Alright. anything else ? 13:54:01 nothing from me 13:55:30 Alright, have a good week! 13:55:32 #endmeeting