On Wed, Dec 19, 2018 at 9:01 AM Andrea Cosentino
wrote:
> Does it work for everybody if I remove the sandbox/camel-3.x branch now,
> avoiding confusion?
+1 on `sandbox/camel-3.x` removal, `master` looks good to me
zoran
--
Zoran Regvart
+1
---
Luca Burgazzoli
On Wed, Dec 19, 2018 at 10:02 AM Claus Ibsen wrote:
>
> On Wed, Dec 19, 2018 at 9:01 AM Andrea Cosentino
> wrote:
> >
> > Does it work for everybody if I remove the sandbox/camel-3.x branch now,
> > avoiding confusion?
> >
>
> +1
>
> > Thanks
> >
> > --
> > Andrea Cosent
On Wed, Dec 19, 2018 at 9:01 AM Andrea Cosentino
wrote:
>
> Does it work for everybody if I remove the sandbox/camel-3.x branch now,
> avoiding confusion?
>
+1
> Thanks
>
> --
> Andrea Cosentino
> --
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Serv
Does it work for everybody if I remove the sandbox/camel-3.x branch now,
avoiding confusion?
Thanks
--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
Done this morning.
The 2.x branch is now called camel-2.x, while master has been moved to what we
had in sandbox/camel-3.x
--Andrea Cosentino --Apache Camel PMC
ChairApache Karaf CommitterApache Servicemix PMC MemberEmail:
ancosen1985@yahoo.comTwitter: @oscerd2Git
On Mon, Dec 17, 2018 at 3:32 PM Andrea Cosentino
wrote:
>
> If it works for everyone the next steps should be:
>
> - On Wednesday morning I'll send an email with an alert about the creation of
> 2.x branch from master
> - I'll move sanbox/camel-3.x to master shortly after pushing 2.x
>
> Does thi
+1, let's start it.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Mon, Dec 17, 2018 at 10:32 PM Andrea Cosentino
wrote:
>
> If it works for everyone the next steps should be:
>
> - On Wednesday morning I'll send an email with an alert about the creation of
> 2.x branch from master
> - I
+1
---
Luca Burgazzoli
On Mon, Dec 17, 2018 at 3:44 PM Claus Ibsen wrote:
>
> On Mon, Dec 17, 2018 at 3:32 PM Andrea Cosentino
> wrote:
> >
> > If it works for everyone the next steps should be:
> >
> > - On Wednesday morning I'll send an email with an alert about the creation
> > of 2.x bran
On Mon, Dec 17, 2018 at 3:32 PM Andrea Cosentino wrote:
>
> If it works for everyone the next steps should be:
>
> - On Wednesday morning I'll send an email with an alert about the creation of
> 2.x branch from master
> - I'll move sanbox/camel-3.x to master shortly after pushing 2.x
>
> Does thi
If it works for everyone the next steps should be:
- On Wednesday morning I'll send an email with an alert about the creation of
2.x branch from master
- I'll move sanbox/camel-3.x to master shortly after pushing 2.x
Does this work for all? Thoughts?
--
Andrea Cosentino
---
Sure. Let me open a different one.
--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Friday, December 14, 2018, 2:59:22 PM GMT+1, Claus Ibsen
wr
Hi
Can we please move the discussion about Java 8 and 11 to another
thread, and keep this focused on the subj.
On Fri, Dec 14, 2018 at 2:34 AM Willem Jiang wrote:
>
> I think for the average the enterprise JDK user they may still use JDK
> 8 for a long time.
> If we start the Camel 3.x, we stil
I think for the average the enterprise JDK user they may still use JDK
8 for a long time.
If we start the Camel 3.x, we still need to maintain the Camel 2.x
branch for a while.
It could be great, if we can provide a roadmap of JDK8 support time,
BTW, Spring has good backward compatibility for JDK
Logged it https://issues.apache.org/jira/browse/CAMEL-13000
On Thu, 13 Dec 2018, 10:19 Andrea Cosentino You're right, but if we always think about how much effort is needed to
> switch to a new and different JDK, we will never move from JDK 8.
>
> I'd like to have other feedback on this by the wa
You're right, but if we always think about how much effort is needed to switch
to a new and different JDK, we will never move from JDK 8.
I'd like to have other feedback on this by the way.
For the compatibility matrix we need to it to the documentation too.
--
Andrea Cosentino
---
Almost +1, (as points below affects the idea of where to using any camel
versions and even contributing because for example;
if you use (let's say JDK 8) and have come across a problem and solved in
your local branch 2.X and submitted and if Camel 3.X would require JDK 10
as the base minimum versio
On Wed, Dec 12, 2018 at 1:11 PM Andrea Cosentino wrote:
>
> It makes sense to set a date.
>
> Once we checked the documentation and resolved doubts,
> I propose Wed 19th Dec in the morning.
>
> Does it work for all?
>
+1
> Thanks.
>
> --
> Andrea Cosentino
> --
>
It makes sense to set a date.
Once we checked the documentation and resolved doubts,I propose Wed 19th Dec in
the morning.
Does it work for all?
Thanks.
--Andrea Cosentino --Apache Camel PMC
ChairApache Karaf CommitterApache Servicemix PMC MemberEmail:
ancosen1985
On Wed, Dec 12, 2018 at 12:14 PM Guillaume Nodet wrote:
>
> Sounds good to me.
>
> Fwiw, I've been working on the camel build those past days, trying to
> improve things a bit. I'll report when I have something in a correct shape.
>
What if we set a date when we make the change? For example Frid
Sounds good to me.
Fwiw, I've been working on the camel build those past days, trying to
improve things a bit. I'll report when I have something in a correct shape.
Guillaume
Le mer. 12 déc. 2018 à 11:54, Andrea Cosentino
a écrit :
> Hello,
>
> Since we started work of some cleanup about Came
Hello,
Since we started work of some cleanup about Camel 3 and it's already aligned
with master, I'd like to ask what do you think about switching the master to
3.x and create a 2.x branch for the activities on Camel 2.x..
What do you think about this?
Thanks
--
Andrea Cosentino
21 matches
Mail list logo
