I propose that we start step by step for our first LTS I aim to backport port the fixes for every quarter and create a "." release in the same time we create normal releases
ex for 2025: Match 13.0.0 LTS Jun 13.0.1 LTS 13.1.0 regular September 13.0.2 LTS 13.2.0 regular December 13.0.3 LTS 13.3.0 regular If the LTS releases are accepted by the community we will put the release roadmap on our documentation page Best regards Alin On Tue, Feb 11, 2025 at 10:41 AM Sebastien Lorquet <sebast...@lorquet.fr> wrote: > Hello, > > This is an excellent idea. > > How will we manage maintenance of these LTS releases? Some fixes are > likely to require some backports? > > Sebastien > > > On 11/02/2025 09:54, Alin Jerpelea wrote: > > Hi all, > > > > there have been suggestions that we should create LTS releases > > > > I propose that we mark every Q1 (match) release as a LTS release and > > maintain it for 2 years. this would always ensure a fresh LTS overlapping > > the old one and allowing the users to migrate the code to the new > release. > > > > What do you think? > > > > Best regards > > Alin > > >
