Open Stack

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 at 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.html
>
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20221207/04447353/attachment.htm>