19:00:00 #startmeeting releaseteam 19:00:01 Meeting started Thu Jun 27 19:00:00 2019 UTC and is due to finish in 60 minutes. The chair is tonyb. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:02 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:00:05 The meeting name has been set to 'releaseteam' 19:00:23 hi! 19:00:50 diablo_rojo, smcginnis, dhellmann, armstrong, evrardjp: Release team meeting ping 19:00:57 o/ 19:01:00 o/ 19:02:06 I suspect this is all we'll get today/tonight 19:02:23 Only one topic for the agenda 19:02:27 Got all the cool kids though. 19:02:36 ...I added a second topic but its not really important 19:02:59 * fungi is not cool, but here anyway 19:03:05 diablo_rojo: I see that 19:03:28 fungi: you are cool .... and you'll see I relied on your own notifications ;P 19:03:43 #topic Review content for next proposed emails 19:03:45 indeed 19:03:48 Yeah, so I've been reviewing the content for the next two, and I think we can just send one three weeks before M-2, one one-week before M-2 and one on M2 week 19:03:55 #link https://etherpad.openstack.org/p/relmgmt-weekly-emails 19:04:03 One key thing being you send on R-15 the one talkign about R-14 19:04:18 So if you scroll down to R-15... 19:04:38 That would be the one to send next week, to prepare R-14 19:05:07 Overall idea being to only send when we have somethign to say, rather than every week 19:05:15 ttx: Just reading it/them 19:05:26 Sounds like less work that way, and also less faigue in readers 19:05:30 fatigue 19:05:37 That sounds like a good idea. 19:05:58 I only check-drafted the R-15 and R-13 ones 19:06:09 I did get a few folks saying they appreciated the countdown emails, but I think less often will be more useful as a good way to highlight things. 19:06:20 If you look at the rest of the document, I propose similar skips 19:06:34 Obviously starting at R-7 it's weekly 19:06:39 +2 19:06:50 because we have different things to say every week 19:07:41 Looks good to me 19:07:43 tonyb: idea being to sdend teh email toward the end of the week, to prep for what needs to be done the coming week 19:08:13 OK, so if you all agree, I can translate that into tasks on the tracking etherpad 19:08:38 Thanks ttx for bringing this up, diablo_rojo for pulling the data together and smcginnis for writing all the email last cycle we've used ;P 19:09:03 ttx: I want to get in the habbit of sending them right after we close this meeting 19:09:10 * diablo_rojo is a copy pasta pro 19:09:12 ++ 19:09:22 which will be much more doable with all this work in place 19:09:44 Some of that content is a few years old at this point. ;) 19:10:22 yeah, I did a gheavy rewite on the two I check-drafted so far... 19:11:50 Well thanks all round, I was struggling there a little 19:12:12 Happy to help :) 19:12:26 Hmm we might need an email on R-8 about the extra-atcs-deadline in R-7 19:13:52 ttx: We can add it in the important dates now and then do the R-8 thing also 19:14:18 Extra ATC is really only useful now for allowing someone to vote, right? 19:14:18 OK, I moved things around 19:14:42 smcginnis: yeah, arguably not a release thing 19:14:50 and more of a election official thing 19:15:26 Still useful to remind folks. I'm just thinking overall it's less important since not as many projects even need elections now and there is no free pass associated with that status. 19:15:34 Just thinking out loud really. Carry on. :) 19:15:45 I dont think it hurts to mention it. 19:15:45 we can mention it on the '4 weeks before milestone-3" one 19:16:10 I dropped a note to remember 19:16:10 smcginnis: but extra-atcs also get to vote for TC memebers 19:17:02 thanks ttx 19:17:07 So the way it stands we'd send one on R-15 R-13 R-12 R-9 R-7 and then up to R-1 19:17:54 Less than a dozen emails isnt so bad 19:17:58 Also week after previous release, week before milestone-1 and week of milestone-1, but I haven't rewritten those 19:18:01 yes, election-related deadlines were included on the release schedule mainly out of convenience 19:18:25 as they were generally tied to release cycles 19:18:30 So please proofread the ones proposed for R-15 and R-13 when you get a chance 19:18:54 Can do 19:18:57 ttx: \o/ 19:19:09 I'll try to drop a base draft for them a couple of weeks before we need to send them, so as to not do them all at the same time 19:19:23 #topic StoryBoard Backlog + Board 19:20:24 diablo_rojo says: I think the board is pretty out of date and we should probably prioritize some items for when people have free time (free time lol) 19:20:36 #link https://storyboard.openstack.org/#!/board/64 19:20:48 #link https://storyboard.openstack.org/#!/project_group/73 19:21:04 There are probably also items that are done that can be marked as closed 19:21:05 Heh yeah. Was browsing SB the other day and I know we made some stories at the PTG, but that also some of them are done and I dont think its up to date. 19:21:44 The board itself I think is behind a bit too? Not sure if there are other things we have in our backlog that should get prioritized 19:21:45 there's at least one assigned to me since ages i still haven't gotten around to doing 19:21:53 (sorry!) 19:22:33 * diablo_rojo imagines everyone with the board and backlog open browsing 19:22:46 Shouldn't things that are done automatically drop from the board? 19:23:08 Nope. Its not using automatic worklists 19:23:23 Its a manual board/manual worklists 19:23:54 Then it's always going to be out of date. :/ 19:24:36 you can go tag the relevant stories and build automatic lanes based on tag+status queries 19:24:40 I think once people get their stuff merged, they should go ahead and move it to done or remove it frm the worklist 19:25:22 i mean as an alternative to continuing with manual lanes 19:25:53 one is more work up front, the other more work down the road 19:26:01 always a tradeoff 19:26:28 The project group page is probably "okay" we just need to update status on som eof the items but board seems like it needs a lot ove work 19:28:38 *of 19:28:47 I am happy to do a first pass of the board after we get the actual stories closed out that are completed. 19:28:55 I just dont know what all has been done. 19:29:15 There were things marked as Stein.. 19:29:56 Yeah I think most of the stuff on https://storyboard.openstack.org/#!/board/64 is done 19:30:06 Thats kinda what I had thought.. 19:30:56 diablo_rojo: I'll go through the board this week 19:31:06 then we can review it in this meeting next week 19:31:38 tonyb, let me know when you are and I can help. 19:32:06 I like the idea of "building all the automation" but I probably shoudln't ;P 19:32:12 diablo_rojo: will do :) 19:32:38 diablo_rojo: any afternoon that really works or sucks for you next week? 19:33:32 Monday would be good. 19:33:42 The rest of the week I will be out because MURICA 19:33:52 and asettle and andymccr will be around 19:34:22 My monday 19:34:26 your Tuesday 19:34:56 diablo_rojo: Okay, I'll see what I can do with my meetings 19:35:18 #topic Open discussion 19:35:37 tonyb, cool. I can stick around later that day if you can't finagle meeting stuff 19:36:00 As diablo_rojo alluded to, next Thursday is a holiday in the US. Most folks here have the day off from work. 19:36:29 (and are even likely to be nowhere near a computer!) 19:36:32 There are enough non-US members here that I think a meeting could still be useful, but should probably expect a few of us to be AFK. 19:36:41 Oh yeah .. and the meeting in Thursday 19:37:15 friday in tonyb's case ;) 19:37:16 smcginnis: but if it's just ttx and I we could you know not do it at 2100/0500 19:37:26 Very true! ;) 19:38:00 seems like a good opportunity to sleep in 19:38:04 hmm, would be good to at least do a go-nogo on the email? 19:38:25 +2 for sleeping in wherever possib;e 19:38:27 possible 19:38:30 but that can be done through some async channel 19:39:47 ttx: Yeah, I have to leave early on Thursday so I don;t think we can do it earlyish your morning ... 19:40:05 lets do it async during the week 19:40:20 I mean, we could review it now too 19:40:48 I don;t expect anything new being discovered next week 19:41:32 Guessing it will be a quiet week. 19:41:54 Yeah probably 19:42:17 if the gate catches fire and there's nobody around to notice, does it make a funny smell? 19:42:43 hehe 19:45:16 ttx: mail on L253 LGTM ... much better than anything I could have written 19:47:26 tonyb: alright then, no need for meeting next week 19:47:50 \o/ 19:49:10 anything else? 19:49:11 Holiday for everyone. And Tony gets to sleep in. :) 19:50:10 Nothing from me 19:50:22 tonyb, just let me know when you wanna have the storyboard party 19:50:29 Other are of course invited too :) 19:50:36 diablo_rojo: will do ;P 19:51:05 I s'pose I should make sure everyone knows that the week of the 8th I'll be totally AFK 19:51:08 no laptop 19:51:30 I will have my phone but I'll trry not to look at IRC/email 19:51:40 Good call. 19:51:49 Says the man with IRC on his phone lol 19:51:59 It's true 19:52:18 Fell free to ping me there but don't expect fast replies ;P 19:52:29 *feel* even 19:52:44 No free falling. 19:53:11 smcginnis, but skydiving is fun 19:53:42 * ttx runs 19:53:48 #endmeeting