Re: [RESULT] [VOTE] Release Qpid Java 6.0.2 (RC1)

[Oleksandr Rudyy]

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  wrote:

> 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 site.
>
> Kind Regards,
> Alex
>

[RESULT] [VOTE] Release Qpid Java 6.0.2 (RC1)

[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 site.

Kind Regards,
Alex

Re: [VOTE] Release Qpid Java 6.0.2 (RC1)

[Rob Godfrey]

+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 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 of pulling it down from Nexus after creation
> > to do it.
> >
> > The checksums+sigs wouldnt actually need regenerated currently, just
> > renamed, as the sig doesn't consider the name and the checksums
> > generated by Nexus don't contain the name. I think Lorenz pointed out
> > previously that it would be good if the checksums in the dist repo did
> > actually contain the file name, as otherwise they don't work with the
> > handy -c check flag from tools.
> >
> > As Alex said, Keith's key needs added to the KEYS file in the dist
> > repo (and its source in our repo). It is however in
> > https://people.apache.org/keys/committer/kwall.asc and
> > https://people.apache.org/keys/group/qpid.asc so I was able to verify
> > the sig files.
> >
> > I tested things out as follows:
> > - Verified all the sigs
> > - Verified the source release checksums (updated with filename to
> > allow using tool -c flags)
> > - Used RAT to check the licence (see note below).
> > - Ran the source build
> > - Extracted the broker binary, started it, created a queue with the web
> console.
> > - Ran the Qpid JMS 0.9.0 HelloWorld example against the broker.
> >
> > When doing "mvn apache-rat:check" within the src archvie it fails due
> > to the DEPENDENCIES file maven auto generated. The check passes after
> > deleting that file. Not a blocker, but would be good to fix for future
> > (perhaps just excluding the file, given it doesnt contain any useful
> > dep info as the build pom has no deps itself).
> >
> > For now I'm +0.9, I'd be +1 with a rename.
> >
> > Robbie
> >
> > On 15 April 2016 at 11:19, Oleksandr Rudyy  wrote:
> >> I made the following checks:
> >> 1) Verified pgp signatures against public keys in
> >> http://www.apache.org/dist/qpid/KEYS. Keith's signature is not there
> >> and should be appended manually.
> >> 2) Source bundle is named qpid-java-build-6.0.2.tar.gz but the site
> >> generating script(s) expect(s) it to be named qpid-java-6.0.2.tar.gz.
> >> I am fine with naming it qpid-java-build-6.0.2.tar.gz but we should
> >> change site scripts. Alternatively, bundle can be renamed manually and
> >> signatures regenerated
> >> 3) Started broker and briefly clicked through operations on Web
> >> Management Console. Everything worked fine for me
> >> 4) Compiled 6.0.2 artifacts from source bundle. Everything compiled
> successfully
> >> 5) Run Hello/Spout/Drain examples.
> >>
> >> The question is do we want to rename source bundle into
> qpid-java-6.0.2.tar.gz?
> >>
> >> Kind Regards,
> >> Alex
> >>
> >> 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:
> >>>
> >>>
> 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 source and binary archives can be grabbed from here:
> >>> https://dist.apache.org/repos/dist/dev/qpid/java/6.0.2-rc1
> >>>
> >>> Those files and the other maven artifacts are also staged for now at:
> >>> https://repository.apache.org/content/repositories/orgapacheqpid-1071
> >>>
> >>> Kind regards
> >>>
> >>> P.S. If you want to test it out using maven (e.g with the examples src,
> >>> or your own things), you can temporarily add this to your poms to
> access
> >>> the staging repo:
> >>>
> >>>   
> >>> 
> >>>   staging
> >>>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1071
> 
> >>> 
> >>>   
> >>>
> >>> -
> >>> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> >>> For additional commands, e-mail: users-h...@qpid.apache.org
> >>>
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> >> For additional commands, e-mail: users-h...@qpid.apache.org
> >>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: [VOTE] Release Qpid Java 6.0.2 (RC1)

[Robbie Gemmell]

+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
> with that name, e.g having a dedicated module do it, or just
> tweak/script the process of pulling it down from Nexus after creation
> to do it.
>
> The checksums+sigs wouldnt actually need regenerated currently, just
> renamed, as the sig doesn't consider the name and the checksums
> generated by Nexus don't contain the name. I think Lorenz pointed out
> previously that it would be good if the checksums in the dist repo did
> actually contain the file name, as otherwise they don't work with the
> handy -c check flag from tools.
>
> As Alex said, Keith's key needs added to the KEYS file in the dist
> repo (and its source in our repo). It is however in
> https://people.apache.org/keys/committer/kwall.asc and
> https://people.apache.org/keys/group/qpid.asc so I was able to verify
> the sig files.
>
> I tested things out as follows:
> - Verified all the sigs
> - Verified the source release checksums (updated with filename to
> allow using tool -c flags)
> - Used RAT to check the licence (see note below).
> - Ran the source build
> - Extracted the broker binary, started it, created a queue with the web 
> console.
> - Ran the Qpid JMS 0.9.0 HelloWorld example against the broker.
>
> When doing "mvn apache-rat:check" within the src archvie it fails due
> to the DEPENDENCIES file maven auto generated. The check passes after
> deleting that file. Not a blocker, but would be good to fix for future
> (perhaps just excluding the file, given it doesnt contain any useful
> dep info as the build pom has no deps itself).
>
> For now I'm +0.9, I'd be +1 with a rename.
>
> Robbie
>
> On 15 April 2016 at 11:19, Oleksandr Rudyy  wrote:
>> I made the following checks:
>> 1) Verified pgp signatures against public keys in
>> http://www.apache.org/dist/qpid/KEYS. Keith's signature is not there
>> and should be appended manually.
>> 2) Source bundle is named qpid-java-build-6.0.2.tar.gz but the site
>> generating script(s) expect(s) it to be named qpid-java-6.0.2.tar.gz.
>> I am fine with naming it qpid-java-build-6.0.2.tar.gz but we should
>> change site scripts. Alternatively, bundle can be renamed manually and
>> signatures regenerated
>> 3) Started broker and briefly clicked through operations on Web
>> Management Console. Everything worked fine for me
>> 4) Compiled 6.0.2 artifacts from source bundle. Everything compiled 
>> successfully
>> 5) Run Hello/Spout/Drain examples.
>>
>> The question is do we want to rename source bundle into 
>> qpid-java-6.0.2.tar.gz?
>>
>> Kind Regards,
>> Alex
>>
>> 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:
>>>
>>> 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 source and binary archives can be grabbed from here:
>>> https://dist.apache.org/repos/dist/dev/qpid/java/6.0.2-rc1
>>>
>>> Those files and the other maven artifacts are also staged for now at:
>>> https://repository.apache.org/content/repositories/orgapacheqpid-1071
>>>
>>> Kind regards
>>>
>>> P.S. If you want to test it out using maven (e.g with the examples src,
>>> or your own things), you can temporarily add this to your poms to access
>>> the staging repo:
>>>
>>>   
>>> 
>>>   staging
>>>   
>>> https://repository.apache.org/content/repositories/orgapacheqpid-1071
>>> 
>>>   
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
>>> For additional commands, e-mail: users-h...@qpid.apache.org
>>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
>> For additional commands, e-mail: users-h...@qpid.apache.org
>>

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Qpid Java 6.0.2 (RC1)

[Oleksandr Rudyy]

+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 standard configuration from the
> Apache parent pom.  It takes the name of the parent module:
> qpid-java-build. With hindsight the parent module should not have been
> named so, but this is now moot.  We could consider a rename of the
> parent artefact for v6.1, but this would create a breaking change for
> users consuming the qpid-java-build pom artefact.  As Robbie points
> out we could add a module dedicated to generating a src artefact with
> the right name, but this feels like overkill.  I've taken the
> pragmatic approach for now of tweaking the release instructions to
> include the rename step.  In the medium term, when the Java Broker is
> split from the (legacy) JMS clients in to separate, we can get this
> right.
>
> [1] 
> https://cwiki.apache.org/confluence/display/qpid/Releasing+Qpid+Java+Components
>
> On 15 April 2016 at 11:19, Oleksandr Rudyy  wrote:
>> I made the following checks:
>> 1) Verified pgp signatures against public keys in
>> http://www.apache.org/dist/qpid/KEYS. Keith's signature is not there
>> and should be appended manually.
>> 2) Source bundle is named qpid-java-build-6.0.2.tar.gz but the site
>> generating script(s) expect(s) it to be named qpid-java-6.0.2.tar.gz.
>> I am fine with naming it qpid-java-build-6.0.2.tar.gz but we should
>> change site scripts. Alternatively, bundle can be renamed manually and
>> signatures regenerated
>> 3) Started broker and briefly clicked through operations on Web
>> Management Console. Everything worked fine for me
>> 4) Compiled 6.0.2 artifacts from source bundle. Everything compiled 
>> successfully
>> 5) Run Hello/Spout/Drain examples.
>>
>> The question is do we want to rename source bundle into 
>> qpid-java-6.0.2.tar.gz?
>>
>> Kind Regards,
>> Alex
>>
>> 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:
>>>
>>> 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 source and binary archives can be grabbed from here:
>>> https://dist.apache.org/repos/dist/dev/qpid/java/6.0.2-rc1
>>>
>>> Those files and the other maven artifacts are also staged for now at:
>>> https://repository.apache.org/content/repositories/orgapacheqpid-1071
>>>
>>> Kind regards
>>>
>>> P.S. If you want to test it out using maven (e.g with the examples src,
>>> or your own things), you can temporarily add this to your poms to access
>>> the staging repo:
>>>
>>>   
>>> 
>>>   staging
>>>   
>>> https://repository.apache.org/content/repositories/orgapacheqpid-1071
>>> 
>>>   
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
>>> For additional commands, e-mail: users-h...@qpid.apache.org
>>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
>> For additional commands, e-mail: users-h...@qpid.apache.org
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Qpid Java 6.0.2 (RC1)

[Keith W]

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 module:
qpid-java-build. With hindsight the parent module should not have been
named so, but this is now moot.  We could consider a rename of the
parent artefact for v6.1, but this would create a breaking change for
users consuming the qpid-java-build pom artefact.  As Robbie points
out we could add a module dedicated to generating a src artefact with
the right name, but this feels like overkill.  I've taken the
pragmatic approach for now of tweaking the release instructions to
include the rename step.  In the medium term, when the Java Broker is
split from the (legacy) JMS clients in to separate, we can get this
right.

[1] 
https://cwiki.apache.org/confluence/display/qpid/Releasing+Qpid+Java+Components

On 15 April 2016 at 11:19, Oleksandr Rudyy  wrote:
> I made the following checks:
> 1) Verified pgp signatures against public keys in
> http://www.apache.org/dist/qpid/KEYS. Keith's signature is not there
> and should be appended manually.
> 2) Source bundle is named qpid-java-build-6.0.2.tar.gz but the site
> generating script(s) expect(s) it to be named qpid-java-6.0.2.tar.gz.
> I am fine with naming it qpid-java-build-6.0.2.tar.gz but we should
> change site scripts. Alternatively, bundle can be renamed manually and
> signatures regenerated
> 3) Started broker and briefly clicked through operations on Web
> Management Console. Everything worked fine for me
> 4) Compiled 6.0.2 artifacts from source bundle. Everything compiled 
> successfully
> 5) Run Hello/Spout/Drain examples.
>
> The question is do we want to rename source bundle into 
> qpid-java-6.0.2.tar.gz?
>
> Kind Regards,
> Alex
>
> 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:
>>
>> 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 source and binary archives can be grabbed from here:
>> https://dist.apache.org/repos/dist/dev/qpid/java/6.0.2-rc1
>>
>> Those files and the other maven artifacts are also staged for now at:
>> https://repository.apache.org/content/repositories/orgapacheqpid-1071
>>
>> Kind regards
>>
>> P.S. If you want to test it out using maven (e.g with the examples src,
>> or your own things), you can temporarily add this to your poms to access
>> the staging repo:
>>
>>   
>> 
>>   staging
>>   
>> https://repository.apache.org/content/repositories/orgapacheqpid-1071
>> 
>>   
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
>> For additional commands, e-mail: users-h...@qpid.apache.org
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Qpid Java 6.0.2 (RC1)

[Robbie Gemmell]

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 of pulling it down from Nexus after creation
to do it.

The checksums+sigs wouldnt actually need regenerated currently, just
renamed, as the sig doesn't consider the name and the checksums
generated by Nexus don't contain the name. I think Lorenz pointed out
previously that it would be good if the checksums in the dist repo did
actually contain the file name, as otherwise they don't work with the
handy -c check flag from tools.

As Alex said, Keith's key needs added to the KEYS file in the dist
repo (and its source in our repo). It is however in
https://people.apache.org/keys/committer/kwall.asc and
https://people.apache.org/keys/group/qpid.asc so I was able to verify
the sig files.

I tested things out as follows:
- Verified all the sigs
- Verified the source release checksums (updated with filename to
allow using tool -c flags)
- Used RAT to check the licence (see note below).
- Ran the source build
- Extracted the broker binary, started it, created a queue with the web console.
- Ran the Qpid JMS 0.9.0 HelloWorld example against the broker.

When doing "mvn apache-rat:check" within the src archvie it fails due
to the DEPENDENCIES file maven auto generated. The check passes after
deleting that file. Not a blocker, but would be good to fix for future
(perhaps just excluding the file, given it doesnt contain any useful
dep info as the build pom has no deps itself).

For now I'm +0.9, I'd be +1 with a rename.

Robbie

On 15 April 2016 at 11:19, Oleksandr Rudyy  wrote:
> I made the following checks:
> 1) Verified pgp signatures against public keys in
> http://www.apache.org/dist/qpid/KEYS. Keith's signature is not there
> and should be appended manually.
> 2) Source bundle is named qpid-java-build-6.0.2.tar.gz but the site
> generating script(s) expect(s) it to be named qpid-java-6.0.2.tar.gz.
> I am fine with naming it qpid-java-build-6.0.2.tar.gz but we should
> change site scripts. Alternatively, bundle can be renamed manually and
> signatures regenerated
> 3) Started broker and briefly clicked through operations on Web
> Management Console. Everything worked fine for me
> 4) Compiled 6.0.2 artifacts from source bundle. Everything compiled 
> successfully
> 5) Run Hello/Spout/Drain examples.
>
> The question is do we want to rename source bundle into 
> qpid-java-6.0.2.tar.gz?
>
> Kind Regards,
> Alex
>
> 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:
>>
>> 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 source and binary archives can be grabbed from here:
>> https://dist.apache.org/repos/dist/dev/qpid/java/6.0.2-rc1
>>
>> Those files and the other maven artifacts are also staged for now at:
>> https://repository.apache.org/content/repositories/orgapacheqpid-1071
>>
>> Kind regards
>>
>> P.S. If you want to test it out using maven (e.g with the examples src,
>> or your own things), you can temporarily add this to your poms to access
>> the staging repo:
>>
>>   
>> 
>>   staging
>>   
>> https://repository.apache.org/content/repositories/orgapacheqpid-1071
>> 
>>   
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
>> For additional commands, e-mail: users-h...@qpid.apache.org
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Qpid Java 6.0.2 (RC1)

[Keith W]

+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 distribution
5) Ran Joram tests against Qpid JMS client 0.9.0.

No problems found.

I also removed the hashes of the ASCs (the asc.md5/asc.sha1) from
repository.apache.org as suggested by Robbie.


On 14 April 2016 at 14:44, Robbie Gemmell  wrote:
> 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 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 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:
>>> >
>>> >
>>> 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 source and binary archives can be grabbed from here:
>>> > https://dist.apache.org/repos/dist/dev/qpid/java/6.0.2-rc1
>>> >
>>> > Those files and the other maven artifacts are also staged for now at:
>>> > https://repository.apache.org/content/repositories/orgapacheqpid-1071
>>> >
>>> > Kind regards
>>> >
>>> > P.S. If you want to test it out using maven (e.g with the examples src,
>>> > or your own things), you can temporarily add this to your poms to access
>>> > the staging repo:
>>> >
>>> >   
>>> > 
>>> >   staging
>>> >   
>>> https://repository.apache.org/content/repositories/orgapacheqpid-1071
>>> 
>>> > 
>>> >   
>>> >
>>> > -
>>> > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
>>> > For additional commands, e-mail: users-h...@qpid.apache.org
>>> >
>>>
>>> As a first quick look comment, can we remove all the *.asc.md5 and
>>> *.asc.sha1 files (which Nexus created) from the dist repo? They are
>>> rather redundant and really just clutter things up, plus we probably
>>> wont ever link to them.
>>>
>>> Robbie
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
>>> For additional commands, e-mail: users-h...@qpid.apache.org
>>>
>>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Qpid Java 6.0.2 (RC1)

[Robbie Gemmell]

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 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 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:
>> >
>> >
>> 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 source and binary archives can be grabbed from here:
>> > https://dist.apache.org/repos/dist/dev/qpid/java/6.0.2-rc1
>> >
>> > Those files and the other maven artifacts are also staged for now at:
>> > https://repository.apache.org/content/repositories/orgapacheqpid-1071
>> >
>> > Kind regards
>> >
>> > P.S. If you want to test it out using maven (e.g with the examples src,
>> > or your own things), you can temporarily add this to your poms to access
>> > the staging repo:
>> >
>> >   
>> > 
>> >   staging
>> >   
>> https://repository.apache.org/content/repositories/orgapacheqpid-1071
>> 
>> > 
>> >   
>> >
>> > -
>> > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
>> > For additional commands, e-mail: users-h...@qpid.apache.org
>> >
>>
>> As a first quick look comment, can we remove all the *.asc.md5 and
>> *.asc.sha1 files (which Nexus created) from the dist repo? They are
>> rather redundant and really just clutter things up, plus we probably
>> wont ever link to them.
>>
>> Robbie
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
>> For additional commands, e-mail: users-h...@qpid.apache.org
>>
>>

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Qpid Java 6.0.2 (RC1)

[Jakub Scholz]

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 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:
> >
> >
> 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 source and binary archives can be grabbed from here:
> > https://dist.apache.org/repos/dist/dev/qpid/java/6.0.2-rc1
> >
> > Those files and the other maven artifacts are also staged for now at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1071
> >
> > Kind regards
> >
> > P.S. If you want to test it out using maven (e.g with the examples src,
> > or your own things), you can temporarily add this to your poms to access
> > the staging repo:
> >
> >   
> > 
> >   staging
> >   
> https://repository.apache.org/content/repositories/orgapacheqpid-1071
> 
> > 
> >   
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> > For additional commands, e-mail: users-h...@qpid.apache.org
> >
>
> As a first quick look comment, can we remove all the *.asc.md5 and
> *.asc.sha1 files (which Nexus created) from the dist repo? They are
> rather redundant and really just clutter things up, plus we probably
> wont ever link to them.
>
> Robbie
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: [VOTE] Release Qpid Java 6.0.2 (RC1)

[Robbie Gemmell]

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:
>
> 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 source and binary archives can be grabbed from here:
> https://dist.apache.org/repos/dist/dev/qpid/java/6.0.2-rc1
>
> Those files and the other maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1071
>
> Kind regards
>
> P.S. If you want to test it out using maven (e.g with the examples src,
> or your own things), you can temporarily add this to your poms to access
> the staging repo:
>
>   
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1071
> 
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>

As a first quick look comment, can we remove all the *.asc.md5 and
*.asc.sha1 files (which Nexus created) from the dist repo? They are
rather redundant and really just clutter things up, plus we probably
wont ever link to them.

Robbie

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

[VOTE] Release Qpid Java 6.0.2 (RC1)

[Keith W]

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 source and binary archives can be grabbed from here:
https://dist.apache.org/repos/dist/dev/qpid/java/6.0.2-rc1

Those files and the other maven artifacts are also staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1071

Kind regards

P.S. If you want to test it out using maven (e.g with the examples src,
or your own things), you can temporarily add this to your poms to access
the staging repo:

  

  staging
  
https://repository.apache.org/content/repositories/orgapacheqpid-1071

  

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org