17:00:13 <hberaud> #startmeeting releaseteam
17:00:15 <openstack> Meeting started Thu Mar 11 17:00:13 2021 UTC and is due to finish in 60 minutes.  The chair is hberaud. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:16 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:16 <hberaud> #link https://etherpad.opendev.org/p/wallaby-relmgt-tracking Agenda
17:00:18 <openstack> The meeting name has been set to 'releaseteam'
17:00:20 <hberaud> Ping list: ttx armstrong elod damani
17:00:32 <elod> o/
17:00:33 <armstrong> o/
17:01:03 <hberaud> We're way down on line 411 now.
17:01:25 <hberaud> Will just wait a couple minutes for folks.
17:01:31 <armstrong> ok
17:04:02 <hberaud> #topic Review task completion
17:04:13 <hberaud> Process any remaining library freeze exception => Done
17:04:22 <hberaud> Early in the week, email openstack-discuss list to remind PTLs that cycle-highlights are due this week => Done
17:04:43 <hberaud> Propose autoreleases for cycle-with-intermediary client libraries which had commits that have not been included in a release => Patches need validations
17:04:48 <hberaud> https://review.opendev.org/q/topic:%2522cwi-client-final%2522+(status:open)
17:04:53 <hberaud> https://review.opendev.org/q/topic:%22wallaby-no-change-libs%22+(status:open)
17:06:01 <hberaud> elod, ttx: feel free to validate those accepted by PTLs and that needs a final +2 ^
17:06:03 <ttx> o/
17:06:09 <hberaud> o/
17:06:19 <elod> hberaud: ack
17:07:06 <hberaud> concerning those we missed ( https://review.opendev.org/q/topic:%22wallaby-no-change-libs%22+(status:open) ) do we want to wait for PTLs/liaisons?
17:07:43 <hberaud> Since no significant changes have been merged yet maybe we could simply force them
17:07:52 <hberaud> Any opinion?
17:08:18 <ttx> I'd wait until Monday yes
17:08:47 <hberaud> elod: it would be nice to merge those who have been approved today
17:09:06 <hberaud> ttx: it's okay with me
17:09:09 <armstrong> @ttx +1
17:09:26 <hberaud> prometheanfire: FYI ^
17:09:39 <elod> hberaud: ack, too :)
17:09:43 <hberaud> we will wait until monday for a couple of patches
17:10:48 <hberaud> prometheanfire: I think that if requirements updates aren't in these lists who should refuse them
17:11:11 <hberaud> s/who/we
17:11:41 <hberaud> ok next task from last week
17:12:28 <hberaud> Evaluate any libraries that did not have any change merged over the cycle => partially done, @ttx: do you want to add something?
17:12:40 <hberaud> https://review.opendev.org/q/topic:%22move-to-independent%22+(status:open)
17:12:45 <ttx> no that's under control I think
17:13:05 <hberaud> I think we can approve the oslo part
17:13:16 <hberaud> any volunteer to push the final button?
17:14:29 <hberaud> Ok I'll approve oslo
17:15:57 <hberaud> I don't expect that the oslo part will receive new comments as it have been already discussed previously this cycle
17:17:03 <hberaud> Ok next task from last week
17:17:31 <hberaud> List cycle-with-intermediary deliverables that have not been released yet => Done thanks armstrong
17:17:44 <armstrong> np
17:17:51 <hberaud> http://lists.openstack.org/pipermail/openstack-discuss/2021-March/020989.html
17:18:53 <hberaud> AFAIK we didn't get any feedback apart from requirements team
17:20:11 * diablo_rojo joins late
17:20:45 <hberaud> o/
17:21:03 <prometheanfire> ack
17:21:30 <hberaud> next task was "On Friday, remind the requirements team to freeze changes to openstack/requirements" => already started
17:21:53 <hberaud> that point depends on the previous ones
17:22:07 <hberaud> ok next topic
17:22:13 <hberaud> #topic Assign R-4 tasks
17:22:39 <hberaud> thanks armstrong for taking this on
17:22:40 <hberaud> one
17:22:59 <hberaud> well, everything seems more or less already distribued
17:23:27 <hberaud> armstrong: yours is more or less similar to your previous one
17:23:41 <armstrong> ok
17:24:08 <hberaud> Anything else to add for next week tasks?
17:25:04 <hberaud> Ok move on
17:25:20 <hberaud> #topic Review countdown email contents
17:25:33 <hberaud> #link https://etherpad.opendev.org/p/relmgmt-weekly-emails
17:28:09 <diablo_rojo> Looks all correct to me.
17:28:23 <hberaud> \o/
17:28:42 <diablo_rojo> I am only one set of eyes though :)
17:28:51 <diablo_rojo> Hopefully others can check it too.
17:28:52 <hberaud> rotfl
17:29:36 <ttx> +1
17:29:46 <diablo_rojo> I guess, as a one off we could add one final call for cycle highlights
17:29:51 <diablo_rojo> but I can do that in a separate email
17:29:58 <diablo_rojo> in hopes that more people actually see it lol
17:30:10 <hberaud> Can't hurt
17:30:10 <diablo_rojo> so, coming full circle, lol, it looks good to me.
17:30:19 <hberaud> ok thanks
17:30:28 <armstrong> LGTM
17:30:42 <diablo_rojo> Thank you hberaud :) And congrats on being our fearless leader for another cycle.
17:31:22 <hberaud> My pleasure! This is a fearless team so it's not complicated for me
17:31:55 <hberaud> Ok move on
17:31:59 <hberaud> #topic Releasing requirements - Tagless project
17:32:04 <hberaud> #link https://review.opendev.org/c/openstack/releases/+/779832
17:32:17 <hberaud> Just a minor heads up about this patch
17:33:18 <hberaud> As said in my latest comment I think we need to hold this one until our batches of patches are fully merged.
17:33:25 <hberaud> Any opinion?
17:33:41 <ttx> I'm wondering why we need to release this
17:33:46 <ttx> digging in
17:34:09 <hberaud> Also reqs is tagless so I don't think we need a version
17:34:22 <hberaud> I think we only need to cut the branch that's all
17:34:24 <ttx> right
17:34:34 <ttx> you just need a location
17:34:52 <hberaud> Already discussed about this with prometheanfire (FYI ^)
17:34:53 <fungi> yes, requirements branches but it doesn't release
17:35:09 <ttx> ok
17:35:21 <ttx> https://opendev.org/openstack/releases/src/branch/master/deliverables/victoria/requirements.yaml
17:35:21 <hberaud> Thanks for your confirmation
17:35:34 <prometheanfire> ya, once we freeze and get those last client releases into reqs we can branch
17:35:35 <ttx> then yes it should match req freeze
17:35:38 <hberaud> yeah and ussuri did the same
17:35:55 <hberaud> thanks prometheanfire
17:36:24 <ttx> last time we waited until Oct 4
17:36:43 <ttx> that's R-2
17:36:44 <openstackgerrit> Michael Johnson proposed openstack/releases master: Release Octavia 6.2.0 for stable/ussuri  https://review.opendev.org/c/openstack/releases/+/779503
17:36:58 <hberaud> yeah final RC
17:37:05 <hberaud> that's not too late?
17:37:26 <prometheanfire> there are some projects that are used as libs (horizon and neutron mainly), not sure if we need to wait for something there
17:37:38 <ttx> It's in the process
17:37:58 <hberaud> however it's just one more weeks
17:38:00 <hberaud> ok sold
17:38:02 <ttx> Pretty sure we should wait until R-2 to make sure we have all the exceptions in
17:38:12 <hberaud> Sold
17:38:13 <ttx> even if in theory it should not move
17:38:25 <hberaud> make sense
17:38:38 <hberaud> prometheanfire: WFY?
17:40:03 <prometheanfire> WFY?
17:40:25 <hberaud> that works for you? (freezing on R-2)
17:41:00 <prometheanfire> yes
17:41:10 <hberaud> I just left a related comment directly on the patch
17:41:17 <fungi> the way zuul jobs integrate branches of required projects, if no matching branch name exists master is used, so that means projects should be able to branch ahead of requirements
17:41:18 <hberaud> ok cool
17:41:51 <fungi> but requirements will still have to remain frozen until it branches
17:42:08 <hberaud> I see
17:42:14 <hberaud> thanks for details
17:42:30 <prometheanfire> yep, last time it was just a couple of weeks, 1-2, I'm trying to reduce the time
17:43:04 <hberaud> Maybe we could discuss this point on PTG?
17:43:20 <hberaud> (reducing the time)
17:44:39 <hberaud> OK, we can discuss this point after the meeting.
17:44:42 <hberaud> #topic Governance oversight - Freshly added projects not present in release
17:44:42 <prometheanfire> ya
17:45:11 <ttx> must be very fresh
17:45:19 <hberaud> I made another round of vigilance
17:45:25 <ttx> werent around at m-2 for sure
17:45:41 <hberaud> ok so I think we should ignore them
17:45:53 <ttx> which is theoretically when we freeze (so that we do not have to do a last round of vigilance :) )
17:45:53 <hberaud> I prefered to ask first
17:46:10 <hberaud> ok :)
17:46:32 <hberaud> next topic
17:46:39 <hberaud> #topic Tag and create missing ussuri branch os-refresh-config
17:47:05 <hberaud> ttx and myself agreed about https://review.opendev.org/c/openstack/releases/+/776636
17:47:32 <hberaud> however I wanted to give a chance to react before pushing the buttons
17:47:51 <ttx> yeah I don;t care enough about the issue to spend more time on it
17:48:05 <hberaud> elod: FYI ^
17:48:11 <ttx> both work
17:48:33 <ttx> (not doing it and doing it) so let's not spend too much time on it
17:48:33 <hberaud> Ok then I just +2'd
17:48:47 <elod> hberaud: I don't have hard feelings either, looks OK :)
17:48:56 <hberaud> ok thanks
17:49:03 <hberaud> feel free to close the debate
17:49:19 <hberaud> #topic OpenstackSDK transition to client-library?
17:49:50 <hberaud> so yoctozepto asked for a FFE on openstackSDK
17:49:57 <hberaud> http://lists.openstack.org/pipermail/openstack-discuss/2021-March/021004.html
17:50:06 <hberaud> everybody approved
17:50:09 <ttx> I think this is not urgent. That affects where the library appears on release page. And when the deadline is
17:50:20 <ttx> (the transition to client-lib)
17:50:31 <hberaud> ok
17:50:48 <ttx> So we can keep that thread open and push the patch if needed
17:50:59 <ttx> the urgent thing is the FFE
17:51:13 <hberaud> I see, that's point is done
17:51:39 <hberaud> Ok move on
17:51:43 <hberaud> #topic Feature branch for Helm
17:51:46 <ttx> Personally I would keep it the same and consider moving it for next cycle
17:52:07 <hberaud> #link https://review.opendev.org/c/openstack/releases/+/779583
17:52:10 <hberaud> +1
17:52:30 <ttx> So this one... basically helm is not using release management but wants a feature branch created
17:52:40 <hberaud> yes
17:52:44 <ttx> I don;t think they should create a deliverable file for that
17:52:50 <ttx> We can create the branch manually
17:53:11 <hberaud> AFAIK normally they have credential to create branches
17:53:18 <hberaud> no?
17:53:25 <ttx> checking
17:53:51 <hberaud> I think it's depends on if they are a SIG or not
17:54:08 <hberaud> I'm not sure on this point
17:54:50 <ttx> hmm newest gerrit does not display ACLs anymore
17:55:02 <hberaud> fungi: any idea? ^
17:55:03 <ttx> checking config files
17:55:06 <fungi> they've already worked that out with the tact sig/opendev
17:55:25 <ttx> ah then just abandon
17:55:28 <fungi> we merged a change yesterday or today to allow them to create branches manually themselves
17:55:35 <ttx> https://review.opendev.org/admin/repos/openstack/openstack-helm,access is a bit dry
17:56:01 <hberaud> ok so let's just abandon the patch
17:56:04 <ttx> fungi: if you have a ref we can close https://review.opendev.org/c/openstack/releases/+/779583    referencing it
17:56:04 <fungi> gerrit hides acl entries from you if you're not authorized to do those things described by the acl
17:56:48 <ttx> fungi: even on repos I have large rights on it looks very dry. But off topic
17:56:48 <hberaud> ah I missed that it was already abandonned
17:57:19 <ttx> ah ENOTAPROBLEM -- next topic!
17:57:24 <hberaud> Ok next topic
17:57:28 <fungi> #link https://review.opendev.org/779872 Add create ref acl for osh release groups
17:57:28 <hberaud> #topic Release errors
17:57:45 <hberaud> Tripleo-ipsec tagging issue
17:57:52 <ttx> I have not caught up on that thread
17:58:05 <ttx> checking now
17:58:40 <fungi> that's the one where it looks like their .gitreview file may not have ever been updated to the new review.opendev.org hostname, and we may not be preinstalling a known_hosts entry for the old name
17:58:53 <fungi> specifically on the stable/rocky branch they'
17:58:56 <fungi> re trying to eol
17:59:17 <ttx> ok let's do (2) as suggested
17:59:27 <hberaud> +1
17:59:29 <ttx> next!
17:59:32 <elod> +1
17:59:35 <ttx> we can still make it
17:59:40 <hberaud> yarn fail http://lists.openstack.org/pipermail/openstack-discuss/2021-March/021002.html
17:59:42 <elod> :D
17:59:47 <ttx> 15 seconds left
17:59:57 <hberaud> I think we need a js expert here
18:00:00 <ttx> wtf yarn!
18:00:14 <hberaud> surely a package manager
18:00:29 <ttx> yeah it's athe NPM upload thing iirc
18:00:37 <ttx> let's wait for someone to chime in
18:00:50 <hberaud> I propose to continue this topic directly on the ML
18:00:54 <fungi> does that job fail consistently for all projects using it, or only that repo?
18:01:00 <hberaud> I'll add a note for next weel
18:01:03 <hberaud> week
18:01:05 <fungi> but yeah, ml makes more sense
18:01:39 <hberaud> ok next point
18:01:49 <hberaud> #topic PTG reminder
18:01:56 <hberaud> Don't forget to vote
18:01:58 <ttx> fungi:  last time it worked was in 2017
18:02:07 <ttx> last time it ran was in 2017 too.
18:02:08 <fungi> wow
18:02:08 <hberaud> #link https://doodle.com/poll/8d8n2picqnhchhsv
18:02:14 <ttx> https://zuul.opendev.org/t/openstack/builds?job_name=release-openstack-javascript&project=openstack/monasca-grafana-datasource
18:02:18 <ttx> ah hm
18:02:27 <ttx> too many filters
18:02:45 <hberaud> #link https://etherpad.opendev.org/p/xena-ptg-os-relmgt
18:02:55 <hberaud> Feel free to add topics to our etherpad
18:03:05 <ttx> it actually ran successfully last time, but that was 18months ago
18:03:25 <fungi> 2019-09-26 yeah
18:03:27 <hberaud> #topic Quick Open Discussion
18:03:31 <ttx> It's independent so not really release-process-critical
18:03:40 <openstackgerrit> Merged openstack/releases master: Tag and create missing ussuri branch os-refresh-config  https://review.opendev.org/c/openstack/releases/+/776636
18:03:49 <ttx> hberaud: thanks!
18:03:54 <hberaud> Anything else?
18:04:24 <hberaud> Sorry we overflowed a little
18:04:33 <ttx> np
18:04:39 <ttx> it's feature freeze after all
18:04:43 <hberaud> :)
18:04:47 <ttx> If we do not overflow today, when do we
18:04:47 <hberaud> champagne
18:04:52 <hberaud> +20 minutes
18:05:10 <hberaud> (free)
18:05:42 <ttx> https://stackoverflow.com/questions/64414716/unexpected-token-in-yarn-installation
18:05:55 <ttx> "The error is caused by the old version of nodejs (usually lower than v6)."
18:06:14 <ttx> yay backward compatibility
18:06:18 <hberaud> https://governance.openstack.org/tc/reference/runtimes/wallaby.html#node-js-runtime-for-wallaby
18:06:41 <hberaud> We use nodejs 10
18:07:31 <ttx> not sure that's what is installed on the host tho
18:07:35 <hberaud> hm wait which branch it was?
18:07:57 <ttx> independent so master
18:08:02 <hberaud> ok
18:08:29 <hberaud> So I suppose it rely on the series supported runtimes
18:08:46 <ttx> I bet system-installed yarn is older than nodejs10
18:09:00 <hberaud> could be
18:09:09 <ttx> but then I'm just speaking weird words
18:09:21 <ttx> yarn node node yarn
18:09:40 <hberaud> :)
18:09:41 <ttx> So let's wait for ML discussion with people who actually grok js
18:09:46 <hberaud> +1
18:09:55 <hberaud> Anything else?
18:10:02 <ttx> maybe push it back to next week meet agenda so that it does not fall between the cracks
18:10:14 <hberaud> already done
18:10:21 <ttx> my man!
18:10:30 <hberaud> lol
18:11:11 <hberaud> OK, thanks everyone. Let's wrap up!
18:11:20 <hberaud> #endmeeting