On 8/21/25 10:20 AM, thomas@goirand.fr wrote:
Please name that somewhere. Are you suggesting I maintain my own deployment of Gerrit?
Create a custom repo using a host of your choice; I would probably use something like codeberg these days. I do not know if the OpenDev team would be willing to host anything unofficial but generally speaking the point is just that: it wouldn't be official and it wouldn't be a sap on the resources of the larger management team.
Also, the fact users cannot invest enough of their time upgrading is still something unadressed in OpenStack. If we're lacking workforce, there are ways to fix it, like having a release per year instead of 2, so we'd have 3 years of support instead of just one and a half.
As Jeremy already indicated, we have taken these actions including: - reducing the number of branches that extend into stable support which lowers the overall contributor load. I do not wish to reintroduce additional load by adding additional branches to manage. - implementing SLURP so that users have to upgrade half as often as they used to
P.S: you do realise Red Hat still maintains Train, right ?
No, I didn't actually -- and that's the point. Train was released in 2019 -- it's 6 years old at this point. Nobody should run it. If we had a publicly open train branch, even for downstream collaboration, I suspect we'd still be seeing a huge number of operators using train -- even though it doesn't officially support any upstream-supported python versions. If Redhat chooses to support this for their customers, I appreciate that they don't publicize this fact loudly for the reasons I stated in my last email. -JayF