16:02:27 #startmeeting releaseteam 16:02:27 o/ 16:02:27 Meeting started Thu Feb 7 16:02:27 2019 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:02:28 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:02:31 The meeting name has been set to 'releaseteam' 16:02:37 Here but also covering a topic at the midcycle. 16:02:38 o/ 16:03:17 Agenda is at https://etherpad.openstack.org/p/stein-relmgt-tracking 16:03:30 down to R-9 / line 326-ish 16:03:46 \I only had a couple of items 16:03:55 #topic Assign week tasks 16:04:23 I can probably handle my tasks tomorrow. 16:04:26 o/ 16:04:27 We had a bunch of tasks for this week - I'm not sure if those got done yet, and if not we should probably make sure we assign them 16:04:46 smcginnis: for the first two, right ? 16:04:52 Yep 16:05:09 Unless someone else is really excited to do them. :) 16:05:09 Anyone up for updating PROCESS ? If no volunteers I'll take it 16:05:41 I'll help with reviews 16:05:58 me too 16:06:20 ok, I'll try to do that tomorrow as well 16:06:41 any other urgent task needing assignment? 16:07:21 #topic Feedback on review days 16:08:02 I wanted to ask for any difficulties encountered by our new review-day owners 16:08:18 But evrardjp is not here and I think diablo_rojo was traveling on her day this week 16:08:27 Still... does anyone have questions, feedback? 16:08:36 I was :/ 16:08:44 Nothing from me for this week. 16:09:03 Next week things should be more normal 16:09:15 I feel like that could be a regular topic for our meetings -- making sure we don't let our new reviewers alone 16:09:28 ++ 16:09:29 if you're traveling, just let us know (via the tracking etherpad) and we can cover 16:09:30 although I encourage to just ask on channel 16:10:18 #topic any other business 16:10:47 dhellmann, I'll make sure I do that next time. 16:10:52 Next week looks calm enough, we'll probably be focused on processing those model changes that smcginnis will post tomorrow 16:11:06 and having the interesting discussions it may trigger 16:11:10 diablo_rojo :-) 16:11:29 change is afoot 16:11:44 anything else before we close? 16:11:48 I do have one, unrelated to any other topic so far, question 16:11:51 ah! 16:11:57 I like questions 16:12:10 About when should I start the cat herding process for collecting cycle-highlights? 16:12:31 Was there a like..standard number of weeks before release? 16:12:56 I think Anne usually started doing that right before RC time. 16:13:03 hmm, that should be mentioned in PROCESS... i think there are countdown-email reminders too 16:13:31 IIRC, I think I would add it to the countdown emails after milestone 3. 16:13:37 I don't see "highlight" in doc/source/reference/process.rst 16:13:39 no mention of highlights in process 16:14:08 If we can decide on a process I can add the highlight info to process :) 16:15:03 I feel like it should start around FF time 16:15:09 a heads-up that it's coming before the RC period and then a reminder during the RC period seems good 16:15:11 So around m3 send reminder that highlights are a thing and that PTLs should start thinking about what they want to add? Is there any setup on our end that needs to happen? 16:15:13 In theory the featureset should be complete around then 16:15:32 diablo_rojo : they just include them in their deliverable file, so there's no extra work to be done 16:15:36 RC is more of the deadline to submit them 16:15:47 dhellmann, coolio 16:15:47 yeah, good point 16:15:48 so that the marketing machine can start digesting them into a message 16:15:57 and documenting the last point at which we care about updates would be good, too 16:16:09 So... maybe a reminder a couple of weeks before M3 in the countdown email 16:16:25 maybe that "last point of caring" is the same as the deadline 16:16:44 then actively start chasing them on M3 week, making it clear RC1 is the deadline, even if you can still fix them afterwards 16:17:12 wfm 16:17:14 Sounds good. 16:17:17 diablo_rojo: we don;t really have a "process" so you should probably define it 16:17:25 and add it to PROCESS.rst 16:17:37 which is no longer capitalized 16:17:44 I should be able to get the countdown out today and I will mention it's coming so it's on people's radar. 16:17:45 doc/source/reference/process.rst 16:17:52 * diablo_rojo writes post-it for defining process for cycle highlights to pile of to-do post-its for today 16:18:02 Just seemed more important when it was all caps. :) 16:18:16 It is PROCESS. Follow PROCESS. 16:18:32 Lol smcginnis PROCESS does seem more important 16:19:03 anything else? 16:19:14 Should just mention we had some release failures yesterday. 16:19:22 That appears to be resolved. 16:19:28 Just affected doc publishing. 16:19:32 yes due to base-jobs split. 16:19:48 hmm fungi is missing from the ping list 16:20:04 Nothing more about it, just thought it would be good to state it happened and is no longer an issue 16:20:14 fixed ping list 16:20:21 oh,i've been lurking and reading 16:20:41 alright, if nothing else, let's all return to the TODO pile 16:20:44 it's just been a really busy morning 16:20:55 have a great rest-of-week! 16:20:59 i have this meeting on my reminders already 16:21:00 o/ 16:21:11 #emdmeeting 16:21:18 * diablo_rojo goes to procure caffeine before swan diving into todo pile 16:21:19 #endmeeting