| *** dave-mccowan has quit IRC | 00:00 | |
| *** evrardjp has quit IRC | 00:04 | |
| *** evrardjp has joined #openstack-release | 00:05 | |
| *** brinzhang has joined #openstack-release | 00:14 | |
| *** armax has quit IRC | 01:40 | |
| *** tinwood has quit IRC | 02:08 | |
| *** tinwood has joined #openstack-release | 02:11 | |
| *** ianychoi__ has joined #openstack-release | 03:22 | |
| *** ianychoi_ has quit IRC | 03:25 | |
| *** mrdoug has joined #openstack-release | 04:50 | |
| *** mrdoug has quit IRC | 04:55 | |
| *** mrdoug has joined #openstack-release | 04:55 | |
| *** mrdoug_ has joined #openstack-release | 04:56 | |
| *** mrdoug_ has quit IRC | 04:57 | |
| *** whoami-rajat__ has joined #openstack-release | 04:57 | |
| *** mrdoug has quit IRC | 04:58 | |
| *** mrdoug has joined #openstack-release | 04:59 | |
| *** ykarel has joined #openstack-release | 05:03 | |
| *** evrardjp has quit IRC | 05:33 | |
| *** evrardjp has joined #openstack-release | 05:33 | |
| *** sboyron has joined #openstack-release | 07:50 | |
| *** slaweq has joined #openstack-release | 08:06 | |
| *** rpittau|afk is now known as rpittau | 08:37 | |
| *** tosky has joined #openstack-release | 08:39 | |
| *** vishalmanchanda has joined #openstack-release | 09:01 | |
| *** dtantsur|afk is now known as dtantsur | 10:02 | |
| *** elod has quit IRC | 11:01 | |
| *** elod has joined #openstack-release | 11:02 | |
| *** mrdoug has quit IRC | 11:17 | |
| *** icey has quit IRC | 13:09 | |
| *** icey has joined #openstack-release | 13:11 | |
| *** e0ne has joined #openstack-release | 13:20 | |
| *** vishalmanchanda has quit IRC | 13:30 | |
| *** e0ne has quit IRC | 13:33 | |
| *** diablo_rojo has joined #openstack-release | 13:54 | |
| *** brtknr has quit IRC | 13:57 | |
| *** irclogbot_1 has quit IRC | 14:09 | |
| *** irclogbot_0 has joined #openstack-release | 14:13 | |
| *** e0ne has joined #openstack-release | 14:23 | |
| *** dave-mccowan has joined #openstack-release | 14:37 | |
| *** slaweq has quit IRC | 14:37 | |
| *** slaweq has joined #openstack-release | 14:40 | |
| *** dave-mccowan has quit IRC | 14:42 | |
| *** e0ne has quit IRC | 14:44 | |
| *** e0ne has joined #openstack-release | 14:45 | |
| *** e0ne has quit IRC | 14:45 | |
| *** armax has joined #openstack-release | 15:09 | |
| *** diablo_rojo has quit IRC | 15:11 | |
| *** slaweq has quit IRC | 15:22 | |
| *** slaweq has joined #openstack-release | 15:28 | |
| openstackgerrit | Hervé Beraud proposed openstack/release-test master: Add doc/requirements https://review.opendev.org/c/openstack/release-test/+/769775 | 15:50 |
|---|---|---|
| nicolasbock | Hi! Who can add me to the designate stable release core group? | 15:54 |
| hberaud | good question, what's the context? | 15:54 |
| nicolasbock | I am core in the designate projects | 15:55 |
| nicolasbock | But that doesn't cover my reviews for the stable branches | 15:55 |
| nicolasbock | In other words I can't approve backports | 15:55 |
| hberaud | it's more a stable branch topic | 15:55 |
| nicolasbock | I couldn't find an iRC channel that had the term 'stable' in it :) | 15:56 |
| hberaud | #openstack-stable | 15:56 |
| nicolasbock | So maybe this is not the right place to ask this question | 15:56 |
| nicolasbock | Oh | 15:56 |
| nicolasbock | That was easy :) | 15:56 |
| hberaud | lol | 15:56 |
| nicolasbock | Thanks hberaud ! | 15:56 |
| hberaud | nicolasbock: I would suggest to ask there first and if nobody respond to you then do not hesitate to come back here :) | 15:57 |
| hberaud | nicolasbock: you are welcome | 15:57 |
| nicolasbock | Thanks! I just asked there. Let's see if I get a response :) | 15:58 |
| hberaud | ack | 15:58 |
| *** armstrong has joined #openstack-release | 16:02 | |
| * diablo_rojo_phon sneaks in a bit late | 16:08 | |
| diablo_rojo_phon | No meeting today? | 16:09 |
| hberaud | In 1 hour | 16:09 |
| hberaud | 5pm UTV | 16:09 |
| hberaud | UTC | 16:09 |
| armstrong | @diablo_rojo_phon: you sneaked in too early :) | 16:10 |
| hberaud | :) | 16:10 |
| *** ykarel has quit IRC | 16:12 | |
| diablo_rojo_phon | Oh oops. | 16:21 |
| diablo_rojo_phon | That's two meetings today I've been off by an hour for. | 16:22 |
| hberaud | np | 16:23 |
| *** elod has quit IRC | 16:40 | |
| *** elod has joined #openstack-release | 16:40 | |
| fungi | just a heads up, we had an afs server get stuck in a pathological way from 05:50 utc today until 16:10 utc when we hard rebooted the server instance. this would have impacted things like tarball uploads and release note publication. doesn't look like any release requests merged in that timeframe but if you find something which needs to be rerun, just let me know | 16:48 |
| openstackgerrit | Merged openstack/releases master: Release kolla deliverables Victoria RC2 https://review.opendev.org/c/openstack/releases/+/769322 | 16:55 |
| hberaud | fungi: ack thanks for the heads up | 16:57 |
| hberaud | #startmeeting releaseteam | 17:00 |
| openstack | Meeting started Thu Jan 7 17:00:18 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 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 17:00 |
| *** openstack changes topic to " (Meeting topic: releaseteam)" | 17:00 | |
| hberaud | #link https://etherpad.opendev.org/p/wallaby-relmgt-tracking Agenda | 17:00 |
| ttx | o/ | 17:00 |
| openstack | The meeting name has been set to 'releaseteam' | 17:00 |
| hberaud | Ping list: ttx armstrong elod | 17:00 |
| armstrong | o/ | 17:00 |
| hberaud | We're way down on line 194 now. | 17:00 |
| hberaud | Will just wait a couple minutes for folks. | 17:00 |
| *** diablo_rojo has joined #openstack-release | 17:01 | |
| openstackgerrit | Merged openstack/releases master: Release kolla deliverables for Ussuri https://review.opendev.org/c/openstack/releases/+/769324 | 17:01 |
| openstackgerrit | Merged openstack/releases master: Release kolla deliverables for Train https://review.opendev.org/c/openstack/releases/+/769325 | 17:01 |
| elod | o/ | 17:01 |
| diablo_rojo | o/ | 17:01 |
| hberaud | Let's just start by saying welcome back and happy new year to everyone, I hope you enjoyed your end of the year parties | 17:02 |
| ttx | socially-distanced of course | 17:02 |
| hberaud | lol | 17:02 |
| elod | :) | 17:02 |
| fungi | virtuparty | 17:02 |
| diablo_rojo | I am so over virtual anything lol | 17:03 |
| hberaud | So let's go! | 17:04 |
| hberaud | #topic Assign R-13 tasks | 17:04 |
| *** openstack changes topic to "Assign R-13 tasks (Meeting topic: releaseteam)" | 17:04 | |
| hberaud | So next week will be the Victoria Cycle-Trailing Release Deadline | 17:04 |
| hberaud | All projects following the cycle-trailing release model must release their Victoria deliverables by 14 January, 2021. | 17:04 |
| * ttx checks current status | 17:05 | |
| hberaud | I think it could be worth to send a friendly reminder | 17:05 |
| openstackgerrit | Dmitry Tantsur proposed openstack/releases master: Release ironic-python-agent-builder 2.4.0 https://review.opendev.org/c/openstack/releases/+/769802 | 17:05 |
| hberaud | Any volunteer? | 17:05 |
| ttx | a bunch have RCs already | 17:05 |
| ttx | I think it's good if it comes from the release manager. More intimidating and all | 17:06 |
| hberaud | I didn't verified but I agree it could be worth to check before | 17:06 |
| hberaud | You're right | 17:06 |
| hberaud | I'll check and send! | 17:06 |
| hberaud | the second thing was "Ahead of MembershipFreeze, run governance_consistency.py" but I see that ttx & armstrong are already on it, thanks! | 17:07 |
| ttx | armstrong: we could sync on Monday about that? | 17:08 |
| ttx | hmm wait, my schedule is a bit busy | 17:08 |
| armstrong | sounds good to me | 17:08 |
| ttx | early in the day for you would be good (early afternoon for me) | 17:08 |
| armstrong | @ttx anytime next week looks good to me | 17:08 |
| ttx | Monday 14UTC? | 17:08 |
| armstrong | @ttx Yes | 17:09 |
| ttx | ok, meet here if you need help :) | 17:09 |
| armstrong | ok | 17:09 |
| hberaud | Then I think we can move the next topic | 17:09 |
| hberaud | *to | 17:10 |
| hberaud | #topic EM for branchless projects | 17:10 |
| *** openstack changes topic to "EM for branchless projects (Meeting topic: releaseteam)" | 17:10 | |
| hberaud | Do we want to continue with EM for branchless projects? | 17:10 |
| hberaud | elod voluntary ignored them, and some of us think that this mixing concept that are separated | 17:10 |
| ttx | I think gmann made a good rationale about why we should accept them | 17:10 |
| elod | actually not just voluntarily but the validator failed if I remember correctly :) | 17:10 |
| ttx | I don't have enough brain cells right now to question the status quo | 17:11 |
| hberaud | elod: Ah sorry I misunderstood | 17:11 |
| hberaud | I'm not against that, it was already did during previous cycle (c.f queens) | 17:11 |
| ttx | one issue is that the patch chain looks weird | 17:11 |
| ttx | (Indirect ancestor and all) | 17:11 |
| hberaud | ah | 17:12 |
| ttx | so wondering if approving it will not bork all the others | 17:12 |
| hberaud | maybe | 17:12 |
| ttx | fungi: what does indirect ancestor mean? | 17:12 |
| hberaud | another issue is that some of these patch also face the doc issue | 17:12 |
| hberaud | so they need to be rebased on the top of the related patch here => https://review.opendev.org/q/topic:%2522fix-relmgt-pip-doc%2522+(status:open) | 17:13 |
| hberaud | but we will speak about that more deeply in the next topics | 17:13 |
| ttx | ah, a new patchset was posted for it, and now all the patches that were posted on top of it are potentially a problem | 17:13 |
| *** dtantsur is now known as dtantsur|afk | 17:13 | |
| ttx | they will probably need to be rebased | 17:14 |
| hberaud | ok | 17:14 |
| elod | fwiw, if this was done for queens, then it should be approved to stein (and rocky?) as well (of course if the ancestor problem doesn't make any breakage) | 17:14 |
| hberaud | gmann: FYI ^ | 17:14 |
| hberaud | elod: yes make sense | 17:14 |
| fungi | sorry, which change? | 17:15 |
| fungi | is "indirect ancestor" something gerrit is displaying somewhere? | 17:15 |
| ttx | fungi: I think I got it. was https://review.opendev.org/c/openstack/releases/+/768566 | 17:15 |
| hberaud | fungi: https://review.opendev.org/q/topic:%22tempest-plugin-stein-em%22+(status:open%20OR%20status:merged) | 17:15 |
| ttx | it's the inverse of "Not current" | 17:16 |
| fungi | ahh, neat | 17:16 |
| fungi | i don't think i've seen that before | 17:16 |
| ttx | Like Change 2 is stacked on top of patchset 1 of Change 1 | 17:16 |
| ttx | but then you post patchset 2 of Change 1 | 17:16 |
| ttx | Then change 1 will show as "not current" in change 2 | 17:16 |
| ttx | and change 2 will be "indirect ancestor" of change 1 | 17:17 |
| fungi | yep, makes sense, i agree | 17:17 |
| ttx | iiuc | 17:17 |
| ttx | shoudl be safe, but might force rebases for all the patch 2s | 17:17 |
| *** rpittau is now known as rpittau|afk | 17:18 | |
| fungi | gerrit will require them to be rebased anyway, because they have ancestor commits which will never appear in the target branch | 17:18 |
| ttx | With the current state of my brain cells I'll trust gmann and just follow his request | 17:18 |
| ttx | just posted +2 | 17:19 |
| hberaud | So if I summarize, we want to continue with these changes, and we should also update some of our machinery => https://review.opendev.org/c/openstack/releases/+/768566 , is it make sense for everyone? | 17:19 |
| ttx | yeah, avoids validation fail | 17:20 |
| gmann | fungi: ttx hberaud i can rebase once it is merged, at least that would not lose hberaud +2 on plugins releases | 17:20 |
| fungi | gmann: yep, that should work | 17:20 |
| ttx | ok, those need the doc changes before we can process them anyway | 17:20 |
| gmann | ttx: which one? | 17:20 |
| hberaud | ttx: before +2 ensure that repo aren't part of https://review.opendev.org/q/topic:%2522fix-relmgt-pip-doc%2522+(status:open) | 17:21 |
| ttx | most of the *-tempest-plugin fall into http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019612.html | 17:21 |
| gmann | hberaud: I will reply to your comment on 768566, was busy in other things | 17:21 |
| hberaud | ok | 17:21 |
| hberaud | ttx: yes | 17:21 |
| gmann | i see, got it | 17:21 |
| hberaud | and patches are only on master for now | 17:22 |
| hberaud | We will risk to have to reenqueue lot of jobs | 17:23 |
| hberaud | it is problematic... | 17:23 |
| hberaud | gmann: Do you think we could deactivate some job on these branches before moving to EOL? | 17:24 |
| elod | just one question: if we allow EM tagging for branchless repos, is there any other repo that we have to be careful? | 17:24 |
| elod | I mean, e.g. not *tempest-plugin, but other branchless repository | 17:25 |
| elod | if there exists such | 17:25 |
| hberaud | gmann: docs and releasenotes job AFAIK | 17:25 |
| hberaud | gmann: it could solve our issue easily | 17:25 |
| hberaud | and it could be done by using a script | 17:26 |
| fungi | what is em tagging for branchless repos? | 17:26 |
| gmann | hberaud: we had same kind of situation in Ocata time when due to stestr we could not run the unit/integration tests there and then it end up going to EOL | 17:26 |
| gmann | fungi: for tempest and tempest plugins, it will be current master has when branch went to EM means this is last compatible version can work against EM branches code | 17:27 |
| elod | fungi: allowing to tag with *-em, regarding this patch: https://review.opendev.org/c/openstack/releases/+/768566 | 17:27 |
| hberaud | else we could simply assume to ignore all the related failing job... | 17:27 |
| hberaud | (doc & releasenotes job fails only) | 17:28 |
| gmann | hberaud: only issue is we would be backport the doc or releasenotes untested and they are EM so not good. | 17:28 |
| gmann | but at same time we can argue these might be less such changes so as long as we test unit/func/integration we can assume these EM are tested | 17:29 |
| fungi | gmann: elod: what is the benefit of adding the *-em tags to tempest? | 17:30 |
| hberaud | and keep them non-EM? | 17:30 |
| hberaud | gmann: ^ | 17:30 |
| fungi | does tempest extended maintenance differ from when tempest drops support? | 17:30 |
| gmann | hberaud: you mean 'unmaintained' ? | 17:30 |
| gmann | fungi: it will help to find the last compatible version of Tempest for that stable branch | 17:30 |
| hberaud | no I mean not moving to EM | 17:30 |
| fungi | gmann: "extended maintenance" seems like a very confusing term in that case | 17:31 |
| fungi | tempest is ceasing maintenance for that series, not extending it | 17:31 |
| gmann | fungi: i tried to explain these versioning thing for Tempest and plugins here https://docs.openstack.org/tempest/latest/tempest_and_plugins_compatible_version_policy.html | 17:31 |
| gmann | fungi: yeah that is faire point, i used -em along with new version number also so that they can be easily understandable with our stable branch -em tag | 17:32 |
| fungi | gmann: yeah, the support policy makes sense, but calling what tempest is doing "extended maintenance" doesn't really match what it describes | 17:32 |
| hberaud | https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html#testing | 17:33 |
| gmann | hberaud: I think i lost in your comment, 'keep them non-EM?' 'them' you mean current stable branches or EM branches ? | 17:33 |
| fungi | anyway, i don't really have a strong opinion on it, i was simply confused because it initially sounded like you were saying tempest was adding an extended maintenance phase | 17:33 |
| gmann | fungi: or we can say *-eol which will be right thing for Tempest and plugins | 17:34 |
| ttx | AIUI it does not make sense in itself, but is useful to trick the tests to run with the right code | 17:34 |
| hberaud | gmann: np I think I misunderstood you when here "but at same time we can argue these might be less such changes so as long as we test unit/func/integration we can assume these EM are tested" | 17:35 |
| fungi | -eol or -final or -end or something would make more sense, just from a confused user perspective | 17:35 |
| gmann | hberaud: ohk, i mean it for already EM branches. | 17:35 |
| elod | I like -final :) | 17:35 |
| elod | however, usually final things won't be finals ;) | 17:36 |
| hberaud | eol could be an option | 17:36 |
| fungi | -final is usually followed by -really-final and then -no-we-mean-it-this-time-final | 17:36 |
| hberaud | :) | 17:36 |
| elod | that's true :D | 17:36 |
| gmann | one more tricky thing here is other later version of Tempest might work but this tag is last guaranteed working one | 17:36 |
| fungi | it's the last one you tested with it, right | 17:37 |
| gmann | yeah | 17:37 |
| gmann | -last-compatible ? but it is too long | 17:37 |
| fungi | or simply -last | 17:38 |
| hberaud | +1 -last | 17:38 |
| gmann | yeah, that's better | 17:38 |
| elod | -last sounds better to me, too | 17:38 |
| fungi | anyway, this is devolving into bikeshedding, so i'm violating my personal policy of bikeshedding on names for things | 17:38 |
| elod | true, again :) | 17:39 |
| gmann | cool, I will update it with rebase once 768566 is merged for easy update | 17:39 |
| gmann | hberaud: can you check, i replied to your comment - https://review.opendev.org/c/openstack/releases/+/768566 | 17:40 |
| hberaud | What do we do if a pip issue appear with these patches and doc/reno, do we assume to ignore them? | 17:41 |
| * hberaud read | 17:41 | |
| elod | one more thing: if we are not using the -em tag for this, then we don't need the validator modification patch either, am I right? | 17:42 |
| hberaud | gmann: ok I'm fine with that, thanks | 17:43 |
| hberaud | elod: I think that yes | 17:44 |
| openstackgerrit | Thierry Carrez proposed openstack/releases master: molteniron does not need releases https://review.opendev.org/c/openstack/releases/+/769597 | 17:44 |
| hberaud | IMO this patch isn't needed anymore if we use -last | 17:45 |
| elod | as 768566 is specially for -em tag | 17:46 |
| hberaud | Yes | 17:46 |
| hberaud | OK, we can get those out after the meeting then. We've other topics to discuss | 17:46 |
| ttx | indeed | 17:46 |
| hberaud | #topic moltiron's abandon, what's the exact process to follow? | 17:47 |
| elod | hberaud: ok, thanks \o/ | 17:47 |
| ttx | the wrong reno should be fixed now? | 17:47 |
| *** openstack changes topic to "moltiron's abandon, what's the exact process to follow? (Meeting topic: releaseteam)" | 17:47 | |
| ttx | OK, I just did work on that | 17:47 |
| hberaud | Yes thanks | 17:47 |
| gmann | hberaud: thanks | 17:47 |
| ttx | So the proper way to express that a deliverable is actually not using releases is... | 17:47 |
| ttx | a release-management: none key in the governance projects.yaml file | 17:47 |
| hberaud | ok | 17:47 |
| ttx | I just proposed it in replacement of this patch | 17:48 |
| ttx | That's the occasion to explain one thing | 17:48 |
| hberaud | awesome thanks (FYI iurygregory) | 17:48 |
| ttx | which is not well documented (I'll fix it) | 17:48 |
| hberaud | ^ | 17:48 |
| hberaud | ack | 17:48 |
| ttx | You can read the commit message on https://review.opendev.org/c/openstack/governance/+/613268 | 17:48 |
| ttx | but basically... | 17:48 |
| iurygregory | hberaud, np =) | 17:48 |
| ttx | The TC gives us a list of official openstack deliverables | 17:48 |
| gmann | hberaud: elod ah yeah, let's discuss 768566 after meeting | 17:49 |
| ttx | by default, the Release management team is tasked with doing release management for all of them | 17:49 |
| ttx | But some are actually not released | 17:49 |
| ttx | and some are released but not by us | 17:49 |
| hberaud | Good to know | 17:49 |
| gmann | ttx: i think there was some script to validate those releade model or it was just manual finding if any mismatch? | 17:49 |
| ttx | those are exceptions that are documented in governance | 17:49 |
| ttx | using the release-management: none and release-management: external keys | 17:49 |
| gmann | i remember you corrected many in past | 17:50 |
| ttx | indeed. We plan to run that script next week | 17:50 |
| gmann | k | 17:50 |
| ttx | as part of the membershipfreeze | 17:50 |
| ttx | Here since the deliverable was never released it's pretty easy | 17:50 |
| ttx | just set the key in governance and remove the deliverable file that should never have been created | 17:50 |
| ttx | But that shows that those keys are not well documented | 17:51 |
| ttx | I'll probably post something to the project-team-guide | 17:51 |
| gmann | +1 | 17:51 |
| hberaud | ack thank | 17:51 |
| ttx | that is all! | 17:51 |
| hberaud | #topic Wrong reno with (22.0.0.0rc1 is a victoria tag marked as unreleased) | 17:52 |
| *** openstack changes topic to "Wrong reno with (22.0.0.0rc1 is a victoria tag marked as unreleased) (Meeting topic: releaseteam)" | 17:52 | |
| hberaud | I missed this topic previously | 17:52 |
| hberaud | This is just a heads up | 17:52 |
| hberaud | the problem have been fixed by https://review.opendev.org/c/openstack/project-config/+/769128 | 17:52 |
| hberaud | #topic Remove misleading error message on our jobs | 17:52 |
| *** openstack changes topic to "Remove misleading error message on our jobs (Meeting topic: releaseteam)" | 17:52 | |
| hberaud | Another heads up | 17:53 |
| hberaud | ttx proposed some changes in our tools to avoid misleading logs | 17:53 |
| hberaud | https://review.opendev.org/c/openstack/project-config/+/769353, so please keep an eye open in the very unlikely case it creates a regression. | 17:53 |
| hberaud | #topic releasenotes/docs jobs issues related to pip's latest resolver, | 17:54 |
| *** openstack changes topic to "releasenotes/docs jobs issues related to pip's latest resolver, (Meeting topic: releaseteam)" | 17:54 | |
| hberaud | And the last but not the least... | 17:54 |
| hberaud | As you surely seen previously during our discussion and on the ML we faced some issues with docs/release c.f http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019611.html | 17:55 |
| hberaud | I asked you to hold our validations for a while | 17:55 |
| fungi | it mostly stems from bugs in projects where they're listing incompatible versions of linters in their test-requirements.txt files | 17:56 |
| hberaud | now all identified repos received fixes, https://review.opendev.org/q/topic:%2522fix-relmgt-pip-doc%2522+(status:open+OR+status:merged) | 17:56 |
| hberaud | However stable haven't been addressed yet | 17:57 |
| hberaud | *branches | 17:57 |
| hberaud | I think we can restart patch valiation but we should take care of the list of projects to see if they are sensitive projects | 17:59 |
| hberaud | else we will have to reenqueue lot of failed jobs. | 18:00 |
| hberaud | we reached the end of the meeting time slot | 18:00 |
| hberaud | #topic open discussion | 18:01 |
| *** openstack changes topic to "open discussion (Meeting topic: releaseteam)" | 18:01 | |
| hberaud | Anything else? | 18:01 |
| ttx | nothing from here | 18:01 |
| elod | neither from me | 18:01 |
| armstrong | nothing from me | 18:01 |
| hberaud | Let's discuss about topics that need more time outside of the meeting slot | 18:01 |
| hberaud | OK, thanks everyone. Let's wrap up. | 18:02 |
| hberaud | #endmeeting | 18:02 |
| *** 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/" | 18:02 | |
| openstack | Meeting ended Thu Jan 7 18:02:23 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 18:02 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/releaseteam/2021/releaseteam.2021-01-07-17.00.html | 18:02 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/releaseteam/2021/releaseteam.2021-01-07-17.00.txt | 18:02 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/releaseteam/2021/releaseteam.2021-01-07-17.00.log.html | 18:02 |
| ttx | thanks hberaud ! | 18:02 |
| elod | thanks! | 18:02 |
| gmann | ttx: hberaud elod I will abandon this as we agreed to use *-last for tempest and plugins - https://review.opendev.org/c/openstack/releases/+/768566 | 18:02 |
| armstrong | thanks | 18:02 |
| hberaud | gmann: +1 for -last | 18:02 |
| elod | gmann: ++ | 18:02 |
| gmann | cool, thanks | 18:03 |
| hberaud | gmann: notice that it could be worth to document this "state" somewhere to ensure that it's understood by everybody | 18:04 |
| hberaud | and what's your needs and your goal by doing that | 18:04 |
| hberaud | s/what's/what was/ | 18:05 |
| gmann | hberaud: sure. do you know in which doc i can add that? in this? https://releases.openstack.org/reference/using.html | 18:12 |
| gmann | i was searching if *-em is defined or so but could not find | 18:12 |
| elod | *-em and *-eol are mentioned in the stable policy ( https://docs.openstack.org/project-team-guide/stable-branches.html ) | 18:18 |
| elod | but I don't know whether tags are documented somehwere else officially | 18:19 |
| gmann | elod: thanks, I think i can add it there under the 'Extended Maintenance' section which is the phase we need -last tag also | 18:21 |
| gmann | hberaud: ^^ is that work fine from? | 18:21 |
| fungi | hberaud: you mentioned that once the release notes building fixes are implemented in stable branches we'll need to reenqueue things... will we though? those jobs are effectively branchless and the release notes will get correctly refreshed for those projects on their next release for any series | 18:21 |
| fungi | s/branchless/branch-agnostic/ | 18:22 |
| *** sboyron has quit IRC | 18:29 | |
| *** sboyron has joined #openstack-release | 18:29 | |
| hberaud | gmann: WFM | 19:02 |
| hberaud | fungi: Ah yes exact good point | 19:02 |
| fungi | i'm happy to reenqueue anything which needs to be rerun, but i have a feeling we can just ignore most of those | 19:25 |
| hberaud | yes | 19:26 |
| hberaud | anyway as you already said this is issue mostly depends on the alignment of the stars... if req tests are ok even if no doc reqs.txt exist it would be ok | 19:28 |
| hberaud | But standardization can't hurt and I prefer to be more suspicious than not enough | 19:30 |
| *** whoami-rajat__ has quit IRC | 20:02 | |
| *** diablo_rojo has quit IRC | 20:20 | |
| *** armstrong has quit IRC | 20:52 | |
| openstackgerrit | Ghanshyam proposed openstack/releases master: [Tempest] Tag stein EM https://review.opendev.org/c/openstack/releases/+/768565 | 21:17 |
| openstackgerrit | Ghanshyam proposed openstack/releases master: [Tempest] Tag stein-last https://review.opendev.org/c/openstack/releases/+/768565 | 21:19 |
| openstackgerrit | Ghanshyam proposed openstack/releases master: [Tempest Plugins] Tag stein-last https://review.opendev.org/c/openstack/releases/+/768547 | 21:20 |
| openstackgerrit | Ghanshyam proposed openstack/releases master: [Tempest Plugins] Tag stein-last https://review.opendev.org/c/openstack/releases/+/768547 | 21:20 |
| openstackgerrit | Ghanshyam proposed openstack/releases master: [Tempest Plugins] Tag stein EM https://review.opendev.org/c/openstack/releases/+/768553 | 21:22 |
| openstackgerrit | Ghanshyam proposed openstack/releases master: [Tempest Plugins] Tag stein-last https://review.opendev.org/c/openstack/releases/+/768553 | 21:22 |
| *** noonedeadpunk has quit IRC | 21:47 | |
| *** noonedeadpunk has joined #openstack-release | 21:48 | |
| *** jbadiapa has quit IRC | 23:21 | |
| *** tosky has quit IRC | 23:53 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!