---- On Thu, 06 Jul 2023 10:05:29 -0700 Nikolla, Kristi wrote ---
Thanks for making that point Jeremy.
As a courtesy to allow the TC to provide a resolution with coordinated guidelines for EOL-ing branches across projects, we please ask that you wait until the end of July at the latest.
If no consensus has been reached on approving a new EM policy has been reached until the end of July, it is within your power, as the policy is written today, to EOL all branches based on an internal team decision.
As every TC policy resolution requires staying open for at least 1 week, and taking into account 1-2 weeks of deliberation, that is the earliest that we can reasonably approve a new policy.
Also, we will be discussing it in next TC meeting in Tuesday video call. if no consensus in that meeting, I will send more call invite so that we can discuss this in speedy way. Everyone are welcome to join the TC call in that discussion. - https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee -gmann
Thank you, Kristi Nikolla
On Jul 5, 2023, at 4:18 PM, Jeremy Stanley fungi@yuggoth.org> wrote:
On 2023-07-05 11:14:21 -0700 (-0700), Ghanshyam Mann wrote: [...]
Even though we were not able to get any solution to existing EM issue and TC is working on that and hopefully we will come to the agreement soon (even it might be killing the EM process). [...] IMO, we should wait for overall decision on EM so that we can keep consistency to our operator. Whatever the agreement will be, it will be same for all projects and give a clear consistency to Operators. [...]
While I appreciate that this decision on the part of the Cinder contributors puts the overall OpenStack community in a bit of a quandary, it would be good to let them know how long they're being asked to wait for official feedback from the TC, so that they can proceed with their original plan (backed by existing stable maintenance policy) if the debate continues to drag out. Can the TC please commit to reaching a conclusion by some specific deadline? -- Jeremy Stanley