Thursday, 2021-01-14

*** tosky has quit IRC00:36
*** armax has quit IRC01:12
*** armax has joined #openstack-release01:13
*** armstrong has quit IRC01:19
*** armax has quit IRC02:25
*** armax has joined #openstack-release02:53
*** armax has quit IRC02:54
*** brinzhang0 has joined #openstack-release03:27
*** brinzhang0 has quit IRC03:29
*** brinzhang0 has joined #openstack-release03:29
*** brinzhang_ has quit IRC03:30
*** brinzhang0 has quit IRC03:30
*** brinzhang0 has joined #openstack-release03:31
*** ricolin_ has joined #openstack-release04:13
*** whoami-rajat__ has joined #openstack-release04:22
*** ricolin_ has quit IRC04:24
*** amotoki has quit IRC04:44
*** amotoki has joined #openstack-release04:44
*** ykarel has joined #openstack-release05:22
*** evrardjp has quit IRC05:33
*** evrardjp has joined #openstack-release05:35
*** ykarel has quit IRC05:39
*** ykarel has joined #openstack-release05:41
*** ykarel_ has joined #openstack-release05:54
*** ykarel has quit IRC05:57
*** ykarel__ has joined #openstack-release06:05
*** ykarel__ is now known as ykarel06:07
*** ykarel_ has quit IRC06:08
*** ricolin has quit IRC06:17
*** brinzhang_ has joined #openstack-release06:25
*** brinzhang0 has quit IRC06:28
openstackgerritHervé Beraud proposed openstack/releases master: Release Oslo's projects for Wallaby 2020-01-14
hberaudttx, smcginnis: o/ When you'll have minute, please can you validate this one, deadline is today? Thanks =>
*** ricolin has joined #openstack-release07:39
*** rpittau|afk is now known as rpittau07:47
*** e0ne has joined #openstack-release07:56
*** slaweq has joined #openstack-release08:03
openstackgerritHervé Beraud proposed openstack/releases master: Remove useless email section
*** brinzhang0 has joined #openstack-release08:45
*** brinzhang_ has quit IRC08:48
*** tosky has joined #openstack-release08:49
*** slaweq has quit IRC08:55
*** slaweq has joined #openstack-release09:00
openstackgerritRajat Dhasmana proposed openstack/releases master: Release cinderlib 3.0.0
*** ykarel_ has joined #openstack-release09:13
*** ykarel has quit IRC09:16
*** e0ne has quit IRC09:24
*** ykarel_ is now known as ykarel10:06
openstackgerritMerged openstack/releases master: Release victoria tripleo-ipsec os-collect-config os-refresh-config
openstackgerritMerged openstack/releases master: Bump version for the start of Puppet OpenStack Wallaby
openstackgerritMerged openstack/releases master: Website: Add link to the git repository
hberaudttx: You didn't leave any comments, that's normal?
hberaudno wait10:21
hberaudyou left 12 comments, I need better glasses10:21
hberaudttx: ignore my question10:21
ttxI just added the -1 to make my 12 comments more visible :)10:22
hberaudI missed all of them previously so it was useful10:24
*** dtantsur|afk is now known as dtantsur10:56
*** brinzhang has joined #openstack-release10:57
*** brinzhang has quit IRC10:58
*** brinzhang has joined #openstack-release10:58
*** brinzhang0 has quit IRC10:59
openstackgerritHervé Beraud proposed openstack/releases master: Add doc related to validation status (red, orange, green)
*** brinzhang has quit IRC11:25
*** brinzhang has joined #openstack-release11:25
*** brinzhang_ has joined #openstack-release11:26
*** brinzhang_ has quit IRC11:28
*** brinzhang_ has joined #openstack-release11:29
*** brinzhang has quit IRC11:30
*** e0ne has joined #openstack-release11:32
*** rakhmerov has joined #openstack-release11:34
*** brinzhang0 has joined #openstack-release12:03
*** brinzhang_ has quit IRC12:05
openstackgerritzhongshengping proposed openstack/releases master: Puppet OpenStack wallaby Milestone 1
ykarelhberaud, seeing missing tarballs again12:57
ykarelfor recent released
ykarelos-refresh-config, tripleo-ipsec, os-collect-config12:57
hberaudI didn't noticed release-failures, @fungi FYI ^12:58
ykareljobs passed but tarballs not in;O=D12:58
hberaudykarel: maybe it could be something similar =>
ykarelyes possible13:00
hberaudykarel: it could explain why we didn't get errors here too13:01
hberaud(because no error happened on our side)13:01
hberaudykarel: could be worth to ask on #openstack-infra13:02
ykarelyes i think13:03
hberaudSo this is due to another AFS issue13:09
hberaudttx, smcginnis: FYI ^13:09
hberaudc.f the #openstack-infra discussion13:10
*** e0ne has quit IRC13:12
*** brinzhang0 has quit IRC13:13
*** brinzhang0 has joined #openstack-release13:14
*** sboyron has joined #openstack-release13:26
openstackgerritMerged openstack/releases master: Release cinderlib 3.0.0
*** ykarel has quit IRC14:02
*** dave-mccowan has joined #openstack-release14:20
fungihberaud: we're behind on updating the public replica volume for the tarballs site, it's expected. the jobs haven't failed14:42
fungithere was a cinder host outage in rackspace which took down one of the devices which make up the data store for our afs02.dfw server so lots of very large volumes (including package mirrors) are having to be re-replicated from scratch and it's taking a while14:43
hberaudfungi: ack, thanks for the heads-up, frickler made me notice that too on #openstack-infra14:44
*** damani has quit IRC14:45
*** damani has joined #openstack-release14:47
*** ykarel has joined #openstack-release15:02
*** armax has joined #openstack-release15:14
*** sboyron has quit IRC15:31
*** armstrong_ has joined #openstack-release15:52
*** ykarel is now known as ykarel|away16:24
*** ykarel|away has quit IRC16:46
hberaud#startmeeting releaseteam17:00
openstackMeeting started Thu Jan 14 17:00:11 2021 UTC and is due to finish in 60 minutes.  The chair is hberaud. Information about MeetBot at
hberaud#link Agenda17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: releaseteam)"17:00
openstackThe meeting name has been set to 'releaseteam'17:00
hberaudPing list: ttx armstrong elod17:00
hberaudWe're way down on line 218 now.17:00
hberaudWill just wait a couple minutes for folks.17:00
hberaudOk let's go!17:04
hberaud#topic Review task completion17:04
*** openstack changes topic to "Review task completion (Meeting topic: releaseteam)"17:04
hberaudVictoria Cycle-Trailing Release Deadline => done17:04
*** diablo_rojo has joined #openstack-release17:04
hberaudAnd I think we can move directly to the next topic as it will speak about the membership freeze17:05
hberaud#topic Discuss findings of governance consistency checks above and resulting necessary actions17:05
*** openstack changes topic to "Discuss findings of governance consistency checks above and resulting necessary actions (Meeting topic: releaseteam)"17:05
hberaudttx, armstrong_ : the floor is yours17:05
ttxSo the goal of this is to make sure we are aligned between the releases and governance repos17:06
ttxAnd, as always, we are not17:06
ttxFirst, things that are in governance, but not in releases deliverable files17:06
ttxkarbor, karbor-dashboard, python-karborclient: newly-abandoned project. Will be fixed once merges17:06
ttxansible-role-atos-hsm, ansible-role-thales-hsm: New barbican deliverables, we should probably reach out to barbican team ask if we should plan to release for Wallaby17:07
hberaudany takers?17:07
ttxand if yes, craete deliverable files for those17:07
hberaudI can ping them17:07
ttxetcd3gw: New oslo deliverable, see with oslo team if we should plan to release for Wallaby. or make it _independent17:07
hberaudI think we can move it to independent17:08
hberaudbut before I'll bring that to the next oslo meeting17:08
bnemecIt was previously being released independently, so that makes sense.17:08
hberaudjust to confirm17:08
ttxNow onto more problematic ones17:08
hberaudbnemec: thanks for the heads up17:08
ttxbarbican-ui: (Added Oct 2019) -- never released yet, was not ready yet for ussuri and victoria. maybe we should abandon this instead of waiting?17:08
ttxit's been basically two cycles tat we have waited for it to be in releasable shape17:09
ttxhberaud: maybe you can ask about it while you ping barbican folks?17:09
hberaudI don't see reason to continue more further if nothing should be released anymore17:09
ttxIt was never released17:09
hberaudIt was the same scenario with few tripleo repo17:09
ttxso unless they are still making progress we might want to deprecate it17:10
ttxSame question for the next one:17:10
ttxopenstack-tempest-skiplist:  (Added Mar 20, 2020) never released yet, was not ready yet for ussuri and victoria. maybe we should abandon this instead of waiting? we should ask gmann's opinion17:10
ttxor maybe it's not meant to be released, idk17:11
ttxThird in this "not eady yet for a long time" category:17:11
ttxjs-openstack-lib: (Added January 9, 2020) -- never released yet, was not ready for ussuri or victoria. maybe we should abandon this instead of waiting. Ask OpenStackSDK17:11
hberaudI'll ping all these teams to clarify the situation17:11
ttxFinally: monasca-ceilometer, monasca-log-api: Released in train but not released in ussuri nor victoria. Should be deprecated in governance? Ask Monsaca17:11
hberaudsame thing17:12
ttxThen we have a bunch that are in deliverable files but no longer in project teams17:12
ttxenderspec, rpm-packaging, pymod2pkg: _independent deliverables from RPM Packaging team. Should be marked release-model: abandoned ? to be discussed as team policy17:12
ttxSo they used to be a project team, now a SIG17:12
ttxWe could make them "abandoned" but that would not be technically correct17:13
hberaudconcerning the rpm-packaging stuff, I'm a core team member there so I'll bring that in the next meeting17:13
ttxwe have no good answer for that scenario17:13
ttxIn the past we did remove the files completely, so that they would not show as "abandoned"17:13
hberaudYes it could be useful to clarify the situation with the TC about this scenario17:13
ttxNot sure that should involve the TC... It's about how we want those to show up in the releases website17:14
hberaudMaybe we should update a bit the SIG model to match this case17:14
hberaudah I see17:14
ttxNewer releases will not appear in the site, so my preference is to remove them completely so that we do not list an old release17:14
gmannttx: hberaud openstack-tempest-skiplist is under TripleO governance, may be we can ask marios or Chandan :
hberaudSo lemme discuss about with the team member, but the file removing seems a good option17:15
ttxand also so that they  do not appear as "abandoned"17:15
ttxthat is what we did for other SIG transitions.17:15
hberaudyes it could be misleading17:15
ttxbasically make it look like it was produced by a SIG all the time. It's OK for _independenmt deliverables17:16
ttxIf they were series deliverables we would keep them arounmd17:16
hberaudI see17:16
ttxNow that I think of it, it's the only good answer17:16
ttxand I remember that's how we handled the case last time it popped up17:17
ttxso.. maybe a non-issue. I'll file the file removals17:17
hberaudAck, thanks17:17
ttxok done17:17
ttxI'll add those tasks on next week17:17
hberaudThanks, I already added few of them17:18
hberaud#topic Discussing Victoria Cycle-Trailing Release Deadline17:19
*** openstack changes topic to "Discussing Victoria Cycle-Trailing Release Deadline (Meeting topic: releaseteam)"17:19
hberaudNothing more to add17:19
hberaudI forgot to remove that section17:19
hberaudSo we can move on17:19
hberaud#topic Encouraging projects to apply for tag 'assert:supports-api-interoperability'17:20
*** openstack changes topic to "Encouraging projects to apply for tag 'assert:supports-api-interoperability' (Meeting topic: releaseteam)"17:20
hberaudYou surely gmann's ML thread
hberaudI've a couple of thinking/questions related to that17:20
hberaudOnly Nova seems to support it for now and they start each new series with a new major version and that doesn't reflect this tag as a major version could mean that the backward compat is broken17:21
hberaudDo we need/want to clarify this point on our side?17:21
hberaudDo we should suggest a governance updates to reflect the semver part? This tag seems to have been introduced long time ago and AFAIK nobody complained about the semver part17:21
hberaudSo to summarize do we want/need to raise our banner in this thread?17:22
gmannhberaud: this tag is for API versioning not the service versioning, we can see both are different.17:22
ttxnot sure there is anything we should do...17:22
hberaudyes but as semver reflect this too maybe we have some grey area17:22
gmannin API versioning (this tag), we assert that all API changes happening should be under some version so that they can be discovered.17:23
gmannand versioning for API is quite open like it can be semver way or microversion way or anything else, as long as they are discoverable it is good17:24
hberaudAs nobody complained previously I think we can continue like that17:24
hberaudThanks for details17:24
hberaudfair enough17:25
hberaud#topic Tempest stein-last17:25
*** openstack changes topic to "Tempest stein-last (Meeting topic: releaseteam)"17:25
hberaudSo 1) gmann documented the "-last" tags, 2) we proposed a patch to update our machinery accordingly 3) all patches have been updated accordingly to 1 and 217:26
gmannon 1st part,  I just updated the project-team-guide patch with correct link, if you can check it again
hberaudgmann: ack17:27
gmannand ttx ^^17:27
hberaudAs 2 depends-on 1 I think it is safe to start to approve 317:27
hberaud*safe enough17:27
* hberaud look at
hberaudOk I think we can move on17:29
hberaud#topic The pip's resolver issue17:30
*** openstack changes topic to "The pip's resolver issue (Meeting topic: releaseteam)"17:30
hberaudJust a friendly reminder about the doc/pip issue, we are still in "orange" status17:30
ttxI would keep it that way until we can get the exception list a bit smaller17:31
hberaudCan't hurt17:31
ttxmaybe we should check which of those are under release-management17:31
ttxLike for example we should not wait on openstack/api-site17:32
ttxsince it's not released, so it should not block return to GREEN17:32
* hberaud check the list17:32
ttxSo, maybe change the topic for the ones that are release-management:none17:32
* ttx does a quick check17:33
ttx openstack/release-test17:33
ttx openstack/i18n17:33
hberaudI think that all the monasca* are under our scope17:34
ttx openstack/os-service-types17:34
hberaudand some of them are failing17:34
hberaudtelemetry, solum too17:34
ttxthe rest are "releasable" so the list is not empty yet17:34
hberaudYes it's worth to stay Orange for now17:34
ttxcould you update the topic on the ones we should not care about?17:35
ttxso that the list only contains ones we care about?17:35
ttx(from a green/orange standpoint)17:35
hberaudThe list contains ~8-9 projects that we care about17:35
hberaudor maybe a bit more17:36
ttxI just listed the ones we should not care about17:36
ttxcontributor-guide release-test i18n os-service-types api-site17:37
hberaudI was thinking to generate a dedicated dashboard17:37
hberaudI'll reply on the ML to share them more widely17:38
hberaudOk move on17:39
hberaud#topic Assign R-12 tasks17:39
*** openstack changes topic to "Assign R-12 tasks (Meeting topic: releaseteam)"17:39
hberaudOk everything seems already assigned17:40
hberaudAny volunteer on some of them?17:40
hberaudElse, is not an issue and we can continue with that17:41
hberaudOk move on17:42
hberaud#topic Review countdown email contents17:42
*** openstack changes topic to "Review countdown email contents (Meeting topic: releaseteam)"17:42
*** rpittau is now known as rpittau|afk17:42
hberaudI ignored a section of the email template17:43
hberaudAnd I proposed to remove her
hberaudLet me know if it make sense to you, c.f the commit message for further details17:44
hberaudI didn't see this list during victoria either17:45
hberaud(the project list)17:45
hberaudAny comment?17:47
ttxnope, content looks good17:47
hberaudack, thanks17:47
hberaud#topic Open floor17:47
*** openstack changes topic to "Open floor (Meeting topic: releaseteam)"17:47
hberaudAnything else to discuss today?17:48
ttxI just approved the stein-last things that were ready17:48
eloda heads-up from me maybe,17:48
hberaudelod: the floor is yours17:48
elodthough train-em is far (05-12)17:48
elod(as I said before) I'm planning to generate train release patches17:49
hberaudWe do you suggest?17:49
elodmaybe some time after milestone-2?17:49
hberaudCould be in February/March17:50
hberaudelod: Is it ok for you ^17:50
elodI thought maybe end of next week, the week after :)17:50
elodso a bit sooner :)17:50
elodbut if you think I can wait with that till Feb or March17:51
hberaudWhat do you plan to release exactly? everything that need to be released?17:51
elodwhere there are unreleased patches, yes17:52
hberaudI mean all the changes not yet released?17:52
hberaudSo you're right ASAP could be better17:52
elodas smcginnis did in july (?)17:52
hberaudIt will avoid loaded agenda17:52
elodhberaud: yes, ack17:53
* hberaud check the agenda17:53
hberaudYes definitely, March will be FF and M3, and we will be heavy loaded17:54
hberaud+1 for M2 the week after17:55
elodhberaud: ack17:55
elodthanks, that's it :X17:55
hberaudelod: thanks to have bring that here17:55
hberaudAnything else?17:56
hberaudelod: Just one thing17:56
hberaudI think it could be worth to send a friendly reminder17:56
hberaudabout that17:56
elodhberaud: ok17:57
hberaudelod: do you want to handle that as you did with stein?17:57
hberaudIt will inform the teams that train will be released soon17:57
elodhberaud: just to be clear: this is not the 'final-release-before-[4~em'17:58
hberaudBut it could let's a chance to them to prioritize their reviews17:58
hberaudThat's all for me17:59
hberaudOK, thanks everyone. Almost there!17:59
hberaudWe consumed all our time17:59
ttxthanks hberaud !17:59
*** openstack changes topic to "OpenStack Release Managers office - Come here to discuss how to release OpenStack components - Logged at"18:00
openstackMeeting ended Thu Jan 14 18:00:27 2021 UTC.  Information about MeetBot at . (v 0.1.4)18:00
openstackMinutes (text):
elodhberaud: so about steim-em, I'm planning to handle that, too, in may as I did with stein18:01
hberaudstein? train?18:01
hberaudelod: awesome, thanks18:02
elodhberaud: so about train-em, I'm planning to handle that, too, in May as I did with stein18:02
elodthis is how I wanted to write ^^^18:02
*** dtantsur is now known as dtantsur|afk18:10
*** diablo_rojo has quit IRC18:34
iurygregoryhberaud, we can probably move on in
*** slaweq has quit IRC18:38
*** diablo_rojo has joined #openstack-release18:43
hberaudiurygregory: ack thanks for the heads-up, ttx, smcginnis FYI ^18:43
hberaudjust need a final approval18:43
iurygregorynot sure the patch didn't put +1 in the PTL label hehe18:51
*** whoami-rajat__ has quit IRC19:20
*** e0ne has joined #openstack-release19:28
*** e0ne has quit IRC19:39
*** armstrong_ has quit IRC20:10
*** e0ne has joined #openstack-release20:19
*** slaweq has joined #openstack-release20:19
*** slaweq has quit IRC20:27
*** e0ne has quit IRC20:37
*** e0ne has joined #openstack-release20:39
*** e0ne has quit IRC20:39
*** e0ne has joined #openstack-release20:49
*** e0ne has quit IRC20:49
*** jrosser has quit IRC21:29
*** fnordahl has quit IRC21:30
openstackgerritMerged openstack/releases master: molteniron does not need releases
*** fnordahl has joined #openstack-release21:31
*** jrosser has joined #openstack-release21:32
*** diablo_rojo has quit IRC21:48

Generated by 2.17.2 by Marius Gedminas - find it at!