EOL Camel 3.0.x

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

EOL Camel 3.0.x

Claus Ibsen-2
Hi

When Camel 3.1.0 is GA I would actually like to EOL 3.0.x quickly.

This release has some flaws like excessive object allocations and a
memory leak in recipient list / toD under certain conditions, among
others things.

The 3.1.0 is really a much better release and we should encourage
3.0.x users to update to it. And we have a good guide
https://camel.apache.org/manual/latest/camel-3x-upgrade-guide.html



--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Reply | Threaded
Open this post in threaded view
|

Re: EOL Camel 3.0.x

Andrea Cosentino-3
I'm +1 on this. We have some fixes on camel-3.0.x, so maybe we could have a
little patch release and then stop.

Il giorno lun 24 feb 2020 alle ore 17:22 Claus Ibsen <[hidden email]>
ha scritto:

> Hi
>
> When Camel 3.1.0 is GA I would actually like to EOL 3.0.x quickly.
>
> This release has some flaws like excessive object allocations and a
> memory leak in recipient list / toD under certain conditions, among
> others things.
>
> The 3.1.0 is really a much better release and we should encourage
> 3.0.x users to update to it. And we have a good guide
> https://camel.apache.org/manual/latest/camel-3x-upgrade-guide.html
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
Reply | Threaded
Open this post in threaded view
|

Re: EOL Camel 3.0.x

Gregor Zurowski-2
In reply to this post by Claus Ibsen-2
Yes, it makes sense. I would suggest we put something about this on our
website so that users are aware of this.

Thanks,
Gregor


On Mon, Feb 24, 2020, 5:22 PM Claus Ibsen <[hidden email]> wrote:

> Hi
>
> When Camel 3.1.0 is GA I would actually like to EOL 3.0.x quickly.
>
> This release has some flaws like excessive object allocations and a
> memory leak in recipient list / toD under certain conditions, among
> others things.
>
> The 3.1.0 is really a much better release and we should encourage
> 3.0.x users to update to it. And we have a good guide
> https://camel.apache.org/manual/latest/camel-3x-upgrade-guide.html
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
Reply | Threaded
Open this post in threaded view
|

Re: EOL Camel 3.0.x

Claus Ibsen-2
On Tue, Feb 25, 2020 at 2:49 PM Gregor Zurowski
<[hidden email]> wrote:
>
> Yes, it makes sense. I would suggest we put something about this on our
> website so that users are aware of this.
>

Yeah lets include this details in the 3.1 release notes and also
create a separate news blog about the EOL and suggested to upgrade to
3.1.0 when possible.

Then we can work on cutting 2.25.1 patch and a 3.1.1 patch releases next month.


> Thanks,
> Gregor
>
>
> On Mon, Feb 24, 2020, 5:22 PM Claus Ibsen <[hidden email]> wrote:
>
> > Hi
> >
> > When Camel 3.1.0 is GA I would actually like to EOL 3.0.x quickly.
> >
> > This release has some flaws like excessive object allocations and a
> > memory leak in recipient list / toD under certain conditions, among
> > others things.
> >
> > The 3.1.0 is really a much better release and we should encourage
> > 3.0.x users to update to it. And we have a good guide
> > https://camel.apache.org/manual/latest/camel-3x-upgrade-guide.html
> >
> >
> >
> > --
> > 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