On Fri, Aug 19, 2016 at 5:25 PM, Raul Kripalani <r...@evosent.com> wrote: > On Fri, Aug 19, 2016 at 3:54 PM, Claus Ibsen <claus.ib...@gmail.com> wrote: > >> There is already CI jobs for this - they are the ones named notest, >> which ought to be configured to publish to staging m2 repo after >> success: >> https://builds.apache.org/view/A-D/view/Camel/ >> > > If I switch the current version to 2.18.0-SNAPSHOT, the snapshots will be > published under 2.18.0-SNAPSHOT. >
Yeah sure. Remember the JIRA and commit message so we can track back to this change and discussion. > I meant creating a 2nd job to build and publish the tip of the maintained > branches under 2.18-SNAPSHOT, 2.17-SNAPSHOT, etc. too – to cover the use > case you proposed, i.e. "building against the bleeding edge of a release > line". To me, this is not necessary, but it's a nice to have. > Oh we have plenty of CI jobs already. The value of 2.18.0-SNAPSHOT is leading up to the release. Then the master moves on to 2.19.0-SNAPSHOT and so on. So lets leave the CI jobs as-is today. > Cheers. > > --- > Raúl Kripalani > linkedin.com/in/raulkripalani | evosent.com > <http://evosent.com/?utm_source=email&utm_medium=email&utm_campaign=evosent_raul> > | blog: raul.io > <http://raul.io?utm_source=email&utm_medium=email&utm_campaign=evosent_raul> | > skype: raul.fuse -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
