Release artifacts (was: [VOTE] Release 0.16)

[Robbie Gemmell <ro...@gmail.com>]

Hi Justin,

I think it would be good to prepare the final artifacts (some seem
like they could just be renamed, but others indicate RC4 in their
content) so we can test them before we vote, and signing them would
also allow the maven artifacts to be deployed to a staging repo and
tested in advance of the vote closing rather than afterwards.

Also, looking at the RC3 thread I notice Darryl raised a request for
inclusion relating to updating the ruby gem name which still seems
open, is that being deferred to 0.18?

Robbie

On 10 May 2012 01:57, Justin Ross <jr...@redhat.com> wrote:
> Hi.  I've now produced 0.16-rc4 at the following location:
>
>  http://people.apache.org/~jross/qpid-0.16-rc4/
>
> It has just one change beyond RC3, r1336378, which disables the HA tests if
> required test tools are not in the environment (Thanks, Alan).
>
> There was one other issue with RC3 that Cajus raised, the Perl client
> install on Debian.  Darryl looked into it, and it seems to be a Debian
> specific problem.  With this information, I think it's best we press ahead
> with the release.  If the fix is minor, we can consider introducing it on
> the 0.16 release branch when it becomes available.
>
> So, I'd like to jump straight to the vote.  If you favor releasing the
> 0.16-rc4 bits as 0.16, vote +1.  If you have a reason to think RC4 is not
> ready for release, vote -1.
>
> Thanks!
> Justin
>
> ---
> 0.16 release page: https://cwiki.apache.org/qpid/016-release.html
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
> For additional commands, e-mail: dev-help@qpid.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

Re: Release artifacts (was: [VOTE] Release 0.16)

[Oleksandr Rudyy <or...@gmail.com>]

Justin, Robbie,

I tested Java Broker, Java Client and Management Console artefacts.

Everything worked fine for me. No issue is found.

Details of the tests:
Started Java Broker.
Created test queue using Management Console and bound that queue to
the direct exchange.
Published test messages into the test queue using Spout example.
Consumed test messages from the test queue using Drain example.
Used Management Console to verify test queue attributes before and
after publishing and consuming.

The scenario above was used to test broker with Memory message store
and Berkeley Message Store.

I have not tested maven artefacts.

Kind Regards,
Alex

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

Re: Release artifacts (was: [VOTE] Release 0.16)

[Justin Ross <jr...@redhat.com>]

Hi, Robbie.  Yes, you're right.  I've corrected the RC4 artifacts at the 
existing RC4 link.

As to Darryl's request, in my opinion we should defer it.

Justin

On Thu, 10 May 2012, Robbie Gemmell wrote:

> Hi Justin,
>
> I think it would be good to prepare the final artifacts (some seem
> like they could just be renamed, but others indicate RC4 in their
> content) so we can test them before we vote, and signing them would
> also allow the maven artifacts to be deployed to a staging repo and
> tested in advance of the vote closing rather than afterwards.
>
> Also, looking at the RC3 thread I notice Darryl raised a request for
> inclusion relating to updating the ruby gem name which still seems
> open, is that being deferred to 0.18?
>
> Robbie
>
> On 10 May 2012 01:57, Justin Ross <jr...@redhat.com> wrote:
>> Hi.  I've now produced 0.16-rc4 at the following location:
>>
>>  http://people.apache.org/~jross/qpid-0.16-rc4/
>>
>> It has just one change beyond RC3, r1336378, which disables the HA tests if
>> required test tools are not in the environment (Thanks, Alan).
>>
>> There was one other issue with RC3 that Cajus raised, the Perl client
>> install on Debian.  Darryl looked into it, and it seems to be a Debian
>> specific problem.  With this information, I think it's best we press ahead
>> with the release.  If the fix is minor, we can consider introducing it on
>> the 0.16 release branch when it becomes available.
>>
>> So, I'd like to jump straight to the vote.  If you favor releasing the
>> 0.16-rc4 bits as 0.16, vote +1.  If you have a reason to think RC4 is not
>> ready for release, vote -1.
>>
>> Thanks!
>> Justin
>>
>> ---
>> 0.16 release page: https://cwiki.apache.org/qpid/016-release.html
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
>> For additional commands, e-mail: dev-help@qpid.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
> For additional commands, e-mail: dev-help@qpid.apache.org
>
>