Thursday, 2020-01-09

*** tetsuro has joined #openstack-release00:05
*** tetsuro_ has quit IRC00:07
*** armax has quit IRC00:08
*** armax has joined #openstack-release00:12
*** armax has quit IRC00:45
*** portdirect has quit IRC01:02
*** tetsuro has quit IRC01:04
*** tetsuro has joined #openstack-release01:04
*** tetsuro has quit IRC01:08
*** slaweq has joined #openstack-release01:11
*** slaweq has quit IRC01:17
*** tetsuro has joined #openstack-release01:17
*** tetsuro_ has joined #openstack-release01:22
*** tetsuro has quit IRC01:26
*** tetsuro has joined #openstack-release02:00
*** tetsuro_ has quit IRC02:04
*** tonyb has quit IRC02:10
*** tinwood has quit IRC02:10
*** tinwood has joined #openstack-release02:12
*** ekcs has quit IRC02:18
*** tetsuro has quit IRC03:07
*** ricolin has quit IRC03:07
*** slaweq has joined #openstack-release03:11
*** slaweq has quit IRC03:16
*** ricolin has joined #openstack-release03:28
*** ricolin_ has joined #openstack-release03:57
*** ricolin_ has quit IRC03:57
*** tetsuro has joined #openstack-release03:59
*** ricolin has quit IRC04:02
*** udesale has joined #openstack-release04:03
*** ricolin has joined #openstack-release04:03
*** zxiiro has quit IRC04:10
*** ykarel|away has joined #openstack-release04:42
*** slaweq has joined #openstack-release05:11
*** slaweq has quit IRC05:16
*** ykarel|away is now known as ykarel05:25
*** evrardjp has quit IRC05:33
*** evrardjp has joined #openstack-release05:34
*** udesale has quit IRC05:40
*** slaweq has joined #openstack-release06:29
*** slaweq has quit IRC06:33
*** udesale has joined #openstack-release07:12
*** openstackgerrit has joined #openstack-release07:16
openstackgerritAkihiro Motoki proposed openstack/releases master: Release horizon 17.2.0 (ussuri)  https://review.opendev.org/70167207:16
*** slaweq has joined #openstack-release07:52
*** pcaruana has joined #openstack-release08:02
*** hberaud|gone is now known as hberaud08:04
*** rpittau|afk is now known as rpittau08:06
*** ykarel is now known as ykarel|lunch08:06
*** tosky has joined #openstack-release08:25
*** slaweq_ has joined #openstack-release08:29
*** slaweq has quit IRC08:31
*** udesale has quit IRC08:32
*** trident has quit IRC08:37
*** trident has joined #openstack-release08:39
*** e0ne has joined #openstack-release08:42
*** tetsuro has quit IRC08:43
*** ykarel|lunch is now known as ykarel09:06
*** udesale has joined #openstack-release09:11
*** jtomasek has joined #openstack-release09:13
*** e0ne has quit IRC09:20
*** electrofelix has joined #openstack-release09:36
*** slaweq_ has quit IRC09:38
*** tetsuro has joined #openstack-release09:45
*** slaweq_ has joined #openstack-release09:50
*** tetsuro has quit IRC10:05
*** e0ne has joined #openstack-release10:08
openstackgerritMerged openstack/releases master: Release python-octaviaclient 2.0.0  https://review.opendev.org/70144910:51
*** dtantsur|afk is now known as dtantsur10:55
*** hberaud is now known as hberaud|school-r10:57
openstackgerritMerged openstack/releases master: Release OpenStack-Ansible Stein  https://review.opendev.org/69997811:00
*** hberaud|school-r is now known as hberaud|lunch11:02
*** tetsuro has joined #openstack-release11:07
*** udesale has quit IRC11:12
*** ykarel is now known as ykarel|afk11:16
*** rpittau is now known as rpittau|bbl11:18
*** ykarel has joined #openstack-release11:28
*** ykarel is now known as ykarel|afk12:10
*** tetsuro has quit IRC12:15
*** hberaud|lunch is now known as hberaud12:16
*** ykarel|afk has quit IRC12:26
*** ykarel|afk has joined #openstack-release12:57
*** zbr|rover has quit IRC13:00
openstackgerritMark Goddard proposed openstack/releases master: Release Kayobe 7.0.0 for Train  https://review.opendev.org/70172413:11
*** rpittau|bbl is now known as rpittau13:25
*** ykarel|afk is now known as ykarel13:25
*** ykarel is now known as ykarel|afk13:46
openstackgerritAkihiro Motoki proposed openstack/releases master: Release horizon 18.0.0 (ussuri)  https://review.opendev.org/70167214:00
*** zbr has joined #openstack-release14:18
*** zxiiro has joined #openstack-release14:18
*** zbr is now known as zbr|rover14:18
*** slaweq_ is now known as slaweq14:26
*** portdirect has joined #openstack-release14:31
*** pcaruana has quit IRC14:47
*** pcaruana has joined #openstack-release15:02
*** udesale has joined #openstack-release15:04
*** armstrong has joined #openstack-release15:23
armstrongHello15:23
armstrongmeeting time changed?15:23
*** dave-mccowan has quit IRC15:25
*** hberaud is now known as hberaud|school-r15:29
*** udesale has quit IRC15:33
smcginnisA few more minutes.15:57
armstrongok15:58
*** armax has joined #openstack-release15:59
smcginnis#startmeeting releaseteam16:00
openstackMeeting started Thu Jan  9 16:00:10 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
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: releaseteam)"16:00
openstackThe meeting name has been set to 'releaseteam'16:00
smcginnisPing list: ttx armstrong diablo_rojo, diablo_rojo_phon16:00
*** hberaud|school-r is now known as hberaud16:00
evrardjpo/16:00
hberaudo/16:00
diablo_rojo_phonO/16:00
evrardjplook who is back from holidays! me \o/16:00
armstrongo/16:01
smcginnis#link https://etherpad.openstack.org/p/ussuri-relmgt-tracking Agenda16:01
evrardjpL22516:02
ttxo/16:02
* evrardjp guesses16:02
smcginnis#topic Remaining ussuri-1 refresh16:02
*** openstack changes topic to "Remaining ussuri-1 refresh (Meeting topic: releaseteam)"16:02
smcginnis#link https://review.opendev.org/#/c/698508/16:02
smcginnishberaud: Do you know if your concern has been addressed there? ^16:03
* hberaud take a look16:04
smcginnisOh, sorry. Actual comment was from dtantsur16:04
dtantsurwhat have I done? :)16:04
hberaudyep the reno is still missing16:04
hberauddtantsur: ^^16:05
dtantsurah16:05
smcginnisThis is just milestone 1. What does everyone think? Should we just abandon this one and pick it up at milestone 2?16:05
dtantsurmordred: ^^^16:05
hberaudI think we can go ahead to catch error ASAP16:06
smcginnishberaud: You mean go ahead with getting this released now so we can catch errors sooner?16:06
hberaudyes16:06
evrardjpand have the next release have the reno?16:06
smcginnisThat makes sense to me. Finding out if there are issues with it sooner rather than later is better.16:06
evrardjpthat sounds okay to me16:06
hberaudIMHO it's more safer16:07
smcginnisIt would be great if we can quick get a reno added, but not the end of the world.16:07
hberaudsmcginnis: sure16:07
smcginnisI've removed my -1 on there. Would be great if the team can ack if they think it's good to go ahead with it now.16:07
*** mlavalle has joined #openstack-release16:07
dtantsurI'm -0 on releasing anything so major without a reno..16:08
smcginnisIs there one proposed yet?16:08
smcginnisI haven't had a chance to look.16:08
evrardjpdtantsur: that's why we hope to have a reno patch soon merged so we can bump the sha and release ? :D16:08
dtantsurI haven't looked, I'm not following o-c-c closely16:08
dtantsurI can prepare one if nobody else wants to16:09
smcginnisThat would be great!16:09
evrardjpthat would be awesome!16:09
evrardjpsmcginnis: haha16:09
smcginnisHopefully that can get through ASAP and we can get this released after the sha gets updated.16:09
smcginnisLet's plan on that then. dtantsur, if you happen to remember, please let me know the patch adding the reno so I can review/watch it.16:10
smcginnis#topic Validate countdown email content16:10
*** openstack changes topic to "Validate countdown email content (Meeting topic: releaseteam)"16:10
smcginnis#link https://etherpad.openstack.org/p/relmgmt-weekly-emails16:10
evrardjpor ping in this channel so other people can also vote16:10
smcginnis++16:11
smcginnisLine 87 in the countdown etherpad.16:11
* smcginnis reads16:11
evrardjpI read mid-milestone2 can't find anything to say more. It looks good16:11
ttxOK, I'll turn it into process tomorrow16:12
smcginnisYep, content looks good to me.16:12
smcginnis#topic False positive tests16:13
*** openstack changes topic to "False positive tests (Meeting topic: releaseteam)"16:13
dtantsursmcginnis: https://review.opendev.org/#/c/701761/16:13
smcginnis#link https://review.opendev.org/#/c/698845/116:13
smcginnisdtantsur: Thanks!16:13
smcginnisI think we only have a check for all repos in later releases.16:14
smcginnisSo if one release contains, for example, three repos, then all subsequent releases need to contain all three.16:14
ttxhmm16:15
ttxdoes it sound like something we should add?16:15
ttxIt's a bit hard to spot16:15
smcginnisSince some teams need to release some of their repos separately, I don't think we have any kind of reconciliation with the governance data.16:15
ttxThe gov/rel consistency check I'm workign on will catch it16:15
ttxbut it's a periodic check, not immediate16:16
smcginnisHow will that work if a team has some c-w-i deliverables and some c-w-rc?16:16
*** slaweq has quit IRC16:17
evrardjpwasn't that a problem for OSA in some stable branches?16:17
ttxthose would be separate files right16:18
smcginnisevrardjp: Maybe16:18
evrardjpbecause some things were split out into different deliverables in governance16:18
smcginnisttx: Yes. So just looking at the governance data, how do we tell if something is missing or just not released separately?16:18
evrardjpso inside a cycle, some have disappeared to move somewhere else16:18
ttxgovernance defines deliverables16:18
evrardjpsome repo could have moved to a different deliverable :p16:19
smcginnisOr deliverables added or removed mid-cycle.16:19
evrardjpbefore m2 I guess but after m1 indeed16:19
ttxLike governance says A contains a1 and a2... we could check that A.yaml contanis a1 and a216:19
smcginnisWe can try it out. If it works in this consistency check, maybe we can extend that into our validate job.16:19
ttxbut yeah, stable branches would not work16:20
evrardjpttx: well governance is not stable branched16:20
evrardjp:)16:20
evrardjpyou said it ! :p16:20
ttxBUT stable used to be master once16:20
evrardjpoh I see, you think it's fine forward16:20
ttxand we have a check to check that later releases are ok16:20
smcginnisI suppose we could start tagging governance. :)16:20
evrardjpsmcginnis: I thought of that multiple times tbh.16:20
evrardjpwould simplify releases...16:21
ttxSo if we just used governance to check that initial master releases are OK, it would propagate16:21
smcginnisIt's something at least.16:21
ttxI can have a look at what it would take16:21
ttxprobably not that difficult16:21
ttxok next16:22
ttxjust not today (or this month really)16:23
smcginnisYeah...16:23
smcginnis#topic cliff issue postmortem16:23
*** openstack changes topic to "cliff issue postmortem (Meeting topic: releaseteam)"16:23
smcginnisWorthy of its own topic. :)16:23
smcginnisI haven't had a chance to try to triage what happened here.16:23
ttxsame thing... is that something we could/should have caught16:23
ttxmaybe we can postpone discussion then16:23
smcginnisSomehow the automation picked up a very old commit for cliff.16:23
ttxuntil somone has a look and can explain it16:23
ttxit's not urgent... just whenever a probem slips through we should have a look and see if we could avoid it in the future16:24
smcginnisFor now at least, let's make sure we are extra careful reviewing those automated milestone patches.16:24
smcginnisDefinitely. I don't like not knowing how something like that happened when the script should be pulling the latest from HEAD.16:24
ttxdo you have a link?16:24
smcginnisTo the cliff release patch?16:24
ttxyeah16:25
smcginnishttps://review.opendev.org/#/c/698485/16:25
evrardjpis that the right link?16:25
smcginnisOddly, list-changes shows what changed between 2.11.0 and that.16:25
ttxhmm we should definitely check the WHY before doing milestone2 autoreleases16:26
evrardjpoh my bad16:26
smcginnisWhen it should have been since 2.16.016:26
ttxwho can have a look in the next 4 weeks?16:26
ttx(hint: not me)16:26
smcginnisIt would have been a good clue looking at the "Release will NOT include" section.16:26
smcginnisI will try to.16:26
ttxno point in using meeting time to further investigate16:27
smcginnis#topic "Decentralizing release approvals" thread and resulting TODOs16:27
*** openstack changes topic to ""Decentralizing release approvals" thread and resulting TODOs (Meeting topic: releaseteam)"16:27
ttxyeah so there was this thread16:27
ttxwhere some speed-up solutions were proposed16:27
ttxfirst one is easy16:28
ttxgoing back to single-approval of releases changes16:28
ttxWaiting for two +2s can take some time16:28
ttxespecially when the proposer is Sean or me16:28
evrardjpprevious topic makes me think two approvals could (but no certainty) have helped16:28
ttxIt's obviously a trade-off16:29
evrardjpyup but it's one in a x16:29
ttxmore reviewers means we catch more things, but delays releases16:29
smcginnisMaybe for those auto-patches we keep the two +2's.16:29
smcginnisAs much as we can.16:29
evrardjpI would be inclined to trust the auto-patches more, so I am sad here :p16:29
evrardjphaha16:29
smcginnisYeah, very true. Very sadly true.16:29
ttxI think single-approval is the right tradeoff16:30
ttxbetween two reviews and no review at all16:30
smcginnisOnce we get root cause, maybe that will explain things sufficiently to not have to worry about more than 1 +2 on those.16:30
evrardjpAs long as it doesnt' prevent people to onboard releases.16:30
smcginnisI agree. For the most part, our automation is good at catching most issues.16:30
ttxthere will be more errors yes, but also less frustration due to delays16:30
evrardjpI think that's what matters16:30
smcginnisSo a single human review checking things like semver rules is probably enough in most cases.16:31
evrardjpwhen projects do follow them... ahem.. :p16:31
ttxThe second proposal is around stable releases16:31
ttxnot waiting for a Monday to pass16:31
ttxAt this point the Monday does not help16:31
evrardjpso wait, what's the difference? a day?16:31
ttxsince we don;t really get stable reviews by waiting16:31
smcginnisFor single +2, should we try +2 first, wait a bit to give someone else a chance, then +A after some set amount of delay? Or just go for it?16:32
smcginnisYeah, the Monday stable review day hasn't been working for quite awhile now I think.16:32
evrardjpsmcginnis: +116:32
ttxsmcginnis: I'd just go for it if you're comfortable with it16:32
evrardjpttx: doesn't that apply for all votes? :p16:32
ttxif you're not sure, just do not w+116:32
smcginnisStable review in general. I've been thinking maybe those are just the ones where we require two +2's so we get more eyes on watching for stable policy issues.16:32
smcginnisttx: ++16:33
ttxthat would be fair16:33
evrardjpyeah I think stable should keep the 2x+2 rule16:33
smcginnisThere's some "specialized" knowledge with stable, but nothing that much more that normal release team folks shouldn't be able to handle.16:33
ttxSo... master = single-approval OK, can wait for more in case of doubt16:33
ttxstable = 2x +2s needed, no wait16:34
*** slaweq has joined #openstack-release16:34
ttxlet's see how that goes16:34
smcginnisThat sounds like a good plan to me.16:34
evrardjpyeah, and in doubt don't +2 just +1 ?16:34
smcginnisWe can always course correct down the road if we find it's causing issues.16:34
evrardjpthat's what I have been doing for now16:34
ttx+2 in case of "yes but could use a second opinion"16:34
evrardjpyup16:34
ttx+2 w+1 in case of "I'm pretty sure this is good"16:35
ttxLike when an experienced liaison submits it16:35
evrardjpthat's my rule :)16:35
smcginnisThese all seem reasonable to me.16:35
evrardjpseems to work so far, I didn't break the world16:35
evrardjp(yet)16:35
smcginnis;)16:35
ttxsmcginnis: maybe close the thread by saying we've relaxed the rules to speed up release processing, let's see how that goes?16:35
smcginnis#agreed Current releases only require 1 +2 and can be approved if comfortable. Stable reviews should have two from any release manager.16:36
smcginnisWill do.16:36
ttxNote that it's also valid for all those patches from me that you have +2ed and nobody else reviewed :P16:36
smcginnisSubtle hint? :)16:36
ttxsubtle is my middle name16:36
evrardjphaha16:37
diablo_rojo_phonHaha16:37
smcginnis#topic Dropping cycle-automatic for tempest plugins16:37
evrardjpptl is different, you know that smcginnis has all the rights in the world for releases.16:37
*** openstack changes topic to "Dropping cycle-automatic for tempest plugins (Meeting topic: releaseteam)"16:37
ttx"you are so subtle" said noone to me ever16:37
evrardjpttx: oh really?16:37
evrardjp:p16:37
evrardjpanyway16:37
smcginnisI think I added this topic, though it was weeks (years) ago.16:37
ttxa lot of people say "you are so devilishly crafty"16:38
smcginnishehe16:38
ttxyeah, what's that about16:38
evrardjpsmcginnis: ofc. You want also to say it was last decade?16:38
smcginnisWith c-a release model, we originally conceived of that for things like tempest plugins that had not previously been released.16:38
ttxlike cycle-automatic was designed for tempest plugins16:38
smcginnisWith the idea that we just needed to get them tagged at the end of a cycle to have a way to track the version that goes with a given version of tempest.16:39
ttxwell c-a was mostly to make sure there would be a end release for those oft-overlooked things16:39
smcginnisTo know what is expected to work as tempest evolves.16:39
smcginnisYeah, that too.16:39
ttxso why on Earth would you stop doing that?16:39
smcginnisWe originally had validation in place to make sure there weren't multiple releases, IIRC.16:39
ttxah, that sounds silly16:40
*** slaweq has quit IRC16:40
smcginnisBut now it turns out teams, and some downstream consumers like Red Hat, want multiple releases throughout the cycle.16:40
smcginnisMaking them look a lot more like cycle-with-intermediary.16:40
johnsomOctavia is in that camp. We have had requests for "more often than once a release" tags.16:41
smcginnisSince we now have been doing more final c-w-i automatically proposed releases, do we need cycle-automatic, or do we just include those things in our final checks for c-w-i that have outstanding commits to release?16:41
smcginnisjohnsom: Thanks, good to know that.16:41
ttxhmm16:41
ttxc-w-i would not do a final release at the very end16:42
smcginnisOr, we keep cycle-automatic, we treat it just like we treat c-w-i, but no matter what we always do a final release at the end of the cycle.16:42
smcginnisI guess that last one is really what we've been doing now.16:43
ttxyeah c-a = c-wi + final release16:43
evrardjpcycle-automatic doesn't prevent more releases , does it ?16:43
ttxno16:43
smcginnisOriginally it did, but then folks had $reasons for wanting intermediate releases.16:43
ttx+ No stable branch will be automatically created.16:43
ttxhttps://releases.openstack.org/reference/release_models.html#cycle-automatic16:43
ttxThe “cycle-automatic” model is used by specific technical deliverables that need to be automatically released once at the end of a cycle. Those may, optionally, also be released in the middle of the cycle. Those do not need a stable branch created. This may be applied only to “tempest-plugin” or “other” deliverables.16:44
ttxI feel like that's a clear definition16:44
smcginnisOK, that is clear enough. So I guess we are good then.16:44
toskythanks :)16:44
armstrong@ttx best math equation: c-a = c-wi + final release16:44
smcginnis:)16:44
smcginnis#topic AOB16:45
*** openstack changes topic to "AOB (Meeting topic: releaseteam)"16:45
smcginnisAnything else to discuss today?16:45
ttxfinal release = wi-a16:45
evrardjpsmcginnis: nope16:45
smcginnisI do have a patch I think we should get through:16:46
smcginnishttps://review.opendev.org/#/c/700221/16:46
smcginnisOur release announcements have bad links right now because of that.16:46
* ttx will apply new rules16:46
ttx:boom:16:46
smcginnisThank16:46
smcginniss16:47
smcginnis:016:47
evrardjpwow16:47
evrardjpwouldn't that be a rpoblem for a bunch of automation?16:47
smcginnisI think it depends on the context that the job is run.16:47
evrardjpoh I see16:47
smcginnisLike our list-changes output includes an example of the release announcement, and I think it was fine there.16:47
smcginnisBecause in that case we call it differently and pass in the name or something. It's a little fuzzy now since I've swapped out that part.16:48
evrardjptarball/null does look good though :p16:48
smcginnisThe issue started because of an infra change I think that would clear the remote information.16:48
smcginnisSo suddenly we would extract "null" instead of the repo name.16:48
smcginnisOK, if we don't have anything else, let's move along.16:49
smcginnisThanks everyone!16:49
evrardjpthanks smcginnis and others!16:49
smcginnis#endmeeting16:49
*** openstack changes topic to "OpenStack Release Managers office - Come here to discuss how to release OpenStack components - Logged at http://eavesdrop.openstack.org/irclogs/%23openstack-release/"16:49
openstackMeeting ended Thu Jan  9 16:49:38 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/releaseteam/2020/releaseteam.2020-01-09-16.00.html16:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/releaseteam/2020/releaseteam.2020-01-09-16.00.txt16:49
openstackLog:            http://eavesdrop.openstack.org/meetings/releaseteam/2020/releaseteam.2020-01-09-16.00.log.html16:49
*** N3l1x has joined #openstack-release16:52
*** e0ne has quit IRC16:56
openstackgerritMerged openstack/releases master: Fix library shortname identification in announce script  https://review.opendev.org/70022117:02
*** dtantsur is now known as dtantsur|afk17:03
*** ricolin has quit IRC17:03
*** tosky has quit IRC17:05
*** tosky has joined #openstack-release17:06
*** hberaud is now known as hberaud|gone17:13
openstackgerritMerged openstack/releases master: Release oslo.messaging 9.5.1 for Stein  https://review.opendev.org/70108017:31
*** ykarel|afk is now known as ykarel|away17:31
*** evrardjp has quit IRC17:33
*** evrardjp has joined #openstack-release17:34
*** ykarel|away has quit IRC17:40
*** rpittau is now known as rpittau|afk17:44
openstackgerritSean McGinnis proposed openstack/releases master: Address review comments for make_missing_releases  https://review.opendev.org/70178817:57
openstackgerritMerged openstack/releases master: Introduce 'abandoned' release model  https://review.opendev.org/69973218:03
openstackgerritMerged openstack/releases master: Tag abandoned deliverables  https://review.opendev.org/69973318:03
openstackgerritMerged openstack/releases master: Oslo train releases for 2020-01-07  https://review.opendev.org/70139818:03
openstackgerritMerged openstack/releases master: Release Kayobe 7.0.0 for Train  https://review.opendev.org/70172418:06
openstackgerritSean McGinnis proposed openstack/releases master: Add tools/bulk_review.sh and get-contacts  https://review.opendev.org/65256618:18
*** ekcs has joined #openstack-release18:27
*** electrofelix has quit IRC18:31
openstackgerritMerged openstack/releases master: Release horizon 18.0.0 (ussuri)  https://review.opendev.org/70167218:38
openstackgerritMerged openstack/releases master: Add wrapper script that can be used to update deliverables  https://review.opendev.org/64828918:41
openstackgerritMerged openstack/releases master: Add simple liaisons wrapper module  https://review.opendev.org/69444718:41
openstackgerritMerged openstack/releases master: Oslo stein releases for 2020-01-07  https://review.opendev.org/70141518:41
*** tosky has quit IRC18:48
*** pcaruana has quit IRC19:35
*** openstackgerrit has quit IRC19:59
*** slaweq has joined #openstack-release20:07
*** openstackgerrit has joined #openstack-release20:10
openstackgerritSean McGinnis proposed openstack/releases master: Release os-client-config for Ussuri milestone 1  https://review.opendev.org/69850820:10
*** armstrong has quit IRC20:12
openstackgerritMerged openstack/releases master: Oslo Rocky releases for 2020-01-07  https://review.opendev.org/70145420:22
openstackgerritMerged openstack/releases master: Display abandoned deliverables in separate section  https://review.opendev.org/69994820:22
openstackgerritMerged openstack/releases master: Mark retired deliverables EOL  https://review.opendev.org/70001320:22
openstackgerritMerged openstack/releases master: Add command to list cycle-trailing to process  https://review.opendev.org/69752820:22
*** jtomasek has quit IRC21:32
*** e0ne has joined #openstack-release21:42
*** N3l1x has quit IRC22:13
*** slaweq has quit IRC22:19
*** slaweq has joined #openstack-release23:20
*** ekcs has quit IRC23:21
*** slaweq has quit IRC23:25
*** e0ne has quit IRC23:25
*** e0ne has joined #openstack-release23:26
*** e0ne has quit IRC23:26
*** ekcs has joined #openstack-release23:47

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!