Maintaining an entire project, especially catching it up after it's been neglected, is a serious amount of work. Are you (and your employer) committing to do this work? Are there any other interested parties that could keep Mistral maintained if you were to move on? Just wanting to ensure we're going to have the project setup for long-term support, given we promise each release will be supported for years to come.

Thanks, Jay

On Wed, Dec 7, 2022 at 5:34 AM Arnaud Morin arnaud.morin@gmail.com wrote:

Hey all,

With Axel [1], we propose to maintain the Mistral development.

This is new to us, so we will need help from the community but we really want to be fully commited so mistral will continue beeing maintained under openinfra.

If you think we are too late for antelope, this can maybe happen for the next release?

Cheers,

[1] https://lists.openstack.org/pipermail/openstack-discuss/2022-December/031417...

On 05.12.22 - 10:52, Elõd Illés wrote:

...

Hi,

Mistral projects are unfortunately not actively maintained and caused

hard times in latest official series releases for release management team. Thus we discussed this and decided to propose to deprecate Mistral [1] to avoid broken releases and last minute debugging of gate issues (which usually fall to release management team), and remove mistral projects from 2023.1 Antelope release [2].

...

We would like to ask @TC to evaluate the situation and review our

patches (deprecation [1] + removal from the official release [2]).

...

Thanks in advance,

Előd Illés irc: elodilles @ #openstack-release

[1] https://review.opendev.org/c/openstack/governance/+/866562 [2] https://review.opendev.org/c/openstack/releases/+/865577

Hi everyone, I'm one of mistral core team members. As was mentioned, mistral is also used by other companies (Netcracker). As the community was kinda quiet, we were focused on our personal mistral fork, also we had not enough human resources to keep it up with upstream. But now things have changed - as you may notice by gerrit, we started to push our bugfixes/improvements to upstream and we have a huge list to complete.

It's an amazing coincidence that the topic about deprecating mistral was started *after* two companies that are interested in mistral returned for community work. I'm also happy that someone is ready to take responsibility to perform PTL stuff and we will help them as much as we can. Let me know if you have any questions.

Best regards, Oleg Ovcharuk

чт, 8 дек. 2022 г. в 11:46, Axel Vanzaghi axel.vanzaghi@ovhcloud.com:

Hello,

We (me and my employer) are really committing to do this work, it has been discussed and we agreed on this internally.

Thing is, this project is currently vital for us so we will maintain it, either we do it with the community or not. We know it's a serious amount of work, more than if we keep it for us, but we think it would be better for everyone if we give back to the community.

We also know we are not the only ones using it, someone has seen the discussion about its deprecation and us proposing to maintain it [1], and sent us a mail to tell us he has use cases, and even features and improvements. I'll ask him to stand up in this thread.

Regards,

Axel

[1] https://review.opendev.org/c/openstack/governance/+/866562

*From:* Jay Faulkner jay@gr-oss.io *Sent:* Wednesday, December 7, 2022 5:06:14 PM *To:* Arnaud Morin *Cc:* Elõd Illés; openstack-discuss@lists.openstack.org *Subject:* Re: [tc][mistral][release] Propose to deprecate Mistral

Maintaining an entire project, especially catching it up after it's been neglected, is a serious amount of work. Are you (and your employer) committing to do this work? Are there any other interested parties that could keep Mistral maintained if you were to move on? Just wanting to ensure we're going to have the project setup for long-term support, given we promise each release will be supported for years to come.

Thanks, Jay

On Wed, Dec 7, 2022 at 5:34 AM Arnaud Morin arnaud.morin@gmail.com wrote:

...

Hey all,

With Axel [1], we propose to maintain the Mistral development.

This is new to us, so we will need help from the community but we really want to be fully commited so mistral will continue beeing maintained under openinfra.

If you think we are too late for antelope, this can maybe happen for the next release?

Cheers,

[1] https://lists.openstack.org/pipermail/openstack-discuss/2022-December/031417...

On 05.12.22 - 10:52, Elõd Illés wrote:

...

Hi,

Mistral projects are unfortunately not actively maintained and caused

hard times in latest official series releases for release management team. Thus we discussed this and decided to propose to deprecate Mistral [1] to avoid broken releases and last minute debugging of gate issues (which usually fall to release management team), and remove mistral projects from 2023.1 Antelope release [2].

...

We would like to ask @TC to evaluate the situation and review our

patches (deprecation [1] + removal from the official release [2]).

...

Thanks in advance,

Előd Illés irc: elodilles @ #openstack-release

[1] https://review.opendev.org/c/openstack/governance/+/866562 [2] https://review.opendev.org/c/openstack/releases/+/865577

---- On Thu, 08 Dec 2022 10:47:03 -0800 Ghanshyam Mann wrote ---

---- On Thu, 08 Dec 2022 01:22:43 -0800 Oleg Ovcharuk wrote ---

...

Hi everyone, I'm one of mistral core team members.As was mentioned, mistral is also used by other companies (Netcracker). As the community was kinda quiet, we were focused on our personal mistral fork, also we had not enough human resources to keep it up with upstream.But now things have changed - as you may notice by gerrit, we started to push our bugfixes/improvements to upstream and we have a huge list to complete. It's an amazing coincidence that the topic about deprecating mistral was started *after* two companies that are interested in mistral returned for community work. I'm also happy that someone is ready to take responsibility to perform PTL stuff and we will help them as much as we can.Let me know if you have any questions.

Thanks, Oleg for your response. It is good to see more than one companies are interested to maintain the Mistral. As the next step, let's do this:

• Do the required work to release it. You can talk to the release team about pending things. Accordingly, we can decide on this patch https://review.opendev.org/c/openstack/governance/+/866562
• Oleg or any other existing core member can onboard Axel and Arnaud in the maintainer list (what all resp you would like to give it up to the existing core members of Mistral).
• As Mistral is in the DPL model now, if you guys wanted to be moved to the PTL model, you can do it any time. These are the requirement[1] and example[2]

Ping us in #openstack-tc IRC channel for any query/help you need.

Hi Mistral team,

As the Mistral gate is fixed now and things are better. Is there any plan to release it for m-2.

Accordingly, we can decide on the - https://review.opendev.org/c/openstack/governance/+/866562

-gmann

[1] https://governance.openstack.org/tc/resolutions/20200803-distributed-project... [2] https://review.opendev.org/c/openstack/governance/+/829037

-gmann

...

Best regards,Oleg Ovcharuk чт, 8 дек. 2022 г. в 11:46, Axel Vanzaghi axel.vanzaghi@ovhcloud.com>: Hello,

We (me and my employer) are really committing to do this work, it has been discussed and we agreed on this internally.

Thing is, this project is currently vital for us so we will maintain it, either we do it with the community or not. We know it's a serious amount of work, more than if we keep it for us, but we think it would be better for everyone if we give back to the community.

We also know we are not the only ones using it, someone has seen the discussion about its deprecation and us proposing to maintain it [1], and sent us a mail to tell us he has use cases, and even features and improvements. I'll ask him to stand up in this thread.

Regards, Axel

[1] https://review.opendev.org/c/openstack/governance/+/866562

From: Jay Faulkner jay@gr-oss.io> Sent: Wednesday, December 7, 2022 5:06:14 PM To: Arnaud Morin Cc: Elõd Illés; openstack-discuss@lists.openstack.org Subject: Re: [tc][mistral][release] Propose to deprecate Mistral Maintaining an entire project, especially catching it up after it's been neglected, is a serious amount of work. Are you (and your employer) committing to do this work? Are there any other interested parties that could keep Mistral maintained if you were to move on? Just wanting to ensure we're going to have the project setup for long-term support, given we promise each release will be supported for years to come.

Thanks,Jay

On Wed, Dec 7, 2022 at 5:34 AM Arnaud Morin arnaud.morin@gmail.com> wrote: Hey all,

With Axel [1], we propose to maintain the Mistral development.

This is new to us, so we will need help from the community but we really want to be fully commited so mistral will continue beeing maintained under openinfra.

If you think we are too late for antelope, this can maybe happen for the next release?

Cheers,

[1] https://lists.openstack.org/pipermail/openstack-discuss/2022-December/031417...

On 05.12.22 - 10:52, Elõd Illés wrote:

...

Hi,

Mistral projects are unfortunately not actively maintained and caused hard times in latest official series releases for release management team. Thus we discussed this and decided to propose to deprecate Mistral [1] to avoid broken releases and last minute debugging of gate issues (which usually fall to release management team), and remove mistral projects from 2023.1 Antelope release [2].

We would like to ask @TC to evaluate the situation and review our patches (deprecation [1] + removal from the official release [2]).

Thanks in advance,

Előd Illés irc: elodilles @ #openstack-release

[1] https://review.opendev.org/c/openstack/governance/+/866562 [2] https://review.opendev.org/c/openstack/releases/+/865577