opendevreview | Merged openstack/releases master: Fix new-release command for cycle independent projects https://review.opendev.org/c/openstack/releases/+/937249 | 10:49 |
---|---|---|
opendevreview | Dmitriy Rabotyagov proposed openstack/releases master: [OpenStackAnsible] Transition 2023.1 Antelope to Unmaintained https://review.opendev.org/c/openstack/releases/+/934495 | 11:09 |
opendevreview | Dmitriy Rabotyagov proposed openstack/releases master: Release OpenStack-Ansible 2023.1 for EOM https://review.opendev.org/c/openstack/releases/+/940512 | 11:18 |
opendevreview | Dmitriy Rabotyagov proposed openstack/releases master: [OpenStackAnsible] Transition 2023.1 Antelope to Unmaintained https://review.opendev.org/c/openstack/releases/+/934495 | 11:28 |
noonedeadpunk | elodilles: here we go with osa eom ^ | 11:28 |
elodilles | noonedeadpunk: \o/ thanks! lgtm, i've +2'd the release patch | 11:50 |
opendevreview | Merged openstack/releases master: Release OpenStack-Ansible 2023.1 for EOM https://review.opendev.org/c/openstack/releases/+/940512 | 12:25 |
opendevreview | Dmitriy Rabotyagov proposed openstack/releases master: Revert^2 "Set antelope/2023.1 status to unmaintained" https://review.opendev.org/c/openstack/releases/+/940517 | 12:32 |
noonedeadpunk | ok, I didn't spot revert already being present | 12:32 |
opendevreview | Merged openstack/releases master: [OpenStackAnsible] Transition 2023.1 Antelope to Unmaintained https://review.opendev.org/c/openstack/releases/+/934495 | 13:12 |
frickler | elodilles: ^^ with that we should be finally ready for the revert, or am I missing something? also are you fine with proceeding with the victoria patch? | 13:15 |
elodilles | frickler: we should wait until the tagging is ready and post jobs have finished, but probably these are done already, let me check | 13:46 |
elodilles | frickler: there was some release-post job still running but now it's gone, so I think we should proceed with the revert^2: https://review.opendev.org/c/openstack/releases/+/939895 | 14:04 |
opendevreview | Merged openstack/releases master: Revert^2 "Set antelope/2023.1 status to unmaintained" https://review.opendev.org/c/openstack/releases/+/939895 | 15:15 |
elodilles | \o/ | 15:30 |
opendevreview | Merged openstack/releases master: [octavia-tempest-plugin] Tag 2023.1-last https://review.opendev.org/c/openstack/releases/+/933954 | 15:59 |
opendevreview | Merged openstack/releases master: [watcher-tempest-plugin] Tag 2023.1-last https://review.opendev.org/c/openstack/releases/+/933959 | 16:02 |
opendevreview | Merged openstack/releases master: [cloudkitty-tempest-tempest] Tag 2023.1-last https://review.opendev.org/c/openstack/releases/+/933947 | 16:12 |
opendevreview | Merged openstack/releases master: [heat-tempest-plugin] Tag 2023.1-last https://review.opendev.org/c/openstack/releases/+/933963 | 16:12 |
opendevreview | Merged openstack/releases master: [manila-tempest-plugin] Tag 2023.1-last https://review.opendev.org/c/openstack/releases/+/933943 | 16:12 |
opendevreview | Merged openstack/releases master: [zun-tempest-plugin] Tag 2023.1-last https://review.opendev.org/c/openstack/releases/+/933942 | 16:14 |
opendevreview | Merged openstack/releases master: [telemetry-tempest-plugin] Tag 2023.1-last https://review.opendev.org/c/openstack/releases/+/933953 | 16:14 |
opendevreview | Merged openstack/releases master: [glance-tempest-plugin] Tag 2023.1-last https://review.opendev.org/c/openstack/releases/+/933958 | 16:15 |
opendevreview | Merged openstack/releases master: [barbican-tempest-plugin] Tag 2023.1-last https://review.opendev.org/c/openstack/releases/+/933956 | 16:15 |
opendevreview | Merged openstack/releases master: [designate-tempest-plugin] Tag 2023.1-last https://review.opendev.org/c/openstack/releases/+/933952 | 16:15 |
elodilles | ~o~ | 16:18 |
fungi | those were lots of releases of projects with - in their names, still no new warning e-mails from pypi | 16:46 |
elodilles | oh i forgot we should have had a slower pace at approving changes to see if things work fine :S | 16:51 |
clarkb | are we aiming for a pbr release mondayish? | 16:56 |
clarkb | I know the work to update the release tooling was partially in support of that and pbr is probably a good thing to avoid releasing on friday with people at a conference all weekend | 16:57 |
clarkb | fungi: also https://review.opendev.org/c/zuul/zuul-jobs/+/940074 could use reviews for install twine in a virtualenv | 16:57 |
fungi | yeah, monday would be good for pbr 6.1.1, i think damani[m] still needs to +1 940118 before that can happen though | 17:01 |
elodilles | did a quick run on the missing-releases command and it seems there are some hits: https://paste.opendev.org/show/b45eA1Q1xDkHpkvWrzxK/ | 17:01 |
fungi | right, those are all the projects with "-" in their names that had releases tagged today | 17:01 |
elodilles | i wonder if we just fix the 'tarball-base' in the yamls fixes everything or will it creat other issues? O.o | 17:01 |
clarkb | as fungi pointed out then you'll have the old releases failing instead of the new ones | 17:02 |
fungi | keep in mind that their prior releases will still have a "-" in the sdist filenames, but the new ones will have a "_" and presumably we need to check for both | 17:03 |
elodilles | (as the deliverables are there, just with "_" however the script searches for "-") | 17:03 |
clarkb | I think you need to check the normal and non normal versions of the name and if one matches you are good | 17:03 |
fungi | same as for projects with "." in their names | 17:03 |
fungi | and yeah, we presumably already do this with wheels since they've had normalized filenames for far longer | 17:04 |
elodilles | clarkb: yeah, maybe that will be the most viable fix | 17:04 |
fungi | another release-test round is probably in order now that haleyb's ensure-twine role update merged | 18:12 |
fungi | just so we're not surprised by anything new | 18:12 |
clarkb | do we want to bump back to noble again first for the job(s)? | 18:12 |
* haleyb hopes he didn't break the world with that | 18:12 | |
fungi | i'm on the fence about testing it separately from the noble switch | 18:13 |
fungi | if it breaks something on jammy then we'll know to revert the change in the role asap, whereas if we test it with noble and it breaks we don't know for sure that undoing one of those will be sufficient without additional testing, which could further delay getting back to a working state | 18:14 |
clarkb | ack | 18:14 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!