You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Justin Ross <jr...@apache.org> on 2014/09/11 21:32:12 UTC
0.30 release update - Release candidate
Hi, everyone. The 0.30 release candidate is now available:
https://dist.apache.org/repos/dist/dev/qpid/0.30-rc/
Maven repos for qpid-java and qpid-java-qmf-tools respectively:
https://repository.apache.org/content/repositories/orgapacheqpid-1012
https://repository.apache.org/content/repositories/orgapacheqpid-1013
Take notice! This remains pre-release software. Use it only for testing.
http://people.apache.org/~jross/qpid-0.30-rc.log
There's been quite a bit of good testing and feedback so far. Thanks very
much to those who have helped. My testing on Fedora 19 x86-64 showed no
test failures (though it does show some test clean up issues). Please test
the RC in your own environment and report back to this list.
These artifacts are signed. If approved by vote, the RC bits will be the
GA bits. I plan to open the vote Tuesday next week if no new blockers are
discovered in the mean time.
Now that we've begun to produce release candidates, only "blocker" issues
will be considered for inclusion. See the release page for more
information.
Thanks!
Justin
---
0.30 release page:
https://cwiki.apache.org/confluence/display/qpid/0.30+Release
Re: 0.30 release update - Release candidate
Posted by Robbie Gemmell <ro...@gmail.com>.
On 11 September 2014 20:52, Justin Ross <jr...@apache.org> wrote:
> On Thu, Sep 11, 2014 at 3:41 PM, Robbie Gemmell <ro...@gmail.com>
> wrote:
>
> > On 11 September 2014 20:32, Justin Ross <jr...@apache.org> wrote:
> >
> > > Hi, everyone. The 0.30 release candidate is now available:
> > >
> > > https://dist.apache.org/repos/dist/dev/qpid/0.30-rc/
> > >
> > > Maven repos for qpid-java and qpid-java-qmf-tools respectively:
> > >
> > >
> https://repository.apache.org/content/repositories/orgapacheqpid-1012
> > >
> https://repository.apache.org/content/repositories/orgapacheqpid-1013
> > >
> > >
> > There appear to be artifacts for the qmf tools in both of the staging
> > repos.
> >
> > If the earlier deploy doesnt have the final bits then the repo will need
> to
> > be dropped and recreated. If they are ok the second repo can be dropped.
>
>
> Ah, thanks. I was under the mistaken impression that each deploy would
> produce a distinct repo, so I retried the second when I didn't see it pop
> up.
>
>
The implicit repos allow multiple deploys while initially open after
creation, so that you can stage and manage related bits together. Its only
once you close them will you get a new implicit repo from the next deploy.
(We use the simpler implicit staging profiles on the ASF Nexus instance,
the more complicated explicit staging uses a maven plugin which does happen
to default to closing the staging repo after the deploy)
> The former (-1012) should be sufficient then. I'll remove the -1013 repo
> from the release page.
>
Re: 0.30 release update - Release candidate
Posted by Justin Ross <jr...@apache.org>.
On Thu, Sep 11, 2014 at 3:41 PM, Robbie Gemmell <ro...@gmail.com>
wrote:
> On 11 September 2014 20:32, Justin Ross <jr...@apache.org> wrote:
>
> > Hi, everyone. The 0.30 release candidate is now available:
> >
> > https://dist.apache.org/repos/dist/dev/qpid/0.30-rc/
> >
> > Maven repos for qpid-java and qpid-java-qmf-tools respectively:
> >
> > https://repository.apache.org/content/repositories/orgapacheqpid-1012
> > https://repository.apache.org/content/repositories/orgapacheqpid-1013
> >
> >
> There appear to be artifacts for the qmf tools in both of the staging
> repos.
>
> If the earlier deploy doesnt have the final bits then the repo will need to
> be dropped and recreated. If they are ok the second repo can be dropped.
Ah, thanks. I was under the mistaken impression that each deploy would
produce a distinct repo, so I retried the second when I didn't see it pop
up.
The former (-1012) should be sufficient then. I'll remove the -1013 repo
from the release page.
Re: 0.30 release update - Release candidate
Posted by Robbie Gemmell <ro...@gmail.com>.
On 11 September 2014 20:32, Justin Ross <jr...@apache.org> wrote:
> Hi, everyone. The 0.30 release candidate is now available:
>
> https://dist.apache.org/repos/dist/dev/qpid/0.30-rc/
>
> Maven repos for qpid-java and qpid-java-qmf-tools respectively:
>
> https://repository.apache.org/content/repositories/orgapacheqpid-1012
> https://repository.apache.org/content/repositories/orgapacheqpid-1013
>
>
There appear to be artifacts for the qmf tools in both of the staging repos.
If the earlier deploy doesnt have the final bits then the repo will need to
be dropped and recreated. If they are ok the second repo can be dropped.
> Take notice! This remains pre-release software. Use it only for testing.
>
> http://people.apache.org/~jross/qpid-0.30-rc.log
>
> There's been quite a bit of good testing and feedback so far. Thanks very
> much to those who have helped. My testing on Fedora 19 x86-64 showed no
> test failures (though it does show some test clean up issues). Please test
> the RC in your own environment and report back to this list.
>
> These artifacts are signed. If approved by vote, the RC bits will be the
> GA bits. I plan to open the vote Tuesday next week if no new blockers are
> discovered in the mean time.
>
> Now that we've begun to produce release candidates, only "blocker" issues
> will be considered for inclusion. See the release page for more
> information.
>
> Thanks!
> Justin
>
> ---
> 0.30 release page:
> https://cwiki.apache.org/confluence/display/qpid/0.30+Release
>
Re: 0.30 release update - Release candidate
Posted by Andrew MacBean <an...@gmail.com>.
Justin,
I have tested the sanity tested the Java Broker and have had no issues.
I have also done some quite focussed testing on the new HA and Web
Management UI features/functionality and again have not discovered any
blockers.
--Andrew
On 11 September 2014 20:32, Justin Ross <jr...@apache.org> wrote:
> Hi, everyone. The 0.30 release candidate is now available:
>
> https://dist.apache.org/repos/dist/dev/qpid/0.30-rc/
>
> Maven repos for qpid-java and qpid-java-qmf-tools respectively:
>
> https://repository.apache.org/content/repositories/orgapacheqpid-1012
> https://repository.apache.org/content/repositories/orgapacheqpid-1013
>
> Take notice! This remains pre-release software. Use it only for testing.
>
> http://people.apache.org/~jross/qpid-0.30-rc.log
>
> There's been quite a bit of good testing and feedback so far. Thanks very
> much to those who have helped. My testing on Fedora 19 x86-64 showed no
> test failures (though it does show some test clean up issues). Please test
> the RC in your own environment and report back to this list.
>
> These artifacts are signed. If approved by vote, the RC bits will be the
> GA bits. I plan to open the vote Tuesday next week if no new blockers are
> discovered in the mean time.
>
> Now that we've begun to produce release candidates, only "blocker" issues
> will be considered for inclusion. See the release page for more
> information.
>
> Thanks!
> Justin
>
> ---
> 0.30 release page:
> https://cwiki.apache.org/confluence/display/qpid/0.30+Release
>
Re: 0.30 release update - Release candidate
Posted by Chuck Rolke <cr...@redhat.com>.
Tested qpid-cpp-0.30.tar.gz on windows and everything works as expected.
Built 64-bit broker/clients/dotnet_binding and they all interoperate.
----- Original Message -----
> From: "Gordon Sim" <gs...@redhat.com>
> To: users@qpid.apache.org
> Sent: Friday, September 12, 2014 12:55:39 PM
> Subject: Re: 0.30 release update - Release candidate
>
> On 09/11/2014 08:32 PM, Justin Ross wrote:
> > Hi, everyone. The 0.30 release candidate is now available:
> >
> > https://dist.apache.org/repos/dist/dev/qpid/0.30-rc/
> >
> > Maven repos for qpid-java and qpid-java-qmf-tools respectively:
> >
> > https://repository.apache.org/content/repositories/orgapacheqpid-1012
> > https://repository.apache.org/content/repositories/orgapacheqpid-1013
> >
> > Take notice! This remains pre-release software. Use it only for testing.
> >
> > http://people.apache.org/~jross/qpid-0.30-rc.log
> >
> > There's been quite a bit of good testing and feedback so far. Thanks very
> > much to those who have helped. My testing on Fedora 19 x86-64 showed no
> > test failures (though it does show some test clean up issues). Please test
> > the RC in your own environment and report back to this list.
> >
> > These artifacts are signed. If approved by vote, the RC bits will be the
> > GA bits. I plan to open the vote Tuesday next week if no new blockers are
> > discovered in the mean time.
> >
> > Now that we've begun to produce release candidates, only "blocker" issues
> > will be considered for inclusion. See the release page for more
> > information.
>
> I've gone through some basic testing on all the packages:
>
> * qpid-cpp builds and tests pass (couple of expected failures due to
> missing dependencies)
> * python tests pass against c++ broker (qpid-python, qpid-tests)
> * c++ client works over 0-10 and 1.0 against c++ broker
> * qpid tools work against broker (qpid-python, qpid-qmf, qpid-tools)
> * JMS Drain works against c++ broker
>
> * the qpid-java-qmf-tools stuff builds ok; the scripts didn't work 'out
> of the box for me' I had to setup a classpath manually and was then able
> to run QpidConfig and also the REST management service
>
> * qpid-java builds and runs internal tests ok
> * ran JMS client (0-10 only) against c++ broker
> * had to dig around to find how to start the broker from this package,
> but did eventually get it going
> * c++ clients can send and receive ok over 0-10 and 1.0
> * out of the box broker only supports CRAM-MD5, which the python client
> doesn't support. I changed the broker to allow anonymous and tests ran
> with one failure:
> qpid_tests.broker_0_10.dtx.DtxTests.test_set_timeout_too_high raised
> error 'Xid already started an neither join nor resume setXid(format=0,
> globalId="dummy", branchId="v24")'
>
> Nothing I would consider a blocker.
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: 0.30 release update - Release candidate
Posted by Gordon Sim <gs...@redhat.com>.
On 09/11/2014 08:32 PM, Justin Ross wrote:
> Hi, everyone. The 0.30 release candidate is now available:
>
> https://dist.apache.org/repos/dist/dev/qpid/0.30-rc/
>
> Maven repos for qpid-java and qpid-java-qmf-tools respectively:
>
> https://repository.apache.org/content/repositories/orgapacheqpid-1012
> https://repository.apache.org/content/repositories/orgapacheqpid-1013
>
> Take notice! This remains pre-release software. Use it only for testing.
>
> http://people.apache.org/~jross/qpid-0.30-rc.log
>
> There's been quite a bit of good testing and feedback so far. Thanks very
> much to those who have helped. My testing on Fedora 19 x86-64 showed no
> test failures (though it does show some test clean up issues). Please test
> the RC in your own environment and report back to this list.
>
> These artifacts are signed. If approved by vote, the RC bits will be the
> GA bits. I plan to open the vote Tuesday next week if no new blockers are
> discovered in the mean time.
>
> Now that we've begun to produce release candidates, only "blocker" issues
> will be considered for inclusion. See the release page for more
> information.
I've gone through some basic testing on all the packages:
* qpid-cpp builds and tests pass (couple of expected failures due to
missing dependencies)
* python tests pass against c++ broker (qpid-python, qpid-tests)
* c++ client works over 0-10 and 1.0 against c++ broker
* qpid tools work against broker (qpid-python, qpid-qmf, qpid-tools)
* JMS Drain works against c++ broker
* the qpid-java-qmf-tools stuff builds ok; the scripts didn't work 'out
of the box for me' I had to setup a classpath manually and was then able
to run QpidConfig and also the REST management service
* qpid-java builds and runs internal tests ok
* ran JMS client (0-10 only) against c++ broker
* had to dig around to find how to start the broker from this package,
but did eventually get it going
* c++ clients can send and receive ok over 0-10 and 1.0
* out of the box broker only supports CRAM-MD5, which the python client
doesn't support. I changed the broker to allow anonymous and tests ran
with one failure:
qpid_tests.broker_0_10.dtx.DtxTests.test_set_timeout_too_high raised
error 'Xid already started an neither join nor resume setXid(format=0,
globalId="dummy", branchId="v24")'
Nothing I would consider a blocker.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org