I've created issues to do a release of camel-k / camel-k-runtime before creating a branche for 2.x:
- https://github.com/apache/camel-k-runtime/issues/72 - https://github.com/apache/camel-k/issues/683 --- Luca Burgazzoli On Thu, May 23, 2019 at 9:52 AM Claus Ibsen <[email protected]> wrote: > Hi > > +1 to drop Camel 2.x quickly and move onwards to Camel 3 for Camel K. > That was also IMHO our intentions, that Camel 3 and K goes GA at the same > time. > > > On Wed, May 22, 2019 at 7:14 PM Luca Burgazzoli <[email protected]> > wrote: > > > > Hello, > > > > we need to start planning what features we want to include in Camel K 1.0 > > so I've created milestone 1.0.0 for both camel-k and camel-k runtime > [1][2] > > to have a better visibility of what's left so I kindly ask everyone to > > review the open issue and think about what we should include in 1.0. > > > > One of the things we need to decide as earlier as possible is what > version > > of camel we want to support on camel-k-runtime: as today we do support > from > > 2.18.x to 3.x but it is becoming more and more complex as the development > > of the camel 3 goes ahead so I'm proposing to: > > > > - create a branch for the current code-base of camel-k-runtime we can > name > > says camel-2.x which will be used for everyone that need to run camel-k > and > > freeze the version to 0.3.x (and eventually remove camel 3 bits) > > - set the master branch to something like 1.0.0.SNAPSHOT and base it to > > camel 3.x only > > > > Thoughts ? > > > > [1] https://github.com/apache/camel-k/milestone/1 > > [2] https://github.com/apache/camel-k-runtime/milestone/1 > > [3] https://github.com/apache/camel-k-runtime/issues/56 > > > > --- > > Luca Burgazzoli > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 >
