You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Justin Ross <jr...@redhat.com> on 2012/01/11 23:55:53 UTC
Re: [VOTE] Release 0.14
I must apologize for the delay. I went on vacation right where this
thread left off.
A quick note before I prepare the full release update. Here's the plan:
* Fix the issue Robbie mentioned below if it's easy (punt if not)
* Produce signed artifacts
* Declare the release voted "in favor"
* Publish web site updates, including the release notes with Andrew's
notes
* And of course, push the artifacts out for general consumption
Tomorrow is busy, so I probably won't complete this until Friday.
Thanks,
Justin
On Thu, 15 Dec 2011, Robbie Gemmell wrote:
> Thanks Justin.
>
> On closer inspection there was another difference with the Java broker
> package that I hadnt spotted, so the full rebuild was a good call.
>
> Looking it over again I notice that the SVN revision doesnt seem to
> have been passed through the release correctly somehow, the Java
> components embed it into properties files for version reporting but it
> is simply showing up as a dash in the files, although I tried running
> the release myself (using ./release.sh branches/0.14/qpid 1209041
> 0.14) and it seemed to work fine? I dont necessarily think it warrants
> another respin, but it'd be good to work out what happened and avoid
> it for future releases.
>
> I also tried to upload the maven artifacts to a staging repo on the
> Nexus instance but couldnt as as the signature files are required
> artifacts.
>
> Robbie
>
> On 15 December 2011 19:09, Justin Ross <jr...@redhat.com> wrote:
>> I went ahead and produced the fixed distribution. The original is still
>> there under a very long name.
>>
>> before:
>> http://people.apache.org/~jross/qpid-0.14-before-restoring-missing-maven-artifacts/maven/org/apache/qpid/
>> after: http://people.apache.org/~jross/qpid-0.14/maven/org/apache/qpid/
>>
>> Justin
>>
>>
>> On Thu, 15 Dec 2011, Justin Ross wrote:
>>
>>> On Thu, 15 Dec 2011, Robbie Gemmell wrote:
>>>
>>>> The maven artifacts folder doesnt seem to contain everything I
>>>> expected it should. Only the client and common artifacts are present,
>>>> whereas Andrew had previously added additional artifacts which are
>>>> mentioned in the ivy.xml file used for upload and the release.sh
>>>> script. Was an old copy of the release script possibly used to
>>>> generate the build?
>>>
>>>
>>> That's precisely what I did wrong. Thanks for catching this. I'll
>>> rebuild the RC2 distribution now from the same revision, but properly with
>>> the current release script.
>>>
>>>> Everything else I tested (Java broker, client, management artifacts)
>>>> seemed fine and I was on course to just vote positively until I
>>>> noticed that.
>>>>
>>>> Do you happen to still have the build folder used to generate the
>>>> artifacts to see if they were actually built? Either they still exist
>>>> and we use them, or we decide to rebuild them, or we just modify the
>>>> ivy.xml file and upload the existing artifacts without them. Thoughts?
>>>
>>>
>>> I think the rebuild will be the most straightforward, so long as that's
>>> acceptable. (Fwiw, I've checked my build folder, and the remaining
>>> artifacts are present afaict.)
>>>
>>>> Robbie
>>>>
>>>> On 12 December 2011 14:58, Justin Ross <jr...@redhat.com> wrote:
>>>>>
>>>>> Hello, everyone. There have been no new changes on the release branch
>>>>> since
>>>>> our proposed final RC, available here:
>>>>>
>>>>> http://people.apache.org/~jross/qpid-0.14/
>>>>>
>>>>> If you favor releasing this distribution as Qpid 0.14, vote +1. If
>>>>> instead
>>>>> you think there are problems that should prevent this distribution from
>>>>> being released, vote -1.
>>>>>
>>>>> I'd like to complete the vote by Thursday so I can push the release
>>>>> Friday,
>>>>> provided we vote in favor.
>>>>>
>>>>> Thanks, everyone, for all your help getting the release out.
>>>>>
>>>>> Justin
>>>>>
>>>>> ---
>>>>> 0.14 release page: https://cwiki.apache.org/qpid/014-release.html
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>> Project: http://qpid.apache.org
>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> Apache Qpid - AMQP Messaging Implementation
>>>> Project: http://qpid.apache.org
>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>
>>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project: http://qpid.apache.org
>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
Re: [VOTE] Release 0.14
Posted by Justin Ross <jr...@redhat.com>.
:), I very much understand. Thanks, Robbie, for handling the maven
artifacts.
We haven't publicized the 0.14 artifacts yet, so I believe we can still
push corrections if necessary.
Justin
On Mon, 23 Jan 2012, Robbie Gemmell wrote:
> Sorry for the delay Justin, I was OoO much of last week and *still*
> have no phoneline at home.
>
> I have downloaded the updated binaries, deployed the maven artifacts
> to a staging repo on the ASF Nexus instance, and used a noddy Maven
> project to test the client artifacts against a standalone Java broker.
>
> Andrew, the artifacts are currently staged at
> https://repository.apache.org/content/repositories/orgapacheqpid-120
> awaiting promotion, could you please test the
> broker/bdbstore/management-common artifacts you added for the work you
> are doing. They appear ok, but it would be nice to confirm all is well
> before releasing them (although given the main release artifacts were
> already mirrored I dont suppose theres much to be done now except not
> release them if they arent ok)
>
> Robbie
>
> On 19 January 2012 22:16, Justin Ross <jr...@redhat.com> wrote:
>> To the best of my knowledge, the artifacts as published are correct and
>> ready for release. I declare this vote closed, with 6 votes in favor and
>> none against.
>>
>> The 0.14 artifacts are now replicated to the mirrors. I'll publish the
>> final web site updates and send the announce mail tomorrow, and 0.14 will be
>> done.
>>
>> Thanks everyone for your continued efforts.
>>
>> Justin
>>
>>
>> On Wed, 18 Jan 2012, Justin Ross wrote:
>>
>>> Another Apache contributor helpfully pointed out that I had used the wrong
>>> key to sign these. That's now corrected.
>>>
>>> On Tue, 17 Jan 2012, Justin Ross wrote:
>>>
>>>> I'd like to declare this release approved. Robbie, were you able use the
>>>> maven artifacts in the updated (and signed) 0.14 distribution? If that's
>>>> working, and there aren't any other surprises, I'll close the vote.
>>>>
>>>> Justin
>>>>
>>>> On Fri, 13 Jan 2012, jross@redhat.com wrote:
>>>>
>>>>> An interim update:
>>>>>
>>>>> - I've repaired the embedded revision problem that Robbie found. The
>>>>> cause of this is still a bit of a mystery.
>>>>>
>>>>> - The artifacts are now signed. Check them out at:
>>>>>
>>>>> people.apache.org/~jross/qpid-0.14
>>>>>
>>>>> The other items remain incomplete; I'll have more to say Monday morning.
>>>>>
>>>>> Thanks!
>>>>> Justin
>>>>>
>>>>> On Wed, 11 Jan 2012, Justin Ross wrote:
>>>>>
>>>>>> I must apologize for the delay. I went on vacation right where this
>>>>>> thread left off.
>>>>>>
>>>>>> A quick note before I prepare the full release update. Here's the
>>>>>> plan:
>>>>>>
>>>>>> * Fix the issue Robbie mentioned below if it's easy (punt if not)
>>>>>> * Produce signed artifacts
>>>>>> * Declare the release voted "in favor"
>>>>>> * Publish web site updates, including the release notes with Andrew's
>>>>>> notes
>>>>>> * And of course, push the artifacts out for general consumption
>>>>>>
>>>>>> Tomorrow is busy, so I probably won't complete this until Friday.
>>>>>>
>>>>>> Thanks,
>>>>>> Justin
>>>>>>
>>>>>> On Thu, 15 Dec 2011, Robbie Gemmell wrote:
>>>>>>
>>>>>>> Thanks Justin.
>>>>>>>
>>>>>>> On closer inspection there was another difference with the Java broker
>>>>>>> package that I hadnt spotted, so the full rebuild was a good call.
>>>>>>>
>>>>>>> Looking it over again I notice that the SVN revision doesnt seem to
>>>>>>> have been passed through the release correctly somehow, the Java
>>>>>>> components embed it into properties files for version reporting but it
>>>>>>> is simply showing up as a dash in the files, although I tried running
>>>>>>> the release myself (using ./release.sh branches/0.14/qpid 1209041
>>>>>>> 0.14) and it seemed to work fine? I dont necessarily think it warrants
>>>>>>> another respin, but it'd be good to work out what happened and avoid
>>>>>>> it for future releases.
>>>>>>>
>>>>>>> I also tried to upload the maven artifacts to a staging repo on the
>>>>>>> Nexus instance but couldnt as as the signature files are required
>>>>>>> artifacts.
>>>>>>>
>>>>>>> Robbie
>>>>>>>
>>>>>>> On 15 December 2011 19:09, Justin Ross <jr...@redhat.com> wrote:
>>>>>>>>
>>>>>>>> I went ahead and produced the fixed distribution. The original is
>>>>>>>> still
>>>>>>>> there under a very long name.
>>>>>>>>
>>>>>>>> before:
>>>>>>>>
>>>>>>>> http://people.apache.org/~jross/qpid-0.14-before-restoring-missing-maven-artifacts/maven/org/apache/qpid/
>>>>>>>> after:
>>>>>>>> http://people.apache.org/~jross/qpid-0.14/maven/org/apache/qpid/
>>>>>>>>
>>>>>>>> Justin
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, 15 Dec 2011, Justin Ross wrote:
>>>>>>>>
>>>>>>>>> On Thu, 15 Dec 2011, Robbie Gemmell wrote:
>>>>>>>>>
>>>>>>>>>> The maven artifacts folder doesnt seem to contain everything I
>>>>>>>>>> expected it should. Only the client and common artifacts are
>>>>>>>>>> present,
>>>>>>>>>> whereas Andrew had previously added additional artifacts which are
>>>>>>>>>> mentioned in the ivy.xml file used for upload and the release.sh
>>>>>>>>>> script. Was an old copy of the release script possibly used to
>>>>>>>>>> generate the build?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> That's precisely what I did wrong. Thanks for catching this. I'll
>>>>>>>>> rebuild the RC2 distribution now from the same revision, but
>>>>>>>>> properly with
>>>>>>>>> the current release script.
>>>>>>>>>
>>>>>>>>>> Everything else I tested (Java broker, client, management
>>>>>>>>>> artifacts)
>>>>>>>>>> seemed fine and I was on course to just vote positively until I
>>>>>>>>>> noticed that.
>>>>>>>>>>
>>>>>>>>>> Do you happen to still have the build folder used to generate the
>>>>>>>>>> artifacts to see if they were actually built? Either they still
>>>>>>>>>> exist
>>>>>>>>>> and we use them, or we decide to rebuild them, or we just modify
>>>>>>>>>> the
>>>>>>>>>> ivy.xml file and upload the existing artifacts without them.
>>>>>>>>>> Thoughts?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I think the rebuild will be the most straightforward, so long as
>>>>>>>>> that's
>>>>>>>>> acceptable. (Fwiw, I've checked my build folder, and the remaining
>>>>>>>>> artifacts are present afaict.)
>>>>>>>>>
>>>>>>>>>> Robbie
>>>>>>>>>>
>>>>>>>>>> On 12 December 2011 14:58, Justin Ross <jr...@redhat.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Hello, everyone. There have been no new changes on the release
>>>>>>>>>>> branch
>>>>>>>>>>> since
>>>>>>>>>>> our proposed final RC, available here:
>>>>>>>>>>>
>>>>>>>>>>> http://people.apache.org/~jross/qpid-0.14/
>>>>>>>>>>>
>>>>>>>>>>> If you favor releasing this distribution as Qpid 0.14, vote +1.
>>>>>>>>>>> If
>>>>>>>>>>> instead
>>>>>>>>>>> you think there are problems that should prevent this distribution
>>>>>>>>>>> from
>>>>>>>>>>> being released, vote -1.
>>>>>>>>>>>
>>>>>>>>>>> I'd like to complete the vote by Thursday so I can push the
>>>>>>>>>>> release
>>>>>>>>>>> Friday,
>>>>>>>>>>> provided we vote in favor.
>>>>>>>>>>>
>>>>>>>>>>> Thanks, everyone, for all your help getting the release out.
>>>>>>>>>>>
>>>>>>>>>>> Justin
>>>>>>>>>>>
>>>>>>>>>>> ---
>>>>>>>>>>> 0.14 release page: https://cwiki.apache.org/qpid/014-release.html
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>>>>>>>> Project: http://qpid.apache.org
>>>>>>>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>>>>>>> Project: http://qpid.apache.org
>>>>>>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>>>>> Project: http://qpid.apache.org
>>>>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>>>> Project: http://qpid.apache.org
>>>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project: http://qpid.apache.org
>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
Re: [VOTE] Release 0.14
Posted by Robbie Gemmell <ro...@gmail.com>.
Sorry for the delay Justin, I was OoO much of last week and *still*
have no phoneline at home.
I have downloaded the updated binaries, deployed the maven artifacts
to a staging repo on the ASF Nexus instance, and used a noddy Maven
project to test the client artifacts against a standalone Java broker.
Andrew, the artifacts are currently staged at
https://repository.apache.org/content/repositories/orgapacheqpid-120
awaiting promotion, could you please test the
broker/bdbstore/management-common artifacts you added for the work you
are doing. They appear ok, but it would be nice to confirm all is well
before releasing them (although given the main release artifacts were
already mirrored I dont suppose theres much to be done now except not
release them if they arent ok)
Robbie
On 19 January 2012 22:16, Justin Ross <jr...@redhat.com> wrote:
> To the best of my knowledge, the artifacts as published are correct and
> ready for release. I declare this vote closed, with 6 votes in favor and
> none against.
>
> The 0.14 artifacts are now replicated to the mirrors. I'll publish the
> final web site updates and send the announce mail tomorrow, and 0.14 will be
> done.
>
> Thanks everyone for your continued efforts.
>
> Justin
>
>
> On Wed, 18 Jan 2012, Justin Ross wrote:
>
>> Another Apache contributor helpfully pointed out that I had used the wrong
>> key to sign these. That's now corrected.
>>
>> On Tue, 17 Jan 2012, Justin Ross wrote:
>>
>>> I'd like to declare this release approved. Robbie, were you able use the
>>> maven artifacts in the updated (and signed) 0.14 distribution? If that's
>>> working, and there aren't any other surprises, I'll close the vote.
>>>
>>> Justin
>>>
>>> On Fri, 13 Jan 2012, jross@redhat.com wrote:
>>>
>>>> An interim update:
>>>>
>>>> - I've repaired the embedded revision problem that Robbie found. The
>>>> cause of this is still a bit of a mystery.
>>>>
>>>> - The artifacts are now signed. Check them out at:
>>>>
>>>> people.apache.org/~jross/qpid-0.14
>>>>
>>>> The other items remain incomplete; I'll have more to say Monday morning.
>>>>
>>>> Thanks!
>>>> Justin
>>>>
>>>> On Wed, 11 Jan 2012, Justin Ross wrote:
>>>>
>>>>> I must apologize for the delay. I went on vacation right where this
>>>>> thread left off.
>>>>>
>>>>> A quick note before I prepare the full release update. Here's the
>>>>> plan:
>>>>>
>>>>> * Fix the issue Robbie mentioned below if it's easy (punt if not)
>>>>> * Produce signed artifacts
>>>>> * Declare the release voted "in favor"
>>>>> * Publish web site updates, including the release notes with Andrew's
>>>>> notes
>>>>> * And of course, push the artifacts out for general consumption
>>>>>
>>>>> Tomorrow is busy, so I probably won't complete this until Friday.
>>>>>
>>>>> Thanks,
>>>>> Justin
>>>>>
>>>>> On Thu, 15 Dec 2011, Robbie Gemmell wrote:
>>>>>
>>>>>> Thanks Justin.
>>>>>>
>>>>>> On closer inspection there was another difference with the Java broker
>>>>>> package that I hadnt spotted, so the full rebuild was a good call.
>>>>>>
>>>>>> Looking it over again I notice that the SVN revision doesnt seem to
>>>>>> have been passed through the release correctly somehow, the Java
>>>>>> components embed it into properties files for version reporting but it
>>>>>> is simply showing up as a dash in the files, although I tried running
>>>>>> the release myself (using ./release.sh branches/0.14/qpid 1209041
>>>>>> 0.14) and it seemed to work fine? I dont necessarily think it warrants
>>>>>> another respin, but it'd be good to work out what happened and avoid
>>>>>> it for future releases.
>>>>>>
>>>>>> I also tried to upload the maven artifacts to a staging repo on the
>>>>>> Nexus instance but couldnt as as the signature files are required
>>>>>> artifacts.
>>>>>>
>>>>>> Robbie
>>>>>>
>>>>>> On 15 December 2011 19:09, Justin Ross <jr...@redhat.com> wrote:
>>>>>>>
>>>>>>> I went ahead and produced the fixed distribution. The original is
>>>>>>> still
>>>>>>> there under a very long name.
>>>>>>>
>>>>>>> before:
>>>>>>>
>>>>>>> http://people.apache.org/~jross/qpid-0.14-before-restoring-missing-maven-artifacts/maven/org/apache/qpid/
>>>>>>> after:
>>>>>>> http://people.apache.org/~jross/qpid-0.14/maven/org/apache/qpid/
>>>>>>>
>>>>>>> Justin
>>>>>>>
>>>>>>>
>>>>>>> On Thu, 15 Dec 2011, Justin Ross wrote:
>>>>>>>
>>>>>>>> On Thu, 15 Dec 2011, Robbie Gemmell wrote:
>>>>>>>>
>>>>>>>>> The maven artifacts folder doesnt seem to contain everything I
>>>>>>>>> expected it should. Only the client and common artifacts are
>>>>>>>>> present,
>>>>>>>>> whereas Andrew had previously added additional artifacts which are
>>>>>>>>> mentioned in the ivy.xml file used for upload and the release.sh
>>>>>>>>> script. Was an old copy of the release script possibly used to
>>>>>>>>> generate the build?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> That's precisely what I did wrong. Thanks for catching this. I'll
>>>>>>>> rebuild the RC2 distribution now from the same revision, but
>>>>>>>> properly with
>>>>>>>> the current release script.
>>>>>>>>
>>>>>>>>> Everything else I tested (Java broker, client, management
>>>>>>>>> artifacts)
>>>>>>>>> seemed fine and I was on course to just vote positively until I
>>>>>>>>> noticed that.
>>>>>>>>>
>>>>>>>>> Do you happen to still have the build folder used to generate the
>>>>>>>>> artifacts to see if they were actually built? Either they still
>>>>>>>>> exist
>>>>>>>>> and we use them, or we decide to rebuild them, or we just modify
>>>>>>>>> the
>>>>>>>>> ivy.xml file and upload the existing artifacts without them.
>>>>>>>>> Thoughts?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> I think the rebuild will be the most straightforward, so long as
>>>>>>>> that's
>>>>>>>> acceptable. (Fwiw, I've checked my build folder, and the remaining
>>>>>>>> artifacts are present afaict.)
>>>>>>>>
>>>>>>>>> Robbie
>>>>>>>>>
>>>>>>>>> On 12 December 2011 14:58, Justin Ross <jr...@redhat.com> wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hello, everyone. There have been no new changes on the release
>>>>>>>>>> branch
>>>>>>>>>> since
>>>>>>>>>> our proposed final RC, available here:
>>>>>>>>>>
>>>>>>>>>> http://people.apache.org/~jross/qpid-0.14/
>>>>>>>>>>
>>>>>>>>>> If you favor releasing this distribution as Qpid 0.14, vote +1.
>>>>>>>>>> If
>>>>>>>>>> instead
>>>>>>>>>> you think there are problems that should prevent this distribution
>>>>>>>>>> from
>>>>>>>>>> being released, vote -1.
>>>>>>>>>>
>>>>>>>>>> I'd like to complete the vote by Thursday so I can push the
>>>>>>>>>> release
>>>>>>>>>> Friday,
>>>>>>>>>> provided we vote in favor.
>>>>>>>>>>
>>>>>>>>>> Thanks, everyone, for all your help getting the release out.
>>>>>>>>>>
>>>>>>>>>> Justin
>>>>>>>>>>
>>>>>>>>>> ---
>>>>>>>>>> 0.14 release page: https://cwiki.apache.org/qpid/014-release.html
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>>>>>>> Project: http://qpid.apache.org
>>>>>>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>>>>>> Project: http://qpid.apache.org
>>>>>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>>>> Project: http://qpid.apache.org
>>>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>>> Project: http://qpid.apache.org
>>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: [VOTE] Release 0.14
Posted by Justin Ross <jr...@redhat.com>.
To the best of my knowledge, the artifacts as published are correct and
ready for release. I declare this vote closed, with 6 votes in favor and
none against.
The 0.14 artifacts are now replicated to the mirrors. I'll publish the
final web site updates and send the announce mail tomorrow, and 0.14 will
be done.
Thanks everyone for your continued efforts.
Justin
On Wed, 18 Jan 2012, Justin Ross wrote:
> Another Apache contributor helpfully pointed out that I had used the wrong
> key to sign these. That's now corrected.
>
> On Tue, 17 Jan 2012, Justin Ross wrote:
>
>> I'd like to declare this release approved. Robbie, were you able use the
>> maven artifacts in the updated (and signed) 0.14 distribution? If that's
>> working, and there aren't any other surprises, I'll close the vote.
>>
>> Justin
>>
>> On Fri, 13 Jan 2012, jross@redhat.com wrote:
>>
>>> An interim update:
>>>
>>> - I've repaired the embedded revision problem that Robbie found. The
>>> cause of this is still a bit of a mystery.
>>>
>>> - The artifacts are now signed. Check them out at:
>>>
>>> people.apache.org/~jross/qpid-0.14
>>>
>>> The other items remain incomplete; I'll have more to say Monday morning.
>>>
>>> Thanks!
>>> Justin
>>>
>>> On Wed, 11 Jan 2012, Justin Ross wrote:
>>>
>>>> I must apologize for the delay. I went on vacation right where this
>>>> thread left off.
>>>>
>>>> A quick note before I prepare the full release update. Here's the plan:
>>>>
>>>> * Fix the issue Robbie mentioned below if it's easy (punt if not)
>>>> * Produce signed artifacts
>>>> * Declare the release voted "in favor"
>>>> * Publish web site updates, including the release notes with Andrew's
>>>> notes
>>>> * And of course, push the artifacts out for general consumption
>>>>
>>>> Tomorrow is busy, so I probably won't complete this until Friday.
>>>>
>>>> Thanks,
>>>> Justin
>>>>
>>>> On Thu, 15 Dec 2011, Robbie Gemmell wrote:
>>>>
>>>>> Thanks Justin.
>>>>>
>>>>> On closer inspection there was another difference with the Java broker
>>>>> package that I hadnt spotted, so the full rebuild was a good call.
>>>>>
>>>>> Looking it over again I notice that the SVN revision doesnt seem to
>>>>> have been passed through the release correctly somehow, the Java
>>>>> components embed it into properties files for version reporting but it
>>>>> is simply showing up as a dash in the files, although I tried running
>>>>> the release myself (using ./release.sh branches/0.14/qpid 1209041
>>>>> 0.14) and it seemed to work fine? I dont necessarily think it warrants
>>>>> another respin, but it'd be good to work out what happened and avoid
>>>>> it for future releases.
>>>>>
>>>>> I also tried to upload the maven artifacts to a staging repo on the
>>>>> Nexus instance but couldnt as as the signature files are required
>>>>> artifacts.
>>>>>
>>>>> Robbie
>>>>>
>>>>> On 15 December 2011 19:09, Justin Ross <jr...@redhat.com> wrote:
>>>>>> I went ahead and produced the fixed distribution. The original is
>>>>>> still
>>>>>> there under a very long name.
>>>>>>
>>>>>> before:
>>>>>> http://people.apache.org/~jross/qpid-0.14-before-restoring-missing-maven-artifacts/maven/org/apache/qpid/
>>>>>> after: http://people.apache.org/~jross/qpid-0.14/maven/org/apache/qpid/
>>>>>>
>>>>>> Justin
>>>>>>
>>>>>>
>>>>>> On Thu, 15 Dec 2011, Justin Ross wrote:
>>>>>>
>>>>>>> On Thu, 15 Dec 2011, Robbie Gemmell wrote:
>>>>>>>
>>>>>>>> The maven artifacts folder doesnt seem to contain everything I
>>>>>>>> expected it should. Only the client and common artifacts are present,
>>>>>>>> whereas Andrew had previously added additional artifacts which are
>>>>>>>> mentioned in the ivy.xml file used for upload and the release.sh
>>>>>>>> script. Was an old copy of the release script possibly used to
>>>>>>>> generate the build?
>>>>>>>
>>>>>>>
>>>>>>> That's precisely what I did wrong. Thanks for catching this. I'll
>>>>>>> rebuild the RC2 distribution now from the same revision, but properly
>>>>>>> with
>>>>>>> the current release script.
>>>>>>>
>>>>>>>> Everything else I tested (Java broker, client, management artifacts)
>>>>>>>> seemed fine and I was on course to just vote positively until I
>>>>>>>> noticed that.
>>>>>>>>
>>>>>>>> Do you happen to still have the build folder used to generate the
>>>>>>>> artifacts to see if they were actually built? Either they still exist
>>>>>>>> and we use them, or we decide to rebuild them, or we just modify the
>>>>>>>> ivy.xml file and upload the existing artifacts without them.
>>>>>>>> Thoughts?
>>>>>>>
>>>>>>>
>>>>>>> I think the rebuild will be the most straightforward, so long as
>>>>>>> that's
>>>>>>> acceptable. (Fwiw, I've checked my build folder, and the remaining
>>>>>>> artifacts are present afaict.)
>>>>>>>
>>>>>>>> Robbie
>>>>>>>>
>>>>>>>> On 12 December 2011 14:58, Justin Ross <jr...@redhat.com> wrote:
>>>>>>>>>
>>>>>>>>> Hello, everyone. There have been no new changes on the release
>>>>>>>>> branch
>>>>>>>>> since
>>>>>>>>> our proposed final RC, available here:
>>>>>>>>>
>>>>>>>>> http://people.apache.org/~jross/qpid-0.14/
>>>>>>>>>
>>>>>>>>> If you favor releasing this distribution as Qpid 0.14, vote +1. If
>>>>>>>>> instead
>>>>>>>>> you think there are problems that should prevent this distribution
>>>>>>>>> from
>>>>>>>>> being released, vote -1.
>>>>>>>>>
>>>>>>>>> I'd like to complete the vote by Thursday so I can push the release
>>>>>>>>> Friday,
>>>>>>>>> provided we vote in favor.
>>>>>>>>>
>>>>>>>>> Thanks, everyone, for all your help getting the release out.
>>>>>>>>>
>>>>>>>>> Justin
>>>>>>>>>
>>>>>>>>> ---
>>>>>>>>> 0.14 release page: https://cwiki.apache.org/qpid/014-release.html
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>>>>>> Project: http://qpid.apache.org
>>>>>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>>>>> Project: http://qpid.apache.org
>>>>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>>> Project: http://qpid.apache.org
>>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>> Project: http://qpid.apache.org
>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>>
>>>>>
>>>>
>>>
>>
>
Re: [VOTE] Release 0.14
Posted by Justin Ross <jr...@redhat.com>.
Another Apache contributor helpfully pointed out that I had used the wrong
key to sign these. That's now corrected.
On Tue, 17 Jan 2012, Justin Ross wrote:
> I'd like to declare this release approved. Robbie, were you able use the
> maven artifacts in the updated (and signed) 0.14 distribution? If that's
> working, and there aren't any other surprises, I'll close the vote.
>
> Justin
>
> On Fri, 13 Jan 2012, jross@redhat.com wrote:
>
>> An interim update:
>>
>> - I've repaired the embedded revision problem that Robbie found. The
>> cause of this is still a bit of a mystery.
>>
>> - The artifacts are now signed. Check them out at:
>>
>> people.apache.org/~jross/qpid-0.14
>>
>> The other items remain incomplete; I'll have more to say Monday morning.
>>
>> Thanks!
>> Justin
>>
>> On Wed, 11 Jan 2012, Justin Ross wrote:
>>
>>> I must apologize for the delay. I went on vacation right where this
>>> thread left off.
>>>
>>> A quick note before I prepare the full release update. Here's the plan:
>>>
>>> * Fix the issue Robbie mentioned below if it's easy (punt if not)
>>> * Produce signed artifacts
>>> * Declare the release voted "in favor"
>>> * Publish web site updates, including the release notes with Andrew's
>>> notes
>>> * And of course, push the artifacts out for general consumption
>>>
>>> Tomorrow is busy, so I probably won't complete this until Friday.
>>>
>>> Thanks,
>>> Justin
>>>
>>> On Thu, 15 Dec 2011, Robbie Gemmell wrote:
>>>
>>>> Thanks Justin.
>>>>
>>>> On closer inspection there was another difference with the Java broker
>>>> package that I hadnt spotted, so the full rebuild was a good call.
>>>>
>>>> Looking it over again I notice that the SVN revision doesnt seem to
>>>> have been passed through the release correctly somehow, the Java
>>>> components embed it into properties files for version reporting but it
>>>> is simply showing up as a dash in the files, although I tried running
>>>> the release myself (using ./release.sh branches/0.14/qpid 1209041
>>>> 0.14) and it seemed to work fine? I dont necessarily think it warrants
>>>> another respin, but it'd be good to work out what happened and avoid
>>>> it for future releases.
>>>>
>>>> I also tried to upload the maven artifacts to a staging repo on the
>>>> Nexus instance but couldnt as as the signature files are required
>>>> artifacts.
>>>>
>>>> Robbie
>>>>
>>>> On 15 December 2011 19:09, Justin Ross <jr...@redhat.com> wrote:
>>>>> I went ahead and produced the fixed distribution. The original is still
>>>>> there under a very long name.
>>>>>
>>>>> before:
>>>>> http://people.apache.org/~jross/qpid-0.14-before-restoring-missing-maven-artifacts/maven/org/apache/qpid/
>>>>> after: http://people.apache.org/~jross/qpid-0.14/maven/org/apache/qpid/
>>>>>
>>>>> Justin
>>>>>
>>>>>
>>>>> On Thu, 15 Dec 2011, Justin Ross wrote:
>>>>>
>>>>>> On Thu, 15 Dec 2011, Robbie Gemmell wrote:
>>>>>>
>>>>>>> The maven artifacts folder doesnt seem to contain everything I
>>>>>>> expected it should. Only the client and common artifacts are present,
>>>>>>> whereas Andrew had previously added additional artifacts which are
>>>>>>> mentioned in the ivy.xml file used for upload and the release.sh
>>>>>>> script. Was an old copy of the release script possibly used to
>>>>>>> generate the build?
>>>>>>
>>>>>>
>>>>>> That's precisely what I did wrong. Thanks for catching this. I'll
>>>>>> rebuild the RC2 distribution now from the same revision, but properly
>>>>>> with
>>>>>> the current release script.
>>>>>>
>>>>>>> Everything else I tested (Java broker, client, management artifacts)
>>>>>>> seemed fine and I was on course to just vote positively until I
>>>>>>> noticed that.
>>>>>>>
>>>>>>> Do you happen to still have the build folder used to generate the
>>>>>>> artifacts to see if they were actually built? Either they still exist
>>>>>>> and we use them, or we decide to rebuild them, or we just modify the
>>>>>>> ivy.xml file and upload the existing artifacts without them. Thoughts?
>>>>>>
>>>>>>
>>>>>> I think the rebuild will be the most straightforward, so long as that's
>>>>>> acceptable. (Fwiw, I've checked my build folder, and the remaining
>>>>>> artifacts are present afaict.)
>>>>>>
>>>>>>> Robbie
>>>>>>>
>>>>>>> On 12 December 2011 14:58, Justin Ross <jr...@redhat.com> wrote:
>>>>>>>>
>>>>>>>> Hello, everyone. There have been no new changes on the release
>>>>>>>> branch
>>>>>>>> since
>>>>>>>> our proposed final RC, available here:
>>>>>>>>
>>>>>>>> http://people.apache.org/~jross/qpid-0.14/
>>>>>>>>
>>>>>>>> If you favor releasing this distribution as Qpid 0.14, vote +1. If
>>>>>>>> instead
>>>>>>>> you think there are problems that should prevent this distribution
>>>>>>>> from
>>>>>>>> being released, vote -1.
>>>>>>>>
>>>>>>>> I'd like to complete the vote by Thursday so I can push the release
>>>>>>>> Friday,
>>>>>>>> provided we vote in favor.
>>>>>>>>
>>>>>>>> Thanks, everyone, for all your help getting the release out.
>>>>>>>>
>>>>>>>> Justin
>>>>>>>>
>>>>>>>> ---
>>>>>>>> 0.14 release page: https://cwiki.apache.org/qpid/014-release.html
>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>>>>> Project: http://qpid.apache.org
>>>>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>>>> Project: http://qpid.apache.org
>>>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>> Project: http://qpid.apache.org
>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>
>>>> ---------------------------------------------------------------------
>>>> Apache Qpid - AMQP Messaging Implementation
>>>> Project: http://qpid.apache.org
>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>
>>>>
>>>
>>
>
Re: [VOTE] Release 0.14
Posted by Justin Ross <jr...@redhat.com>.
I'd like to declare this release approved. Robbie, were you able use the
maven artifacts in the updated (and signed) 0.14 distribution? If that's
working, and there aren't any other surprises, I'll close the vote.
Justin
On Fri, 13 Jan 2012, jross@redhat.com wrote:
> An interim update:
>
> - I've repaired the embedded revision problem that Robbie found. The
> cause of this is still a bit of a mystery.
>
> - The artifacts are now signed. Check them out at:
>
> people.apache.org/~jross/qpid-0.14
>
> The other items remain incomplete; I'll have more to say Monday morning.
>
> Thanks!
> Justin
>
> On Wed, 11 Jan 2012, Justin Ross wrote:
>
>> I must apologize for the delay. I went on vacation right where this thread
>> left off.
>>
>> A quick note before I prepare the full release update. Here's the plan:
>>
>> * Fix the issue Robbie mentioned below if it's easy (punt if not)
>> * Produce signed artifacts
>> * Declare the release voted "in favor"
>> * Publish web site updates, including the release notes with Andrew's
>> notes
>> * And of course, push the artifacts out for general consumption
>>
>> Tomorrow is busy, so I probably won't complete this until Friday.
>>
>> Thanks,
>> Justin
>>
>> On Thu, 15 Dec 2011, Robbie Gemmell wrote:
>>
>>> Thanks Justin.
>>>
>>> On closer inspection there was another difference with the Java broker
>>> package that I hadnt spotted, so the full rebuild was a good call.
>>>
>>> Looking it over again I notice that the SVN revision doesnt seem to
>>> have been passed through the release correctly somehow, the Java
>>> components embed it into properties files for version reporting but it
>>> is simply showing up as a dash in the files, although I tried running
>>> the release myself (using ./release.sh branches/0.14/qpid 1209041
>>> 0.14) and it seemed to work fine? I dont necessarily think it warrants
>>> another respin, but it'd be good to work out what happened and avoid
>>> it for future releases.
>>>
>>> I also tried to upload the maven artifacts to a staging repo on the
>>> Nexus instance but couldnt as as the signature files are required
>>> artifacts.
>>>
>>> Robbie
>>>
>>> On 15 December 2011 19:09, Justin Ross <jr...@redhat.com> wrote:
>>>> I went ahead and produced the fixed distribution. The original is still
>>>> there under a very long name.
>>>>
>>>> before:
>>>> http://people.apache.org/~jross/qpid-0.14-before-restoring-missing-maven-artifacts/maven/org/apache/qpid/
>>>> after: http://people.apache.org/~jross/qpid-0.14/maven/org/apache/qpid/
>>>>
>>>> Justin
>>>>
>>>>
>>>> On Thu, 15 Dec 2011, Justin Ross wrote:
>>>>
>>>>> On Thu, 15 Dec 2011, Robbie Gemmell wrote:
>>>>>
>>>>>> The maven artifacts folder doesnt seem to contain everything I
>>>>>> expected it should. Only the client and common artifacts are present,
>>>>>> whereas Andrew had previously added additional artifacts which are
>>>>>> mentioned in the ivy.xml file used for upload and the release.sh
>>>>>> script. Was an old copy of the release script possibly used to
>>>>>> generate the build?
>>>>>
>>>>>
>>>>> That's precisely what I did wrong. Thanks for catching this. I'll
>>>>> rebuild the RC2 distribution now from the same revision, but properly
>>>>> with
>>>>> the current release script.
>>>>>
>>>>>> Everything else I tested (Java broker, client, management artifacts)
>>>>>> seemed fine and I was on course to just vote positively until I
>>>>>> noticed that.
>>>>>>
>>>>>> Do you happen to still have the build folder used to generate the
>>>>>> artifacts to see if they were actually built? Either they still exist
>>>>>> and we use them, or we decide to rebuild them, or we just modify the
>>>>>> ivy.xml file and upload the existing artifacts without them. Thoughts?
>>>>>
>>>>>
>>>>> I think the rebuild will be the most straightforward, so long as that's
>>>>> acceptable. (Fwiw, I've checked my build folder, and the remaining
>>>>> artifacts are present afaict.)
>>>>>
>>>>>> Robbie
>>>>>>
>>>>>> On 12 December 2011 14:58, Justin Ross <jr...@redhat.com> wrote:
>>>>>>>
>>>>>>> Hello, everyone. There have been no new changes on the release branch
>>>>>>> since
>>>>>>> our proposed final RC, available here:
>>>>>>>
>>>>>>> http://people.apache.org/~jross/qpid-0.14/
>>>>>>>
>>>>>>> If you favor releasing this distribution as Qpid 0.14, vote +1. If
>>>>>>> instead
>>>>>>> you think there are problems that should prevent this distribution
>>>>>>> from
>>>>>>> being released, vote -1.
>>>>>>>
>>>>>>> I'd like to complete the vote by Thursday so I can push the release
>>>>>>> Friday,
>>>>>>> provided we vote in favor.
>>>>>>>
>>>>>>> Thanks, everyone, for all your help getting the release out.
>>>>>>>
>>>>>>> Justin
>>>>>>>
>>>>>>> ---
>>>>>>> 0.14 release page: https://cwiki.apache.org/qpid/014-release.html
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>>>> Project: http://qpid.apache.org
>>>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>>> Project: http://qpid.apache.org
>>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> Apache Qpid - AMQP Messaging Implementation
>>>> Project: http://qpid.apache.org
>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>
>>> ---------------------------------------------------------------------
>>> Apache Qpid - AMQP Messaging Implementation
>>> Project: http://qpid.apache.org
>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>
>>>
>>
>
Re: [VOTE] Release 0.14
Posted by jr...@redhat.com.
An interim update:
- I've repaired the embedded revision problem that Robbie found. The
cause of this is still a bit of a mystery.
- The artifacts are now signed. Check them out at:
people.apache.org/~jross/qpid-0.14
The other items remain incomplete; I'll have more to say Monday morning.
Thanks!
Justin
On Wed, 11 Jan 2012, Justin Ross wrote:
> I must apologize for the delay. I went on vacation right where this thread
> left off.
>
> A quick note before I prepare the full release update. Here's the plan:
>
> * Fix the issue Robbie mentioned below if it's easy (punt if not)
> * Produce signed artifacts
> * Declare the release voted "in favor"
> * Publish web site updates, including the release notes with Andrew's
> notes
> * And of course, push the artifacts out for general consumption
>
> Tomorrow is busy, so I probably won't complete this until Friday.
>
> Thanks,
> Justin
>
> On Thu, 15 Dec 2011, Robbie Gemmell wrote:
>
>> Thanks Justin.
>>
>> On closer inspection there was another difference with the Java broker
>> package that I hadnt spotted, so the full rebuild was a good call.
>>
>> Looking it over again I notice that the SVN revision doesnt seem to
>> have been passed through the release correctly somehow, the Java
>> components embed it into properties files for version reporting but it
>> is simply showing up as a dash in the files, although I tried running
>> the release myself (using ./release.sh branches/0.14/qpid 1209041
>> 0.14) and it seemed to work fine? I dont necessarily think it warrants
>> another respin, but it'd be good to work out what happened and avoid
>> it for future releases.
>>
>> I also tried to upload the maven artifacts to a staging repo on the
>> Nexus instance but couldnt as as the signature files are required
>> artifacts.
>>
>> Robbie
>>
>> On 15 December 2011 19:09, Justin Ross <jr...@redhat.com> wrote:
>>> I went ahead and produced the fixed distribution. The original is still
>>> there under a very long name.
>>>
>>> before:
>>> http://people.apache.org/~jross/qpid-0.14-before-restoring-missing-maven-artifacts/maven/org/apache/qpid/
>>> after: http://people.apache.org/~jross/qpid-0.14/maven/org/apache/qpid/
>>>
>>> Justin
>>>
>>>
>>> On Thu, 15 Dec 2011, Justin Ross wrote:
>>>
>>>> On Thu, 15 Dec 2011, Robbie Gemmell wrote:
>>>>
>>>>> The maven artifacts folder doesnt seem to contain everything I
>>>>> expected it should. Only the client and common artifacts are present,
>>>>> whereas Andrew had previously added additional artifacts which are
>>>>> mentioned in the ivy.xml file used for upload and the release.sh
>>>>> script. Was an old copy of the release script possibly used to
>>>>> generate the build?
>>>>
>>>>
>>>> That's precisely what I did wrong. Thanks for catching this. I'll
>>>> rebuild the RC2 distribution now from the same revision, but properly
>>>> with
>>>> the current release script.
>>>>
>>>>> Everything else I tested (Java broker, client, management artifacts)
>>>>> seemed fine and I was on course to just vote positively until I
>>>>> noticed that.
>>>>>
>>>>> Do you happen to still have the build folder used to generate the
>>>>> artifacts to see if they were actually built? Either they still exist
>>>>> and we use them, or we decide to rebuild them, or we just modify the
>>>>> ivy.xml file and upload the existing artifacts without them. Thoughts?
>>>>
>>>>
>>>> I think the rebuild will be the most straightforward, so long as that's
>>>> acceptable. (Fwiw, I've checked my build folder, and the remaining
>>>> artifacts are present afaict.)
>>>>
>>>>> Robbie
>>>>>
>>>>> On 12 December 2011 14:58, Justin Ross <jr...@redhat.com> wrote:
>>>>>>
>>>>>> Hello, everyone. There have been no new changes on the release branch
>>>>>> since
>>>>>> our proposed final RC, available here:
>>>>>>
>>>>>> http://people.apache.org/~jross/qpid-0.14/
>>>>>>
>>>>>> If you favor releasing this distribution as Qpid 0.14, vote +1. If
>>>>>> instead
>>>>>> you think there are problems that should prevent this distribution from
>>>>>> being released, vote -1.
>>>>>>
>>>>>> I'd like to complete the vote by Thursday so I can push the release
>>>>>> Friday,
>>>>>> provided we vote in favor.
>>>>>>
>>>>>> Thanks, everyone, for all your help getting the release out.
>>>>>>
>>>>>> Justin
>>>>>>
>>>>>> ---
>>>>>> 0.14 release page: https://cwiki.apache.org/qpid/014-release.html
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>>> Project: http://qpid.apache.org
>>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> Apache Qpid - AMQP Messaging Implementation
>>>>> Project: http://qpid.apache.org
>>>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>>>
>>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> Apache Qpid - AMQP Messaging Implementation
>>> Project: http://qpid.apache.org
>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project: http://qpid.apache.org
>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>
>>
>