[VOTE] Release Apache Qpid Proton-J 0.20.0

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[VOTE] Release Apache Qpid Proton-J 0.20.0

Robbie Gemmell
Administrator
Hi folks,

I have put together a first spin for a Qpid Proton-J 0.20.0 release,
please test it and vote accordingly.

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.20.0-rc1/

(Note: the .sha checksum files are generated using SHA512)

The maven artifacts are staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1111

The JIRAs currently assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12341280

Regards,
Robbie

P.S. If you want to test things out using maven with your own build
you can temporarily add this to your poms to access the staging repo:

  <repositories>
    <repository>
      <id>staging</id>
      <url>https://repository.apache.org/content/repositories/orgapacheqpid-1111</url>
    </repository>
  </repositories>

The dependency for proton-j would then be:

  <dependency>
    <groupId>org.apache.qpid</groupId>
    <artifactId>proton-j</artifactId>
    <version>0.20.0</version>
  </dependency>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [VOTE] Release Apache Qpid Proton-J 0.20.0

Robbie Gemmell
Administrator
On 2 August 2017 at 15:33, Robbie Gemmell <[hidden email]> wrote:

> Hi folks,
>
> I have put together a first spin for a Qpid Proton-J 0.20.0 release,
> please test it and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.20.0-rc1/
>
> (Note: the .sha checksum files are generated using SHA512)
>
> The maven artifacts are staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1111
>
> The JIRAs currently assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12341280
>
> Regards,
> Robbie
>
> P.S. If you want to test things out using maven with your own build
> you can temporarily add this to your poms to access the staging repo:
>
>   <repositories>
>     <repository>
>       <id>staging</id>
>       <url>https://repository.apache.org/content/repositories/orgapacheqpid-1111</url>
>     </repository>
>   </repositories>
>
> The dependency for proton-j would then be:
>
>   <dependency>
>     <groupId>org.apache.qpid</groupId>
>     <artifactId>proton-j</artifactId>
>     <version>0.20.0</version>
>   </dependency>


Adding my +1.

I checked things over as follows:
 - Verified the signatures and checksum files.
 - Checked the LICENCE and NOTICE files in the release archives.
 - Ran the source build and tests.
 - Used mvn apache-rat:check to verify the source release licence headers.
 - Checked the bin convenience archive contained the expected bits.
 - Used the staging repo to run the Qpid JMS client master build and tests.
 - Used the staging repo to run the ActiveMQ 5 master build and AMQP tests.
 - Ran the JMS client HelloWorld example against Qpid Broker-J 6.1.4 and
   and ActiveMQ 5 master brokers.

Robbie

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [VOTE] Release Apache Qpid Proton-J 0.20.0

Gary Tully
+1 (non binding)

verified ActiveMQ Artemis use of the new setInitialRemoteMaxFrameSize using
the staging repo

On Wed, 2 Aug 2017 at 16:30 Robbie Gemmell <[hidden email]> wrote:

> On 2 August 2017 at 15:33, Robbie Gemmell <[hidden email]>
> wrote:
> > Hi folks,
> >
> > I have put together a first spin for a Qpid Proton-J 0.20.0 release,
> > please test it and vote accordingly.
> >
> > The source and binary archives can be grabbed from:
> > https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.20.0-rc1/
> >
> > (Note: the .sha checksum files are generated using SHA512)
> >
> > The maven artifacts are staged for now at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1111
> >
> > The JIRAs currently assigned are:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12341280
> >
> > Regards,
> > Robbie
> >
> > P.S. If you want to test things out using maven with your own build
> > you can temporarily add this to your poms to access the staging repo:
> >
> >   <repositories>
> >     <repository>
> >       <id>staging</id>
> >       <url>
> https://repository.apache.org/content/repositories/orgapacheqpid-1111
> </url>
> >     </repository>
> >   </repositories>
> >
> > The dependency for proton-j would then be:
> >
> >   <dependency>
> >     <groupId>org.apache.qpid</groupId>
> >     <artifactId>proton-j</artifactId>
> >     <version>0.20.0</version>
> >   </dependency>
>
>
> Adding my +1.
>
> I checked things over as follows:
>  - Verified the signatures and checksum files.
>  - Checked the LICENCE and NOTICE files in the release archives.
>  - Ran the source build and tests.
>  - Used mvn apache-rat:check to verify the source release licence headers.
>  - Checked the bin convenience archive contained the expected bits.
>  - Used the staging repo to run the Qpid JMS client master build and tests.
>  - Used the staging repo to run the ActiveMQ 5 master build and AMQP tests.
>  - Ran the JMS client HelloWorld example against Qpid Broker-J 6.1.4 and
>    and ActiveMQ 5 master brokers.
>
> Robbie
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [VOTE] Release Apache Qpid Proton-J 0.20.0

Timothy Bish
In reply to this post by Robbie Gemmell
On 08/02/2017 10:33 AM, Robbie Gemmell wrote:

> Hi folks,
>
> I have put together a first spin for a Qpid Proton-J 0.20.0 release,
> please test it and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.20.0-rc1/
>
> (Note: the .sha checksum files are generated using SHA512)
>
> The maven artifacts are staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1111
>
> The JIRAs currently assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12341280
>
> Regards,
> Robbie
>
> P.S. If you want to test things out using maven with your own build
> you can temporarily add this to your poms to access the staging repo:
>
>    <repositories>
>      <repository>
>        <id>staging</id>
>        <url>https://repository.apache.org/content/repositories/orgapacheqpid-1111</url>
>      </repository>
>    </repositories>
>
> The dependency for proton-j would then be:
>
>    <dependency>
>      <groupId>org.apache.qpid</groupId>
>      <artifactId>proton-j</artifactId>
>      <version>0.20.0</version>
>    </dependency>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
+1

* Reviewed bin and src archives for proper license and notice files
* Validated signatures and checksums
* Built from source and ran the tests.
* Built Qpid JMS using staged binary and ran the tests
* Built Artemis using staged binary and ran test broker AMQP tests.



--
Tim Bish


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [VOTE] Release Apache Qpid Proton-J 0.20.0

Keith Wall
+1

* Ran Apache RAT check
* Verified checksums and signatures on artefacts
* Manually retested SCRAM-SHA SASL authentication using staged
Proton-J artefacts with Qpid JMS Client (master) against the Java
Broker (master). I ran this test twice, firstly with the Broker
configured to use SaslOutcome to send the final challenge (new
behaviour) and again with it switched to the old behaviour.
* Tested staged Proton-J artefacts with Qpid JMS Client 0.23.0 against
Qpid Broker for Java (master) using the Joram test suite

All tests passed.

On 2 August 2017 at 17:41, Timothy Bish <[hidden email]> wrote:

> On 08/02/2017 10:33 AM, Robbie Gemmell wrote:
>>
>> Hi folks,
>>
>> I have put together a first spin for a Qpid Proton-J 0.20.0 release,
>> please test it and vote accordingly.
>>
>> The source and binary archives can be grabbed from:
>> https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.20.0-rc1/
>>
>> (Note: the .sha checksum files are generated using SHA512)
>>
>> The maven artifacts are staged for now at:
>> https://repository.apache.org/content/repositories/orgapacheqpid-1111
>>
>> The JIRAs currently assigned are:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12341280
>>
>> Regards,
>> Robbie
>>
>> P.S. If you want to test things out using maven with your own build
>> you can temporarily add this to your poms to access the staging repo:
>>
>>    <repositories>
>>      <repository>
>>        <id>staging</id>
>>
>> <url>https://repository.apache.org/content/repositories/orgapacheqpid-1111</url>
>>      </repository>
>>    </repositories>
>>
>> The dependency for proton-j would then be:
>>
>>    <dependency>
>>      <groupId>org.apache.qpid</groupId>
>>      <artifactId>proton-j</artifactId>
>>      <version>0.20.0</version>
>>    </dependency>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
> +1
>
> * Reviewed bin and src archives for proper license and notice files
> * Validated signatures and checksums
> * Built from source and ran the tests.
> * Built Qpid JMS using staged binary and ran the tests
> * Built Artemis using staged binary and ran test broker AMQP tests.
>
>
>
> --
> Tim Bish
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [VOTE] Release Apache Qpid Proton-J 0.20.0

Lorenz Quack
In reply to this post by Robbie Gemmell
+1

* verified checksums and signatures
* ran apache-rat:check
* build and ran test of src bundle
* ran HelloWorld of the qpid-jms (master) against the qpid-broker-j (master)
  using proton-j (0.20.0 from staging repo)
* as above but with sending additionalData in the SaslOutcome (SCRAM-SHA-256)

Kind regards,
Lorenz


On Wed, 2017-08-02 at 15:33 +0100, Robbie Gemmell wrote:

> Hi folks,
>
> I have put together a first spin for a Qpid Proton-J 0.20.0 release,
> please test it and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.20.0-rc1/
>
> (Note: the .sha checksum files are generated using SHA512)
>
> The maven artifacts are staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1111
>
> The JIRAs currently assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12341280
>
> Regards,
> Robbie
>
> P.S. If you want to test things out using maven with your own build
> you can temporarily add this to your poms to access the staging repo:
>
>   <repositories>
>     <repository>
>       <id>staging</id>
>       <url>https://repository.apache.org/content/repositories/orgapacheqpid-1111</url>;
>     </repository>
>   </repositories>
>
> The dependency for proton-j would then be:
>
>   <dependency>
>     <groupId>org.apache.qpid</groupId>
>     <artifactId>proton-j</artifactId>
>     <version>0.20.0</version>
>   </dependency>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [VOTE] Release Apache Qpid Proton-J 0.20.0

Oleksandr Rudyy
In reply to this post by Robbie Gemmell
+1
Tested SCRAM-SHA SASL authentication against Java Broker
 * with sending of final server message as additionalData in SaslOutcome
(new behaviour)
 * with sending of final server message in SaslChallenge (old behaviour)

On 2 August 2017 at 15:33, Robbie Gemmell <[hidden email]> wrote:

> Hi folks,
>
> I have put together a first spin for a Qpid Proton-J 0.20.0 release,
> please test it and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.20.0-rc1/
>
> (Note: the .sha checksum files are generated using SHA512)
>
> The maven artifacts are staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1111
>
> The JIRAs currently assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12313720&version=12341280
>
> Regards,
> Robbie
>
> P.S. If you want to test things out using maven with your own build
> you can temporarily add this to your poms to access the staging repo:
>
>   <repositories>
>     <repository>
>       <id>staging</id>
>       <url>https://repository.apache.org/content/
> repositories/orgapacheqpid-1111</url>
>     </repository>
>   </repositories>
>
> The dependency for proton-j would then be:
>
>   <dependency>
>     <groupId>org.apache.qpid</groupId>
>     <artifactId>proton-j</artifactId>
>     <version>0.20.0</version>
>   </dependency>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Loading...