17:00:01 <hberaud> #startmeeting releaseteam
17:00:02 <openstack> Meeting started Thu Mar 18 17:00:01 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:03 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:05 <openstack> The meeting name has been set to 'releaseteam'
17:00:09 <hberaud> #link https://etherpad.opendev.org/p/wallaby-relmgt-tracking Agenda
17:00:12 <hberaud> Ping list: ttx armstrong elod damani
17:00:15 <armstrong> o/
17:00:16 <hberaud> We're way down on line 465 now.
17:00:21 <hberaud> Will just wait a couple minutes for folks.
17:00:24 <elod> o/
17:01:41 <ttx> o/
17:03:02 <hberaud> Ok let's go!
17:03:06 <hberaud> #topic Review task completion
17:04:42 <hberaud> Process any remaining client library freeze exception. AFAIK everything is done
17:04:42 <hberaud> neutron-lib and manilaclient have been merged
17:04:49 <hberaud> and all the patches related to client and non-client lib have been merged
17:05:19 <hberaud> https://review.opendev.org/q/topic:%22wallaby-no-change-libs%22+(status:open)
17:05:25 <hberaud> https://review.opendev.org/q/topic:%2522cwi-client-final%2522+(status:open)
17:05:49 <hberaud> prometheanfire: FYI ^
17:06:03 <ttx> re: client libs we probably want python-openstackclient released soon enough
17:06:25 <prometheanfire> yarp
17:06:46 <hberaud> someone proposed a patch for python-openstackclient => https://review.opendev.org/c/openstack/releases/+/781029
17:07:04 <hberaud> however it's just a branching
17:07:11 <prometheanfire> once reqs re-adds the cross-neutron check and the two master changes merge we can probably branch
17:07:19 <prometheanfire> unless osc needs a release
17:07:42 <hberaud> I left a comment concerning osc
17:07:50 <prometheanfire> cool
17:07:58 <hberaud> I think we need a new tag
17:08:05 <prometheanfire> ya
17:08:06 <hberaud> ttx: any opinion?
17:08:16 <hberaud> to allow a fixing window
17:08:21 <hberaud> for W
17:08:44 <hberaud> c.f https://review.opendev.org/c/openstack/releases/+/781029/1#message-c5a3625cfaab85c3593f611adf5c4b623ff1053f
17:10:20 <hberaud> Anyway this osc is on the next week tasks and I think that tomorrow I'll propose the patches accordingly
17:10:58 <hberaud> Ok next task
17:11:04 <hberaud> Propose stable/$series branch creation for all client and non-client libraries => done
17:11:31 <ttx> yeah I'd tag it again, soonish
17:11:44 <hberaud> a couple of patches remains opened https://review.opendev.org/q/topic:%22wallaby-stable-branches%22+(status:open%20OR%20status:merged)
17:11:49 <hberaud> ttx: ok
17:11:58 <hberaud> tomorrow I'll propose the tag
17:12:52 <hberaud> concerning the remaining patches I think that tomorrow evening we will force them
17:13:22 <elod> even if no approval from PTL/liaison?
17:13:27 <hberaud> yes
17:13:29 <elod> ok
17:13:41 <hberaud> they are client and non-client lib
17:13:41 <elod> then I'll review them tomorrow with that respect
17:14:22 <hberaud> so I don't think that we want wait more at this point
17:14:31 <elod> understood
17:14:44 <hberaud> next task
17:15:09 <hberaud> List cycle-with-intermediary deliverables that have not been refreshed in the last 2 months. Done thanks armstrong
17:15:18 <hberaud> http://lists.openstack.org/pipermail/openstack-discuss/2021-March/021089.html
17:15:34 <hberaud> I seen a couple of related responses and patches
17:16:07 <hberaud> I'll have another look tomorrow
17:17:01 <hberaud> next task
17:17:09 <hberaud> Tracking yarn fail => done
17:17:43 <hberaud> I submitted an email with some details => http://lists.openstack.org/pipermail/openstack-discuss/2021-March/021117.html
17:18:50 <hberaud> I think that ttx was right, the pulled version of nodejs provided by xenial seems meet the condition to face the issue
17:18:56 <hberaud> fungi: FYI ^
17:20:04 <hberaud> My main concern is why this job use xenial and not focal
17:21:21 <fungi> yeah, probably historical
17:21:40 <fungi> it may be that the old branches are pinned to xenial too. was this for master?
17:22:12 <hberaud> AFAIK independent
17:23:07 <hberaud> fungi: https://opendev.org/openstack/releases/src/branch/master/deliverables/_independent/monasca-grafana-datasource.yaml
17:23:53 <hberaud> I don't know what's behind independent I was thinking it was the same that with master
17:24:45 <hberaud> in other words that's not old branches
17:25:32 <elod> i'm not seeing yet the full picture, but the answer is maybe around here: https://zuul.opendev.org/t/openstack/build/cdffd2a26a0d4a5b8137edb392fa5971/log/zuul-info/inventory.yaml#30
17:26:34 <hberaud> Could be
17:26:40 <hberaud> ok let's continue to discuss this topic on the ML
17:26:46 <elod> which points to a nodejs4-publish-to-npm template with pinned node_version 4? >>> https://opendev.org/openstack/openstack-zuul-jobs/src/branch/master/zuul.d/project-templates.yaml#L1587-1606
17:27:11 <elod> hberaud: ack
17:27:33 <elod> I'll try to investigate a bit tomorrow if nothing happens
17:27:47 <hberaud> elod: do you mind to reply directly on the thread to keep things centralized there?
17:28:04 <elod> hberaud: sure
17:28:10 <hberaud> thanks elod
17:28:20 <hberaud> Ok next topic
17:28:24 <hberaud> #topic Assign R-3 tasks
17:28:43 <fungi> there's a nodejs8-publish-to-npm template in there too
17:29:30 <hberaud> ok maybe the solution is just to use it
17:30:06 <hberaud> I don't know update that
17:31:09 <hberaud> Ok let's go for next week taks
17:31:13 <hberaud> tasks
17:32:01 <hberaud> We mostly have to generate release requests
17:32:10 <hberaud> I already put my name
17:32:37 <hberaud> thanks armstrong for helping on that point
17:33:17 <armstrong> np
17:33:33 <hberaud> This is mostly one big batch of patches with few entry points
17:33:48 <hberaud> I'll generate them tomorrow
17:33:56 <hberaud> armstrong: are you available?
17:34:07 <armstrong> yes
17:34:08 <armstrong> I am
17:34:24 <hberaud> armstrong: we can proceed as usually
17:34:46 <armstrong> hberaud: usual time?
17:35:15 <hberaud> yes around 2pm UTC
17:35:25 <hberaud> that work for you?
17:35:28 <armstrong> yes
17:35:32 <hberaud> excellent
17:35:36 <hberaud> see you there :)
17:35:40 <hberaud> see you here :)
17:36:01 <armstrong> ok
17:36:27 <hberaud> Ok next topic
17:36:34 <hberaud> #topic Review countdown email contents
17:36:44 <hberaud> https://etherpad.opendev.org/p/relmgmt-weekly-emails
17:36:50 <ttx> looking
17:39:05 <ttx> I did change "master" -> "the master branch" which is slightly less offending
17:39:16 <hberaud> excellent
17:39:21 <hberaud> I'll update the template
17:39:37 <ttx> also tere were two consecutive "will"
17:39:47 <ttx> clear to send!
17:42:20 <hberaud> ok thanks
17:42:41 <hberaud> #topic tripleo-ipsec tags
17:42:48 <openstackgerrit> Hervé Beraud proposed openstack/releases master: improve docs  https://review.opendev.org/c/openstack/releases/+/781525
17:42:55 <hberaud> ttx: the fix ^
17:43:35 <ttx> +2
17:44:05 <hberaud> Just a quick summary concerning the tripleo-ipsec stuff
17:44:23 <hberaud> elod proposed the fix for rocky
17:44:50 <hberaud> if these fixes pass then I think that we can unlock https://review.opendev.org/c/openstack/releases/+/778925
17:45:22 <hberaud> ttx: do you mind to approve the both fixes?
17:45:43 <hberaud> https://review.opendev.org/c/openstack/releases/+/781122 https://review.opendev.org/c/openstack/releases/+/781123/
17:46:05 <elod> just wanted to paste https://review.opendev.org/q/topic:%22tripleo-ipsec-rocky-eol%22
17:46:08 <elod> :)
17:46:22 <hberaud> lol
17:46:47 <elod> but I was late again... :X
17:47:25 <hberaud> ok let's see what will happen :)
17:47:34 <hberaud> next topic
17:47:35 <ttx> done
17:47:39 <hberaud> awesome
17:47:53 <hberaud> #topic puppet Milestone 3
17:48:29 <hberaud> Please let me know what do you think about that https://review.opendev.org/c/openstack/releases/+/780559/2#message-98487dba55dc6901f953e01beead0bfcfa95cacb
17:49:05 <hberaud> the author proposed 2 patches at the same time, one for M2 and one for M3
17:49:21 <hberaud> First, I don't think we need M2 at this point
17:50:40 <hberaud> Also the author abandonned the M3 patch and he only keep the M2 patch, accordingly to the used SHA that mean that lot of changes have been skipped
17:51:01 <ttx> frankly for milestones I would let them have it the way they want
17:51:16 <hberaud> why not
17:51:21 <ttx> i.e. whatever works for you man
17:51:39 <ttx> You can point at the weirdness, but i would not have held it -- too much work for nothing
17:52:01 <hberaud> ok then I'll reopen the M3 patch
17:52:19 <ttx> now you will spend time on it while the net effect on the release is insignificant
17:52:26 <hberaud> and let's merge the M2 patch
17:52:37 <ttx> +1
17:52:48 <hberaud> thanks for feedback
17:53:01 <hberaud> ok
17:53:05 <hberaud> last topic
17:53:09 <hberaud> #topic Remaining Wallaby Cycle Highlight
17:53:49 <hberaud> diablo_rojo: any opinion about this patch? https://review.opendev.org/c/openstack/releases/+/780217
17:54:33 <diablo_rojo> hberaud, I am find to land it when the feature lands?
17:54:40 <hberaud> I asked for feedback but for now I didn't get response
17:55:00 <hberaud> yes
17:55:15 <hberaud> are you ok from your point of view
17:55:15 <elod> if I'm not mistaken the last patch is on the gate, but couldn't get confirmed by gibi,
17:55:24 <hberaud> that was my question
17:55:25 <elod> as he has EOD already
17:55:35 <hberaud> ok
17:55:41 <hberaud> good to know that
17:55:41 <pabelanger> o/ I was hoping to ask a question about the upper-constraint jobs openstack runs.  As an example if the requirement.txt file, does not contain the transient dependency, but the upper-constraint.txt does, will pip do the right thing and cap the transient deps? or should said transient dep also be included into the requirements.txt file
17:55:46 <diablo_rojo> Yeah totally. I am fine merging any of the cycle highlight stuff even if its retroactive.
17:56:09 <hberaud> diablo_rojo: ok thanks
17:56:13 <diablo_rojo> We mostly had the deadline because thats when the marketing machine starts their processing of what is there to make the rpress release etc.
17:56:17 <hberaud> let's wait for gibi
17:56:23 <diablo_rojo> hberaud, sounds good :)
17:56:27 <diablo_rojo> The more the merrier :)
17:56:41 <hberaud> ahah
17:56:43 <hberaud> #topic Open Floor
17:56:55 <hberaud> Anything else?
17:57:07 <hberaud> pabelanger: the floor is yours
17:57:22 <diablo_rojo> Nothing from me :)
17:57:53 <hberaud> pabelanger: I think that's more a question for #openstack-requirements
17:58:05 <clarkb> contraints files apply to all package installs being evaluated in that pip run
17:58:18 <pabelanger> thanks, also sorry I didn't look to see if a meeting was going on
17:58:18 <clarkb> doesn't matter if they are transient or not if constraints says to constrain it then pip is supposed to
17:58:29 <hberaud> pabelanger: np
17:58:48 <pabelanger> clarkb: ack, that is what I thought. I think I might be hitting issues with older version of pip (19.0.1)
17:58:57 <pabelanger> will move to requirements channel now
17:59:02 <hberaud> thanks
17:59:10 <hberaud> Anything else?
17:59:47 <elod> nothing from me :X
17:59:56 <hberaud> OK, thanks everyone. Let's wrap up. (just in time)
17:59:59 <armstrong> nothing from me
18:00:02 <hberaud> #endmeeting