Open Stack

Hi all,

Ironic has a large amount of stable branches still in EM. We need to take
action to ensure those branches are either retired or have CI repaired to
the point of being usable.

Specifically, I'm looking at these branches across all Ironic projects:
- stable/queens
- stable/rocky
- stable/stein
- stable/train
- stable/ussuri
- stable/victoria

In lieu of any volunteers to maintain the CI, my recommendation for all the
branches listed above is that they be marked EOL. If someone wants to
volunteer to maintain CI for those branches, they can propose one of the
below paths be taken instead:

1 - Someone volunteers to maintain these branches, and also report the
status of CI of these older branches periodically on the Ironic whiteboard
and in Ironic meetings. If you feel strongly that one of these branches
needs to continue to be in service; volunteering in this way is how to save
them.

2 - We seriously reduce CI. Basically removing all tempest tests to ensure
that CI remains reliable and able to merge emergency or security fixes when
needed. In some cases; this still requires CI fixes as some older inspector
branches are failing *installing packages* in unit tests. I would still
like, in this case, that someone volunteers to ensure the minimalist CI
remains happy.

My intention is to let this message serve as notice and a waiting period;
and if I've not heard any response here or in Monday's Ironic meeting (in 6
days), I will begin taking action on retiring these branches.

This is simply a start; other branches (including bugfix branches) are also
in bad shape in CI, but getting these retired will significantly reduce the
surface area of projects and branches to evaluate.

I know it's painful to drop support for these branches; but we've provided
good EM support for these branches for a long time and by pruning them
away, we'll be able to save time to dedicate to other items.

Thanks,
Jay Faulkner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20221004/5c7732c2/attachment.htm>