[oslo] Propose to EOL stable/queens, stable/rocky on all the oslo scope
Hi,
On our last meeting of the oslo team we discussed the problem with broken stable branches (rocky and older) in oslo's projects [1].
Indeed, almost all these branches are broken. Előd Illés kindly generated a list of periodic-stable errors on Oslo's stable branches [2].
Given the lack of active maintainers on Oslo and given the current status of the CI in those branches, I propose to make them End Of Life.
I will wait until the end of month for anyone who would like to maybe step up as maintainer of those branches and who would at least try to fix CI of them.
If no one will volunteer for that, I'll EOLing those branches for all the projects under the oslo umbrella.
Let us know your thoughts.
Thank you for your attention.
[1] https://meetings.opendev.org/meetings/oslo/2021/oslo.2021-10-04-15.00.log.tx... [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023939.html
Hi Herve,
Please correct me, does that mean we have to also EOL stable/queens and stable/rocky for most of the other projects technically? Or it should be OK? Thanks.
On 5/10/21 5:09 am, Herve Beraud wrote:
Hi,
On our last meeting of the oslo team we discussed the problem with broken stable branches (rocky and older) in oslo's projects [1].
Indeed, almost all these branches are broken. Előd Illés kindly generated a list of periodic-stable errors on Oslo's stable branches [2].
Given the lack of active maintainers on Oslo and given the current status of the CI in those branches, I propose to make them End Of Life.
I will wait until the end of month for anyone who would like to maybe step up as maintainer of those branches and who would at least try to fix CI of them.
If no one will volunteer for that, I'll EOLing those branches for all the projects under the oslo umbrella.
Let us know your thoughts.
Thank you for your attention.
[1] https://meetings.opendev.org/meetings/oslo/2021/oslo.2021-10-04-15.00.log.tx... [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023939.html
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud
Hi,
On poniedziałek, 4 października 2021 20:46:29 CEST feilong wrote:
Hi Herve,
Please correct me, does that mean we have to also EOL stable/queens and stable/rocky for most of the other projects technically? Or it should be OK? Thanks.
I don't think we have to. I think it's not that common that we are using new versions of oslo libs in those stable branches so IMHO if all works fine for some project and it has maintainers, it still can be in EM phase. Or is my understanding wrong here?
On 5/10/21 5:09 am, Herve Beraud wrote:
Hi,
On our last meeting of the oslo team we discussed the problem with broken stable branches (rocky and older) in oslo's projects [1].
Indeed, almost all these branches are broken. Előd Illés kindly generated a list of periodic-stable errors on Oslo's stable branches [2].
Given the lack of active maintainers on Oslo and given the current status of the CI in those branches, I propose to make them End Of Life.
I will wait until the end of month for anyone who would like to maybe step up as maintainer of those branches and who would at least try to fix CI of them.
If no one will volunteer for that, I'll EOLing those branches for all the projects under the oslo umbrella.
Let us know your thoughts.
Thank you for your attention.
2021-10-04-15.00.log.tx
t [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-July/
023939.html
On 10/4/21 2:00 PM, Slawek Kaplonski wrote:
Hi,
On poniedziałek, 4 października 2021 20:46:29 CEST feilong wrote:
Hi Herve,
Please correct me, does that mean we have to also EOL stable/queens and stable/rocky for most of the other projects technically? Or it should be OK? Thanks.
I don't think we have to. I think it's not that common that we are using new versions of oslo libs in those stable branches so IMHO if all works fine for some project and it has maintainers, it still can be in EM phase. Or is my understanding wrong here?
The Oslo libs released for those versions will continue to work, so you're right that it wouldn't be necessary to EOL all of the consumers of Oslo.
The danger would be if a critical bug were found in one of those old releases and a fix needed to be released. However, at this point the likelihood of finding such a serious bug seems pretty low, and in some cases it may be possible to use a newer Oslo release with an older service.
On 5/10/21 5:09 am, Herve Beraud wrote:
Hi,
On our last meeting of the oslo team we discussed the problem with broken stable branches (rocky and older) in oslo's projects [1].
Indeed, almost all these branches are broken. Előd Illés kindly generated a list of periodic-stable errors on Oslo's stable branches [2].
Given the lack of active maintainers on Oslo and given the current status of the CI in those branches, I propose to make them End Of Life.
I will wait until the end of month for anyone who would like to maybe step up as maintainer of those branches and who would at least try to fix CI of them.
If no one will volunteer for that, I'll EOLing those branches for all the projects under the oslo umbrella.
Let us know your thoughts.
Thank you for your attention.
2021-10-04-15.00.log.tx
t [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-July/
023939.html
What Ben wrote is correct.
One comment for the topic: oslo projects have Pike open (and broken) as well, so together with stablre/rocky and stable/queens stable/pike branches should be also marked as End of Life if no maintainers stepping up for these branches.
Thanks,
Előd
On 2021. 10. 04. 22:59, Ben Nemec wrote:
On 10/4/21 2:00 PM, Slawek Kaplonski wrote:
Hi,
On poniedziałek, 4 października 2021 20:46:29 CEST feilong wrote:
Hi Herve,
Please correct me, does that mean we have to also EOL stable/queens and stable/rocky for most of the other projects technically? Or it should be OK? Thanks.
I don't think we have to. I think it's not that common that we are using new versions of oslo libs in those stable branches so IMHO if all works fine for some project and it has maintainers, it still can be in EM phase. Or is my understanding wrong here?
The Oslo libs released for those versions will continue to work, so you're right that it wouldn't be necessary to EOL all of the consumers of Oslo.
The danger would be if a critical bug were found in one of those old releases and a fix needed to be released. However, at this point the likelihood of finding such a serious bug seems pretty low, and in some cases it may be possible to use a newer Oslo release with an older service.
On 5/10/21 5:09 am, Herve Beraud wrote:
Hi,
On our last meeting of the oslo team we discussed the problem with broken stable branches (rocky and older) in oslo's projects [1].
Indeed, almost all these branches are broken. Előd Illés kindly generated a list of periodic-stable errors on Oslo's stable branches [2].
Given the lack of active maintainers on Oslo and given the current status of the CI in those branches, I propose to make them End Of Life.
I will wait until the end of month for anyone who would like to maybe step up as maintainer of those branches and who would at least try to fix CI of them.
If no one will volunteer for that, I'll EOLing those branches for all the projects under the oslo umbrella.
Let us know your thoughts.
Thank you for your attention.
2021-10-04-15.00.log.tx
t [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-July/
023939.html
Hi Oslo team,
Is there anything that hinders the transition to EOL? This thread is seemingly got stuck somewhere.
...the periodic stable job failure count is still quite high, mostly because oslo's old stable branches are still failing :-/ Since those gates are broken for several months now and no patches were able to land, I think moving oslo's rocky, queens and pike branches to End of Life is unfortunately quite reasonable.
(Also note, that I've just sent a mail about mass-EOL Pike series [1])
[1] http://lists.openstack.org/pipermail/openstack-discuss/2022-June/029250.html
Thanks,
Előd
On 2021. 10. 14. 15:42, Előd Illés wrote:
What Ben wrote is correct.
One comment for the topic: oslo projects have Pike open (and broken) as well, so together with stablre/rocky and stable/queens stable/pike branches should be also marked as End of Life if no maintainers stepping up for these branches.
Thanks,
Előd
On 2021. 10. 04. 22:59, Ben Nemec wrote:
On 10/4/21 2:00 PM, Slawek Kaplonski wrote:
Hi,
On poniedziałek, 4 października 2021 20:46:29 CEST feilong wrote:
Hi Herve,
Please correct me, does that mean we have to also EOL stable/queens and stable/rocky for most of the other projects technically? Or it should be OK? Thanks.
I don't think we have to. I think it's not that common that we are using new versions of oslo libs in those stable branches so IMHO if all works fine for some project and it has maintainers, it still can be in EM phase. Or is my understanding wrong here?
The Oslo libs released for those versions will continue to work, so you're right that it wouldn't be necessary to EOL all of the consumers of Oslo.
The danger would be if a critical bug were found in one of those old releases and a fix needed to be released. However, at this point the likelihood of finding such a serious bug seems pretty low, and in some cases it may be possible to use a newer Oslo release with an older service.
On 5/10/21 5:09 am, Herve Beraud wrote:
Hi,
On our last meeting of the oslo team we discussed the problem with broken stable branches (rocky and older) in oslo's projects [1].
Indeed, almost all these branches are broken. Előd Illés kindly generated a list of periodic-stable errors on Oslo's stable branches [2].
Given the lack of active maintainers on Oslo and given the current status of the CI in those branches, I propose to make them End Of Life.
I will wait until the end of month for anyone who would like to maybe step up as maintainer of those branches and who would at least try to fix CI of them.
If no one will volunteer for that, I'll EOLing those branches for all the projects under the oslo umbrella.
Let us know your thoughts.
Thank you for your attention.
2021-10-04-15.00.log.tx
t [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-July/
023939.html
participants (5)
-
Ben Nemec
-
Előd Illés
-
feilong
-
Herve Beraud
-
Slawek Kaplonski