Friday, 2024-04-05

opendevreviewMerged openstack/releases master: Add missing release notes for former releases  https://review.opendev.org/c/openstack/releases/+/91399807:37
opendevreviewDr. Jens Harbott proposed openstack/releases master: [senlin] Transition EM branches to EOL  https://review.opendev.org/c/openstack/releases/+/91511307:42
fricklerelodilles: ^^ to get things moving I now created ^^ as an alternative to your eom patch. please let me know if you want me to update your existing patches instead. also please let me know if you indeed intend to (un)maintain any of the still open projects07:44
elodillesfrickler: ACK, thanks, will review this and i'll go through the rest of the patches hopefully today07:56
elodillesbtw, do we have the relmgt weekly meeting today, or do we want to postpone it to next week (PTG)?07:58
fricklerI was expecting a meeting to happen and to talk about the vwx things and also about dalmatian->2024.2, but we can also defer to next week if others prefer08:15
hberaudrelease-team: do we want to run our weekly meeting this afternoon?08:43
hberaudoh sorry, just seen your discussion08:43
hberaudgithub seems really flaky today 08:47
ttxI think we can do a quick meeting, look at the review backlog12:31
fricklernote it will be at 16:00 CEST until we decide to move it, which we plan to talk about at the PTG, right?12:38
elodillesfrickler: ahh, you are right, 16:00 CEST12:50
elodillesmeanwhile i've started to prepare the dalmatian-relmgt-tracking pad: https://etherpad.opendev.org/p/dalmatian-relmgt-tracking12:50
elodilles(it's not yet finished, so colors will be lost)12:51
elodillesonly added next week's tasks so far12:52
fricklerelodilles: shouldn't that be https://etherpad.opendev.org/p/2024.2-relmgt-tracking ? *scnr*13:03
elodillesi don't want to confuse anyone with changing the habit o:)13:13
ttxso fun fact...13:56
ttxCaracal is the development cycle name. 2024.1 is the release name13:56
ttxThat's why milestones are called caracal-1 etc13:56
ttxIn theory we could delay the release until 2025, at which point its name would change to 2025.113:57
ttxso a lot of early things are named after the cycle13:57
ttx(that's the theory, at least)13:57
fricklerhmm, interesting theory13:58
ttxIt's all based on Ubuntu, where we originally took the idea13:58
ttxIn theory there (also lost in history, but I was there) Noble Numbat is the development cycle name, 24.04 is the release name13:58
fricklerthey're going to have a hard time to avoid it becoming 24.05 from what I'm currently seeing ;)14:00
ttxBack in early releases, you would have the "Essex" development cycle ending in a 2012.1 release14:00
ttxthen we stopped doing common release version names, then they were back14:01
ttxmeeting time! I can chair14:01
ttx#startmeeting releaseteam14:01
opendevmeetMeeting started Fri Apr  5 14:01:57 2024 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
opendevmeetThe meeting name has been set to 'releaseteam'14:01
fungiyou could say it's based on debian, their use of codenames pre-dates ubuntu's existence, and was precisely because of the inability to predict version numbers14:01
hberaudo/14:02
elodillesthanks ttx!14:02
elodilleso/14:02
frickler\o14:02
elodilles(we forgot to call for a chair on last meeting :S)14:02
ttxfungi: indeed. We borrowed the alpha ordering to ubuntu :)14:02
ttxPing list: elod armstrong release-team14:02
ttx#topic Review task completion14:03
ttxI hope they are all done, otherwise we have a problem :)14:03
elodilles:]14:03
ttxI did log one thing to change... check the map earlier in the process so that it's ready to update at release time14:04
elodillesall done fortunately, we striked out every finished tasks o:)14:04
fungii do need to remember to merge the signing key rotation change on monday14:04
ttxbut otherwise it went reasonably well14:04
ttxPyPI acted up a bit, and Zuul was not in its best day14:04
fungi#link https://review.opendev.org/913274 Replace 2024.1/Caracal key with 2024.2/Dalmatian14:04
fungialso i guess we can approve the revert of the semaphore removals now14:05
hberaudindeed14:05
ttxoh yes14:05
elodillesfungi: +114:05
fungi#link https://review.opendev.org/914689 Revert "Temporarily remove release docs semaphores"14:05
fungias for the zuul slowness we observed, we think we narrowed down the cause to a change in database queries which took effect on saturday in our weekly automated upgrades14:06
fungiupgrading the database server version ought to help, but we're still evaluating what we're going to upgrade it to14:07
hberaudupdate at which level? zuul?14:07
ttxhmm, maybe we should hold on those the weekend before release... but that would likely be a complex exception14:07
fungiyes, some database queries in zuul were made more correct, but that ended up not being able to take advantage of optimizations on older mysql versions14:07
hberaudi see thx14:08
ttx#topic Assign next week tasks14:08
fungiand the query planner on latest mariadb seems to also have problems with those queries, so we're doing parallel evaluations between mysql and mariadb performance now14:08
ttx#link https://etherpad.opendev.org/p/dalmatian-relmgt-tracking14:08
hberaudwon't be there so I'm skipping my turn14:09
elodillesACK14:09
ttxI can chair the PTG meeting unless someone else wants to14:11
elodillesttx: please do o:)14:11
ttxAlright all assigned14:12
ttx#topic Open Discussion14:12
ttxTwo things...14:12
elodillesnote: etherpad is not complete yet, so updates might arrive14:12
ttxI would move up the meeting time one hour now that everyone is on DST... but after next week PTG meeting14:13
ttxso 13:00utc instead of 14:00utc, starting April 1914:13
frickler+1 I proposed that last week already14:13
elodillesttx: +114:13
ttxwell starting May 3rd since next two irc meetings are skipped14:13
elodilles+114:14
ttxI can push the update to irc-meetings after the meeting14:14
elodillesagreed14:14
elodillesthanks o/14:14
ttxSecond... I'd like to look at the review backlog since there are a bunch of things that seem stuck14:14
ttxLike https://review.opendev.org/c/openstack/releases/+/88750514:15
ttxSo let's link to our favorite stuck reviews to give them immediate attention14:15
elodillesis there anyone from tripleo who could comment?14:16
elodillesi mean, if there isn't then let's merge :)14:17
fricklermost of the tripleo retirement is still blocked on content removal, but that one could go in IMO14:17
fricklerthe team is dissolved afaict14:17
frickleralso https://review.opendev.org/c/openstack/releases/+/910395 could then be abandoned IMO14:18
elodillesACK, if there's no activity at all around tripleo deliverables, then I'm OK with this14:18
elodillespatch LGTM14:18
fricklerthen there's the remainder of https://review.opendev.org/q/topic:%22vwx-unmaintained%22+status:open14:19
fricklerelodilles: did you look at my proposal from this morning yet?14:19
fricklerI can do that for the other inactive projects, too, if you agree14:20
frickler#link https://review.opendev.org/c/openstack/releases/+/91511314:20
fricklerjust for ref14:20
elodillesfrickler: haven't double-checked the hashes yet, but otherwise looks fine14:21
elodillesfrickler: please do14:21
ttxhberaud: looks like https://review.opendev.org/c/openstack/releases/+/872653 is blocked on you14:22
fricklerelodilles: I didn't check the hashes either I must admit, just took them from your patch ;)14:23
hberaudlemme check14:23
elodillesttx hberaud : wasn't that updated already with a different patch? :-o14:23
elodillesit looks familiar to me14:23
hberauddon't remember14:24
fricklerI think we did that recentish, yes14:24
elodillesoh, nope, that was another patch14:24
elodilleswe did add it to R-8 week's mail14:25
elodilles'Cycle highlights deadline: $highlights (R-4 week)'14:25
ttxWe also need some stance on https://review.opendev.org/c/openstack/reno/+/904049 -- I don;t care that much either way, but would lean toward accepting since it's been so gracefully proposed14:25
fricklerto me this is similar to pbr, we shouldn't drop support until we really need to14:27
ttxShould we close https://review.opendev.org/q/topic:%22zed-stable%22+status:open in the absence of PTL+1 ?14:27
frickler+1 to closing zed-stable14:27
opendevreviewHervĂ© Beraud proposed openstack/releases master: update the cycle highlight date into the mail template  https://review.opendev.org/c/openstack/releases/+/87265314:28
ttxthere is a non-zero chance those releases are no longer current anyway14:28
elodilleswell, i'll close them then, zed will move to Unmaintained in a month anyway14:28
elodillesi'm sure that e.g. neutron team will do another release before the transition14:28
fricklerthen there's the 2024.2 vs. dalmatian situation for links and possibly also for the deliverables directory name. despite ttx's theory I'd like to use the former everywhere14:28
ttxfungi: is there a project-wide stance on aggressive Python version abandonment?14:28
elodillesbut let's abandon these old patches14:28
fricklerhttps://review.opendev.org/c/openstack/releases/+/903635 seems related14:29
fungittx: not really, no14:29
* elodilles clicks and doing the abandonings14:29
ttxfungi: context: https://review.opendev.org/c/openstack/reno/+/90404914:29
hberaudpython 3.6 is EOL14:29
fricklerand https://review.opendev.org/c/openstack/releases/+/914619 need discussion I guess14:29
hberaudand Python 3.7 is close to EOL14:29
hberaudI think that's the point with this reno patch...14:30
fricklerhberaud: but only upstream, not for distros, right?14:30
hberaudyes14:30
fungithere's a project-wide stance on adding support for new python versions as early as possible, but we don't insist or necessarily even encourage projects to drop support or testing for old versions unless there's some other reason it's necessary14:30
ttxAny reason to hold on https://review.opendev.org/c/openstack/releases/+/912714 https://review.opendev.org/c/openstack/releases/+/910456 https://review.opendev.org/c/openstack/releases/+/913305 ?14:30
fungi"stop supporting x because it's old" isn't really a great argument. "stop supporting x because we want to use some newer thing that will be really hard to retain backward compatibility for" is reasonable14:31
ttxok14:31
fungithat said, reno doesn't strictly need to be run on older python versions, unlike pbr14:32
fricklerttx: those all depends on open gov changes?14:32
elodillesttx: the patches on 'depends-on' not merged there14:32
ttxdamn14:32
elodillesthough it would be good to merge these 'retire' patches ASAP :/14:32
elodillesbefore trailing Caracal release at least :P14:33
ttxAlrigth, that's all I had14:34
ttxAnything else before we close the meeting?14:34
elodillesabout py36&py37 dropping patch: we had a bad experience when the community started to drop py38 versions and things became broken due to things not supporting the proper versions :S so i have a fear when seeing these patches o:)14:35
ttxre: openstack map on the website I'll get it updated asap to match openstack-map repo contents14:35
fricklerassuming I'll get feedback on the patches I mentioned later, that's it for me14:35
fricklerttx: I'll be happy to review a new review before pusblishing if needed14:36
frickler*a new version14:36
frickler*publishing14:36
ttxack thanks14:37
ttxok, last words?14:37
elodilles:X14:38
elodilles(nothing from me)14:38
ttx#endmeeting14:38
opendevmeetMeeting ended Fri Apr  5 14:38:41 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:38
opendevmeetMinutes:        https://meetings.opendev.org/meetings/releaseteam/2024/releaseteam.2024-04-05-14.01.html14:38
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/releaseteam/2024/releaseteam.2024-04-05-14.01.txt14:38
opendevmeetLog:            https://meetings.opendev.org/meetings/releaseteam/2024/releaseteam.2024-04-05-14.01.log.html14:38
elodillesthanks ttx o/14:38
ttxThanks everyone! Great work on Caracal!14:38
elodilles\o/14:38
*** hberaud is now known as hberaud_PTO15:00
elodillesfrickler: your senlin patch LGTM, +2'd. thanks for proposing it! about the rest: feel free to reuse my patches, or prepare a separate patch if you want, it's up to you.15:02
elodillesfrickler: solum, freezer, sahara, murano, karbor, qinling, tripleo patches could be the same15:05
elodillesfrickler: btw, i can also update the patches if you want me to do that15:05
elodillesjust let me know which one you prefer o:)15:06
opendevreviewElod Illes proposed openstack/releases master: [Puppet OpenStack] Transition EM branches to Unmaintained  https://review.opendev.org/c/openstack/releases/+/91040815:15
opendevreviewElod Illes proposed openstack/releases master: [sahara] Transition EM branches to Unmaintained  https://review.opendev.org/c/openstack/releases/+/91041515:27
elodillesfrickler: sahara patch ^^^15:28
opendevreviewElod Illes proposed openstack/releases master: [sahara] Transition EM branches to EOL  https://review.opendev.org/c/openstack/releases/+/91041515:31
elodilleseven ^^^15:31
fricklerelodilles: thx, will check later and see what you've left for me ;)15:50
opendevreviewElod Illes proposed openstack/releases master: [solum] Transition EM branches to EOL  https://review.opendev.org/c/openstack/releases/+/91039615:51
elodillesdoing them slowly, will see how far i get :)15:52
opendevreviewElod Illes proposed openstack/releases master: [freezer] Transition EM branches to EOL  https://review.opendev.org/c/openstack/releases/+/91040715:56
opendevreviewElod Illes proposed openstack/releases master: [murano] Transition EM branches to EOL  https://review.opendev.org/c/openstack/releases/+/91042215:59
ttxfrickler: a new map should be up later today... let me know if you see any remaining issue with it16:16
opendevreviewElod Illes proposed openstack/releases master: [karbor] Transition EM branches to EOL  https://review.opendev.org/c/openstack/releases/+/91042716:52
opendevreviewElod Illes proposed openstack/releases master: [qinling] Transition EM branches to EOL  https://review.opendev.org/c/openstack/releases/+/91042616:54
fungifrickler: ttx: probably worth asking for input from the tc once the new map is published, whether e.g. skyline should be omitted since it's still in an "emerging technology" state, and whether there was a reason to intentionally omit sunbeam or whether that's an oversight17:44
fungiaha, it's up! https://www.openstack.org/software/17:46
gmannttx: frickler:fungi: I think it can be confusing for Inactive project moving to Active projects. I replied in tc channel 17:52
gmannI think sunbeam is just oversight17:52
gmannwe have the task to update map in 'repo retirement process' but many times it can be missed and we fix that as soon as it is detected17:53

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