Wednesday, 2026-03-04

*** ykarel_ is now known as ykarel07:03
fricklermnasiadka: I missed to discuss this in the TC meeting, but since there was no objection here, I've now gone ahead and added you to the requirements-core group. we'll need to talk to elodilles about the stable group, but for now I think the master branch has the most focus08:12
frickler(stable branches are mostly still borked anyway (not that it wouldn't be great to get them fixed, but I won't have time to look into that any time soon))08:12
mnasiadkafrickler: ack, but I guess it’s FF time, so there’s only stephenfin’s request?08:23
fricklermnasiadka: well there are a couple of other changes that could use a CR-2 and an explaining comment, like https://review.opendev.org/c/openstack/requirements/+/969327 https://review.opendev.org/c/openstack/requirements/+/978157 and https://review.opendev.org/c/openstack/requirements/+/97762608:40
frickleralso technically, requirements freeze is a bit different from feature freeze, it only affects non-openstack libraries. new "new-release" patches are still to be merged asap08:41
mnasiadkaIt would probably good to document the requirements freeze process a bit (and how to request for an exception) - I don’t see it in https://docs.openstack.org/project-team-guide/dependency-management.html08:45
fricklermnasiadka: yes, I was thinking the same, but I also lack the historical context. the best I could find is https://releases.openstack.org/reference/process.html#r-5-week-milestone-3 , but yes, an explicit doc would be better. elodilles do you still know more about this?08:55
elodilleslet me read back08:57
elodillesyeah, so, yes, what i know is what we have in RelMgt Process docs o:)08:59
elodillesso basically what frickler wrote08:59
elodillesi think RFEs need to be considered one-by-one, whether they could bring more risks in if we merge them than benefit.09:00
elodillesso definitely no mass req bumps should be merged09:01
mnasiadkaOk, I was thinking about the explaining comment - it would be nice to just have a link09:13
fricklerI fear linking to the release process is the best we have for now09:14
opendevreviewMerged openstack/requirements master: update constraint for networking-generic-switch to new release 9.0.0  https://review.opendev.org/c/openstack/requirements/+/97867910:45
stephenfinmnasiadka: frickler: On my request, is there anything I need to do beyond that email? I'd obviously like to get our gates back in a passing state so I can merge some other bugfixes12:20
stephenfinI am also likely to have another requests for fixtures for the same reason. I'm guessing I should send a separate mail for that12:20
opendevreviewStephen Finucane proposed openstack/requirements master: Bump fixtures  https://review.opendev.org/c/openstack/requirements/+/97887112:29
mnasiadkaprometheanfire: what about the testtools FFE that stephenfin raised as well? I don’t feel empowered yet enough to grant it (since the DPL reset patch hasn’t landed yet) - but happy to do so if you’re fine with it15:38
* stephenfin lurks15:39
mnasiadkastephenfin: I’ll wait for next 20 minutes, if prometheanfire doesn’t oppose - I’ll take the liberty to approve and merge15:44
stephenfinmnasiadka: ack, thanks15:49
mnasiadkastephenfin: done15:59
stephenfinmnasiadka++ ty16:53
stephenfinand prometheanfire++ too (just saw the emails)17:28
-opendevstatus- NOTICE: The Gerrit service on review.opendev.org will be offline momentarily for a software upgrade18:12
opendevreviewMerged openstack/requirements master: Bump fixtures  https://review.opendev.org/c/openstack/requirements/+/97887118:32
opendevreviewMerged openstack/requirements master: Bump testtools  https://review.opendev.org/c/openstack/requirements/+/97832918:38
prometheanfiresorry, was afk, looks like it was managed though :D22:25

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