My apologies,
I provided an URL to voting thread for 6.0.1 RC3 in the result voting email
for 6.0.2 RC1.
The correct voting thread URL is:
http://qpid.2158936.n2.nabble.com/VOTE-Release-Qpid-Java-6-0-2-RC1-td7641806.html
Kind Regards,
Alex
On 18 April 2016 at 13:48, Oleksandr Rudyy
There were 5 binding +1 votes, and no other votes received. The vote has
passed.
Voting thread:
http://qpid.2158936.n2.nabble.com/VOTE-Release-Qpid-Java-6-0-1-RC3-td7638867.html
I am going to publish release artifacts into dist release repo and
maven repo. In 24h after that I will update web
+1
On 15 April 2016 at 15:00, Robbie Gemmell wrote:
> +1
>
> On 15 April 2016 at 12:28, Robbie Gemmell
> wrote:
> > Given the shorter name is consistent with previous 6.0.x releases, is
> > what the contents are actually named, and is just
+1
On 15 April 2016 at 12:28, Robbie Gemmell wrote:
> Given the shorter name is consistent with previous 6.0.x releases, is
> what the contents are actually named, and is just nicer, I would again
> suggest renaming it. It might be good to update the build to create it
+1
On 15 April 2016 at 12:54, Keith W wrote:
> Alex/Robbie
>
> Thanks for spotting the missing signature. It is now fixed.
> I have renamed the source artefact too.
>
> Regarding the src bundle name, the source artefact is being
> automatically created by Maven using
Alex/Robbie
Thanks for spotting the missing signature. It is now fixed.
I have renamed the source artefact too.
Regarding the src bundle name, the source artefact is being
automatically created by Maven using standard configuration from the
Apache parent pom. It takes the name of the parent
Given the shorter name is consistent with previous 6.0.x releases, is
what the contents are actually named, and is just nicer, I would again
suggest renaming it. It might be good to update the build to create it
with that name, e.g having a dedicated module do it, or just
tweak/script the process
+1
Making my own vote and testing explicit:
1) Verified the md5/sha checksums on all binaries
2) Verified signatures on all binaries
3) Built/ran test profiles mms/dby/bdb for 0-9 and 0-10 from source bundle
4) Ran hello world against staged maven artefacts against broker from
binary
No need for a respin. I'm just proposing deletion of some redundant
artifacts that were presumably just pulled from repository.apache.org
with the others after being auto-generated.
Robbie
On 14 April 2016 at 14:20, Jakub Scholz wrote:
> I'm not sure whether we need RC2 and new
I'm not sure whether we need RC2 and new vote to address Robbie's comment.
But I the tested the new release, especially with focus on the AMQP 0-10
client and all works well.
+1
On Wed, Apr 13, 2016 at 4:29 PM, Robbie Gemmell
wrote:
> On 13 April 2016 at 14:04, Keith
On 13 April 2016 at 14:04, Keith W wrote:
> Hi all,
>
> A release candidate for the next release (6.0.2) of the Qpid Java
> Components has been created.
>
> The list of changes can be found in Jira:
>
>
Hi all,
A release candidate for the next release (6.0.2) of the Qpid Java
Components has been created.
The list of changes can be found in Jira:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20QPID%20AND%20fixVersion%20%3D%20qpid-java-6.0.2
Please test and vote accordingly.
The
12 matches
Mail list logo