| elodilles | fungi: thanks, that sounds interesting :-o i'd try to do that, though i don't know at all how to start doing that :-o is there some pointers from the past how porting other ubuntu images went? (in case i won't succeed with the porting, then sadly zed and older unmaintained branches need to go :/) | 07:38 |
|---|---|---|
| frickler | elodilles: looks like mnasiadka already did this https://review.opendev.org/c/opendev/zuul-providers/+/953269 | 08:10 |
| mnasiadka | Yup, needs a recheck but otherwise looks good | 08:16 |
| elodilles | frickler mnasiadka : ah, thanks \o/ that's awesome :) | 08:21 |
| mnasiadka | frickler: hmm, failed again - is there some gitea flakiness expected or is that something else? | 09:44 |
| opendevreview | Elod Illes proposed openstack/releases master: [Puppet OpenStack] Transition 2023.2 Bobcat to End of Life https://review.opendev.org/c/openstack/releases/+/948219 | 11:39 |
| frickler | mnasiadka: not expected, luckily the failures are for existing images, so pretty certainly unrelated to your additions | 12:03 |
| *** haleyb_ is now known as haleyb | 13:48 | |
| noonedeadpunk | huh, folks, do you have any idea why there're no release notes link for OSA: https://releases.openstack.org/epoxy/index.html#deployment-and-packaging-tools ? | 13:53 |
| noonedeadpunk | as notes are apparently published: https://docs.openstack.org/releasenotes/openstack-ansible/2025.1.html | 13:54 |
| frickler | noonedeadpunk: I think these need to be added to https://opendev.org/openstack/releases/src/branch/master/deliverables/epoxy/openstack-ansible.yaml | 13:56 |
| noonedeadpunk | doh | 13:57 |
| noonedeadpunk | you're right | 13:57 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/releases master: Add release notes link to OpenStack-Ansible Epoxy release https://review.opendev.org/c/openstack/releases/+/953314 | 13:59 |
| elodilles | noonedeadpunk: we have a task to run tools/add_release_note_links.sh script at coordinated final release day, and the only prerequisite is to have the "reno-<series>" merged before we run the script so that it discovers and adds all the reno-links. though we don't have a task for doing this after cycle-trailing projects are done with their releases. (though when i don't forget it i do another | 14:33 |
| elodilles | round of the reno-links adding, like i did in May: https://review.opendev.org/c/openstack/releases/+/950147 ) | 14:33 |
| elodilles | (and yepp, i generated the patch just a few days earlier than your patch was merged: https://review.opendev.org/c/openstack/openstack-ansible/+/950419 ) | 14:37 |
| opendevreview | Merged openstack/releases master: Add release notes link to OpenStack-Ansible Epoxy release https://review.opendev.org/c/openstack/releases/+/953314 | 14:40 |
| noonedeadpunk | ah, I see... | 14:41 |
| noonedeadpunk | it's not critical for sure, but good to know the process :) | 14:41 |
| elodilles | but now as your patch has landed the reno link should appear after the page gets rebuilt ^^^ :) | 14:44 |
| elodilles | (and there it is: https://releases.openstack.org/epoxy/index.html#deployment-and-packaging-tools ) | 15:03 |
| frickler | someone could add a periodic job to check for this - as we keep forgetting about it each cycle - but then who has time for something like that? ;) | 15:47 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!