13:00:05 #startmeeting releaseteam 13:00:05 Meeting started Fri May 10 13:00:05 2024 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:05 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:00:05 The meeting name has been set to 'releaseteam' 13:00:12 Ping list: release-team elod 13:00:28 Our agenda is at https://etherpad.opendev.org/p/dalmatian-relmgt-tracking down to line 80 13:00:49 \o 13:01:17 o/ 13:01:40 #topic Review task completion 13:01:52 1/ Process Unmaintained transitioning patches for stable/zed (all) 13:02:04 #link https://review.opendev.org/q/topic:zed-unmaintained+is:open 13:02:47 almost done, noonedeadpunk updated osa earlier today 13:02:51 so yes, we moved all inactive projects' zed branches to EOM 13:03:08 Had a question if we should wait before approving https://review.opendev.org/c/openstack/releases/+/918034 13:03:23 and one more, too: winstackers 13:03:48 I'm still thinking winstackers should not be touched at all anymore, like tripleo or other retired projects 13:04:14 for 918034 I think we don't need to wait for everything, 90% should be fine 13:04:46 elodilles: on 918034 if you agree I'll approve it now 13:04:57 frickler: i'd rather EOL or move to EOM that instead of not doing anything. but maybe we don't need to wait for this patch 13:05:18 ttx: +1, approve it please! 13:05:45 alright done 13:06:01 thx o/ 13:06:03 should we add a reminder to review progress next week? 13:06:10 since we have a few stragglers? 13:06:36 +1 13:06:57 ok done 13:07:06 2/ Review cycle-trailing projects to check which haven’t released yet. Ask them to prepare their releases, if they haven’t already. (elod) 13:07:19 #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/HRC7JFUILNZRXXUILTUDJ2NJ5ZZFAXRS/ 13:07:36 lgtm? 13:07:42 yepp 13:07:49 task was to remind the teams 13:07:54 that's done 13:07:56 Third task I'll complete shortly after meet 13:08:03 kolla prepared a release :) 13:08:09 #topic Assign R-20 week tasks 13:08:09 kayobe and osa is missing 13:08:34 (we also need someone to chair next meeting) 13:09:12 frickler: do you want to chair next meeting? 13:09:27 if not, then i will :) 13:10:08 I'd rather not 13:10:15 plus I added my name to the open tasks, feel free to hijack any of them if you want 13:10:23 frickler: ACK, then i will :) 13:10:38 alright, all set 13:10:42 #topic Review countdown email for week R-20 13:10:52 #link https://etherpad.opendev.org/p/relmgmt-weekly-emails 13:11:33 LGTM! 13:11:49 Dalmatian-1 milestone \o/ 13:11:55 time flies... 13:12:01 Ok will send after meet 13:12:08 ++ 13:12:13 #topic Open Discussion 13:12:20 Anything else we should cover? 13:12:23 - 13:12:50 triploe retirement should be fine now 13:12:57 #link https://review.opendev.org/c/openstack/releases/+/905147 13:12:58 \o/ 13:13:22 except someone wants to debug the issue with tripleo-docs 13:13:29 +2+W'd 13:13:46 yepp. the issue with tripleo-docs is weird 13:14:10 i haven't looked it thoroughly, though... 13:14:15 I also updated some project health status notes 13:14:24 👍️ 13:14:27 and sent a link of that etherpad section to the tc 13:14:28 frickler: +1 13:14:38 +2 13:15:25 Alright, if nothing else, let's end early! 13:15:34 ~o~ 13:15:35 oh, the post0 thing 13:15:41 * ttx holds 13:15:52 maybe someone wants to debug that? seems some pbr issue 13:16:04 #link https://review.opendev.org/c/openstack/releases/+/918032?usp=search 13:16:31 or we say we give up and don't do these kinds of releases 13:16:52 yeah.. what's the target case? 13:17:05 broken pypi uploads for a release 13:17:38 so when e.g. 15.0.0 is broken on pypi, we could do 15.0.0post0 instead of 15.0.1 13:17:42 yepp, we had e.g. Caracal's nova 29.0.0 release that was rejected by pypi somehow 13:17:52 and we had to retry with 29.0.1 13:18:06 (rejected == some upload issue occured) 13:18:31 in theory we could use 29.0.0.post0 13:18:37 not convinced a .0post0 looks a lot better than a .1 13:18:44 instead of PATCH version bump 13:19:33 yeah, neither are nice :S 13:19:38 don't know which is better 13:19:57 anyway, this is still on my TODO o:) 13:20:01 (I mean, for our downstream users, the fact that all our versions follow basic semver is kind of a plus 13:20:18 looking at pbr/tests/test_version.py i think pbr wants to be in control of generating those, so having them appear in tags will run counter to that feature 13:20:45 Merged openstack/releases master: Set Zed state to Unmaintained https://review.opendev.org/c/openstack/releases/+/918034 13:20:47 Merged openstack/releases master: [zun-tempest-plugin] Tag zed-last https://review.opendev.org/c/openstack/releases/+/918354 13:21:19 anyway we don't need to decide now, just wanted to mention this 13:21:39 also it does e.g. 1.2.3.post5 (no leading 0 before "post") 13:21:44 anyway, the issue is probably that it prefers 6.0.0post0? looking at PEP440 13:22:27 or 6.0.0-post0 13:23:38 so yes, probably this has to be added pbr 13:23:52 Could be interesting to test if 6.0.0-post0 would pass tests 13:24:04 i think pbr would probably need to drop it's own "post-versioning" feature to do so 13:24:41 i'll try to work on it, to at least we will have the option if this can be easily added to pbr and release/validator 13:24:48 but that's not going to keep me awake at nights 13:24:53 :) 13:24:59 ok, let's close this 13:25:09 right now it wants to use "dev" for pre-versioned projects and "post" for post-versioned projects when generating versions based on number of commits after a tag 13:26:16 yeah, iirc -post was reserved for per-commit autoversioning, same way as -dev is 13:26:46 alright 13:26:49 #endmeeting