Friday, 2024-05-17

opendevreviewyatin proposed openstack/releases master: New Dalmatian ovsdbapp release 2.7.1  https://review.opendev.org/c/openstack/releases/+/91991604:55
opendevreviewJens Harbott proposed openstack/releases master: Retire sahara: mark deliverables retired  https://review.opendev.org/c/openstack/releases/+/91940208:07
opendevreviewSylvain Bauza proposed openstack/releases master: Nova deadlines for Dalmatian schedule  https://review.opendev.org/c/openstack/releases/+/91842208:31
opendevreviewThierry Carrez proposed openstack/releases master: Update team exceptions in ACL issues script  https://review.opendev.org/c/openstack/releases/+/91992809:22
opendevreviewMerged openstack/releases master: Nova deadlines for Dalmatian schedule  https://review.opendev.org/c/openstack/releases/+/91842209:57
elodillesrelease-team: reminder: the weekly meeting is about to start in ~10 minutes12:49
hberaudack12:50
elodilles#startmeeting releaseteam13:00
opendevmeetMeeting started Fri May 17 13:00:03 2024 UTC and is due to finish in 60 minutes.  The chair is elodilles. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
opendevmeetThe meeting name has been set to 'releaseteam'13:00
hberaudo/13:00
elodillesPing list: release-team elod13:00
frickler\o13:00
elodilles#link https://etherpad.opendev.org/p/dalmatian-relmgt-tracking13:00
elodilleswe are @ L9713:00
elodilleso/13:00
elodillesDalmatian-1 ~o~13:00
hberaudlife is too short...13:01
ttxo/13:02
elodillesand development cycles fly by13:02
elodilleslet's start!13:02
elodilles#topic Review task completion13:02
elodilles1st task: 'Ensure that all trailing projects have been branched for the previous series. (elod)'13:02
elodilleskayobe (kolla) and openstack-ansible were not branched13:02
elodilleshttps://review.opendev.org/q/topic:caracal-trailing-branch-cut13:02
elodillespatches proposed but teams responded with -1 ^^^13:03
elodillesso we have to keep an eye on these and follow up later13:03
elodilles2nd task: 'Propose autoreleases for cycle-with-intermediary libraries which did not release since the previous release. (elod)'13:03
elodilleshttps://review.opendev.org/q/topic:dalmatian-milestone-113:04
elodillespatches were generated ^^^13:04
elodillesmany deliverables had only non-functional changes, so around half needed a release patch13:04
elodillesand as you can see there are many without response from team13:05
elodillesi've +2+PTL-Approved+1'd them, so I think it's OK to proceed with them13:06
elodillesif you'll have time to review13:06
ttxTime to fill out the team reponse scorecard at the bottom of the etherpad!13:06
elodilleshmmm, right, let me add details quickly13:07
elodillesdone13:11
elodillesmove on then:13:12
elodilles3rd task: 'Catch if there are acl issues in newly created repositories (ttx)'13:12
elodilles* puppet-ceph triggered an issue, but was exempted recently13:13
elodilles* updated aclissues to reflect that: https://review.opendev.org/c/openstack/releases/+/91992813:13
elodillesanything to add ttx ?13:13
ttxoh sorry13:13
ttxNot much to add... 13:14
elodillesACK13:14
elodilles4th task: 'Process Unmaintained transitioning patches for stable/zed (all)'13:14
ttxWe could change the code so that it's more granular (per repo instead of per-team) but that will do for now13:14
elodillesttx: +113:14
ttxLinking back to the change with the decision is a great improvement already13:14
elodillesACK13:17
elodillesso, about the zed to unmaintained/zed:13:17
elodilleshttps://review.opendev.org/q/topic:zed-unmaintained+is:open13:17
elodilleswe still have 2 patches to sort out,13:18
elodillesbut these are special cases13:19
elodilleswinstackers -> needs EOL rather13:19
elodillesand openstack-ansible patch needs an update13:20
elodilles#action elod to move winstckers to EOL and update OSA zed-unmtained patch13:21
elodillesi'll take care of these ^^^13:21
ttxsounds good13:22
elodillesthese were all of the tasks!13:22
elodilles#topic Assign R-19 and R-18 week tasks13:22
ttxI'm mostly traveling next week13:22
elodillesACK13:23
hberaudwill be a short one week for me too13:23
ttxwe need a meeting chair for the meeting in two weeks13:23
elodillesa bit shorter to me, too, though it still will be 4 days to me :)13:23
elodillesthx hberaud :)13:24
hberaudtaken13:24
elodillesjust like the tasks! thanks everyone!13:24
elodillesmove on then13:24
elodilles#topic Review countdown email for week R-1913:24
elodilles#link https://etherpad.opendev.org/p/relmgmt-weekly-emails13:24
elodillesplease review ^^^13:25
elodillesone thing to mention:13:25
elodillesi'm not sure about the 'goals'13:25
elodillesare they still active goals?13:25
elodillesit looks like stale tasks13:25
ttxyeah, I was about to ask13:25
elodillese.g. migrate to jammy :S13:26
ttxIIRC last cycle we skipped that mention.. Let me doublecheck13:26
elodillesshould be more like noble :)13:26
fricklersrbac is still active afaict13:26
elodillesyes, that one is a long standing task, that's true13:26
ttxLat cycle we just said "Teams should now be focused on feature development."13:27
elodillesso this somewhat feels half-relevant13:27
ttxthe TC has not set goals for a while now13:27
elodillesyes13:27
fricklerI'll take updating/checking that list to the TC13:27
ttxso I support just saying "feature development"13:27
elodillesat least not 'cycle goals'13:27
elodillesttx: +113:27
hberaudlgtm13:27
elodillesfrickler: thanks!13:27
elodillesmail updated13:28
ttxWe might want to edit the template if goals are not going to come back13:28
fricklerwell we have some in the pipeline like eventlet deprecation13:29
ttxlgtm13:29
fricklerbut no consensus on the path forward yet13:29
frickler+1 to the mail13:29
elodillesyeah, that one, too :S13:29
elodillesanyway, frickler can you update us with info from TC next time?13:30
fricklernot sure it will happen that fast, but I'll try to13:30
elodilleswe could wait with the template update until that is disclosed13:30
elodillesACK13:30
elodillesanyway, thanks for the reviews, i'll send the mail after the meeting some time13:31
elodilles#topic Open Discussion13:31
elodilleswe have one topic:13:31
elodilles#info (frickler) Automated EOL for feature branches13:31
elodilles#link https://review.opendev.org/c/openstack/releases/+/917788/113:31
elodilles#link https://review.opendev.org/c/openstack/releases/+/90081013:32
fricklerI found these while looking at open reviews, not sure how to best proceed13:32
elodillesso these are about feature + bugfix branches13:32
frickleron one hand I'd like to see those feature branches go away, otoh not sure how much we actually want to get involved13:32
elodillesand note, that these are only the branches/deliverables that are listed on releases repo13:33
fricklerwell https://review.opendev.org/c/openstack/releases/+/917781 would want to add tags for branches that aren't listed currently13:34
fricklerif we want to proceed, some agreement on the actual tag name structure would be needed first I guess13:36
elodillesright. so, so far only *deliverables* that are listed in releases repo13:36
ttxNo strong opinion, I would be fine not getting involved13:36
ttxwe handle master and stable branches already, it feels like that's enough :)13:36
hberaud+1 with ttx 13:36
fricklerwell we kind of added the handling of unmaintained branches already13:37
hberaudat first glance I think it complexify things more than something else13:38
fricklerwhich aren't directly release related, so maybe we already crossed a line there13:38
ttxI'm fine with the tooling handling it13:39
elodillesfrickler: true, series-eol and series-eom were not directly release related, but still, they are somewhat closer i'd say13:39
ttxBut I would not necessarily track those13:40
hberaudfeature branches, are just feature branches, not sure to see the point with eoling them...13:40
fricklerso you'd just delete them without a trace?13:40
hberaudyeah13:41
fricklerand you'd let teams do that manually? or how would there be tooling for that if we have no record?13:42
ttxThat's an option. They were meant as glorified sets of changes13:42
hberaudmanually13:42
fricklerand does the same hold for bugfix branches or are those different?13:42
hberaudgood question, I think bugfix branches are slightly different use cases13:43
hberaudIMO13:43
elodillesironic team handled bugfix branches manually, but by some accident, our tooling re-created some of the branches, so i think that's where the automation idea came from, mainly. (that bug i think (and hope) is fixed in our tooling)13:45
hberauda feature branch, if implementation on it is done, is supposed to be reintegrated somewhere in the official branches13:45
ttxyeah I could see making a case for eoling bugfix branches13:45
hberauda feat branch is IMO a temp branch dedicated to develop a feature and basta13:46
elodillesyepp that makes sense ^^^13:46
hberaudbut naming and semnatic can diverge between teams... maybe they are seeing feature branches like bugfix branches... don't know13:47
hberaudbut that's my definition of a feature branch13:47
fricklerok so let's maybe check with timburke whether they can agree to that13:47
hberaudsomething temporary13:47
hberaudok13:47
fricklerand then I'll try with rpittau to proceed with the bugfix patch13:48
elodillesfrickler: ACK, thanks in advance!13:48
elodillesanything else to discuss?13:49
hberaudnope13:49
fricklerwell we had gmann's proposal for eoling stable branches of retired projects13:50
frickler(half my idea I admit)13:50
frickler#link https://review.opendev.org/c/openstack/project-team-guide/+/91960813:50
ttxmakes sense I think?13:52
elodillesoh, i haven't reviewed that yet13:52
elodillesto me it's a bit too harsh to directly EOL those stable branches, but I don't object if that is the decision13:52
elodillesi mean, we close the option to people show up as maintainers for those repos13:53
elodillesbut i know that it is quite unlikely13:53
fricklerthere should be at least 6 months of inactivity before retirement happens13:53
elodillesand even inactivity haven't come out of the blue :)13:54
elodillesso that's true13:54
fricklerand a repo could always be un-retired again13:54
elodillesi mean some of these repos were just inactive through multiple cycles :/13:54
hberaudIt won't hurt IMO13:54
fricklerthe opposing concern that on not doing this, people could continue using the stable branch without noticing the retirement13:55
elodillesso as I said, i don't object o:)13:55
elodillesfrickler: that's also true13:55
elodillesanyway, feel free to ping me for reviews to those EOL patches and I can +2 them13:56
fricklerthose still need to be created iiuc, but will do13:56
elodilles++13:56
fricklergmann: ^^13:56
elodillesany other topic to the remaining 3 minutes? :)13:57
ttxwould not mind having them back before jumpiung on my next meeting :)13:57
elodilles:)13:57
elodillesthanks everyone then! o/13:58
elodilles#endmeeting13:58
opendevmeetMeeting ended Fri May 17 13:58:06 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:58
opendevmeetMinutes:        https://meetings.opendev.org/meetings/releaseteam/2024/releaseteam.2024-05-17-13.00.html13:58
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/releaseteam/2024/releaseteam.2024-05-17-13.00.txt13:58
opendevmeetLog:            https://meetings.opendev.org/meetings/releaseteam/2024/releaseteam.2024-05-17-13.00.log.html13:58
ttxThanks elodilles !13:58
hberaudthanks elodilles 13:58
elodilleso/13:58
fricklerthx all13:58
fungiin theory, at least, successful feature branches should get merged back to the master branch and then deleted at that time14:35
ykarelreview please for ovsdbapp release https://review.opendev.org/c/openstack/releases/+/91991614:43
gmannfrickler: thanks for bringing that.17:01
opendevreviewGhanshyam proposed openstack/releases master: Retire Solum: mark deliverables retired  https://review.opendev.org/c/openstack/releases/+/91922517:41
opendevreviewGhanshyam proposed openstack/releases master: Retire Murano: mark deliverables retired  https://review.opendev.org/c/openstack/releases/+/91937317:44
opendevreviewGhanshyam proposed openstack/releases master: Retire ec2-api: mark deliverables retired  https://review.opendev.org/c/openstack/releases/+/91940117:55

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