16:00:55 <smcginnis> #startmeeting releaseteam
16:00:56 <openstack> Meeting started Thu Apr 23 16:00:55 2020 UTC and is due to finish in 60 minutes.  The chair is smcginnis. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:57 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:01:00 <hberaud> o/
16:01:00 <openstack> The meeting name has been set to 'releaseteam'
16:01:01 <smcginnis> Ping list: ttx armstrong diablo_rojo, diablo_rojo_phon
16:01:10 <smcginnis> #link https://etherpad.opendev.org/p/ussuri-relmgt-tracking
16:01:20 <armstrong> o/
16:01:23 <hberaud> o/
16:01:30 <ttx> o/
16:01:36 <ttx> reporting for duty
16:01:44 <smcginnis> :)
16:01:55 <smcginnis> We are around line 604 for the meeting agenda.
16:02:07 <smcginnis> #topic Review week tasks completion
16:02:20 <smcginnis> I think we were able to get all branch creation through early.
16:02:23 <smcginnis> So that one was easy.
16:02:45 <smcginnis> #link https://review.opendev.org/721299 Canary test
16:02:49 <diablo_rojo> o/
16:02:51 <openstackgerrit> Luigi Toscano proposed openstack/releases master: Release sahara-plugin-vanilla for Ussuri  https://review.opendev.org/721457
16:02:59 <smcginnis> Got the release-test through early in the week, no issues.
16:03:45 <smcginnis> #link https://review.opendev.org/#/q/project:openstack/releases+branch:master+topic:ussuri-rc RC release patches
16:04:14 <smcginnis> #link https://review.opendev.org/#/q/project:openstack/releases+branch:master+topic:ussuri-c-a Cycle automatic patches
16:04:39 <smcginnis> #link https://review.opendev.org/#/q/project:openstack/releases+branch:master+topic:c-w-i-ussuri Cycle with intermediary patches that had not released yet
16:05:12 <smcginnis> That leaves the remaining tasks for the week for us all to quickly process those releases as soon as we get an ack on them.
16:05:31 <ttx> one question re: tempest plugins
16:05:32 <smcginnis> And sending the countdown email, which I will do tomorrow.
16:05:42 <fungi> btw, you probably no longer have to say "around line" since the new etherpad version seems to have fixed that longstanding line number misalignment bug
16:05:47 <ttx> a bunch were on a 0.x.0 scheme and you posted 1.0.0 releases
16:06:10 <smcginnis> fungi: Yes, it is much better. Now the issue is just sometimes my eyes. :)
16:06:15 <ttx> I'm not sure that is warranted tbh, especially since they have limited added functionality
16:06:16 <fungi> hah
16:06:28 <smcginnis> ttx: Yeah, that's true.
16:06:35 <ttx> 0.x+1.0 bumps also are considered major breaking
16:06:46 <smcginnis> I proposed the major bump based on the changes, but expected PTLs or liaisons to say whether that was appropriate or not.
16:07:02 <smcginnis> Since most of those had dropped py2 support.
16:07:29 <ttx> I would prefer not to declare they are now stable if they are not
16:07:29 <smcginnis> I also think a lot of teams don't think about those too much, so probably never consider if they should be considered a 1.0 yet or not.
16:07:42 <ttx> For those ).14.0 is fine by me
16:07:46 <ttx> 0.14.0 I mean
16:07:57 <smcginnis> Since they've now been around for a few releases, I think many are still in development and need more testing, but are also "complete" enough for a full major version number.
16:08:09 <ttx> it's not really meant to be consumed by users anyway
16:08:11 <smcginnis> The framework is now set, so the rest is a matter of expanding test coverage.
16:08:26 <ttx> if you think they are complete enough, I'm fine
16:08:38 <ttx> If they are empty shells, maybe not
16:08:59 <smcginnis> I'm fine either way. They are not really consumed by users (except maybe tempest test concerned ones), so the version number isn't as important to me as others.
16:09:19 <smcginnis> If the team just gave an ack with the version number, I think it's OK to just process them.
16:09:21 <ttx> $ cat tempest.sh
16:09:23 <ttx> exit 0
16:09:39 <smcginnis> But also fine if anyone wants to update the patches to just bump minor version.
16:09:56 <ttx> ok I'll do that on those where we had no PTL feedback yet
16:10:05 <smcginnis> Works for me. Thanks!
16:10:36 <smcginnis> #topic Assign next week tasks
16:10:57 <smcginnis> First thing is something for all of us - process any standing RC1 deadline exceptions.
16:11:10 <smcginnis> We have a few of those with -1 from teams trying to get a few more patches through.
16:11:20 <smcginnis> So looks likely that we will have a few that are delayed.
16:11:32 <ttx> actually, I'll keep 1.0.0... after all those PTLs +1ed it
16:11:52 <ttx> so ignore me
16:12:06 <smcginnis> Whatever you think is good for those. I honestly don't care with the tempest plugins. :)
16:12:22 <smcginnis> I will propose patches for any missing stable branches.
16:12:50 <smcginnis> Next is the patches for devstack.
16:12:54 <smcginnis> Any volunteers for that one?
16:13:05 <smcginnis> It's fairly straightforward, with some good examples referenced.
16:13:12 <hberaud> let's go
16:13:39 <smcginnis> hberaud: I've put your name next to that one.
16:13:46 <smcginnis> Small chance some devstack things have changed.
16:14:02 <smcginnis> If you find anything that needs to be updated, please propose any updates to the process doc.
16:14:11 <smcginnis> But not likely too much has changed with that.
16:14:23 <hberaud> let me ack
16:14:29 <hberaud> s/ack/
16:14:44 <smcginnis> devstack-gate being the only thing I'm not sure. That's been on its way out for awhile, but I don't think we've been able to drop it yet.
16:15:07 <smcginnis> I'm not sure if this is needed anymore either "Remind the I18n PTL to update the translation tools for the new stable series."
16:15:19 <smcginnis> ttx: Is I18n a sig now?
16:15:30 <ttx> almost
16:15:38 <hberaud> lol
16:15:47 <ttx> https://review.opendev.org/#/c/721605/
16:16:02 <smcginnis> Maybe if I mention ianychoi here, that will can be marked off. :)
16:16:35 <smcginnis> I will check in with prometheanfire on branching requirements next week.
16:17:01 <smcginnis> Next task, release notes links.
16:17:13 <smcginnis> That one is super easy. Just need to run a script and submit the results.
16:17:19 <smcginnis> Anyone want to take that one?
16:17:31 <hberaud> I'm volunteer too
16:17:40 <openstackgerrit> Pierre Riteau proposed openstack/releases master: Release blazar for Ussuri  https://review.opendev.org/721392
16:17:40 <smcginnis> I do run the script from time to time to pick up new ones as well.
16:17:58 <smcginnis> hberaud: Thanks again!
16:18:06 <hberaud> you are welcome
16:18:42 <smcginnis> And the last task, other than the countdown email, is really just a reminder to the team for how RCs should work.
16:19:00 <smcginnis> We should encourage teams to do an RC2 or RC3 if needed, but we don't want too many of them.
16:19:39 <smcginnis> So if anyone comes asking, let them know they should do another RC for things like translations and bugfixes, but they can wait a bit to try to get all updates so they don't keep doing a new RC every few days.
16:20:08 <smcginnis> Any other questions or comments about next week's tasks?
16:20:22 <ttx> nope
16:20:24 <smcginnis> Getting really close to the end now.
16:20:30 <ttx> \o/
16:20:31 <hberaud> nope
16:20:38 <smcginnis> #topic Release announcement link broken
16:20:51 <ttx> ~~~~~~~ <-- end of the Ussuri river
16:20:55 <smcginnis> This was pointed out yesterday from one of the release announcements.
16:20:57 <smcginnis> ttx: ;)
16:21:00 <smcginnis> #link http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014359.html
16:21:12 <smcginnis> It seems like this is something that we keep needing to fix.
16:21:23 <smcginnis> Not sure if there are conflicting issues here that cause this to keep happening.
16:21:37 <ttx> hmm, where is that name set
16:21:53 <smcginnis> But from what I remember from the last time, it's an issue with a difference between the tarball name and the package name related to _ and - being in the name.
16:22:01 <ttx> might be a shell (announce) vs. python (upload) thing
16:22:11 <smcginnis> I need to track that down, but I think it's in the script that generates the announce template.
16:22:31 <ttx> hmm, I could have a look at it if that helps
16:22:41 <ttx> (not today)
16:22:46 <smcginnis> ttx: That would be great. I haven't had time to even look into it.
16:23:04 <smcginnis> I have a feeling we just need to add better deduction of the package names.
16:23:07 <ttx> ok, sign me up
16:23:29 <smcginnis> Not sure if there is a good way to test that with all the variations we have, but hopefully fresh eyes will see something obvious,
16:23:54 <smcginnis> #topic Review countdown email
16:23:59 <smcginnis> #link https://etherpad.opendev.org/p/relmgmt-weekly-emails
16:24:16 <smcginnis> Looks like I have the right content in there this week.
16:24:20 <openstackgerrit> Luigi Toscano proposed openstack/releases master: Release sahara-tests for ussuri  https://review.opendev.org/721496
16:24:41 <ttx> lgtm
16:25:05 <ttx> just a quick fix
16:25:07 <smcginnis> Hah, was just about to fix that victoria mention. :)
16:25:08 <smcginnis> Thanks
16:25:32 <smcginnis> OK, I think that looks good then.
16:25:51 <smcginnis> And I didn't drop the PTG mention in the upcoming events.
16:26:08 <smcginnis> So I will send it out around the typical time tomorrow.
16:26:13 <smcginnis> #topic Open discussion
16:26:37 <diablo_rojo> PTG time?
16:26:48 <openstackgerrit> Merged openstack/releases master: Release cyborg-tempest-plugin for ussuri  https://review.opendev.org/721481
16:26:49 <openstackgerrit> Merged openstack/releases master: Release congress-tempest-plugin for ussuri  https://review.opendev.org/721480
16:26:57 <diablo_rojo> We are still waiting to pick times?
16:27:06 <smcginnis> diablo_rojo: We had discussed that we will wait for other teams to get their schedules figured out.
16:27:17 <smcginnis> Then we can just meet whenever we don't have a conflict.
16:27:29 <openstackgerrit> Luigi Toscano proposed openstack/releases master: Release sahara-tests for ussuri  https://review.opendev.org/721496
16:28:11 <diablo_rojo> Yeah I remember that, was just wondering if we were going to do it by x date and just wait till then
16:28:28 <openstackgerrit> Merged openstack/releases master: Release trove-tempest-plugin for ussuri  https://review.opendev.org/721501
16:28:30 <openstackgerrit> Merged openstack/releases master: Release mistral-tempest-plugin for ussuri  https://review.opendev.org/721490
16:28:45 <smcginnis> I'm fine waiting until then. Unless anyone needs to figure out their schedule earlier.
16:29:16 <smcginnis> Personally, it tends to work better for me to not try to plan too far ahead. That never seens to work out well. ;)
16:29:25 <ttx> ack
16:29:40 <ttx> It's easier fir us to pick a time once everyone else has
16:29:44 <ttx> for* even
16:31:24 <smcginnis> OK, anything else?
16:31:49 <smcginnis> Guess I should mention a couple common failures we've been seeing.
16:32:17 <smcginnis> We've been getting docs publishing failures due to a locking issue between concurrent jobs accessing the files.
16:32:31 <openstackgerrit> Niraj Tolia proposed openstack/reno master: Add cache support for release dates  https://review.opendev.org/721728
16:32:33 <smcginnis> Those can be ignored since docs just get updated by every merge.
16:32:55 <smcginnis> The other one has been on sending the announce email.
16:33:03 <smcginnis> We spoke earlier in channel about that one.
16:33:15 <ttx> saw recent the AFS sync fail ?
16:33:31 <smcginnis> We likely need to add some retry logic to our smtp sending code.
16:33:39 <smcginnis> ttx: Yep, that's the concurrency one.
16:34:37 <smcginnis> So just awareness for everyone.
16:34:37 <ttx> ok
16:34:45 <smcginnis> Nothing else from me.
16:34:58 <smcginnis> We can close early if no one else has anything for the meeting.
16:35:13 <smcginnis> Of course, can always bring up anything in the channel outside of the meeting too.
16:35:47 <smcginnis> OK, thanks everyone!
16:35:52 <smcginnis> #endmeeting