This makes lot of sense to me in particular because we have now a number of sub-projects that depends on camel so we don't want them to be left behind
--- Luca Burgazzoli On Fri, Feb 28, 2020 at 8:04 AM Andrea Cosentino <anco...@gmail.com> wrote: > +1, we could also add this information on the website and a column with lts > true/false on the releases page. > > Il giorno ven 28 feb 2020 alle ore 07:45 Jean-Baptiste Onofre < > j...@nanthrax.net> ha scritto: > > > Hi, > > > > I agree, it makes sense to me. I think that more than fast, we should > have > > a "regular pace" in term of releases (even if the releases don’t contain > > much). > > > > Regards > > JB > > > > > Le 28 févr. 2020 à 07:39, Claus Ibsen <claus.ib...@gmail.com> a écrit > : > > > > > > Hi > > > > > > We have released Camel 3.0 and 3.1 yesterday. As Camel v3 is a major > > > new foundation with all the effort that went into it, then we want to > > > take the new few releases to continue as there are things we need to > > > work on. > > > > > > Therefore we want to have a more aggressive release schedule and > > > release more frequent releases but they are not LTS releases (long > > > term support). Therefore these releases likely only have 1 patch > > > releases, eg 3.0.1, or none at all. > > > > > > When we hit Camel 3.3 then its expected to be a LTS release and have > > > patch releases for a longer period of time. > > > > > > And in fact this model is maybe something we want to continue > > > thereafter and be able to mark releases as LTS and non LTS. Eg just > > > like the JDK etc. > > > > > > > > > -- > > > Claus Ibsen > > > ----------------- > > > http://davsclaus.com @davsclaus > > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > >
