I find it very difficult to start a such huge and important challenge as
Camel 3.0 will be, for sure. I think the most difficult part is to get
consensus about what we do it and how we do it. We already collect some
useful ideas at [1], but I have the feeling we have to review these ideas.
First of
Yeah, we need a detail plan and time table for the Camel 3.0.0.
As we have the patch release for the major Camel release, it is make sense to
change the Camel version of 3.0.0
BTW, merge the patches into three different branches makes us have less time to
think about the new version of Camel, I
Christian,
Thanks for taking the initiative and restarting the process for Camel
3.0. The good news imho is that we're under no pressure and we can take
the time to get it right.
I like your proposal of effectively splitting the camel-3.0-roadmap page
into multiple pages. If I understand cor
Hi Hadrian!
Please find my comments inline.
Best,
Christian
On Thu, Jan 17, 2013 at 2:47 PM, Hadrian Zbarcea wrote:
> Christian,
>
> Thanks for taking the initiative and restarting the process for Camel 3.0.
> The good news imho is that we're under no pressure and we can take the time
> to get