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
Le dim. 16 févr. 2020 à 18:44, Andrea Cosentino 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 ra
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 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
(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 wrote:
>
> Hi
>
> The sou
+1
Il dom 16 feb 2020, 17:13 Claus Ibsen 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)
> C
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
