| *** amoralej|off is now known as amoralej | 07:05 | |
| ttx | frickler: hah that was actually simpler than I expected. Thanks for having a look. | 07:58 |
|---|---|---|
| ttx | Now to make it generic... | 08:03 |
| opendevreview | Merged openstack/releases master: Release venus-dashboard RC1 for Antelope https://review.opendev.org/c/openstack/releases/+/875475 | 09:03 |
| opendevreview | Merged openstack/releases master: Release adjutant RC1 for Antelope https://review.opendev.org/c/openstack/releases/+/875386 | 09:03 |
| opendevreview | Merged openstack/releases master: Release adjutant-ui RC1 for Antelope https://review.opendev.org/c/openstack/releases/+/875385 | 09:03 |
| opendevreview | Merged openstack/releases master: Release mistral RC1 for Antelope https://review.opendev.org/c/openstack/releases/+/875425 | 09:03 |
| opendevreview | Merged openstack/releases master: Release mistral-dashboard RC1 for Antelope https://review.opendev.org/c/openstack/releases/+/875424 | 09:03 |
| opendevreview | Merged openstack/releases master: Release compute-hyperv RC1 for Antelope https://review.opendev.org/c/openstack/releases/+/875402 | 09:03 |
| opendevreview | Merged openstack/releases master: Release tacker RC1 for Antelope https://review.opendev.org/c/openstack/releases/+/875471 | 09:03 |
| opendevreview | Merged openstack/releases master: Release magnum-ui RC1 for Antelope https://review.opendev.org/c/openstack/releases/+/875417 | 09:03 |
| opendevreview | Merged openstack/releases master: Release designate RC1 for Antelope https://review.opendev.org/c/openstack/releases/+/875405 | 09:03 |
| opendevreview | Merged openstack/releases master: Release trove-dashboard RC1 for Antelope https://review.opendev.org/c/openstack/releases/+/875473 | 09:03 |
| opendevreview | Merged openstack/releases master: Release nova RC1 for Antelope https://review.opendev.org/c/openstack/releases/+/875447 | 09:04 |
| opendevreview | Merged openstack/releases master: Release trove RC1 for Antelope https://review.opendev.org/c/openstack/releases/+/875474 | 09:04 |
| opendevreview | Merged openstack/releases master: Release glance RC1 for Antelope https://review.opendev.org/c/openstack/releases/+/875410 | 09:04 |
| opendevreview | Merged openstack/releases master: Release masakari RC1 for Antelope https://review.opendev.org/c/openstack/releases/+/875423 | 09:04 |
| opendevreview | Merged openstack/releases master: Release venus RC1 for Antelope https://review.opendev.org/c/openstack/releases/+/875476 | 09:04 |
| bauzas | \o/ | 09:05 |
| elodilles | ~o~ | 09:14 |
| opendevreview | Elod Illes proposed openstack/releases master: Release keystone RC1 for Antelope https://review.opendev.org/c/openstack/releases/+/875414 | 09:37 |
| hberaud | elodilles, ttx: FYI, I think that something went wrong with our command `list-deliverables` to find unbranched projects, as all deliverables seems listed in the results | 09:42 |
| hberaud | I think it is surely due to the new branch naming convention | 09:43 |
| elodilles | hberaud: oh, it must be searching for stable/antelope | 09:45 |
| hberaud | yeah | 09:46 |
| hberaud | I'm doing some test with this cmd | 09:46 |
| * elodilles is looking | 09:47 | |
| hberaud | elodilles: fixed | 09:52 |
| hberaud | I'll submit my fix | 09:53 |
| opendevreview | Hervé Beraud proposed openstack/releases master: Fix list-deliverables command to use release-id https://review.opendev.org/c/openstack/releases/+/876557 | 09:55 |
| hberaud | elodilles, ttx ^ | 09:55 |
| opendevreview | Hervé Beraud proposed openstack/releases master: Release magnum RC1 for Antelope https://review.opendev.org/c/openstack/releases/+/875418 | 10:03 |
| opendevreview | Hervé Beraud proposed openstack/releases master: Release magnum RC1 for Antelope https://review.opendev.org/c/openstack/releases/+/875418 | 10:04 |
| elodilles | hberaud: LGTM | 10:04 |
| hberaud | elodilles: the `get_stable_branch_id` function could become more generic by moving it to a shared module and then reused everywhere it is needed | 10:06 |
| hberaud | Any objections => https://review.opendev.org/c/openstack/releases/+/874758 ? | 10:17 |
| hberaud | elodilles, ttx I'm a bit puzzled by our weekly tasks agenda, indeed we are supposed to engage reqs and QA branching once all the other deliverables are branched (around tomorrow or wednesday), however, the deadline for CWI+other deliverables is next week, so it is not possible to see them branched before the end of next week. Does I missed something? | 10:35 |
| hberaud | see my report on R-2 https://etherpad.opendev.org/p/antelope-relmgt-tracking | 10:36 |
| hberaud | and the cwi+other deadline https://releases.openstack.org/antelope/schedule.html#a-finalrc | 10:37 |
| elodilles | hberaud: as I understand that deadline is for 'only final-release-critical releases' | 11:02 |
| elodilles | hberaud: so we already reached the deadline (last week) for RC1's, cycle-with-intermediary deliverables | 11:03 |
| hberaud | ok | 11:03 |
| elodilles | hberaud: now every project should have been branched (except those who had issues, requested exceptions) | 11:03 |
| elodilles | any project, that needs a 'now-really-final' release should release from their stable/2023.1 branch, according to the process, as I understand | 11:05 |
| elodilles | and we + PTLs should allow only 'release critical' issues to trigger that | 11:05 |
| elodilles | hberaud: about the get_stable_branch_id function: i was thinking the same actually. | 11:06 |
| elodilles | hberaud: for starter, here we could have 'self.name' as default value, if no release-id specified: https://opendev.org/openstack/releases/src/branch/master/openstack_releases/series_status.py#L48 | 11:07 |
| elodilles | though we should be careful with refactoring things (without proper testing) so close to 2023.1 Antelope release :) but definitely we can add tasks to our TODO list for Bobcat (well, this shouldn't be a big refactoring, right? _famous last words_ :)) | 11:10 |
| hberaud | yeah the refactor can happen later during bobcat | 11:16 |
| opendevreview | Hervé Beraud proposed openstack/releases master: Release bifrost 16.0.1 and branch stable/2023.1 https://review.opendev.org/c/openstack/releases/+/876567 | 12:50 |
| opendevreview | Hervé Beraud proposed openstack/releases master: Release ironic-inspector 11.3.1 and branch stable/2023.1 https://review.opendev.org/c/openstack/releases/+/876569 | 12:55 |
| opendevreview | Hervé Beraud proposed openstack/releases master: Branch ironic-P-A-B https://review.opendev.org/c/openstack/releases/+/876571 | 12:59 |
| opendevreview | Hervé Beraud proposed openstack/releases master: release IPA 9.3.1 and branch stable/2023.1 https://review.opendev.org/c/openstack/releases/+/876572 | 13:01 |
| opendevreview | Hervé Beraud proposed openstack/releases master: release ironic 21.4.0 and branch stable/2023.1 https://review.opendev.org/c/openstack/releases/+/876573 | 13:04 |
| opendevreview | Hervé Beraud proposed openstack/releases master: Branch stable/2023.1 for networking-baremetal https://review.opendev.org/c/openstack/releases/+/876574 | 13:06 |
| opendevreview | Hervé Beraud proposed openstack/releases master: Release python-openstackclient 6.2.0 and create branch stable/2023.1 https://review.opendev.org/c/openstack/releases/+/876575 | 13:11 |
| opendevreview | Hervé Beraud proposed openstack/releases master: Branch requirements for stable/2023.1 https://review.opendev.org/c/openstack/releases/+/876576 | 13:14 |
| *** amoralej is now known as amoralej|lunch | 13:22 | |
| opendevreview | Hervé Beraud proposed openstack/releases master: Release swift 2.32.0 and cut branch stable/2023.1 https://review.opendev.org/c/openstack/releases/+/876579 | 13:23 |
| hberaud | ttx, elodilles: the missing patches to create stable branches. I still wonder why the cwi+others deliverables weren't shown by our tools earlier before that point. | 13:26 |
| hberaud | by following the current process we would only see ironic as unreleased next week | 13:27 |
| hberaud | I think either something is missing somewhere or a date in our antelope process isn't correct. | 13:28 |
| hberaud | (somewhere in our process) | 13:29 |
| ttx | hmm would be good to check back how we did it previously, because I don't remember changing anything in that area | 13:30 |
| hberaud | same thing here | 13:31 |
| hberaud | and I don't remember reviewing related process changes | 13:31 |
| ttx | hberaud: reading the process, I think it works as intended? During that week you branch all those that have not been branched before (point 3) and then after all the projects enabled in devstack by default have been branched, we can engage with QA and friends (point 4) | 13:34 |
| ttx | then on R-1 week you can have additional intermediary releases done on teh stable branch that was cut at R-2 | 13:35 |
| ttx | So imagine Swift has 2.32.0 on master. R-2 is the deadline to create stable/2023.1 from that. And R-1 is the deadline for doing a 2.32.1 before final release | 13:36 |
| elodilles | hberaud: about the 'other' typed deliverables: we have these only: https://paste.opendev.org/show/bXdOrX4u2PZw1g6yzQv2/ | 13:37 |
| elodilles | hberaud: only python-openstackclient is a bitt odd in my opinion | 13:37 |
| ttx | And on R-2 once we get branches for all the projects enabled in devstack (likely by end of week) we can engage with QA and friends. | 13:38 |
| elodilles | hberaud: so maybe we could add a task somewhere to release that (or maybe other non-tempest) deliverables | 13:38 |
| ttx | I think it works as intended | 13:38 |
| ttx | Any CWI release done on R-1 should be on the already-cut stable branch | 13:39 |
| ttx | Just like another RC | 13:39 |
| elodilles | agree with ttx , i tried to write the same above :) | 13:39 |
| hberaud | ok, i think i got some brain knots then :) | 13:53 |
| *** amoralej|lunch is now known as amoralej | 13:59 | |
| opendevreview | Thierry Carrez proposed openstack/reno master: Add openstack_branch_ordering option https://review.opendev.org/c/openstack/reno/+/876581 | 14:36 |
| ttx | ok I just built a reno change around frickler's POC -- main drawback of my approach is that we need to update jobs to add --openstack-branch-ordering to all reno calls in our releasenotes jobs... But at least it's a noop for every other users out there | 14:36 |
| ttx | There is probably a more elegant solution | 14:37 |
| frickler | ttx: not sure if elegant, but the other option would be to make that option default to true and cut a major release. | 14:39 |
| frickler | not sure how many other consumer there are out there. and how many might also be using such a weird mix of branch names | 14:40 |
| ttx | frickler: felt like the nice thing to do to switch it on our end. Although I'll admit I have trouble finding where that reno call lives in the Zuul jobs | 14:41 |
| frickler | ttx: it's embedded in the sphinx call somewhere, didn't look in detail yet. | 14:42 |
| frickler | https://opendev.org/openstack/reno/src/branch/master/reno/sphinxext.py | 14:43 |
| ttx | tracked it to zuul-jobs/roles/build-releasenotes/tasks/main.yaml but can't find where it calls onto reno | 14:44 |
| frickler | maybe just meddle a bit in there? | 14:44 |
| frickler | each project has reno.sphinxext in their releasenotes/source/conf.py | 14:44 |
| ttx | hmm that would again make the openstack way the rule for everybody | 14:46 |
| frickler | yes, but from this it sounds like passing options into sphinx is a problem yet unsolved https://opendev.org/openstack/reno/src/branch/master/reno/sphinxext.py#L89-L91 | 14:47 |
| frickler | so not much options I guess | 14:47 |
| frickler | except doing a reno-openstack fork if we really care that much about other consumers | 14:48 |
| frickler | but that would then imply touching every project's releasenotes dir | 14:48 |
| ttx | not a lot funnier | 14:49 |
| ttx | I just don't feel comfortable hardcoding a rule that makes 2* branches sort after z but not 1* | 14:50 |
| ttx | I guess we could make all numbers sort after z and claim that was always the idea | 14:50 |
| ttx | need to sleep on it | 14:50 |
| frickler | well that was just my hack, which I thought to be nice because it creates a y3k problem and because the match is easier | 14:51 |
| frickler | handline all stable/[0-9]* consistently certainly would be much easier to sell, so I'm fine to go that path | 14:52 |
| frickler | handling even | 14:52 |
| ttx | fungi elodilles hberaud thoughts welcome | 14:52 |
| ttx | yeah, sounds like the least worse option at this stage | 14:52 |
| frickler | we can still keep the flag in in case someone needs to override that | 14:53 |
| frickler | (except for the sphinxext possibly, where it might not be that easy) | 14:54 |
| fungi | we could sort of do an in-repo "fork" by making a different entrypoint that has the new alternative behavior and include that extension instead of the original | 14:54 |
| frickler | fungi: that still would mean touching every projects reno conf.py, wouldn't it? | 14:55 |
| fungi | then we don't need to pass options in sphinx config, though it would still need updating ~everywhere | 14:55 |
| fungi | yes | 14:55 |
| fungi | or we could toggle behavior based on an envvar which we set in the zuul jobs for openstack projects, then docs get updated immediately on next build even if local builds need in-repo changes they can take their time merging | 14:56 |
| fungi | or something like an envvar, e.g. check for presence of a flag file... or we could even make the docs jobs inline edit conf.py though that seems... messy | 14:57 |
| elodilles | ttx: ack, i will spend time on thinking on this | 15:01 |
| elodilles | my (abstract) idea is reno somehow could check which is the latest branch or even latest branches and could recognise that the alphabet is restarted. or something like this. but this idea came for me without looking at the implementation | 15:05 |
| frickler | currently it just takes the list of branches and returns them sorted(). digging deeper into git history might be possible, but would likely as well have special cases that could break existing consumers, so IMO that would be overkill | 15:12 |
| frickler | https://opendev.org/openstack/reno/src/branch/master/reno/scanner.py#L871-L877 | 15:12 |
| frickler | actually a bit more complicated because it also maps tags for eol branches back to the original branch names | 15:14 |
| frickler | so no way to order those other than by specifying a sort order. we'd hit that scenarion once zed is eol'd | 15:16 |
| *** gthiemon1e is now known as gthiemonge | 16:24 | |
| *** amoralej is now known as amoralej|off | 16:51 | |
| hberaud | elodilles, ttx: FYI I'll be AFK all the entire day tomorrow. See you Wednesday | 16:57 |
| elodilles | hberaud: ack, see you on Wednesday! | 18:20 |
| gmann | elodilles: ttx: hberaud: ack, please ping me or kopecmartin once we have branches for all the projects enabled in devstack and we will start the QA part | 18:39 |
| elodilles | gmann: sure, thanks in advance! | 18:50 |
| opendevreview | Elod Illes proposed openstack/releases master: Release blazar-tempest-plugin for 2023.1 Antelope https://review.opendev.org/c/openstack/releases/+/876602 | 18:58 |
| opendevreview | Elod Illes proposed openstack/releases master: Release cinder-tempest-plugin for 2023.1 Antelope https://review.opendev.org/c/openstack/releases/+/876603 | 19:00 |
| opendevreview | Elod Illes proposed openstack/releases master: Release cloudkitty-tempest-plugin for 2023.1 Antelope https://review.opendev.org/c/openstack/releases/+/876604 | 19:01 |
| opendevreview | Elod Illes proposed openstack/releases master: Release cyborg-tempest-plugin for 2023.1 Antelope https://review.opendev.org/c/openstack/releases/+/876605 | 19:01 |
| opendevreview | Elod Illes proposed openstack/releases master: Release designate-tempest-plugin for 2023.1 Antelope https://review.opendev.org/c/openstack/releases/+/876606 | 19:02 |
| opendevreview | Elod Illes proposed openstack/releases master: Release ec2api-tempest-plugin for 2023.1 Antelope https://review.opendev.org/c/openstack/releases/+/876607 | 19:02 |
| opendevreview | Elod Illes proposed openstack/releases master: Release freezer-tempest-plugin for 2023.1 Antelope https://review.opendev.org/c/openstack/releases/+/876608 | 19:03 |
| opendevreview | Elod Illes proposed openstack/releases master: Release glance-tempest-plugin for 2023.1 Antelope https://review.opendev.org/c/openstack/releases/+/876609 | 19:03 |
| opendevreview | Elod Illes proposed openstack/releases master: Release heat-tempest-plugin for 2023.1 Antelope https://review.opendev.org/c/openstack/releases/+/876610 | 19:03 |
| opendevreview | Elod Illes proposed openstack/releases master: Release ironic-tempest-plugin for 2023.1 Antelope https://review.opendev.org/c/openstack/releases/+/876611 | 19:04 |
| opendevreview | Elod Illes proposed openstack/releases master: Release keystone-tempest-plugin for 2023.1 Antelope https://review.opendev.org/c/openstack/releases/+/876612 | 19:05 |
| opendevreview | Elod Illes proposed openstack/releases master: Release manila-tempest-plugin for 2023.1 Antelope https://review.opendev.org/c/openstack/releases/+/876613 | 19:11 |
| opendevreview | Elod Illes proposed openstack/releases master: Release mistral-tempest-plugin for 2023.1 Antelope https://review.opendev.org/c/openstack/releases/+/876614 | 19:12 |
| opendevreview | Elod Illes proposed openstack/releases master: Release monasca-tempest-plugin for 2023.1 Antelope https://review.opendev.org/c/openstack/releases/+/876615 | 19:12 |
| opendevreview | Elod Illes proposed openstack/releases master: Release neutron-tempest-plugin for 2023.1 Antelope https://review.opendev.org/c/openstack/releases/+/876616 | 19:13 |
| opendevreview | Elod Illes proposed openstack/releases master: Release octavia-tempest-plugin for 2023.1 Antelope https://review.opendev.org/c/openstack/releases/+/876617 | 19:14 |
| opendevreview | Elod Illes proposed openstack/releases master: Release senlin-tempest-plugin for 2023.1 Antelope https://review.opendev.org/c/openstack/releases/+/876618 | 19:14 |
| opendevreview | Elod Illes proposed openstack/releases master: Release telemetry-tempest-plugin for 2023.1 Antelope https://review.opendev.org/c/openstack/releases/+/876619 | 19:15 |
| opendevreview | Elod Illes proposed openstack/releases master: Release trove-tempest-plugin for 2023.1 Antelope https://review.opendev.org/c/openstack/releases/+/876620 | 19:15 |
| opendevreview | Elod Illes proposed openstack/releases master: Release venus-tempest-plugin for 2023.1 Antelope https://review.opendev.org/c/openstack/releases/+/876621 | 19:16 |
| opendevreview | Elod Illes proposed openstack/releases master: Release vitrage-tempest-plugin for 2023.1 Antelope https://review.opendev.org/c/openstack/releases/+/876622 | 19:16 |
| opendevreview | Elod Illes proposed openstack/releases master: Release zun-tempest-plugin for 2023.1 Antelope https://review.opendev.org/c/openstack/releases/+/876623 | 19:16 |
| opendevreview | Elod Illes proposed openstack/releases master: Release magnum-tempest-plugin for 2023.1 Antelope https://review.opendev.org/c/openstack/releases/+/876627 | 19:46 |
| opendevreview | Elod Illes proposed openstack/releases master: Release kuryr-tempest-plugin for 2023.1 Antelope https://review.opendev.org/c/openstack/releases/+/876628 | 19:47 |
| opendevreview | Ghanshyam proposed openstack/releases master: Release keystone-tempest-plugin for 2023.1 Antelope https://review.opendev.org/c/openstack/releases/+/876612 | 21:52 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!