16:00:11 <smcginnis> #startmeeting releaseteam
16:00:12 <openstack> Meeting started Thu Aug 29 16:00:11 2019 UTC and is due to finish in 60 minutes.  The chair is smcginnis. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:13 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:15 <openstack> The meeting name has been set to 'releaseteam'
16:01:03 <smcginnis> #link https://etherpad.openstack.org/p/train-relmgt-tracking Agenda
16:01:13 <smcginnis> Ping ttx dhellmann diablo_rojo hberaud evrardjp armstrong tonyb
16:01:15 <ttx> ohai
16:01:18 <diablo_rojo> o/
16:01:43 <evrardjp> o/
16:02:39 <smcginnis> Thank you ttx for the agenda again.
16:02:53 <smcginnis> #topic Status update on recent release failures
16:03:02 <smcginnis> #link http://lists.openstack.org/pipermail/release-job-failures/2019-August/thread.html
16:03:05 <smcginnis> All the fails
16:03:09 <ttx> yeah so I motices a bunch
16:03:15 <ttx> damn I can't type anymore
16:03:23 <ttx> noticed a bunch of fails
16:03:37 <smcginnis> I *think* we discussed these in channel, but we can make sure.
16:03:43 <ttx> The propose-update-constraints fails I did not investigate since i think somebody else did
16:04:06 <ttx> They seem to be fixed, just unsure that we corrected the failed ones (or that they need to)
16:04:18 <ttx> So would welcome someone double-checking
16:04:18 <smcginnis> Those we decided were ok. One was manually proposed, the rest are getting picked up in the automatic updates.
16:04:24 <ttx> ok
16:04:33 <ttx> The tag-releases job fail I did investigate
16:04:43 <ttx> while creating ocata-eol tag for all TripleO projects, as a post-job after https://review.opendev.org/#/c/677478/ merged, failed to push ocata-eol tag to openstack/os-cloud-config
16:04:44 <evrardjp> aren't the triple O something to be expected?
16:04:53 <ttx> I think we can ignore them yes
16:05:14 <smcginnis> This is one that has come up in the past. A retired repo does not have a .gitreview file, so it will fail.
16:05:15 <ttx> except that ocata-eol tag is still missing from openstack/os-cloud-config
16:05:41 <ttx> ok, I'm fine with ignoring, not a big deal anyzay
16:05:43 <smcginnis> I think, but not certain, that this should be the last series that will be affected by that.
16:06:00 <smcginnis> It is retired and the current master README makes that very clear.
16:06:01 <ttx> same for publish-release-notes ones
16:06:10 <ttx> probably irrelevant
16:06:11 <evrardjp> ttx: maybe we should just notify the ptl to do the EOL tag him/her-self?
16:06:18 <fungi> well, also retired repos are usually set to read-only, so you can't push tags to them
16:06:25 <ttx> evrardjp: they can't
16:06:28 <evrardjp> It's still mwhahaha for now, right?
16:06:32 <smcginnis> evrardjp: They would have to change ACLs for that.
16:06:37 <clarkb> fungi: that may be broken though
16:06:51 <evrardjp> oh right I thought it was not mutually exclusive in the acl by default
16:06:52 <evrardjp> ok
16:06:55 <clarkb> fungi: jeepyb ignores projects with the retired acl config so doesn't push the acl update to RO them
16:06:57 <ttx> anyway, I think we can ignore it as noise
16:07:18 <ttx> from running an EOL process on dead repos
16:07:22 <fungi> clarkb: ahh, i guess we need to fix that when someone finds time, but i thought it got solved some months ago
16:07:40 * fungi would have to look back at jeepyb git history
16:07:42 <ttx> just wanted to make sure everyone was aware
16:08:09 <smcginnis> FWIW, we did add some clarifying text to the retirement process to make sure .gitreview was kept along with the README so we hopefully don't have this issue again.
16:08:09 <ttx> I have nothing more on that topic
16:08:23 <smcginnis> We could have fixed it for this repo, but it was considered not worth the effort.
16:08:31 <smcginnis> "We'll just remember this for next time" :D
16:08:38 <ttx> cary ove
16:08:40 <ttx> r
16:08:44 <smcginnis> #topic Final release period start
16:08:44 <ttx> r
16:08:56 <ttx> Hi! me again
16:09:12 <smcginnis> #link https://releases.openstack.org/reference/process.html#final-library-release-week-before-milestone-3
16:09:18 <ttx> So I did spend some time this morning planning the end of the cycle on the tracking doc
16:09:21 <ttx> and copying the tasks
16:09:30 <ttx> It should all be set and ready
16:09:35 <smcginnis> Thanks!
16:09:59 <ttx> Including reminders for things we should check in weekly emails
16:10:26 <ttx> One thing that would be cool is if you could add any availability issue
16:10:46 <smcginnis> Thanks for the reminder. I do have some travel coming up.
16:10:55 <ttx> so that the other ones are aware they will have to care for those tasks
16:12:03 <ttx> Then we need to assign next week tasks
16:12:32 <ttx> would be good if someone else did the library autoreleases this time
16:12:51 <ttx> It's a bit manual, but someone might get bored enough to build automation/tools
16:13:29 <smcginnis> We should really get that proposed at the beginning of the week too.
16:13:40 <smcginnis> Or even tomorrow or the weekend to make sure there is time by the actual deadline.
16:13:55 <smcginnis> I can take that unless someone else wants to grab it.
16:14:10 <ttx> I think Monday should be enough... Deadline is Thursday EOD
16:14:28 <ttx> I'll take the weekly post draft
16:15:00 <smcginnis> No other takers on proposing the releases?
16:15:01 <evrardjp> I cannot say 100% I will work on this, so I am preferring to let someone do it, but I will actively review, and help
16:15:23 <evrardjp> I just cannot commit yet
16:15:31 <smcginnis> OK, I will take that, but if someone finds the desire and time to do it before me, I will not be upset. ;)
16:15:36 <ttx> evrardjp: could you take the last task?
16:15:38 <evrardjp> ofc :)
16:15:55 <ttx> I'll let you add your name to it
16:16:03 <evrardjp> the ones with the examples?
16:16:09 <ttx> yes
16:16:36 <ttx> OK we seem to be good
16:16:47 <ttx> Note that starting now we have meetings every week and weekly emails
16:16:54 <evrardjp> that would be sad if I couldn't do one liners
16:16:58 <smcginnis> Crunch time.
16:17:26 <smcginnis> #topic Notify the Infrastructure team to generate an artifact signing key (but not replace the current one yet), and begin the attestation process.
16:17:29 <ttx> That is all I had on this topic. You can scroll down that doc and see what the future looks like now
16:17:40 <smcginnis> fungi: ^^ Notified?
16:17:43 <fungi> thanks smcginnis, i'm adding that to my to do list now!
16:17:49 <smcginnis> Thanks!
16:17:59 <smcginnis> #topic R-6 email content final review
16:18:06 <smcginnis> #link https://etherpad.openstack.org/p/relmgmt-weekly-emails
16:18:07 <ttx> I did a final pass on that one
16:18:12 <evrardjp> fungi: I would be happy to know how things are done, if you don't mind filling me in on the topic after the meeting or at another moment
16:18:16 <ttx> Also removed confusing double R mentions
16:18:32 <fungi> evrardjp: you bet, it's a thoroughly documented process
16:18:39 <smcginnis> ttx: Double R?
16:18:39 <ttx> The R-6 email is sent at the end of the R-7 week, but i use a date to point to that
16:19:09 <ttx> the "send by" in the etyherpad should make it a bit less confusing
16:19:23 <smcginnis> ++
16:19:32 <ttx> So the email to send is ready for you around line 350
16:19:37 <evrardjp> more readable indeed
16:19:44 <smcginnis> Just re-read through it and I think it looks good.
16:20:27 <evrardjp> agreed
16:20:49 <ttx> {o}
16:21:33 <smcginnis> #topic Open discussion
16:21:53 <smcginnis> So... PTL nominations are open.
16:21:56 <ttx> smcginnis: Are you running for U?
16:22:08 <smcginnis> Unless we have someone that wants to, I was going to just go again.
16:22:38 <ttx> ++
16:22:40 <evrardjp> thanks smcginnis!
16:22:48 <fungi> once more unto the breach!
16:23:04 <evrardjp> on another note:
16:23:06 <smcginnis> I'll wait a bit in case someone else steps forward, but I guess I should probably get that drafted.
16:24:59 <smcginnis> Anything else?
16:25:01 <evrardjp> so yeah my other note... hum... how can I say that
16:25:08 <evrardjp> I have a bad news: I won't be there to help you fine folks doing the final release (and the week before). I am a little sad, but family first.
16:25:30 <smcginnis> Don't feel bad about putting your family first.
16:26:02 <ttx> evrardjp: well, it's not as bad as you think. Peak activity is actually the two weeks just before
16:26:03 <evrardjp> I imagined joining you and having a party at my home blowing in the nice wooden whistle for the great pleasure of my neighbours
16:26:07 <evrardjp> but it's not gonna happen
16:26:14 <ttx> Last week we just drink
16:26:18 <smcginnis> :)
16:26:43 <evrardjp> ttx: that's reassuring, but makes me even sader
16:26:48 <evrardjp> even more sad*
16:27:06 <evrardjp> anyway
16:27:07 <smcginnis> Don't worry, we can find some other excuse to drink together to make up for it. ;)
16:27:11 <evrardjp> I will fill that in the etherpad
16:27:11 <fungi> yeah, release week is "push the button, and then cross your fingers and hope you don't need the infra team"
16:27:27 <ttx> smcginnis: btw I did push the "post-RC1 tasks" to the week after RC1 week since that is when we actually did those for all previous releases
16:27:29 <smcginnis> We should actually add that to the process doc ^
16:27:49 <smcginnis> ttx: OK, that makes sense.
16:27:53 <ttx> i don;t expect us having all our ducks^WRC1s in order before well past end of week anyway
16:28:04 <ttx> like always
16:28:12 <smcginnis> Yeah
16:28:18 <ttx> also spreads out load nicely
16:28:43 <smcginnis> Very true.
16:28:49 <ttx> but yeah, R-2 is actually the heaviest week, and *I* won't be around that week much
16:28:57 <ttx> so apologies for that :)
16:29:19 * smcginnis notices ttx has been planning vacations around busy weeks
16:29:20 <smcginnis> :P
16:29:32 <ttx> It's not vacation, it's OID Nordics
16:29:46 <evrardjp> that's a big event
16:29:48 <ttx> I know it looks a lot like vacation but my wife says it's not
16:29:50 <smcginnis> That should be a good one. Wish it was closer for me.
16:29:51 <diablo_rojo> ..I will also be there?
16:29:57 <ttx> diablo_rojo: I hope so
16:30:12 <smcginnis> OK, anything else we should discuss in-meeting?
16:30:20 <evrardjp> I wanted to go, but I decided to stay to help releases. ahem ahem
16:30:24 <ttx> diablo_rojo: you just are better than me at getting work done on the road
16:30:32 <evrardjp> smcginnis: nothing from me
16:30:40 <diablo_rojo> ttx, if you say so lol I do try.
16:30:40 <ttx> evrardjp: I'm not sure I buy that
16:30:45 <evrardjp> :D
16:30:52 <fungi> oh, also in case it didn't get mentioned visibly enough, the opendev sysadmins are performing a batch of project renames (including the kayobe deliverable namespace moves) on monday september 16
16:31:23 <ttx> yes I left a note on that releases review to put it on hold
16:31:33 <ttx> it's cycle-trailing so it should be fine
16:31:36 <smcginnis> fungi: Thanks for pointing that out here. Good to get that captured in meeting notes.
16:31:50 <fungi> #link http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-08-27-19.01.log.html#l-228
16:32:39 <smcginnis> OK, if nothing else, my coffee cup needs a refill. :)
16:32:49 <fungi> thanks smcginnis!!!
16:33:01 <smcginnis> Thanks everyone. And thanks again ttx for managing the agenda and getting the tasks planned out.
16:33:02 <evrardjp> thanks smcginnis
16:33:09 <smcginnis> #endmeeting