| *** bauzas_ is now known as bauzas | 00:50 | |
| opendevreview | Merged openstack/openstack-zuul-jobs master: Move openstack-tox-py311-arm64 to be with openstack-tox-py311 https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/922989 | 03:44 |
|---|---|---|
| opendevreview | Jens Harbott proposed openstack/openstack-zuul-jobs master: Switch the openstack-tox-py312* jobs to distro packages https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/922992 | 03:45 |
| opendevreview | Merged openstack/openstack-zuul-jobs master: Add openstack-tox-py312-arm64 job https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/922990 | 03:46 |
| opendevreview | Merged openstack/openstack-zuul-jobs master: Add openstack-tox-py313 jobs https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/922991 | 03:50 |
| frickler | ^^ approved the whole stack now (cf. the discussion three days ago) | 03:50 |
| opendevreview | Merged openstack/openstack-zuul-jobs master: Switch the openstack-tox-py312* jobs to distro packages https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/922992 | 04:05 |
| frickler | gmann: maybe you remember why we left the stable/v-z branch tags in a lot of places in the templates? can't we simply drop these by now? | 05:36 |
| opendevreview | Merged openstack/project-config master: Migrate release-openstack-puppet to jammy https://review.opendev.org/c/openstack/project-config/+/925986 | 06:21 |
| *** bauzas_ is now known as bauzas | 07:02 | |
| opendevreview | Jens Harbott proposed openstack/project-config master: Update update-constraints job and script https://review.opendev.org/c/openstack/project-config/+/926405 | 10:23 |
| *** bauzas_ is now known as bauzas | 12:30 | |
| gmann | frickler: I think we need to convert them stable/v-z -> */v-z for unmaintained namespace otherewise it can impact unmaintained branch testing | 16:55 |
| frickler | gmann: I really want to get rid of all that extra work needing to get done for unmaintained stuff, this isn't in line with the idea to make things simpler for everyone | 17:04 |
| frickler | I also don't think that having periodic unmaintained jobs will be useful with the current state of the enterprise | 17:05 |
| gmann | frickler: yeah, I cannot disagree with you. I am ok to remove. and if needed they can define job or add those tags back. | 17:06 |
| gmann | they means unmaintained maintainers | 17:06 |
| gmann | but I agree on your point of 'extra work needing to get done for unmaintained stuff,' | 17:07 |
| frickler | ok, I'll do a patch on top of your's once you amend according to jamespage's comment | 17:07 |
| gmann | sure, will check that soon | 17:09 |
| fungi | something we were talking about in #openstack-infra last week was that it might make sense if we can start discussions about finding unmaintained caretakers in the final 6 months of a stable branch's maintenance rather than only starting to talk about it once end-of-maintenance is reached. if so, we could avoid unnecessarily creating unmaintained branches in projects entirely except | 17:18 |
| fungi | where they're explicitly opted into, and that would save a fair amount of work for everyone on branches that are just going to sit there and then get deleted 6 months later when nobody volunteers to take care of them | 17:18 |
| frickler | well there are volunteers that said they would take care, but it seems they underestimated the amount of work that is needed | 17:39 |
| fungi | in some cases yes, but right now the default process is that we automatically add unmaintained branches and then give people 6 months to volunteer to start taking care of them | 17:42 |
| fungi | which means we then end up deleting many of those after a mere 6 months, when we could instead have probably avoided creating them at all | 17:43 |
| frickler | we did that for zed because it still was some transition cycle, but I'm not sure that that is how it is planned to proceed going forward | 17:46 |
| frickler | the release patches that create unmaintained/2023.1 IMO would need approval from volunteers, otherwise they'd be converted to eol patches | 17:48 |
| fungi | going back through https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html#unmaintained-branches it looks like the policy is to create the branches automatically, but maybe the requirement to acknowledge creation of them is merely unstated there | 17:54 |
| frickler | yes, maybe there's still a delta between governance and implementation, or between TC and release team | 18:13 |
| frickler | but if we take "The CI for all branches must be in good standing at the time of opt-in." stricly, a lot of branches are going to be eoled pretty soon | 18:14 |
| opendevreview | Ghanshyam proposed openstack/openstack-zuul-jobs master: Prepare python testing templates for stable/2024.2 https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/926152 | 18:15 |
| gmann | frickler: jamespage ^^ | 18:16 |
| *** bauzas_ is now known as bauzas | 19:01 | |
| *** bauzas_ is now known as bauzas | 23:12 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!