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 version, it will create a regression effort, in terms of building and executing on JDK 10. would it slow down the contribution efforts? )
Can we also discuss the matters of compatibility matrix? Maybe having one like in starters guide or in some other document. I know we have pages [1] [2] [1] http://camel.apache.org/what-are-the-dependencies.html [2] https://github.com/apache/camel/blob/master/docs/user-manual/en/camel-jar-dependencies.adoc Having such matrix considering other integration platforms would be helpful IMHO. Such as Spring Boot, Karaf, CDI etcs... On Wed, Dec 12, 2018 at 3:12 PM Claus Ibsen <claus.ib...@gmail.com> wrote: > On Wed, Dec 12, 2018 at 1:11 PM Andrea Cosentino <ancosen1...@yahoo.com> > 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 > > ---------------------------------- > > Apache Camel PMC Chair > > Apache Karaf Committer > > Apache Servicemix PMC Member > > Email: ancosen1...@yahoo.com > > Twitter: @oscerd2 > > Github: oscerd > > > > > > On Wednesday, December 12, 2018, 1:09:05 PM GMT+1, Claus Ibsen < > claus.ib...@gmail.com> wrote: > > > > > > On Wed, Dec 12, 2018 at 12:14 PM Guillaume Nodet <gno...@apache.org> > 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 Friday 14th > > December or Monday 17th eg? > > > > And we would need to update the contributing document > > with a section about that Camel 2.x is now located in the 2.x branch, > > and that master is for 3.x. > > > > I wonder if this change will affect the current release procedure of > > Camel 2.x? For example when we need to do next round of patch releases > > for 2.x and also the new 2.24.0 release, > > is there something we need to update our release guides at > > http://camel.apache.org/release-guide.html > > > > Gregor if you are listening, is there something on-top-of your head > > you can think of? > > > > > > > > > > > > > Guillaume > > > > > > Le mer. 12 déc. 2018 à 11:54, Andrea Cosentino > > > <ancosen1...@yahoo.com.invalid> a écrit : > > > > > > > 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 > > > > ---------------------------------- > > > > Apache Camel PMC Chair > > > > Apache Karaf Committer > > > > Apache Servicemix PMC Member > > > > Email: ancosen1...@yahoo.com > > > > Twitter: @oscerd2 > > > > Github: oscerd > > > > > > > > > > > > > -- > > > ------------------------ > > > Guillaume Nodet > > > > > > > > > > -- > > 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 >
