| *** amoralej is now known as amoralej|off | 07:26 | |
| *** amoralej|off is now known as amoralej | 07:44 | |
| elodilles | JayF: hi, what 'managed without oversight from the Release Management team' means is more like those deliverables should not follow the release schedule, so they can release mostly any time in the cycle (no mandatory releases at milestones, or before the final release, etc). as I understand this is the meaning of it | 09:02 |
|---|---|---|
| elodilles | hberaud ttx : ^^^ correct me if I'm wrong | 09:02 |
| elodilles | (see JayF's question in the history of the channel: https://meetings.opendev.org/irclogs/%23openstack-release/%23openstack-release.2023-03-29.log.html#t2023-03-29T16:57:48 ) | 09:03 |
| hberaud | yeah independent means not following the release schedule and series cadence | 09:04 |
| hberaud | and branch cutting seems allowed for independent deliverables | 09:07 |
| hberaud | example https://github.com/openstack/releases/blob/master/deliverables/_independent/gnocchi.yaml#L7 | 09:07 |
| elodilles | JayF: about the branches: as i read somewhere, cutting a stable/* branch causes confusions for independent deliverables, so best is to avoid them. bugfix/* branches are speciality for ironic team's request :) otherwise i would think that other branch cuts are not really supported and there was not even a need for that (especially as relmgmt tooling does not support releasing from those | 09:07 |
| elodilles | branches) | 09:07 |
| elodilles | hberaud: ++ | 09:08 |
| hberaud | but I agree with Elod, cutting stable branches from independent deliverables is a bit of nonsense | 09:09 |
| elodilles | thx hberaud | 09:10 |
| ttx | confirming. Independent is a model for OpenStack deliverables that are not released as part of the OpenStack synchronized release | 10:48 |
| ttx | If they would benefit from stable/2023.1 -style branches, they should be "cycle-with-intermediary" which gives them free reins on release timing while syncing on the 6-month release thanks to that stable/ branch | 10:49 |
| ttx | 'managed without oversight from the Release Management team' means that we will not trigger releases to align it with the synced openstack release, nor check stable versioning rules | 10:51 |
| ttx | so our review becomes pretty basic | 10:52 |
| *** amoralej is now known as amoralej|lunch | 11:13 | |
| elodilles | yepp, thx too for confirming | 11:37 |
| opendevreview | Merged openstack/releases master: Release OpenStack-Ansible Yoga https://review.opendev.org/c/openstack/releases/+/878119 | 12:01 |
| opendevreview | Merged openstack/releases master: Release OpenStack-Ansible Zed https://review.opendev.org/c/openstack/releases/+/878120 | 12:01 |
| opendevreview | Merged openstack/reno master: Add support for subsections https://review.opendev.org/c/openstack/reno/+/873165 | 12:03 |
| elodilles | ttx: is it OK to change back the release model for stable series as well? I would think it's not what we support. zed should not be part of the patch, or am I wrong? https://review.opendev.org/c/openstack/releases/+/878730 | 12:12 |
| elodilles | though i see they did not have rc as Takashi wrote | 12:18 |
| ttx | yeah it feels like we actually acted as if it was cwi back then, so fixing it afterwards is fine (and probably a noop) | 12:24 |
| elodilles | ttx: ack | 12:26 |
| opendevreview | Merged openstack/releases master: Bump validation framework to 1.9.0 version https://review.opendev.org/c/openstack/releases/+/878774 | 12:36 |
| opendevreview | Merged openstack/releases master: Switch back Puppet OpenStack to cycle-with-intermediary https://review.opendev.org/c/openstack/releases/+/878730 | 12:46 |
| *** amoralej|lunch is now known as amoralej | 12:47 | |
| *** whoami-rajat__ is now known as whoami-rajat | 13:28 | |
| zigo | [release-announce] [pbr] Generating ChangeLog | 13:29 |
| zigo | Not ideal for $subject ... :P | 13:29 |
| JayF | ttx: elodilles: hberaud: We decided on "no action"; but the main reason we were looking at switching from cycle-with-intermediary is that we wanted to push releases for sushy packages whose cycle was already in EM, and not eligible for release anymore. It's something that comes up maybe once a year, so it's not a major concern, I just wanted to get more education on what | 14:16 |
| JayF | was possible :). | 14:16 |
| elodilles | well, for that case, "independent" release model would not be the solution o:) | 14:31 |
| elodilles | hberaud ttx: zigo is right, we have a problem with the release-announce mails: https://lists.openstack.org/pipermail/release-announce/2023-March/thread.html | 14:32 |
| elodilles | :S | 14:32 |
| hberaud | openstack-ansible, validations-lib, and validations-common seems impacted, I don't know if they have things in common that could explain that bug | 14:35 |
| hberaud | I'd argue validations-lib and validations-common could have things in common | 14:35 |
| elodilles | in the list-changes job logs the generated mail looks good: https://zuul.opendev.org/t/openstack/build/1151f68e6ed6473ab721c16c897e51d8/log/tox/list-changes/list-changes-results.log#433-454 | 14:40 |
| hberaud | indeed | 14:41 |
| jrosser | the banner at the top of the docs pages has an unsual release version - is that right? like here https://docs.openstack.org/nova/latest/ | 14:51 |
| elodilles | jrosser: that looks good to me | 15:01 |
| jrosser | ok :) | 15:01 |
| elodilles | we are in the 2023.2 Bobcat cycle | 15:01 |
| jrosser | 2023.1.antelope <- this is correct ? | 15:01 |
| elodilles | that is the latest release, yes | 15:02 |
| jrosser | ok, it just looks odd written like that all joined together it doesnt look like a version or a branch | 15:02 |
| elodilles | yes, it could have been nicer, like '2023.1 Antelope' | 15:02 |
| elodilles | that i agree | 15:03 |
| jrosser | hah i even managed to get that wrong (version or branch) when actually the thing is supposed to communicate the release /o\ | 15:05 |
| elodilles | yepp, it is the 'release' (according to the new release identification resolution) o:) | 15:10 |
| clarkb | it was also called out that the user guides (and other guides) are not on the index page likely due to a release name mismatch between 2023.1.antelope and whatever the individual guides call the branch | 15:20 |
| clarkb | The openstack-manuals repo probably needs to do a normalization pass to get everything to align | 15:20 |
| elodilles | oh, nice, so that too :/ | 15:28 |
| *** whoami-rajat__ is now known as whoami-rajat | 15:53 | |
| *** amoralej is now known as amoralej|off | 16:36 | |
| opendevreview | Elod Illes proposed openstack/releases master: Add workaround for announce mail script https://review.opendev.org/c/openstack/releases/+/879065 | 17:29 |
| elodilles | hberaud ttx : had a quick look now that i had time about the announce mail issue. I couldn't find the root cause yet, but if we need a quick workaround, i've prepared one ^^^ | 17:30 |
| elodilles | though the best would be to find the root cause and fix that instead of this ugly workaround :/ | 17:31 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!