[all][tc] Proposals for reforming extended maintenance
Hi all, There have been quite a few discussions related extended maintenance in the last few months[0][1]. I have made a first-go at trying to write a policy for extended maintenance moving forward which tries to preserve the value being brought by extended maintenance while strengthening the requirements for keeping branches under that phase. [2] This was based on multiple discussions that I was present at and feedback that I have received from various teams and community members with which I talked, and is my interpretation of that feedback into something that looks like policy. I have also written two opposing policy proposals about what do to with the current branches under extended maintenance. One which attempts to apply the new requirements defined in the first proposal almost immediately[3], and one that aims for a more gradual EOL[4]. Please provide feedback on the proposals and help shape up the future of extended maintenance. Thank you, Kristi Nikolla [0]. https://lists.openstack.org/pipermail/openstack-discuss/2023-June/033980.htm... [1]. https://etherpad.opendev.org/p/vancouver-2023-em [2]. https://review.opendev.org/c/openstack/governance/+/887966 [3]. https://review.opendev.org/c/openstack/governance/+/887968 [4]. https://review.opendev.org/c/openstack/governance/+/887969
---- On Fri, 07 Jul 2023 08:15:30 -0700 Nikolla, Kristi wrote ---
Hi all,
There have been quite a few discussions related extended maintenance in the last few months[0][1].
I have made a first-go at trying to write a policy for extended maintenance moving forward which tries to preserve the value being brought by extended maintenance while strengthening the requirements for keeping branches under that phase. [2] This was based on multiple discussions that I was present at and feedback that I have received from various teams and community members with which I talked, and is my interpretation of that feedback into something that looks like policy.
I have also written two opposing policy proposals about what do to with the current branches under extended maintenance. One which attempts to apply the new requirements defined in the first proposal almost immediately[3], and one that aims for a more gradual EOL[4].
Please provide feedback on the proposals and help shape up the future of extended maintenance.
Thanks, Kristi for the proposal. I have created the below etherpad for this discussion, where we will first discuss all problems and the discussion of the possible solutions before jumping to the one. I have collected a few of the solutions/ways we discussed till now, which include the 887966 proposal too. Feel Free to add more possible options in etherpad. - https://etherpad.opendev.org/p/openstack-exteneded-maintenance We can use the same etherpad to collect the discussion at a single place, either from TC meetings or any further calls if there will be any. -gmann
Thank you, Kristi Nikolla
[0]. https://lists.openstack.org/pipermail/openstack-discuss/2023-June/033980.htm... [1]. https://etherpad.opendev.org/p/vancouver-2023-em [2]. https://review.opendev.org/c/openstack/governance/+/887966 [3]. https://review.opendev.org/c/openstack/governance/+/887968 [4]. https://review.opendev.org/c/openstack/governance/+/887969
There is interesting and useful discussion in the governance patches posted by Kristi. I strongly recommend folks take a look and participate. The more independent opinions we get, the better off the end result will be. Thanks, Jay Faulkner TC Member On Fri, Jul 7, 2023 at 4:25 PM Nikolla, Kristi <knikolla@bu.edu> wrote:
Hi all,
There have been quite a few discussions related extended maintenance in the last few months[0][1].
I have made a first-go at trying to write a policy for extended maintenance moving forward which tries to preserve the value being brought by extended maintenance while strengthening the requirements for keeping branches under that phase. [2] This was based on multiple discussions that I was present at and feedback that I have received from various teams and community members with which I talked, and is my interpretation of that feedback into something that looks like policy.
I have also written two opposing policy proposals about what do to with the current branches under extended maintenance. One which attempts to apply the new requirements defined in the first proposal almost immediately[3], and one that aims for a more gradual EOL[4].
Please provide feedback on the proposals and help shape up the future of extended maintenance.
Thank you, Kristi Nikolla
[0]. https://lists.openstack.org/pipermail/openstack-discuss/2023-June/033980.htm... [1]. https://etherpad.opendev.org/p/vancouver-2023-em [2]. https://review.opendev.org/c/openstack/governance/+/887966 [3]. https://review.opendev.org/c/openstack/governance/+/887968 [4]. https://review.opendev.org/c/openstack/governance/+/887969
Based on discussion from the OpenStack Technical Committee on July 11 and the feedback received on the proposed patch, I have submitted a newer version of the proposal at https://review.opendev.org/c/openstack/governance/+/888771 From: Jay Faulkner <jay@gr-oss.io> Date: Tuesday, July 11, 2023 at 7:06 AM To: Nikolla, Kristi <knikolla@bu.edu> Cc: openstack-discuss <openstack-discuss@lists.openstack.org> Subject: Re: [all][tc] Proposals for reforming extended maintenance There is interesting and useful discussion in the governance patches posted by Kristi. I strongly recommend folks take a look and participate. The more independent opinions we get, the better off the end result will be. Thanks, Jay Faulkner TC Member On Fri, Jul 7, 2023 at 4:25 PM Nikolla, Kristi <knikolla@bu.edu<mailto:knikolla@bu.edu>> wrote: Hi all, There have been quite a few discussions related extended maintenance in the last few months[0][1]. I have made a first-go at trying to write a policy for extended maintenance moving forward which tries to preserve the value being brought by extended maintenance while strengthening the requirements for keeping branches under that phase. [2] This was based on multiple discussions that I was present at and feedback that I have received from various teams and community members with which I talked, and is my interpretation of that feedback into something that looks like policy. I have also written two opposing policy proposals about what do to with the current branches under extended maintenance. One which attempts to apply the new requirements defined in the first proposal almost immediately[3], and one that aims for a more gradual EOL[4]. Please provide feedback on the proposals and help shape up the future of extended maintenance. Thank you, Kristi Nikolla [0]. https://lists.openstack.org/pipermail/openstack-discuss/2023-June/033980.htm... [1]. https://etherpad.opendev.org/p/vancouver-2023-em [2]. https://review.opendev.org/c/openstack/governance/+/887966 [3]. https://review.opendev.org/c/openstack/governance/+/887968 [4]. https://review.opendev.org/c/openstack/governance/+/887969
participants (3)
-
Ghanshyam Mann
-
Jay Faulkner
-
Nikolla, Kristi