On Mon, Jan 2, 2023 at 9:38 AM Christofer Dutz <[email protected]> wrote:
> Hi all, > > Would be cool if anyone could at least acknowledge some of the things I > reported in my vote on 4.20.0. > Or are such thorough release checks not expected or desired? > > It’s usually a lot of work to do such checks … so if they are not wanted, > I’ll just stop doing them ;-) > > Thanks for the review in the 3.20.0 release. This thread is about a patch release (3.20.1) so we want to release it as-is. For the next 3.21 / 4.0 releases, then we have time to look into your findings. To not forget I have created a JIRA https://issues.apache.org/jira/browse/CAMEL-18851 > Chris > > > From: Claus Ibsen <[email protected]> > Date: Wednesday, 28. December 2022 at 19:13 > To: dev <[email protected]> > Subject: Camel 3.20.1 Release > Hi > > I think it would be a good idea to cut a new patch release in January as > 3.20.0 has a performance impact and some other related fixes done. > > For example > https://issues.apache.org/jira/browse/CAMEL-18844 > > To avoid this users of 3.20.0 can exclude camel-console JAR that in some > situations mistakenly is included out of the box. > > This has been corrected via > https://issues.apache.org/jira/browse/CAMEL-18847 so that is no longer the > case. > > Also I have fixed/improved some unnecessary object allocation that are not > needed, only when using camel-tracing/camel-opentelemtry. > > We have also upgraded to Spring Boot 2.7.7 that was recently released. > > > > -- > Claus Ibsen > ----------------- > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen ----------------- @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
