14:00:08 <elodilles> #startmeeting releaseteam
14:00:08 <opendevmeet> Meeting started Fri Mar 11 14:00:08 2022 UTC and is due to finish in 60 minutes.  The chair is elodilles. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:08 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:08 <opendevmeet> The meeting name has been set to 'releaseteam'
14:00:17 <hberaud> o/
14:00:19 <elodilles> Ping list: hberaud ttx armstrong damani
14:00:33 <elodilles> #link https://etherpad.opendev.org/p/yoga-relmgt-tracking
14:00:33 <armstrong> o/
14:01:21 <damani> hi
14:01:27 <elodilles> we are @ line 336
14:01:34 <elodilles> hello everyone \o/
14:02:14 <elodilles> let's start with the topics
14:02:24 <elodilles> #topic Review task completion
14:02:37 <elodilles> 1st task:
14:02:41 <elodilles> "Process any remaining library branching exception"
14:03:50 <elodilles> we had:
14:03:53 <elodilles> keystoneauth: https://review.opendev.org/c/openstack/releases/+/832334
14:04:05 <elodilles> kuryr: https://review.opendev.org/c/openstack/releases/+/832335
14:05:02 <elodilles> and these are still open
14:05:39 <elodilles> kuryr one was approved
14:05:55 <elodilles> so it just needs a 2nd core review :)
14:06:31 <hberaud> omw
14:06:40 <elodilles> hberaud: thanks! :)
14:07:44 <hberaud> done
14:07:50 <elodilles> \o/
14:08:29 <elodilles> also, we need to merge the keystoneauth i think, despite we don't have approval from the team
14:08:37 <hberaud> +1
14:08:53 <hberaud> we enough waited
14:08:58 <elodilles> yepp
14:09:12 <elodilles> OK, i see they are merging now, thanks
14:09:28 <elodilles> so let's go to the next task
14:09:48 <elodilles> "On the Monday, generate release requests for all deliverables that do not have a suitable candidate yet"
14:10:19 <elodilles> there were multiple subtasks, so let's go one by one
14:10:45 <elodilles> I found these devstack-plugins:     devstack-plugins: https://review.opendev.org/c/openstack/releases/+/832340
14:11:20 * hberaud look
14:12:50 <hberaud> LGTM
14:13:31 <elodilles> i've +W'd it :]
14:13:53 <hberaud> me too
14:13:55 <elodilles> next subtask:
14:13:55 <hberaud> :)
14:14:38 <elodilles> '[search for] cycle-with-intermediary deliverables that have not released yet'
14:14:54 <elodilles> only requirements, release-test (no need for release) and tempest plugins (will be proposed in R-2, see tasks there) are listed
14:15:29 <elodilles> which means nothing to do with this fortunately, everything seem to be ontrack
14:15:53 <hberaud> +1
14:16:12 <elodilles> ++
14:16:17 <elodilles> next subtask
14:16:18 <armstrong> +1
14:16:24 <elodilles> 'cycle-with-rc deliverables RC1 release'
14:16:42 <elodilles> https://review.opendev.org/q/topic:yoga-rc1-deadline
14:17:00 <elodilles> these were generated ^^^
14:17:18 <elodilles> and most of them were merged until Thursday,
14:17:35 <elodilles> and some needed force-merge today
14:17:52 <elodilles> the only remaining is cinder: https://review.opendev.org/c/openstack/releases/+/832367
14:17:56 <armstrong> but it seems all are already merged
14:18:14 <elodilles> except cinder :)
14:18:18 <armstrong> ok
14:18:40 <elodilles> the team signalled that they need some patch to merge
14:18:57 <opendevreview> Merged openstack/releases master: [kuryr] Create yoga branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/832335
14:19:28 <hberaud> unfortunatelly they didn't specified which patches they are waiting for
14:19:57 <elodilles> so i've listed cinder to next week's task 'Process any standing RC1 deadline exceptions'
14:20:10 <elodilles> hberaud: unfortunately not
14:20:17 <hberaud> I guess we can give them a chance until early next week
14:20:31 <hberaud> As this is considered as an exception
14:20:49 <elodilles> yepp, i have the feeling that they will answer some time today :)
14:21:09 <hberaud> ok
14:21:15 <hberaud> let's see what happen
14:21:24 <elodilles> hberaud: should we ask for RFE from cinder team?
14:22:22 <hberaud> cinder is a service and an RC deliverable so I don't think we need an RFE as they are not in global requirements
14:22:47 <elodilles> hberaud: oh, yes, that's true
14:23:27 <elodilles> anyway, the patch is added on our tracking page
14:23:28 <hberaud> the RFE accronym mean too many things :)
14:23:38 <elodilles> :]
14:23:57 <hberaud> ok
14:24:04 <opendevreview> Merged openstack/releases master: [keystone] Create yoga branch for client and non-client libs  https://review.opendev.org/c/openstack/releases/+/832334
14:24:58 <elodilles> so we did now more or less this part of the task: 'Discuss standing -1s to see if they should be granted an exception and wait until next week.' ;)
14:25:32 <elodilles> that was the list of our tasks for this week
14:25:50 <elodilles> if nothing to add here, then we can go to the next topic
14:25:56 <hberaud> Well I'm ok to wait however I'd sugguest to ping Brian to ensure that they are on the track too
14:26:48 <elodilles> hberaud: ack, i'll ping the team on IRC as well, and we will see
14:26:58 <hberaud> WFM
14:27:02 <elodilles> after the meeting
14:27:19 <hberaud> ok
14:27:20 <opendevreview> Merged openstack/releases master: Create Yoga branch for devstack plugins  https://review.opendev.org/c/openstack/releases/+/832340
14:27:36 <elodilles> #topic Assign R-2 week tasks
14:28:10 <elodilles> I've added my name to some of the tasks already, just as i see hberaud too :)
14:29:02 <elodilles> by the way, just a thing to mention: i'll be off on Monday and Tuesday,
14:29:23 <elodilles> though i might look at things for a bit,
14:29:31 <elodilles> but can't promise anything :)
14:29:45 <hberaud> enjoy your rest
14:30:00 <elodilles> will do, thx :)
14:32:47 <elodilles> tasks are taken, but feel free to add your name if someone wants to help with a task
14:32:59 <elodilles> next topic then
14:33:18 <elodilles> #topic PTG participation: team is signed up @ Friday 14:00 UTC, April 8th
14:33:27 <elodilles> well, this is mostly an announcement ^^^^
14:33:38 <hberaud> you skipped the email review?
14:33:52 <elodilles> hberaud: oh, you are right
14:33:57 <hberaud> np
14:34:20 <hberaud> ok for the PTG
14:34:26 <hberaud> I take note
14:34:33 <elodilles> anyway, since this is just an announcement: let me know if the timing is not working for any of you
14:34:40 <elodilles> hberaud: ++
14:34:45 <hberaud> ack
14:35:02 <elodilles> then let's do the review topic :)
14:35:13 <elodilles> #topic Review countdown email contents
14:35:24 <elodilles> #link https://etherpad.opendev.org/p/relmgmt-weekly-emails
14:35:29 <elodilles> please review ^^^
14:37:23 <hberaud> LGTM
14:37:58 <armstrong> looks like the same email of last week?
14:38:52 <elodilles> last week's mail was this: http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027537.html
14:39:19 <elodilles> but definitely there are some overlapping content :)
14:39:20 <armstrong> ok i see
14:39:40 <hberaud> agree
14:39:54 <hberaud> some part are a bit redundant
14:40:06 <elodilles> we are emphesizing things time to time :)
14:40:20 <hberaud> and repeat can't hurt
14:40:29 <elodilles> yepp :)
14:41:13 <elodilles> so I'll send this after the meeting. thanks for the reviews!
14:41:22 <hberaud> np
14:41:42 <elodilles> next topic then
14:41:50 <elodilles> #topic Open Discussion
14:42:24 <elodilles> well, maybe this should have been discussed with our 2nd task
14:42:40 <elodilles> iurygregory contacted me with a question:
14:42:51 <elodilles> "would be ok to release networking-baremetal again? (it was broken in tests so it affected building) https://review.opendev.org/c/openstack/networking-baremetal/+/832858 see https://storyboard.openstack.org/#!/story/2009898 "
14:43:13 <iurygregory> o/
14:43:14 <elodilles> so the networking-baremetal RC1 was released
14:43:19 <elodilles> o/
14:43:37 <hberaud> RC2 are made for that
14:43:46 <elodilles> but there is some issue with it
14:43:59 <elodilles> and yepp,
14:44:16 <elodilles> RC2 is the right approach
14:44:23 <elodilles> thanks hberaud for confirming
14:44:25 <hberaud> So yes I don't reasons to not release it again through a RC2
14:44:44 <hberaud> see*
14:45:05 <elodilles> according to the process the best is to aim an RC2 around 1 week later then RC1,
14:45:24 <elodilles> so that other fixes can be added as well if needed
14:45:25 <fungi> this is exactly the reason we allow an unlimited number of release candidates until the final rc deadline
14:45:32 <elodilles> (if i understand correctly)
14:45:48 <hberaud> WFM
14:45:49 <iurygregory> so we can just request 5.1.1 ?
14:45:55 <iurygregory> for networking-baremetal
14:46:09 <fungi> i'm not sure what the concern/harm is in having an rc2 sooner (and then an rc3 if needed)
14:47:03 <elodilles> oh, sorry, i was wrong
14:47:19 <elodilles> networking-baremetal is cycle-with-intermediary
14:47:22 <fungi> ahh
14:47:22 <elodilles> my bad :/
14:47:32 <hberaud> indeed I just see that
14:47:34 <elodilles> so it was a library release
14:47:44 <iurygregory> yeah
14:47:48 <hberaud> Well in this case we need a RFE
14:48:00 <hberaud> and a 5.1.1
14:48:07 <fungi> so this is essentially a critical bugfix release, which yeah will need a global requirements/upper constraints bump
14:48:42 <hberaud> iurygregory: as it is a lib does it will impact some ironic deliverables?
14:48:50 <hberaud> (other deliverables)
14:49:08 <elodilles> and maybe: is it a critical bug?
14:49:21 <hberaud> I mean does it will trigger some requirements bumps on ironic deliverables to move to 5.1.1?
14:49:29 * iurygregory checks
14:50:55 <iurygregory> we still haven't cut yoga for ironic/inspector/ipa
14:51:08 <hberaud> this change seems to only impact tests, isn't?  https://review.opendev.org/c/openstack/networking-baremetal/+/832858
14:51:24 <iurygregory> it causes problem when trying to build the package
14:51:33 <iurygregory> according to the story on the patch
14:51:41 <hberaud> ok
14:52:01 <hberaud> then I think we consider that as critical, fungi thoughts?
14:52:10 <hberaud> can*
14:52:14 <iurygregory> at least that's how I understood
14:52:30 <fungi> looking at the patch now
14:52:46 <iurygregory> I think 5.1.0 it also broke RDO builds if I'm not mistaken
14:52:54 <hberaud> IIUC zuul won't work
14:53:08 <iurygregory> also =)
14:53:21 <hberaud> So the package won't build
14:53:48 <hberaud> but I don't think it will impact your other deliverables
14:54:08 <fungi> the job and test being altered don't look related at all to package building
14:54:41 <fungi> oh, rdo wants to confirm it can run tests against the rpm they build!
14:55:08 <fungi> now i see what you mean by "package" (i was thinking you meant python packaging, i.e. our release process)
14:55:23 <iurygregory> yeah
14:55:28 <iurygregory> sorry
14:56:36 <fungi> i know distros normally carry patches in their packages, especially where testing them is concerned, so i guess it's a question of whether openstack release management and a requirements bump are warranted during the release freeze in order to save rdo from adding a patch
14:57:27 <hberaud> imho if this is only related to RDO I think it can wait
14:59:17 <elodilles> yes, it seems more like a downstream issue then
14:59:34 <hberaud> I don't have a strong opinion, I don't see rush to fix that and I think it can wait the final release.
15:00:09 <elodilles> so it can be fixed on stable branch after Yoga release some time, right?
15:00:52 <hberaud> yes this patch is already merged on master and on stable/yoga
15:01:11 <hberaud> we just have to release the 5.1.1 in a couple of weeks
15:01:30 <elodilles> i agree with this
15:02:28 <fungi> from rdo's perspective it's presumably just a backport from master to 5.1.0
15:02:39 <hberaud> Anyway I suppose that RDO will wait the final release to produce their Yoga series
15:03:13 <elodilles> iurygregory: do you agree as well?
15:03:25 <fungi> if it had been caught before the final lib release deadline/requirements freeze it would be less of a concern
15:03:49 <elodilles> yepp, indeed
15:04:00 <iurygregory> yeah
15:04:01 <fungi> but at this point it would need to be argued for a requirements freeze exception
15:04:10 <hberaud> at least yes
15:04:34 <iurygregory> I'm ok with waiting, just let me know how I should proceed =)
15:05:47 <elodilles> propose a release patch some time after Yoga official release :)
15:06:07 <elodilles> as I understand based on our discussion
15:06:13 <hberaud> yes
15:07:23 <elodilles> and we are overtime, so if nothing else topic left then we should end the meeting o:)
15:07:35 <hberaud> nothing on my end
15:07:42 <elodilles> though discussion can be continued afterwards as well
15:08:02 <armstrong> nothing from me
15:08:11 <elodilles> ok, thanks everyone for participating!  see you next week o/
15:08:17 <elodilles> #endmeeting