i think we cannot avoid committers from working on 2.x, but the general
approach should be to focus on 3.

Il giorno mar 10 dic 2019 alle ore 15:43 Guillaume Nodet <[email protected]>
ha scritto:

> Le mar. 10 déc. 2019 à 11:51, Claus Ibsen <[email protected]> a écrit
> :
>
> > Hi
> >
> > Now that Camel 3 is out, its the main branch for new features etc.
> >
> > Camel 2.x is closing down, and Camel 2.25 is the last planned new
> > minor release for the 2.x line. All net new development happens on
> > Camel 3.x.
> >
> > I think we should work on getting a blog post on the Camel website
> > with the details of this, and the lifecycle of the 2.x.
> >
> > For example we can say something like:
> >
> > Camel 2.25 is the last new minor release of Camel 2.x. All net new
> > development now happens on Camel 3.x.
> >
> > For Camel 2.x, then only bug fixes and security vulnerabilities will
> > be fixed on the 2.25.x branch, and released from time to time in 2020.
> > At the end of the year 2020 Camel 2.x will be retired and EOL.
> >
>
> I would not be so abrupt. Plus, we can't really forbid committer to step up
> and
> support the 2.x branches... so I'd rather say something along:
>
> All new development now happens on Camel 3.x, so Camel 2.25
> is the last planned minor release of the Camel 2.x branch.
>
> We will continue to backport bug fixes and security vulnerabilities
> on the 2.x branches and provide releases from time to time, but we
> won't commit to support the 2.x branches after 2020.
>
> For those reasons, we do encourage all users to upgrade to Camel 3.x.
>
>
> >
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
>
>
> --
> ------------------------
> Guillaume Nodet
>

Reply via email to