Thursday, 2019-04-11

*** armax_ has joined #openstack-release00:32
*** armax has quit IRC00:32
*** tbarron_ has quit IRC00:32
*** armax_ is now known as armax00:32
*** timburke has quit IRC00:32
*** timburke has joined #openstack-release00:34
*** mgoddard has quit IRC00:34
*** mgoddard has joined #openstack-release00:37
*** armax has quit IRC01:14
*** bobh has joined #openstack-release01:22
*** lbragstad has quit IRC01:37
*** ykarel|away has joined #openstack-release02:12
*** ekcs has quit IRC02:25
*** bobh has quit IRC02:31
*** bobh has joined #openstack-release02:32
*** bobh has quit IRC02:36
*** hongbin has joined #openstack-release03:03
*** armax has joined #openstack-release03:10
*** armax has quit IRC03:33
*** ykarel|away has quit IRC03:44
*** diablo_rojo has quit IRC03:50
*** whoami-rajat has joined #openstack-release03:54
*** hongbin has quit IRC04:05
*** ykarel|away has joined #openstack-release04:06
*** ykarel|away is now known as ykarel04:10
*** ricolin has joined #openstack-release04:10
*** ykarel_ has joined #openstack-release04:13
*** ykarel has quit IRC04:16
*** bobh has joined #openstack-release04:30
*** bobh has quit IRC04:35
*** samP has quit IRC04:45
*** diablo_rojo has joined #openstack-release04:50
*** armax has joined #openstack-release04:51
*** e0ne has joined #openstack-release05:28
*** bobh has joined #openstack-release05:35
*** bobh has quit IRC05:39
*** jtomasek has quit IRC05:48
*** e0ne has quit IRC05:50
*** e0ne has joined #openstack-release05:51
*** gouthamr has quit IRC05:56
*** gouthamr has joined #openstack-release06:00
*** udesale has joined #openstack-release06:03
*** e0ne has quit IRC06:08
*** ykarel_ is now known as ykarel06:11
*** whoami-rajat has quit IRC06:13
*** whoami-rajat has joined #openstack-release06:25
*** armax has quit IRC06:26
evrardjpthanks tonyb06:27
*** hberaud|gone is now known as hberaud06:55
*** diablo_rojo has quit IRC06:56
*** bobh has joined #openstack-release07:14
*** jpich has joined #openstack-release07:16
tonyb[m]evrardjp: thanks for?07:17
evrardjptonyb[m]:  proposing the documentation07:17
evrardjpdropping the tribal knowledge somewhere :)07:18
tonyb[m]evrardjp: Ahh okay07:18
tonyb[m]evrardjp: I haven't *done* it yet ;P07:18
*** bobh has quit IRC07:18
evrardjpI have seen :)07:18
evrardjpbut thanks for _thinking about it_ in the first place07:18
evrardjptonyb[m]: will do my best to attend meetings, but can't promise anything07:20
evrardjp(with the new time)07:21
tonybevrardjp: I knwo it's magic 8-ball'ish but woudl you say 90% likely you'd be able to make a 2100 meeting or 50% or 10%?07:22
evrardjpI really can't say in advance. It will depend on my wife's work07:23
evrardjp:)07:23
evrardjpI guess we'll try and see :D07:23
ttxsmcginnis: yes from a script. It's just dividing the number of commits during the Stein timeframe by the number of days in the Stein cycle07:32
ttxStein has more commits than Rocky, but was noticeably longer... so dividing by number of days is more fair07:32
*** ykarel is now known as ykarel|lunch07:32
ttx(counting activities for all repos under the TC at the time of commit)07:34
ttxStein had 34356 commits07:35
*** tosky has joined #openstack-release07:39
*** amoralej|off is now known as amoralej07:40
*** e0ne has joined #openstack-release07:49
*** e0ne has quit IRC07:51
*** e0ne has joined #openstack-release07:56
*** jtomasek has joined #openstack-release08:06
*** priteau has joined #openstack-release08:23
*** ykarel|lunch is now known as ykarel08:24
*** dtantsur|afk is now known as dtantsur08:35
*** e0ne has quit IRC08:39
*** e0ne has joined #openstack-release08:48
*** cdent has joined #openstack-release09:00
openstackgerritMerged openstack/releases master: More stein release note links  https://review.openstack.org/65157809:13
openstackgerritMerged openstack/releases master: tripleoclient: tag RC1 & branch stable/stein  https://review.openstack.org/65125309:18
*** tbarron has joined #openstack-release09:21
*** e0ne has quit IRC09:26
*** e0ne has joined #openstack-release09:30
openstackgerritMerged openstack/releases master: Pick up stable series release notes  https://review.openstack.org/65091109:30
openstackgerritMerged openstack/releases master: Release kolla stable branches  https://review.openstack.org/65041109:32
openstackgerritMerged openstack/releases master: congress-dashboard 3.0.1  https://review.openstack.org/65045209:32
openstackgerritMerged openstack/releases master: congress-dashboard 2.0.1  https://review.openstack.org/65045009:37
openstackgerritMerged openstack/releases master: congress-dashboard 1.0.1  https://review.openstack.org/65044609:37
*** electrofelix has joined #openstack-release09:40
*** bobh has joined #openstack-release09:56
*** bobh has quit IRC10:00
*** e0ne has quit IRC10:10
*** e0ne has joined #openstack-release10:15
*** e0ne has quit IRC10:51
smcginnistonyb: I think a stable release section in the reference is a great idea.10:55
*** amoralej is now known as amoralej|lunch10:56
*** udesale has quit IRC10:57
*** e0ne has joined #openstack-release10:57
*** priteau has quit IRC10:59
*** hberaud has quit IRC11:15
*** e0ne has quit IRC11:17
*** hberaud has joined #openstack-release11:17
*** hberaud is now known as hberaud|lunch11:21
openstackgerritSean McGinnis proposed openstack/releases master: Handle validation of retired repos  https://review.openstack.org/65046511:36
*** ricolin has quit IRC11:37
*** dave-mccowan has joined #openstack-release11:37
openstackgerritThierry Carrez proposed openstack/releases master: No longer create longlines with edit-deliverables  https://review.openstack.org/65176211:43
ttxThat one has been annoying me for a while11:43
openstackgerritSean McGinnis proposed openstack/releases master: Add 'em' tagging to new-release command  https://review.openstack.org/65046211:46
openstackgerritSean McGinnis proposed openstack/releases master: Handle deliverables with legacy teams  https://review.openstack.org/65046311:46
openstackgerritSean McGinnis proposed openstack/releases master: Add script to transition entire series to EM or EOL  https://review.openstack.org/65046411:46
openstackgerritSean McGinnis proposed openstack/releases master: Handle validation of retired repos  https://review.openstack.org/65046511:46
openstackgerritSean McGinnis proposed openstack/releases master: Add decorator to skip validations for EM and EOL  https://review.openstack.org/65046611:46
openstackgerritSean McGinnis proposed openstack/releases master: Tag stable/ocata as extended maintenance  https://review.openstack.org/65046711:46
smcginnisGrr11:46
smcginnisttx: Thoughts on https://review.openstack.org/#/c/650462/ ?11:47
ttxlooking11:57
ttxsmcginnis: I was holding for the doc to come with it as requested by evrardjp11:58
smcginnisttx: OK, so you think we should add a section to the documentation for that?11:59
*** ykarel is now known as ykarel|afk11:59
*** pabelanger has left #openstack-release12:00
ttxhttps://releases.openstack.org/reference/using.html#using-new-release-command already lists the other types12:00
ttxor do you think this is niche usage that should not appear in user doc?12:01
ttxI mean, i could buy that12:01
smcginnisWe've excluded procedural and eol from there. I didn't think we wanted to expose those in the docs, but I can get them all added if we want.12:01
ttxno you're right12:02
ttxusing is directed to !releaseteam12:02
smcginnisPersonally, I would feel more comfortable only including what is currently there to avoid end user confusion.12:02
ttx++12:03
ttx+2a12:03
ttxWe can debate the doc addition if anyone cares enough to propose it as a followup patch12:03
smcginnis++12:03
smcginnisThanks. I knew I shouldn't have had those all in a stack, but it was easier that way. Will make it a little better to update things if we get a few of them merged.12:04
smcginnisttx: Speaking of which, lost your +W on a rebase: https://review.openstack.org/#/c/650463/312:05
smcginnisAnd https://review.openstack.org/#/c/650464/312:05
ttxreapplying12:06
smcginnisThanks12:06
openstackgerritMerged openstack/releases master: Add 'em' tagging to new-release command  https://review.openstack.org/65046212:14
ttxhmm12:16
ttxso we had a release job fail, apparently on transient dns issue?12:17
ttxssh://release@review.openstack.org:29418/openstack/kolla.git did not work. Description: ssh: Could not resolve hostname review.openstack.org: Temporary failure in name resolution12:17
ttxhmm no that was retried12:18
ttxok so the openstack/kolla 5.0.5 tag failed12:20
ttx(that's for pike)12:20
ttx(due to that temporary dns fail)12:22
ttxmaybe fungi can reenqueue that ref in the release-post pipeline12:22
ttxhttp://logs.openstack.org/58/589220327957c8c1e630d0ddef8aab5d9e3978dc/release-post/tag-releases/a0a01da/ara-report/12:22
*** hberaud|lunch is now known as hberaud12:23
ttxthe other two tags worked, but they should be ignored12:23
evrardjpsmcginnis: what about release team onboarding? I mean hiding feature in docs is not a good idea12:24
openstackgerritMerged openstack/releases master: Handle deliverables with legacy teams  https://review.openstack.org/65046312:24
openstackgerritMerged openstack/releases master: Add script to transition entire series to EM or EOL  https://review.openstack.org/65046412:24
openstackgerritMerged openstack/releases master: Handle validation of retired repos  https://review.openstack.org/65046512:24
openstackgerritMerged openstack/releases master: Add decorator to skip validations for EM and EOL  https://review.openstack.org/65046612:24
ttxevrardjp: it should definitely be listed in the em process doc12:24
evrardjp"we do have those extra things hidden" will prevent people from trying those :)12:24
evrardjpttx: that works for me12:24
ttxbut I'm not sure where that lives tbh12:24
evrardjpcurrently many things are intertwined12:25
smcginnisYeah, process.rst would be a good place to have the example commands for their specific uses.12:25
evrardjpI didn't spend time in my whole "I need to get a full grasp of things by emptying my brain" yet12:25
smcginnisttx: Thanks, I was just about to look at the job failure. Agree we can wait to see if fungi and can run it.12:26
evrardjpsmcginnis: correct, I would put all the cli calls there.12:26
smcginnisevrardjp: That retirement of the one openstack-ansible repo may be an issue.12:27
smcginnisI need to check if I ended up skipping it or not, but we did have a check that all repos were included to make sure none were missed.12:27
evrardjpwould it still be?12:27
evrardjpI think that was over nowadays12:27
smcginnisSince there are all the other repos in there, we might need to work around that to get the rest of them tagged.12:27
smcginnisLet me check. I remember running into that when I first started looking at these.12:28
evrardjpalternatively, wouldn't removing this help: https://github.com/openstack/releases/blob/898539d8fe43418aeb252b5675bab87da5101898/deliverables/ocata/openstack-ansible.yaml#L2262 ?12:29
smcginnisMaybe?12:29
evrardjpas the new-release cli would not propose this openstack-ansible-security, and we would bypass it.12:29
smcginnisI'll check it out.12:29
evrardjpdepends on the testing, but I think that is solved nowadays12:29
evrardjp(Love playing with these kind of things, see what breaks :) )12:30
*** amoralej|lunch is now known as amoralej12:33
*** lbragstad has joined #openstack-release12:36
*** ykarel|afk is now known as ykarel12:52
openstackgerritSean McGinnis proposed openstack/releases master: Tag ocata-em for openstack-ansible repos  https://review.openstack.org/65177812:54
smcginnisevrardjp: Kind of had to work around a bit. ^12:54
evrardjpsmcginnis: if you do it, I am fine. It's been ages I thought of doing that, but I thought it was bad :)12:55
*** e0ne has joined #openstack-release12:56
evrardjpI must say I love that change :D12:56
*** udesale has joined #openstack-release13:00
*** jpich has quit IRC13:17
*** jpich has joined #openstack-release13:17
*** e0ne has quit IRC13:18
*** pcaruana has quit IRC13:20
*** mlavalle has joined #openstack-release13:24
*** mlavalle has quit IRC13:25
*** mlavalle has joined #openstack-release13:27
*** e0ne has joined #openstack-release13:27
*** mriedem has joined #openstack-release13:28
*** pcaruana has joined #openstack-release13:42
smcginnis:)13:54
*** ricolin has joined #openstack-release13:55
openstackgerritMark Goddard proposed openstack/releases master: Release kolla-ansible stable branches  https://review.openstack.org/65041214:05
fungilooking at the kolla point release failure now14:06
smcginnisHopefully just a simple reenqueue.14:08
*** armstrong has joined #openstack-release14:12
fungithe jobs for release changes in the release-post pipeline are idempotent?14:13
fungisuch that if i reenqueue 589220327957c8c1e630d0ddef8aab5d9e3978dc in release-post it'll do what we want?14:13
*** ianychoi has quit IRC14:13
*** ianychoi has joined #openstack-release14:14
smcginnisfungi: I believe so. Looks like that should be safe to rerun.14:14
fungialso, the master branch has moved on since that commit... is rerunning jobs for an older commit than the branch tip going to cause any trouble?14:15
smcginnisHmm, I think it will rerun docs publishing from that point, so if there have been newer doc changes they might be lost. But will get republished on the next commit.14:15
fungiokay, i've reenqueued it with `sudo zuul enqueue-ref --tenant=openstack --trigger=gerrit --pipeline=release-post --project=openstack/releases --ref=refs/heads/master --newrev=589220327957c8c1e630d0ddef8aab5d9e3978dc`14:16
fungiand yeah, the only other job looks like publish-tox-docs-static which i guess is the releases.openstack.org site build14:17
*** e0ne has quit IRC14:27
fungithe tag-releases job seems to have succeeded14:29
smcginnisWoohoo, thanks again fungi.14:29
*** e0ne has joined #openstack-release14:31
fungino sweat. it's all in a day's keystrokes14:31
smcginnis:)14:31
*** e0ne has quit IRC14:34
*** udesale has quit IRC14:38
*** ykarel is now known as ykarel|away14:38
*** e0ne has joined #openstack-release14:41
*** bobh has joined #openstack-release14:44
*** ykarel|away has quit IRC14:47
*** e0ne has quit IRC14:48
*** e0ne has joined #openstack-release14:48
*** bobh has quit IRC14:49
*** bobh has joined #openstack-release14:50
*** armax has joined #openstack-release14:57
*** amoralej is now known as amoralej|mtg14:57
*** e0ne has quit IRC15:08
*** e0ne has joined #openstack-release15:13
*** ykarel|away has joined #openstack-release15:18
*** hberaud is now known as hberaud|school-r15:28
*** e0ne has quit IRC15:32
*** hberaud|school-r is now known as hberaud15:37
*** amoralej|mtg is now known as amoralej15:39
*** pcaruana has quit IRC15:42
*** diablo_rojo has joined #openstack-release15:59
dhellmannare we meeting nowish or did we already change the meeting time?15:59
smcginnisChanges next week I think.16:00
smcginnisI plan to start now.16:00
smcginnis#startmeeting releaseteam16:00
openstackMeeting started Thu Apr 11 16:00:13 2019 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: smcginnis ttx dhellmann diablo_rojo hberaud evrardjp fungi armstrong16:00
evrardjpo/16:00
smcginnis#link https://etherpad.openstack.org/p/stein-relmgt-tracking Agenda16:00
ttxo/16:00
fungialoha16:00
diablo_rojoo/16:00
smcginnis#topic Release Postmortem16:00
*** openstack changes topic to "Release Postmortem (Meeting topic: releaseteam)"16:01
dhellmanno/16:01
ttxAny objection to approving https://review.openstack.org/#/c/650173 now?16:01
smcginnisI think overall the final release went well. A few items yet to wrap up.16:01
smcginnisevrardjp had a comment on there.16:01
smcginnisThese were supposed to have happened with the final cwi release, so I don't think we need to wait for any PTLs on that.16:02
evrardjpit's fine16:02
ttx++16:02
evrardjpyeah we don't need to wait16:02
ttxsmcginnis: you do it or should i?16:02
evrardjpI am not sure why I am always careful in those branching cases :)16:02
*** hberaud is now known as hberaud|gone16:02
smcginnisttx: Feel free to take care of that.16:02
ttxdone16:02
smcginnisevrardjp: It's good to be careful earlier on. Really a pain if your repo gets branched and suddenly you realize you need to backport a bunch of things in a time crunch.16:03
smcginnisAt this point though...16:03
ttxnext up is two release page cleanups16:03
smcginnisI can approve those. Unless dhellmann wanted a chance to look?16:03
smcginnis#link https://review.openstack.org/#/c/651551/16:04
smcginnis#link https://review.openstack.org/#/c/651549/16:04
smcginnisOK, I'll approve.16:05
smcginnisttx: Want to talk about Post-release tasks?16:05
ttxsure16:05
ttxthere were a couple lines above though16:06
ttx    Are we all done ?16:06
ttx    Anything missing in the process ?16:06
smcginnisOh, stable/stein releases. Sorry, I skipped that. We can circle back.16:06
smcginnisI do think we are ready to init-series for train.16:07
smcginnisI can grab that unless anyone else wants it.16:07
ttxyeah...16:07
ttxOnce the stable branch process16:07
smcginnisYeah16:07
ttxI mean https://review.openstack.org/#/c/650173/ is in16:07
evrardjpI would prefer if you could do it smcginnis , as I am on holiday tomorrow and next week16:07
dhellmannwas the tripleo team ready for branches yet?16:07
smcginnisevrardjp: ack16:08
ttxdhellmann: those were cwi ones16:08
dhellmannok16:08
smcginnisWe haven't done any cycle-trailing ones yet. Well, "we" haven't. I think one or two have been done by those teams.16:08
ttxmaybe was oversight though. We'll soon know16:08
ttxSo yes, init-series once the stable branches are all in16:10
smcginnisOK, back to the stable/stein releases?16:10
ttxthen we have a few stalled requests16:10
ttx    python-searchlightclient 1.5.1 https://review.openstack.org/#/c/649487/16:10
ttx    python-cloudkittyclient 2.1.1 https://review.openstack.org/#/c/650239/16:10
ttxthat we can now unblock. Could also wait for Monday16:10
*** smrcascao has joined #openstack-release16:10
ttxbut I see no reason why16:10
evrardjpI think it would be fine to do it nowadays?16:10
smcginnisNeither assert stable:follows-policy16:11
dhellmannyeah, I'm in favor of going ahead, assuming the releases look right16:11
smcginnisSince they were caught in the end of cycle freeze, migh be good to get them out right away.16:11
evrardjpofc16:11
ttx++16:11
ttxI can push it16:11
ttxdone16:11
smcginnisOK, on to ocata EM.16:12
smcginnisI broke out the openstack-ansible ones from the main patch. Since they always have to be so difficult. :P16:12
evrardjpha!16:12
smcginnishttps://review.openstack.org/#/c/650467/ and https://review.openstack.org/#/c/651778/16:12
smcginnisWe switched to EM about a year ago. But the docs said we would tag them but we never did that part.16:13
dhellmanndid we tag one final release on all of those before the em? or are we assuming that whatever was there is good enough?16:13
smcginnisI think we had declared them EM, just never tagged them.16:13
smcginnisIIRC, it was on the ML.16:13
dhellmannwhat I mean is, are we tagging at a point that means we have unreleased changes in any of those branches?16:13
ttxyes that is the big question16:14
smcginnisI did not check, but we had already said we would not be doing any more releases at this point. So if there are, I would consider those commits as part of that extended maintenance work.16:14
ttxthat makes sense16:15
ttxit's not lost. It's just EM16:15
dhellmannok16:15
dhellmannjust thinking through what we discussed the other day on the review for changes to the tool that adds the tags16:15
evrardjpit's kinda weird for OSA though, because we are tagging really old things.16:15
evrardjpI have to think about that16:15
smcginnisdhellmann: That was updated to tag -eol at the latest commit and not that last tag's commit.16:16
dhellmannyeah, we also discussed the em tagging policy in there16:16
smcginnisevrardjp: Yeah, all of these are really old at this point.16:16
smcginnisSince we can't release once we are in em, I think the em tag needs to be at the final release.16:16
dhellmannthe osa case is definitely unique. I wonder if we need an em policy setting, like we have for branching, to tell us the type of location allowed16:17
openstackgerritMerged openstack/releases master: Add missing stable/stein branches  https://review.openstack.org/65017316:17
openstackgerritMerged openstack/releases master: Clean up failed releases  https://review.openstack.org/65154916:17
dhellmannor at least  whether to use HEAD or $last-tag16:17
openstackgerritMerged openstack/releases master: Do not generate tarball links for tripleo-ui  https://review.openstack.org/65155116:17
smcginnisAnything after that point is unreleasable.16:17
smcginnisIf we tag em a few commits after the last release, those commits are kind of in a limbo.16:17
dhellmannI agree, mostly, that em should tag the latest release. I'm not sure we want to tag ancient releases, though.16:17
evrardjposa is very weird because also we stopped tagging because the people stopped caring. But sending and EM to these old versions send a wrong message IMO16:18
dhellmannright16:18
evrardjpwhile the openstack-ansible repo one is correct16:18
evrardjpI will request a release tomorrow latest for just this branch, if it's fine with everyone16:18
evrardjpso that we can use those new shas for em16:18
dhellmannat some point osa won't even have tags on some of those repos, so we need to think about how to handle that case16:18
evrardjpsorry for being late16:18
ttxsmcginnis: you were right about them being difficult :P16:18
evrardjpttx: :D16:18
smcginnisSo I would abandon the osa one I have, then you would propose one just for the single repo evrardjp?16:19
evrardjpsmcginnis: correct16:19
smcginnisttx: ;)16:19
smcginnisOK, that works for me.16:19
dhellmannI think we want to tag all the osa repos. The main one should be tagged at its most recent release. The others should be tagged at their HEAD.16:19
smcginnisI would still think their last tag, not HEAD.16:20
evrardjpdhellmann: correct16:20
*** ianychoi has quit IRC16:20
dhellmannwhen stein (or train) goes EM, those OSA repos won't have any version tags at all but we still want to tag them EM16:20
dhellmannbecause we're no longer tagging versions in some of those repos16:20
evrardjpthat's my plan, create a late release with HEAD on those repos, and then use those for EM16:20
smcginnisIf a repo doesn't have tags, then I don't think it needs -em.16:20
evrardjpsmcginnis: but they had tags :)16:20
dhellmannhmm16:20
smcginnisIn the case of ocata, it doesn't seem right to tag a point -em if it hasn't been "released".16:21
dhellmannI guess I thought we wanted to mark everything at once, but if we don't care about marking tagless repos then mayb enot16:21
dhellmannit has been released, though16:21
smcginnisOnce we get to the point where there were no releases done at all, I don't think we need an em tag.16:21
dhellmannthe fact that there's no tag doesn't mean it isn't released in this case16:21
dhellmannit is effectively "vendored" in that main repo16:21
dhellmannbecause that includes the SHA of the commit from each of the other repos to use16:22
evrardjpyeah, so what we could do is to just EM the openstack-ansible repo16:22
dhellmannyeah, ok16:22
evrardjpthat would be enough too16:22
evrardjpbecause it doesn't set a wrong expectations in the roles16:22
openstackgerritMerged openstack/releases master: Release python-searchlight client 1.5.1 for stein  https://review.openstack.org/64948716:22
evrardjp(other repos)16:22
openstackgerritMerged openstack/releases master: Releasing python-cloudkittyclient 2.1.1  https://review.openstack.org/65023916:22
smcginnisopenstack-ansible controls what from those other repos is used, right?16:22
evrardjpcorrect16:22
smcginnisYeah, then I would think we would only tag openstack-ansible.16:22
evrardjpand we are not using tags.16:22
dhellmannwhat is the point of adding the em tags at all? it's to communicate that the *repo* is closed to certain types of changes and to releases, right?16:23
ttxyes16:23
evrardjpso this is why I think the em tags still apply in this case dhellmann16:23
dhellmannso if we don't tag all of the repos, we're not sending the message about being closed to certain types of changes in those repos16:23
evrardjpso two choices: either just do openstack/openstack-ansible as EM and ignore the rest, or do everything on all repos.16:23
dhellmannor to the testing requirements, or whatever else we're changing for that repo when we go to em16:24
dhellmannI think we should tag them all, but I don't feel strongly enough about it to fix the tool to let us do that, so :-)16:24
evrardjpI believe it's semantically more correct to do what dhellmann said and propose earlier16:24
evrardjpdhellmann: but can't I propose a last minute release before we do EM?16:24
smcginnisSo if release-model:untagged, the tool should grab HEAD. Otherwise, use the commit from the last release. Does that make sense?16:25
dhellmannthat only helps if you tag all of the repos. which I guess would be another approach16:25
dhellmannsmcginnis : yeah, that's effectively what I'm saying16:25
smcginnisevrardjp: Not for ocata. It is already in em.16:25
evrardjpsmcginnis: I see, I missed the timeframe16:25
smcginnisWe just never followed through with the tagging.16:25
smcginnisPike on the other hand...16:25
smcginnisThat was supposed to have transitioned at the beginning of March, but we have a little time yet.16:26
smcginnisdhellmann: OK, I'll put it on my todo to update the new-release tool to handle that for the future.16:26
dhellmannk16:26
evrardjpI think that's fair16:27
smcginnisSo I will abandon my osa tagging patch for now. evrardjp will follow up with the "correct" tagging for those repos.16:27
evrardjpI am sorry to say that ttx prophecy was correct16:27
smcginnishehe16:27
smcginnisOK, one more monkey wrench.16:29
smcginnisopenstack-ansible ocata was not tagless. Still allow it?16:29
dhellmannallow?16:29
smcginnisIf we tag HEAD for tagless and last release otherwise, at least as of the state during ocata, what I have up there now is "correct".16:30
smcginnisBut knowing those eventually ended up tagless, we could retroactively apply that to ocata.16:30
dhellmannif all the repos were always tagged for ocata, we should use the tags. but iirc, that was when we did this transition? so in that case I think we want to recon it16:31
dhellmanner, retcon16:31
evrardjpI am not sure when we did this, it was in the MLs. At that time we said we couldn't touch the deliverables files though16:31
evrardjpso we couldn't remove all the repos from those older branches16:32
evrardjpThe solution was, for the future, create a tagless file for the future16:32
smcginnisOK, let's just stick with that last plan. I've abandoned mine. evrardjp can propose a new one treating those other repos as tagless.16:33
evrardjpbut because we didn't touch the old deliverables files, we just said to "just not tag there"16:33
evrardjpI don't like us to be _special_16:33
dhellmannlooking at that deliverable file, I see all the repos being tagged up to 15.1.21, and then only openstack/openstack-ansible being tagged after that16:34
smcginnisAnd now we have validation that complains if you try to do a release and don't include all repos. But that should be fine if you tag HEAD for the ones not released. Just takes a little manual editing.16:34
evrardjpso it's probably in that two week window dhellmann16:34
*** zbr has quit IRC16:34
dhellmannyeah16:34
ttxopenstack-ansible is ... special, Mrs. Gump.16:34
smcginnis:D16:34
evrardjpttx: :)16:34
evrardjpRun ttx , run16:34
smcginnisAre any of the other deliverables in https://review.openstack.org/#/c/650467/ as "special" as osa? :)16:35
dhellmannhttps://media.giphy.com/media/3oriNLnYCrAj1Rg7qE/giphy.gif16:35
dhellmannI think osa is the only snowflake for this case16:35
smcginnisSo then we should be able to finish that tagging for the rest of those.16:36
dhellmann+116:36
evrardjpagreed16:36
ttx++16:36
smcginnisI'll leave it up to y'all to +2+W that then. ;)16:36
dhellmannI've +2ed that on faith, smcginnis :-)16:36
*** jpich has quit IRC16:37
smcginnishah16:37
smcginnis#topic Preparing for train16:37
*** openstack changes topic to "Preparing for train (Meeting topic: releaseteam)"16:37
smcginnisI did ping Tony yesterday about the script we use for setting up the tracking etherpad.16:38
smcginnisHe has that on his todo list to get set up. Checking this morning, looks like it didn't make it to the top of his todo's yet.16:38
smcginnisWhen we moved to storyboard for tracking things, we stopped doing the planning etherpad. I did not do one for stein.16:39
smcginnisI think that has worked out.16:39
*** dave-mccowan has quit IRC16:39
dhellmanndo we have a ptg planning etherpad?16:39
dhellmannor "agenda" or whatever?16:39
ttxWe don;t have that yet16:40
smcginnisI know Tony has mentioned it, but I have not seen one.16:40
dhellmannok16:40
ttxBut we have a bunch of topics16:40
diablo_rojohttps://wiki.openstack.org/wiki/PTG/Train/Etherpads <-- according to that not yet16:40
dhellmannI know we have some things at the bottom of the stein tracking page16:40
ttxat the bottom of https://etherpad.openstack.org/p/stein-relmgt-tracking16:40
*** zbr has joined #openstack-release16:40
ttx(personally I find it good that we don;t have that many things to discuss, means the process is now more solid16:41
smcginnisI'll throw https://etherpad.openstack.org/p/relmgmt-train-ptg in that wiki list and we can start putting some thing there.16:41
dhellmannttx: +1 - less change is good here16:41
evrardjpI would say let's wait for PTLs/release liaisons feedbacks?16:41
ttxcopy pasted16:41
smcginnisAdded to wiki16:42
evrardjpteam team team!16:42
diablo_rojotechnically cut pasted ;)16:42
smcginnis#topic PTG org16:43
*** openstack changes topic to "PTG org (Meeting topic: releaseteam)"16:43
smcginnisNotes from Tony in the etherpad.16:43
smcginnisFriday morning as a meetup time.16:43
diablo_rojo+2 for Friday morning16:43
smcginnisI think that works for me.16:43
smcginnisI've been mentally blocking actually thinking about my schedule for the week.16:44
diablo_rojosmcginnis, lol yeah I bit the bullet and did it a couple days ago16:44
*** ricolin has quit IRC16:44
diablo_rojoits quite painful16:44
smcginnisttx, dhellmann: Do you know if Friday morning will work for your schedules?16:44
dhellmannI think so16:45
smcginnisOK, if anyone has a conflict, I guess let Tony know ASAP.16:45
dhellmannoh, the ptg stuff isn't on my calendar yet. does someone have the link to the schedule handy?16:45
smcginnisThe team photo is also scheduled for Friday morning.16:45
dhellmannI expect to be spending most of my time with ironic16:45
diablo_rojodhellmann, https://www.openstack.org/ptg#tab_schedule16:46
dhellmannthanks16:46
diablo_rojono problem :)16:46
ttxOK reorganized topics in a way that makes sense16:46
dhellmannyeah, I should be available friday morning16:46
smcginnisPretty much all teams are meeting Friday. I don't think it's possible not to have conflicts in the 3 days of this event.16:46
smcginnisLast thing in there, Tony was asking about a team dinner.16:47
smcginnisI would love it if we can all make it out to a dinner again.16:47
ttxcould make for a calm dinner for Friday evening16:48
smcginnisI think the only set evening plan I have so far is Monday night.16:48
diablo_rojoThursday is the happy hour so we could go to dinner after that,16:48
smcginnisFriday night should be good for me.16:48
diablo_rojottx, Friday night is when the game night was gonna maybe be16:48
ttxOOOOH16:48
ttxthen no16:48
dhellmannyeah, small group calm friday or sat after such a long week would be good16:48
smcginnisI leave Saturday evening, so that's the only PTG night that will not work.16:48
dhellmannah16:48
diablo_rojoSaturday works for me16:48
diablo_rojoWednesday night?16:49
smcginnisThursday night might be a good way to prep for Friday morning.16:49
dhellmannmy dance card is completely empty at this point, so whenever16:49
smcginnisHow about this, each of us add a line under that item in the etherpad with the nights we are available? Then tonyb can figure something out.16:50
dhellmann++16:50
*** dtantsur is now known as dtantsur|afk16:50
diablo_rojo+216:50
smcginnis#topic Meeting time16:51
*** openstack changes topic to "Meeting time (Meeting topic: releaseteam)"16:51
ttxIt changes !16:51
smcginnisLast thing - I think it is official now. Meeting time will be moving to 1900.16:51
dhellmannthere was a review to change that, right?16:52
smcginnisProbably about as good as we can get for all the timezones involved.16:52
ttxyes merged now16:52
smcginnishttps://review.openstack.org/#/c/651443/16:52
ttxsome diligent meetings-core person16:52
smcginnis:)16:52
ttxbtw...16:53
ttxif someone else wants to be meetings-core, we recruit16:53
evrardjphaha16:53
smcginnisI would imagine that's pretty low volume.16:53
smcginnisI can try to watch for things there if you want to add me to the list.16:53
ttxIt is so awesome you would not believe16:53
smcginnis:D16:53
evrardjpttx: :)16:53
evrardjpI am wondering what the duties are, with a name like this16:54
diablo_rojottx, if you want another set of hands you can add me to the list too16:54
smcginnismeetings-core must attend every meeting though. :)16:54
evrardjpsmcginnis: isn't that what you are already doing?16:54
smcginnisYou don't actually work on any projects, you just attend all of their meetings.16:54
ttxwell to be fair, I just process them all when they arrive. Could switch to some recview day set up though16:54
smcginnisHah!16:54
smcginnisttx: There's check validation that makes sure a propose meeting move doesn't conflict with another meeting ,right?16:55
dhellmannttx: bot approval?16:55
evrardjplet's discuss this outside the meeting?16:55
smcginnisYeah16:55
ttxdhellmann: we still check things.16:55
smcginnis#topic Open floor16:55
*** openstack changes topic to "Open floor (Meeting topic: releaseteam)"16:55
smcginnisAny final things?16:55
evrardjpnone16:55
smcginnisThis will be my last meeting. tonyb will take if from here.16:55
ttxdhellmann: Like if the PTL is the person asking for it, if there was a thread about it, etc16:55
dhellmannack16:55
dhellmannthank you, smcginnis , for taking the helm again this past cycle!16:56
dhellmannthings went quite smoothly, I think16:56
diablo_rojothanks smcginnis for all your hard work :)16:56
smcginnisThank you all for all the work this cycle and all the work prior to that that made it easy to step in and figure things out.16:56
ttxI wonder what he will now do with all his free time. Apart from meetings-core16:56
smcginnishaha16:56
ttxand fearless Board member16:57
smcginnisOK, I guess we can wrap things up then. Thank you everyone!16:57
smcginnis#endmeeting16:57
*** 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:57
openstackMeeting ended Thu Apr 11 16:57:15 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/releaseteam/2019/releaseteam.2019-04-11-16.00.html16:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/releaseteam/2019/releaseteam.2019-04-11-16.00.txt16:57
ttxThanks smcginnis16:57
openstackLog:            http://eavesdrop.openstack.org/meetings/releaseteam/2019/releaseteam.2019-04-11-16.00.log.html16:57
fungithanks!16:58
*** v12aml has quit IRC17:00
*** armstrong has quit IRC17:04
*** pcaruana has joined #openstack-release17:05
diablo_rojoPhoto is at 10:0017:06
diablo_rojofor reference I added the sign up ethercalc to the stein eitherpad17:06
*** v12aml has joined #openstack-release17:10
EmilienMsmcginnis:17:11
EmilienMhi17:11
*** ekcs has joined #openstack-release17:11
EmilienMwhy did you folks approve https://review.openstack.org/#/c/650173/ without consulting tripleo folks17:11
EmilienMit's probably missing commits from master for os-net-config17:12
EmilienMttx: ^17:13
*** amoralej is now known as amoralej|off17:21
*** ykarel|away has quit IRC17:21
EmilienMsame for paunch and tripleo-validations :-/17:25
EmilienMsmcginnis: I need branch removal for tripleo projects, this patch isn't good for us17:25
EmilienMwe are still working on critical bugs for stein17:26
*** jtomasek has quit IRC17:37
*** ykarel|away has joined #openstack-release17:39
fungii wonder if those deliverables should be switched to cycle-trailing17:44
fungiif they're not actually expected to be ready when the rest of the normal cycle deliverables release17:45
*** ykarel|away has quit IRC17:53
*** bobh has quit IRC17:58
smcginnisEmilienM: Are those deliverables mis-labelled?18:02
openstackgerritGorka Eguileor proposed openstack/releases master: Release cinderlib 0.9.0 and cut stein  https://review.openstack.org/65189518:02
smcginnisEmilienM: Deadline for cycle-with-intermediary is way past and those were overdue for branching.18:02
EmilienMI'm lost with these labels, tbh18:03
EmilienMand i don't understand why we keep changing them every cycle18:03
EmilienMto me, tripleo is trailing cycle and always behind regular projects, and lag in release18:03
*** bobh has joined #openstack-release18:03
smcginnisEmilienM: Well, either something is cycle-trailing and it doesn't get released and branched until after the cycle is over, or it's not and the final release yesterday should have been *after* last release and branching.18:04
smcginnisThe ones that were branched were not cycle-trailing.18:04
EmilienMright and I don't understand why18:04
smcginnisWhat part?18:05
EmilienMwhy they aren't cycle trailing18:05
EmilienMwe really need to remove the branches for those18:05
EmilienMwe're missing a bunch of bug fixes18:05
smcginnisBecause the team didn't mark them as such.18:05
EmilienMand I don't want to backport 20 patches18:05
EmilienMfair enough, it's a issue on our side18:06
EmilienMbut I wish I would have been in the loop for this patch18:06
smcginnisfungi: If we merge a patch to change those things to cycle-trailing and remove the branching, can you manually delete the branches?18:06
smcginnisEmilienM: Well, we can't second guess teams every cycle whether they've declared their release models the way they want or not.18:07
fungisure, as long as there are no open changes on them18:07
EmilienMok so I need to close them all18:07
EmilienMdoing it now18:07
smcginnisEmilienM: You're going to propose the patch mentioned above? ^18:08
EmilienMsmcginnis: yes, I'll take care of a partial revert and changing the cycle mode18:08
clarkbif you've already done backports why undo all of that?18:09
EmilienMthey aren't merged18:09
smcginnisOK, I'll watch for that patch.18:09
fungibut yeah, gerrit won't allow deletion of a branch with open changes18:09
EmilienMfungi: right18:09
EmilienMsorry for the mess ...18:09
fungiand i'll need a list of the repositories for which we need stable/stein branches deleted18:10
smcginnisI'll add you to the patch updating that.18:10
*** bobh has quit IRC18:13
*** gmann is now known as gmann_afk18:15
*** bobh has joined #openstack-release18:16
openstackgerritEmilien Macchi proposed openstack/releases master: TripleO: change release-model for some repos  https://review.openstack.org/65189818:17
openstackgerritEmilien Macchi proposed openstack/releases master: Partial revert "Add missing stable/stein branches"  https://review.openstack.org/65189918:17
EmilienMsmcginnis: ^18:17
openstackgerritEmilien Macchi proposed openstack/releases master: Partial revert "Add missing stable/stein branches"  https://review.openstack.org/65189918:17
EmilienMsmcginnis: I'll follow up next week with RC1 and branch probably18:17
*** ykarel|away has joined #openstack-release18:18
smcginnisOK, sounds good. I'll get these through as soon as they pass.18:18
smcginnisfungi: There are the lists of repos. ^18:18
*** electrofelix has quit IRC18:19
fungiperfect, will delete them now18:20
smcginnisEmilienM: I'm going to squash those into one. Otherwise we risk recreating the branches.18:21
smcginnisfungi: Or, do you want to wait for the first one to go through changing the model?18:21
EmilienMok18:21
fungismcginnis: i can pause18:22
fungistill in the process of getting them pulled up in gerrit anyway18:22
smcginnisOK, I'll push through the first one that still contains the branches. Then give you the green light to delete, then merge the patch that removes them from the deliverables.18:23
fungiperfect18:24
*** tosky has quit IRC18:26
smcginnisEmilienM: Do you recall why you switched the release model for those here: https://review.openstack.org/#/c/561655/18:32
EmilienMsmcginnis: I think we were in a bar and gin tonic was involved18:34
smcginnisHah. Guess that wouldn't be the first time if so. :)18:34
EmilienMLOL18:34
EmilienMTBH I don't remember :-/18:34
fungithat's my preferred method of introducing bugs ;)18:34
EmilienMand it was probably a mistake on my side18:34
EmilienMthe thing is, I don't want to branch to early in tripleo because otherwise we end up sending a lot of backports and wasting CI18:35
smcginnisThey did release and branch by the c-w-i deadline in rocky.18:35
fungiokay, i've got all the deletions queued up so ready to go once you give the word18:35
smcginnisGreat. First change is in the gate queue now.18:36
smcginnisAs soon as the makes it all the way through, I'll wait for confirmation on deletion and push through the second one.18:36
openstackgerritMerged openstack/releases master: TripleO: change release-model for some repos  https://review.openstack.org/65189818:46
fungismcginnis: so, safe to go ahead now?18:50
fungi651898 merged 4 minutes ago18:50
smcginnisIt's running the tag-releases job right now. Should probably wait for that to complete to be safe.18:50
fungiahh, okay will do18:50
smcginnisfungi: OK, looks like it's wrapping up now. You are clear for takeoff.18:55
fungistarting now18:55
fungiand done18:56
smcginnisAnd next patch on its way. Thanks!18:57
fungiEmilienM: please double-check that the expected 8 stable/stein branch deletions are showing up for you18:57
*** pcaruana has quit IRC19:02
openstackgerritMerged openstack/releases master: Partial revert "Add missing stable/stein branches"  https://review.openstack.org/65189919:10
openstackgerritSean McGinnis proposed openstack/releases master: new-release: Handle em for untagged repos  https://review.openstack.org/65190919:10
*** e0ne has joined #openstack-release19:11
smcginnistag-releases completed for the branch removal tag. Spot check of repos looks good.19:20
fungismcginnis: EmilienM: one thing i noticed in handling these branch deletions... openstack/tripleo-ipsec never got a stable/rocky branch either, its only branches are master and stable/queens19:23
*** gmann_afk is now known as gmann19:27
*** e0ne has quit IRC19:31
openstackgerritSean McGinnis proposed openstack/releases master: Add Train deliverable files  https://review.openstack.org/65191619:40
*** ykarel|away has quit IRC20:07
openstackgerritCarlos Goncalves proposed openstack/releases master: Release Octavia Queens 2.1.0 and Rocky 3.1.0  https://review.openstack.org/65147520:32
*** whoami-rajat has quit IRC21:03
*** tosky has joined #openstack-release21:29
*** bobh has quit IRC22:10
*** tosky has quit IRC22:15
openstackgerritBrian Rosmaita proposed openstack/releases master: Release os-brick 1.15.9  https://review.openstack.org/65193622:25
EmilienMfungi: weird cc mwhahaha22:29
EmilienMI guess we just package it from latest tag or something22:29
mwhahahaprobably got missed for that release22:29
mwhahahaclearly we don't backport much to it22:30
*** cdent has quit IRC23:05
*** tbarron has quit IRC23:21
*** N3l1x has quit IRC23:21
*** prometheanfire has quit IRC23:21
*** tobias-urdin has quit IRC23:21
*** corvus has quit IRC23:21
*** mgoddard has quit IRC23:24
*** mgoddard has joined #openstack-release23:27
*** tbarron has joined #openstack-release23:27
*** N3l1x has joined #openstack-release23:27
*** prometheanfire has joined #openstack-release23:27
*** tobias-urdin has joined #openstack-release23:27
*** corvus has joined #openstack-release23:27

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