You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Claus Ibsen <cl...@gmail.com> on 2020/02/28 06:39:47 UTC
[DISCUSS] - LTS and non-LTS releases coming to Apache Camel 3.x
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
Re: [DISCUSS] - LTS and non-LTS releases coming to Apache Camel 3.x
Posted by Luca Burgazzoli <lb...@gmail.com>.
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 <an...@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 <
> jb@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 <cl...@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
> >
> >
>
Re: [DISCUSS] - LTS and non-LTS releases coming to Apache Camel 3.x
Posted by Andrea Cosentino <an...@gmail.com>.
+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 <
jb@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 <cl...@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
>
>
Re: [DISCUSS] - LTS and non-LTS releases coming to Apache Camel 3.x
Posted by Jean-Baptiste Onofre <jb...@nanthrax.net>.
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 <cl...@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
Re: [DISCUSS] - LTS and non-LTS releases coming to Apache Camel 3.x
Posted by Zoran Regvart <zo...@regvart.com>.
Hi Cameleers,
I've created CAMEL-14681[1] for the website changes relating to
LTS/non-LTS releases, please join the discussion there.
zoran
[1] https://issues.apache.org/jira/browse/CAMEL-14681
On Sun, Mar 8, 2020 at 4:12 AM Tadayoshi Sato <sa...@gmail.com> wrote:
>
> Hello,
>
> Node.js is also famous for LTS-based releasing, so it might give some
> inspiration for us:
> https://nodejs.org/en/download/
>
> The download page is separated with the two tabs: LTS and Current (latest
> features), highlighting LTS so users can know which should be used for most
> cases.
>
> My two cents.
>
> On Mon, Mar 2, 2020 at 6:43 PM Claus Ibsen <cl...@gmail.com> wrote:
>
> > Hi
> >
> > Okay so I have looked a bit around what other ASF projects do and I
> > got a bit inspired by Karaf
> > http://karaf.apache.org/download.html
> >
> > So in the top we can have links to the latest downloads (a bit like
> > today) but since we start to have releases that are LTS and not-LTS
> > then we need to show that information. And since this page is
> > automatic then its harder as how would it know if its a TLS release or
> > not?
> >
> > But the Karaf schedule table is nice and that can help users to see
> > Java version and next version etc.
> >
> >
> > On Sat, Feb 29, 2020 at 2:19 PM Claus Ibsen <cl...@gmail.com> wrote:
> > >
> > > Hi
> > >
> > > Okay so lets get some write-up about this as a blog post on the Camel
> > website.
> > >
> > > And change the download page to cover this and we can have a TLS [x]
> > > for which release that gets patch releases.
> > > https://camel.apache.org/download/
> > >
> > > On Fri, Feb 28, 2020 at 7:39 AM Claus Ibsen <cl...@gmail.com>
> > wrote:
> > > >
> > > > 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
> > >
> > >
> > >
> > > --
> > > Claus Ibsen
> > > -----------------
> > > http://davsclaus.com @davsclaus
> > > Camel in Action 2: https://www.manning.com/ibsen2
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
>
>
> --
> Tadayoshi Sato
--
Zoran Regvart
Re: [DISCUSS] - LTS and non-LTS releases coming to Apache Camel 3.x
Posted by Tadayoshi Sato <sa...@gmail.com>.
Hello,
Node.js is also famous for LTS-based releasing, so it might give some
inspiration for us:
https://nodejs.org/en/download/
The download page is separated with the two tabs: LTS and Current (latest
features), highlighting LTS so users can know which should be used for most
cases.
My two cents.
On Mon, Mar 2, 2020 at 6:43 PM Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> Okay so I have looked a bit around what other ASF projects do and I
> got a bit inspired by Karaf
> http://karaf.apache.org/download.html
>
> So in the top we can have links to the latest downloads (a bit like
> today) but since we start to have releases that are LTS and not-LTS
> then we need to show that information. And since this page is
> automatic then its harder as how would it know if its a TLS release or
> not?
>
> But the Karaf schedule table is nice and that can help users to see
> Java version and next version etc.
>
>
> On Sat, Feb 29, 2020 at 2:19 PM Claus Ibsen <cl...@gmail.com> wrote:
> >
> > Hi
> >
> > Okay so lets get some write-up about this as a blog post on the Camel
> website.
> >
> > And change the download page to cover this and we can have a TLS [x]
> > for which release that gets patch releases.
> > https://camel.apache.org/download/
> >
> > On Fri, Feb 28, 2020 at 7:39 AM Claus Ibsen <cl...@gmail.com>
> wrote:
> > >
> > > 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
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
--
Tadayoshi Sato
Re: [DISCUSS] - LTS and non-LTS releases coming to Apache Camel 3.x
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Okay so I have looked a bit around what other ASF projects do and I
got a bit inspired by Karaf
http://karaf.apache.org/download.html
So in the top we can have links to the latest downloads (a bit like
today) but since we start to have releases that are LTS and not-LTS
then we need to show that information. And since this page is
automatic then its harder as how would it know if its a TLS release or
not?
But the Karaf schedule table is nice and that can help users to see
Java version and next version etc.
On Sat, Feb 29, 2020 at 2:19 PM Claus Ibsen <cl...@gmail.com> wrote:
>
> Hi
>
> Okay so lets get some write-up about this as a blog post on the Camel website.
>
> And change the download page to cover this and we can have a TLS [x]
> for which release that gets patch releases.
> https://camel.apache.org/download/
>
> On Fri, Feb 28, 2020 at 7:39 AM Claus Ibsen <cl...@gmail.com> wrote:
> >
> > 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
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: [DISCUSS] - LTS and non-LTS releases coming to Apache Camel 3.x
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Okay so lets get some write-up about this as a blog post on the Camel website.
And change the download page to cover this and we can have a TLS [x]
for which release that gets patch releases.
https://camel.apache.org/download/
On Fri, Feb 28, 2020 at 7:39 AM Claus Ibsen <cl...@gmail.com> wrote:
>
> 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
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2