You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Claus Ibsen <cl...@gmail.com> on 2020/02/16 16:13:18 UTC
Releasing Camel 3.1 now with camel and camel-spring-boot repos
Hi
The source code should now be ready for the release.
I wanted to start a new thread here as Camel 3.1.0 release is two fold
since we have moved out spring boot into camel-spring-boot.
So how do we do this release?
1)
Can we cut first Camel 3.1.0 and push to staging repo.
And then afterwards release Camel Spring Boot 3.1.0 as well because
all the Camel 3.1.0 JARs was built before and are in your local
m2/repoistory.
And since this is done right after each other then the binaries will
go to the SAME staging repo. And then we can VOTE on both of them at
the same time, and run it for 72h.
2)
Release camel and camel-spring-boot as 2 different, but have eg 24h
VOTE for camel-spring-boot to cut down the total time.
Any thoughts?
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Releasing Camel 3.1 now with camel and camel-spring-boot repos
Posted by Gregor Zurowski <gr...@list.zurowski.org>.
I am not sure about whether all artifacts will go into the same
staging repo. I believe that the artifacts for Camel will be stored in
a separate staging repository than the artifacts for Camel Spring
Boot. I don't think it's a problem for the vote though.
Gregor
On Sun, Feb 16, 2020 at 5:13 PM Claus Ibsen <cl...@gmail.com> wrote:
>
> Hi
>
> The source code should now be ready for the release.
>
> I wanted to start a new thread here as Camel 3.1.0 release is two fold
> since we have moved out spring boot into camel-spring-boot.
>
> So how do we do this release?
>
> 1)
> Can we cut first Camel 3.1.0 and push to staging repo.
> And then afterwards release Camel Spring Boot 3.1.0 as well because
> all the Camel 3.1.0 JARs was built before and are in your local
> m2/repoistory.
>
> And since this is done right after each other then the binaries will
> go to the SAME staging repo. And then we can VOTE on both of them at
> the same time, and run it for 72h.
>
> 2)
> Release camel and camel-spring-boot as 2 different, but have eg 24h
> VOTE for camel-spring-boot to cut down the total time.
>
> Any thoughts?
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
Re: Releasing Camel 3.1 now with camel and camel-spring-boot repos
Posted by Andrea Cosentino <an...@gmail.com>.
+1
Il dom 16 feb 2020, 17:13 Claus Ibsen <cl...@gmail.com> ha scritto:
> Hi
>
> The source code should now be ready for the release.
>
> I wanted to start a new thread here as Camel 3.1.0 release is two fold
> since we have moved out spring boot into camel-spring-boot.
>
> So how do we do this release?
>
> 1)
> Can we cut first Camel 3.1.0 and push to staging repo.
> And then afterwards release Camel Spring Boot 3.1.0 as well because
> all the Camel 3.1.0 JARs was built before and are in your local
> m2/repoistory.
>
> And since this is done right after each other then the binaries will
> go to the SAME staging repo. And then we can VOTE on both of them at
> the same time, and run it for 72h.
>
> 2)
> Release camel and camel-spring-boot as 2 different, but have eg 24h
> VOTE for camel-spring-boot to cut down the total time.
>
> Any thoughts?
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
Re: Releasing Camel 3.1 now with camel and camel-spring-boot repos
Posted by Guillaume Nodet <gn...@apache.org>.
Le dim. 16 févr. 2020 à 18:44, Andrea Cosentino <an...@gmail.com> a
écrit :
> You couldn't have a vote for camel sb 3.1 without the first release of
> camel. It's not tempting fate.. it's being rational.
>
> I think what David was referring to is the 24 hours voting period which
I've never seen before. I would rather choose another way too.
The easier to me is a single vote with any number of repositories, as the
number of repos is really not a problem.
Having one or two votes with one or more repositories is fine, the only
thing is that if there's a problem with the main camel release, the
spring-boot-one would have to be rebuilt too.
I already did some releases where the release was split up between 2
repositories because there was a network issue during the upload and nexus
did create another repo.
Guillaume
> Il dom 16 feb 2020, 17:45 David Jencks <da...@gmail.com> ha
> scritto:
>
> > (1) is fine.
> > I don’t think (2) is consistent with Apache policy, why tempt fate?
> > Maybe what you meant for (2) is to have separate staging repos and
> > separate but concurrent votes? I think that is fine too.
> >
> > thanks
> > david jencks
> >
> > > On Feb 16, 2020, at 8:13 AM, Claus Ibsen <cl...@gmail.com>
> wrote:
> > >
> > > Hi
> > >
> > > The source code should now be ready for the release.
> > >
> > > I wanted to start a new thread here as Camel 3.1.0 release is two fold
> > > since we have moved out spring boot into camel-spring-boot.
> > >
> > > So how do we do this release?
> > >
> > > 1)
> > > Can we cut first Camel 3.1.0 and push to staging repo.
> > > And then afterwards release Camel Spring Boot 3.1.0 as well because
> > > all the Camel 3.1.0 JARs was built before and are in your local
> > > m2/repoistory.
> > >
> > > And since this is done right after each other then the binaries will
> > > go to the SAME staging repo. And then we can VOTE on both of them at
> > > the same time, and run it for 72h.
> > >
> > > 2)
> > > Release camel and camel-spring-boot as 2 different, but have eg 24h
> > > VOTE for camel-spring-boot to cut down the total time.
> > >
> > > Any thoughts?
> > >
> > > --
> > > Claus Ibsen
> > > -----------------
> > > http://davsclaus.com @davsclaus
> > > Camel in Action 2: https://www.manning.com/ibsen2
> >
> >
>
--
------------------------
Guillaume Nodet
Re: Releasing Camel 3.1 now with camel and camel-spring-boot repos
Posted by Andrea Cosentino <an...@gmail.com>.
You couldn't have a vote for camel sb 3.1 without the first release of
camel. It's not tempting fate.. it's being rational.
Il dom 16 feb 2020, 17:45 David Jencks <da...@gmail.com> ha
scritto:
> (1) is fine.
> I don’t think (2) is consistent with Apache policy, why tempt fate?
> Maybe what you meant for (2) is to have separate staging repos and
> separate but concurrent votes? I think that is fine too.
>
> thanks
> david jencks
>
> > On Feb 16, 2020, at 8:13 AM, Claus Ibsen <cl...@gmail.com> wrote:
> >
> > Hi
> >
> > The source code should now be ready for the release.
> >
> > I wanted to start a new thread here as Camel 3.1.0 release is two fold
> > since we have moved out spring boot into camel-spring-boot.
> >
> > So how do we do this release?
> >
> > 1)
> > Can we cut first Camel 3.1.0 and push to staging repo.
> > And then afterwards release Camel Spring Boot 3.1.0 as well because
> > all the Camel 3.1.0 JARs was built before and are in your local
> > m2/repoistory.
> >
> > And since this is done right after each other then the binaries will
> > go to the SAME staging repo. And then we can VOTE on both of them at
> > the same time, and run it for 72h.
> >
> > 2)
> > Release camel and camel-spring-boot as 2 different, but have eg 24h
> > VOTE for camel-spring-boot to cut down the total time.
> >
> > Any thoughts?
> >
> > --
> > Claus Ibsen
> > -----------------
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
>
>
Re: Releasing Camel 3.1 now with camel and camel-spring-boot repos
Posted by David Jencks <da...@gmail.com>.
(1) is fine.
I don’t think (2) is consistent with Apache policy, why tempt fate?
Maybe what you meant for (2) is to have separate staging repos and separate but concurrent votes? I think that is fine too.
thanks
david jencks
> On Feb 16, 2020, at 8:13 AM, Claus Ibsen <cl...@gmail.com> wrote:
>
> Hi
>
> The source code should now be ready for the release.
>
> I wanted to start a new thread here as Camel 3.1.0 release is two fold
> since we have moved out spring boot into camel-spring-boot.
>
> So how do we do this release?
>
> 1)
> Can we cut first Camel 3.1.0 and push to staging repo.
> And then afterwards release Camel Spring Boot 3.1.0 as well because
> all the Camel 3.1.0 JARs was built before and are in your local
> m2/repoistory.
>
> And since this is done right after each other then the binaries will
> go to the SAME staging repo. And then we can VOTE on both of them at
> the same time, and run it for 72h.
>
> 2)
> Release camel and camel-spring-boot as 2 different, but have eg 24h
> VOTE for camel-spring-boot to cut down the total time.
>
> Any thoughts?
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2