On Wed, Dec 12, 2018 at 12:14 PM Guillaume Nodet <[email protected]> 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 > <[email protected]> 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: [email protected] > > Twitter: @oscerd2 > > Github: oscerd > > > > > -- > ------------------------ > Guillaume Nodet -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
