Wednesday, 2024-01-17

fricklerif I read https://review.opendev.org/c/openstack/project-config/+/904837/2/roles/copy-release-tools-scripts/files/release-tools/make_branch.sh correctly, projects can eol a branch before it enters unmaintained state? kolla would like to move yoga to eol, but has been waiting so far for the unmaintained tooling to be finished. could we just move to eol right now anyway?12:30
elodillesfrickler: i'm not against eol-ing it before the unmaintained cut14:25
elodillesand yes, that's still possible to EOL without cutting the unmaintained/<series> branch (for train and ussuri we definitely need that; plus we need that in the future as well as far as i understood - if a team decides to go directly to EOL without keeping their project/repository in unmaintained)14:29
fricklerelodilles: thx, discussing this option with the kolla team right now14:48
fricklerregarding the automation patches, do you still want to wait for ttx review? IMO we should proceed and have the testing patches merged14:48
opendevreviewMerged openstack/releases master: [neutron] Transition Ussuri to End of Life  https://review.opendev.org/c/openstack/releases/+/90329414:51
*** blarnath is now known as d34dh0r5314:56
elodillesfrickler: yepp, let's see. I've +W'd them15:46
opendevreviewMerged openstack/releases master: Caracal-2 release for oslo.utils  https://review.opendev.org/c/openstack/releases/+/90494215:52
tkajinamo/ this is not super urgent, but I'm wondering if I can get some help with cleaning old branches in puppet-ceph https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/YIM2NE7YCJWHJ5EI7LDCPHZVW4KJBXAE/15:57
elodillestkajinam: hi, well, release team only deals with EOLing branches for deliverables that are listed in deliverables/<series>/*.yaml files, so probably the easiest is to get gerrit ACL rights for some limited number/group of maintainer (for example PTL) to tag puppet-ceph (so that <branch_name>-eol tag can be added to preserve branch history) and delete branches. after that the team can do the 16:06
elodillescleanup and handle this in the future16:06
tkajinamelodilles, ah, ok. I understand it and it sounds good to me. Do you mind adding the permission to me ?16:08
tkajinamwe are removing all of the existing stable branches in that repo. so far we've been trying to avoid creating a new stable branch, and haven't created new one for a while so I don't think we have to distribute that permission to multiple people for now.16:10
opendevreviewMerged openstack/releases master: Add EOM tag option to new-release command  https://review.opendev.org/c/openstack/releases/+/90476816:16
opendevreviewMerged openstack/releases master: Add EOM tag option to transition_series.sh  https://review.opendev.org/c/openstack/releases/+/90476916:16
opendevreviewMerged openstack/releases master: Test EOM tag on release-test repository  https://review.opendev.org/c/openstack/releases/+/90477016:16
elodillestkajinam: i've proposed this patch: https://review.opendev.org/c/openstack/project-config/+/90597616:27
elodillesi think this is how this should be done16:27
fricklerack, I was about to say the same. ping me or infra-root in #opendev once this is merged to add you to the new group16:34
tkajinamelodilles frickler, thank you, both16:34
*** gthiemon1e is now known as gthiemonge16:41
opendevreviewMerged openstack/releases master: Test unmaintained branch cut from eom tag  https://review.opendev.org/c/openstack/releases/+/90477117:02
elodillescool, both the yoga-eom tag and the unmaintained/yoga branch are created  ( https://opendev.org/openstack/release-test )17:56
elodillesjob logs: https://d27a261b135eda7ce090-506ed7b125b1acb83e6f56847633fe49.ssl.cf5.rackcdn.com/3bdb2416d777cf4847835d870b5a44b416f7d751/release-post/tag-releases/47c411b/job-output.txt17:57
elodillesand https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_143/51e8036b952659106421bceddfaaa62c492e27d8/release-post/tag-releases/143914a/job-output.txt17:57
opendevreviewElod Illes proposed openstack/releases master: DNM: test validation fails for release after yoga-eom  https://review.opendev.org/c/openstack/releases/+/90598418:14
fricklerI was just going to post the matching links on opendev.org, yay19:22
fricklerI don't think this is the error you were looking for, though: deliverables/yoga/release-test.yaml: validate_new_releases_at_end: new release 3.8.1 must be listed last, with one new release per patch19:24

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!