Ok. It makes sense. As we have nothing more to do with 5.2.0 I can stage
today ans start the vote. Next I could do the Karaf upgrade in 5.[3,4].x.
It would be good if you could write the migrations news

Regaeds
Krzysztof
On Jan 9, 2015 3:11 PM, "Gert Vanthienen" <[email protected]> wrote:

> Hi Krzysztof,
>
>
> This is one of those two branches to allow people to smoothly
> transition from Karaf 2.3.x/Camel 2.13.x to Karaf 2.4.x/Camel 2.14.x -
> in this case, by upgrading the Camel version first and staying with
> the original Karaf version. Since we already have the branch set up, I
> think it would make sense to do at least one release of it. Perhaps we
> can do a little "migration" news item to explain the use case for the
> 5.2.0 and 5.3.0 as intermediate releases? If you're already too busy
> doing the other two releases, I don't mind sharing a bit of the
> workload and doing this one.
>
>
> Regards,
>
> Gert Vanthienen
> Regards,
>
> Gert Vanthienen
>
>
> On Thu, Jan 8, 2015 at 9:26 PM, Krzysztof Sobkowiak
> <[email protected]> wrote:
> > Hi
> >
> > We have another branch using following components:
> >
> > Dependency      Version
> > ActiveMQ        5.10.0
> > Camel   2.14.1
> > CXF     3.0.2
> > Karaf   2.3.9
> >
> >
> > We have never released from this branch. Do you think we should release
> > 5.2.0?
> >
> > Regards
> > Krzysztof
> >
> >
> >
> > --
> > Krzysztof Sobkowiak
> >
> > JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer
> > @ ASF
> > Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
> > <http://www.pl.capgemini-sdm.com/> | Wroclaw
> > e-mail: [email protected] <mailto:[email protected]> |
> > Twitter: @KSobkowiak
> > Calendar: http://goo.gl/yvsebC
>

Reply via email to