[RESULT] [VOTE] Release Qpid Proton 0.10 (RC3)
There were 7 binding and 1 non-binding +1 votes, with no other votes received. The vote has passed. I will re-tag the 0.10-rc3 tag in the repo as 0.10 proper, add the release files to the dist release svn repo, and release the maven staging repo. The website will be updated later after the artifacts have had time to sync to the mirrors. Robbie
[jira] [Commented] (PROTON-952) Building Proton with python 2.6 and python 3.4 on Travis CI finds and links wrong libpython
[ https://issues.apache.org/jira/browse/PROTON-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14695989#comment-14695989 ] Andrew Stitcher commented on PROTON-952: It may be a "cmake bug" in that cmake doesn't ensure that it uses the same version for both python and python library. But it is straightforward to solve in the proton cmake files. > Building Proton with python 2.6 and python 3.4 on Travis CI finds and links > wrong libpython > --- > > Key: PROTON-952 > URL: https://issues.apache.org/jira/browse/PROTON-952 > Project: Qpid Proton > Issue Type: Bug >Affects Versions: 0.10 > Environment: Travis CI build environment (highly customised Ubuntu) >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: 0.11 > > > You can specify a specifiv version of python to use in the Traviis build > process and that will set up the build environment to use a python virtualenv > with that version of python. > When using python 2.6 or 3.4 (and probably 3.3 too but I've not tested that) > the cmake installed will find the python 2.7 libs and link them into the > proton bindings extension. This seems to succeed at build time but seems to > make the "python-test" fail to even start in both cases (though with slightly > different symptoms). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (PROTON-952) Building Proton with python 2.6 and python 3.4 on Travis CI finds and links wrong libpython
[ https://issues.apache.org/jira/browse/PROTON-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-952. Resolution: Fixed > Building Proton with python 2.6 and python 3.4 on Travis CI finds and links > wrong libpython > --- > > Key: PROTON-952 > URL: https://issues.apache.org/jira/browse/PROTON-952 > Project: Qpid Proton > Issue Type: Bug >Affects Versions: 0.10 > Environment: Travis CI build environment (highly customised Ubuntu) >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: 0.11 > > > You can specify a specifiv version of python to use in the Traviis build > process and that will set up the build environment to use a python virtualenv > with that version of python. > When using python 2.6 or 3.4 (and probably 3.3 too but I've not tested that) > the cmake installed will find the python 2.7 libs and link them into the > proton bindings extension. This seems to succeed at build time but seems to > make the "python-test" fail to even start in both cases (though with slightly > different symptoms). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (PROTON-952) Building Proton with python 2.6 and python 3.4 on Travis CI finds and links wrong libpython
[ https://issues.apache.org/jira/browse/PROTON-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reopened PROTON-952: Assignee: Andrew Stitcher (was: Ken Giusti) > Building Proton with python 2.6 and python 3.4 on Travis CI finds and links > wrong libpython > --- > > Key: PROTON-952 > URL: https://issues.apache.org/jira/browse/PROTON-952 > Project: Qpid Proton > Issue Type: Bug >Affects Versions: 0.10 > Environment: Travis CI build environment (highly customised Ubuntu) >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: 0.11 > > > You can specify a specifiv version of python to use in the Traviis build > process and that will set up the build environment to use a python virtualenv > with that version of python. > When using python 2.6 or 3.4 (and probably 3.3 too but I've not tested that) > the cmake installed will find the python 2.7 libs and link them into the > proton bindings extension. This seems to succeed at build time but seems to > make the "python-test" fail to even start in both cases (though with slightly > different symptoms). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-952) Building Proton with python 2.6 and python 3.4 on Travis CI finds and links wrong libpython
[ https://issues.apache.org/jira/browse/PROTON-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-952: --- Fix Version/s: 0.11 > Building Proton with python 2.6 and python 3.4 on Travis CI finds and links > wrong libpython > --- > > Key: PROTON-952 > URL: https://issues.apache.org/jira/browse/PROTON-952 > Project: Qpid Proton > Issue Type: Bug >Affects Versions: 0.10 > Environment: Travis CI build environment (highly customised Ubuntu) >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: 0.11 > > > You can specify a specifiv version of python to use in the Traviis build > process and that will set up the build environment to use a python virtualenv > with that version of python. > When using python 2.6 or 3.4 (and probably 3.3 too but I've not tested that) > the cmake installed will find the python 2.7 libs and link them into the > proton bindings extension. This seems to succeed at build time but seems to > make the "python-test" fail to even start in both cases (though with slightly > different symptoms). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-952) Building Proton with python 2.6 and python 3.4 on Travis CI finds and links wrong libpython
[ https://issues.apache.org/jira/browse/PROTON-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14695979#comment-14695979 ] ASF subversion and git services commented on PROTON-952: Commit 23c58ed39678cd359d272ddc3a42e769342653be in qpid-proton's branch refs/heads/master from [~astitcher] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=23c58ed ] PROTON-952: Make sure we use the same python library version as python version > Building Proton with python 2.6 and python 3.4 on Travis CI finds and links > wrong libpython > --- > > Key: PROTON-952 > URL: https://issues.apache.org/jira/browse/PROTON-952 > Project: Qpid Proton > Issue Type: Bug >Affects Versions: 0.10 > Environment: Travis CI build environment (highly customised Ubuntu) >Reporter: Andrew Stitcher >Assignee: Ken Giusti > > You can specify a specifiv version of python to use in the Traviis build > process and that will set up the build environment to use a python virtualenv > with that version of python. > When using python 2.6 or 3.4 (and probably 3.3 too but I've not tested that) > the cmake installed will find the python 2.7 libs and link them into the > proton bindings extension. This seems to succeed at build time but seems to > make the "python-test" fail to even start in both cases (though with slightly > different symptoms). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Release Qpid Proton 0.10 (RC3)
I've now figured out the issue (and it's an instructive problem): PROTON-979: [1] It seems that both OpenSSL and Cyrus SASL have interacting global state. If SASL gets to initialise libcrypto first then when the SSL code tries to do it it fails. Just another emphasis that neither openssl nor Cyrus sasl is really suitable to be used as part of a library. [1] https://issues.apache.org/jira/browse/PROTON-979 On Wed, 2015-08-12 at 17:41 -0400, Andrew Stitcher wrote: > I've tested proton-c on ubuntu1404, ubuntu1204 & FreeBSD 10.1p17 > > Ubuntu 1204 builds and ctests fine. > This is our the OS on our travis CI so it's not a surprise it works. > > Ubuntu 1404 - I'm having problems with the "python" tests and SSL - > investigating whether this is my config or something more. This is a > little worrying > > FreeBSD - I'm getting test failures in > proton_tests.messenger.SelectableMessengerTest.testSelectable* > This might reflect some difference in poll() behaviour. > > I'm also getting failures in > ...*_valgrind with output like this... > AssertionError: Unexpected input while waiting for receiver to > initialize: ==12271== Use of uninitialised value of size 8 > > Which seems like valgrind detected use of an uninitialised value. > I don't know it this is in proton or one of the lib it uses yet. > > Not sure if FreeBSD is important enough to care too much, but it > should > work. > > [so no -1 yet, but investigating. IMO the FreeBSD failures aren't > enough to reject the release, but the Ubuntu failures might be] > > Andrew > > On Tue, 2015-08-11 at 21:08 +0100, Robbie Gemmell wrote: > > Hi all, > > > > I have put up a third cut for 0.10, please test it and vote > > accordingly. > > > > Since RC2 there have been fixes for PROTON-978, PROTON-975, and > > PROTON-899. > > > > The release archive and sig/checksums can be grabbed from: > > https://dist.apache.org/repos/dist/dev/qpid/proton/0.10-rc3/ > > > > Maven artifacts for the Java bits can be found in a temporary > > staging > > repo at: > > https://repository.apache.org/content/repositories/orgapacheqpid-10 > > 42 > > > > It is tagged as 0.10-rc3. You may need to fetch the tags explicitly > > to > > see it, e.g: "git fetch --tags" > > > > Regards,
Re: [VOTE] Release Qpid Proton 0.10 (RC3)
I vote +1: I've tested proton-c & python on: Ubuntu 12.04 (amd64) Ubuntu 14.04 (amd64/i686) Raspberry Pi2 (Raspbian Jesse) FreeBSD 10.1p17 Windows 8.1 with Visual Studio 12 (2013) [Some of these test have had Java & tox as well but it's been uneven) And modulo some (severe) irritations (see the other messages) there have been no blocking problems. Andrew On Tue, 2015-08-11 at 21:08 +0100, Robbie Gemmell wrote: > Hi all, > > I have put up a third cut for 0.10, please test it and vote > accordingly. > > Since RC2 there have been fixes for PROTON-978, PROTON-975, and > PROTON-899. > > The release archive and sig/checksums can be grabbed from: > https://dist.apache.org/repos/dist/dev/qpid/proton/0.10-rc3/ > > Maven artifacts for the Java bits can be found in a temporary staging > repo at: > https://repository.apache.org/content/repositories/orgapacheqpid-1042 > > It is tagged as 0.10-rc3. You may need to fetch the tags explicitly > to > see it, e.g: "git fetch --tags" > > Regards, > Robbie
Re: [VOTE] Release Qpid Proton 0.10 (RC3)
Great, well done figuring it out! Care to vote yet? :) Robbie On 13 August 2015 at 21:16, Andrew Stitcher wrote: > I've now figured out the issue (and it's an instructive problem): > > PROTON-979: [1] > > It seems that both OpenSSL and Cyrus SASL have interacting global > state. If SASL gets to initialise libcrypto first then when the SSL > code tries to do it it fails. > > Just another emphasis that neither openssl nor Cyrus sasl is really > suitable to be used as part of a library. > > > [1] https://issues.apache.org/jira/browse/PROTON-979 > On Wed, 2015-08-12 at 17:41 -0400, Andrew Stitcher wrote: >> I've tested proton-c on ubuntu1404, ubuntu1204 & FreeBSD 10.1p17 >> >> Ubuntu 1204 builds and ctests fine. >> This is our the OS on our travis CI so it's not a surprise it works. >> >> Ubuntu 1404 - I'm having problems with the "python" tests and SSL - >> investigating whether this is my config or something more. This is a >> little worrying >> >> FreeBSD - I'm getting test failures in >> proton_tests.messenger.SelectableMessengerTest.testSelectable* >> This might reflect some difference in poll() behaviour. >> >> I'm also getting failures in >> ...*_valgrind with output like this... >> AssertionError: Unexpected input while waiting for receiver to >> initialize: ==12271== Use of uninitialised value of size 8 >> >> Which seems like valgrind detected use of an uninitialised value. >> I don't know it this is in proton or one of the lib it uses yet. >> >> Not sure if FreeBSD is important enough to care too much, but it >> should >> work. >> >> [so no -1 yet, but investigating. IMO the FreeBSD failures aren't >> enough to reject the release, but the Ubuntu failures might be] >> >> Andrew >> >> On Tue, 2015-08-11 at 21:08 +0100, Robbie Gemmell wrote: >> > Hi all, >> > >> > I have put up a third cut for 0.10, please test it and vote >> > accordingly. >> > >> > Since RC2 there have been fixes for PROTON-978, PROTON-975, and >> > PROTON-899. >> > >> > The release archive and sig/checksums can be grabbed from: >> > https://dist.apache.org/repos/dist/dev/qpid/proton/0.10-rc3/ >> > >> > Maven artifacts for the Java bits can be found in a temporary >> > staging >> > repo at: >> > https://repository.apache.org/content/repositories/orgapacheqpid-10 >> > 42 >> > >> > It is tagged as 0.10-rc3. You may need to fetch the tags explicitly >> > to >> > see it, e.g: "git fetch --tags" >> > >> > Regards,
[jira] [Created] (PROTON-979) build tests fail if Cyrus SASL otp mech is installed
Andrew Stitcher created PROTON-979:
--
Summary: build tests fail if Cyrus SASL otp mech is installed
Key: PROTON-979
URL: https://issues.apache.org/jira/browse/PROTON-979
Project: Qpid Proton
Issue Type: Bug
Components: proton-c
Affects Versions: 0.9.1, 0.10, 0.11
Environment: Ubuntu 14.04, cyrus sasl 2.1.25
Reporter: Andrew Stitcher
If you have the Cyrus SASL OTP module installed (debian package
libsasl2-modules-otp):
While running 'ctest' the python-test fails in a lot of SSL tests but only if
SASL has been initialised first. So if you run many of the failing tests by
them selves using proton-test directly they will succeed.
The first error in a full test run looks like:
{noformat}
1: proton_tests.sasl.SSLSASLTest.testSSLExternalSimple .
fail
1: Error during setup: Traceback (most recent call last):
1: File
"/home/andrew/src/proton/qpid-proton-0.10/tests/python/proton-test", line 360,
in run
1: phase()
1: File
"/home/andrew/src/proton/qpid-proton-0.10/tests/python/proton_tests/sasl.py",
line 373, in setup
1: self.server_domain = SSLDomain(SSLDomain.MODE_SERVER)
1: File
"/home/andrew/src/proton/qpid-proton-0.10/proton-c/bindings/python/proton/__init__.py",
line 3490, in __init__
1: raise SSLUnavailable()
1: SSLUnavailable
{noformat}
It seems that the underlying cause here is that the Cyrus sasl otp code uses
libcrypt which has some global initialisation.
If the otp code gets there first it initiialises libcrypt in a way which makes
this line of code in the proton openssl code fail:
[line 482 of openssl.c]
{code}
domain->ctx = SSL_CTX_new(SSLv23_server_method()); // and TLSv1+
{code}
It is highly plausible that other cyrus sasl mechs that also use ssl and are
actually initialised could also cause this problem (at least sql & ldap)
however in my test environment they aren't initialised.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: [VOTE] Release Qpid Proton 0.10 (RC3)
On 08/13/2015 03:20 PM, Robbie Gemmell wrote: To clarify, my run was also using the x86_64 / amd64 version, using a VM. Neither of us have been able to reproduce what Andrew saw, so unless we can get a better idea what it is specifically then I am inclined to say that we proceed. If there is an issue and it can be identified, I'm sure it will be joined by others once a larger group of folks can actually get there hands on a release, and I'll happilly cut a 0.10.1 to address them if fixes are available. +1 Robbie On 13 August 2015 at 20:05, Ted Ross wrote: I ran the tests under Ubuntu 14.04 (for amd64) running an x86_64 Linux kernel (using Docker). All of the tests, including the SSL tests pass. -Ted On 08/13/2015 09:56 AM, Robbie Gemmell wrote: I have run up a fresh Ubuntu 14.04.3 install didn't see any issues (once I figured out what packages to install to get the tests all running). Can you elaborate on the problem you are seeing? Robbie On 12 August 2015 at 22:41, Andrew Stitcher wrote: I've tested proton-c on ubuntu1404, ubuntu1204 & FreeBSD 10.1p17 Ubuntu 1204 builds and ctests fine. This is our the OS on our travis CI so it's not a surprise it works. Ubuntu 1404 - I'm having problems with the "python" tests and SSL - investigating whether this is my config or something more. This is a little worrying FreeBSD - I'm getting test failures in proton_tests.messenger.SelectableMessengerTest.testSelectable* This might reflect some difference in poll() behaviour. I'm also getting failures in ...*_valgrind with output like this... AssertionError: Unexpected input while waiting for receiver to initialize: ==12271== Use of uninitialised value of size 8 Which seems like valgrind detected use of an uninitialised value. I don't know it this is in proton or one of the lib it uses yet. Not sure if FreeBSD is important enough to care too much, but it should work. [so no -1 yet, but investigating. IMO the FreeBSD failures aren't enough to reject the release, but the Ubuntu failures might be] Andrew On Tue, 2015-08-11 at 21:08 +0100, Robbie Gemmell wrote: Hi all, I have put up a third cut for 0.10, please test it and vote accordingly. Since RC2 there have been fixes for PROTON-978, PROTON-975, and PROTON-899. The release archive and sig/checksums can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton/0.10-rc3/ Maven artifacts for the Java bits can be found in a temporary staging repo at: https://repository.apache.org/content/repositories/orgapacheqpid-1042 It is tagged as 0.10-rc3. You may need to fetch the tags explicitly to see it, e.g: "git fetch --tags" Regards, 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 Proton 0.10 (RC3)
To clarify, my run was also using the x86_64 / amd64 version, using a VM. Neither of us have been able to reproduce what Andrew saw, so unless we can get a better idea what it is specifically then I am inclined to say that we proceed. If there is an issue and it can be identified, I'm sure it will be joined by others once a larger group of folks can actually get there hands on a release, and I'll happilly cut a 0.10.1 to address them if fixes are available. Robbie On 13 August 2015 at 20:05, Ted Ross wrote: > I ran the tests under Ubuntu 14.04 (for amd64) running an x86_64 Linux > kernel (using Docker). All of the tests, including the SSL tests pass. > > -Ted > > > On 08/13/2015 09:56 AM, Robbie Gemmell wrote: >> >> I have run up a fresh Ubuntu 14.04.3 install didn't see any issues >> (once I figured out what packages to install to get the tests all >> running). Can you elaborate on the problem you are seeing? >> >> Robbie >> >> On 12 August 2015 at 22:41, Andrew Stitcher wrote: >>> >>> I've tested proton-c on ubuntu1404, ubuntu1204 & FreeBSD 10.1p17 >>> >>> Ubuntu 1204 builds and ctests fine. >>> This is our the OS on our travis CI so it's not a surprise it works. >>> >>> Ubuntu 1404 - I'm having problems with the "python" tests and SSL - >>> investigating whether this is my config or something more. This is a >>> little worrying >>> >>> FreeBSD - I'm getting test failures in >>> proton_tests.messenger.SelectableMessengerTest.testSelectable* >>> This might reflect some difference in poll() behaviour. >>> >>> I'm also getting failures in >>> ...*_valgrind with output like this... >>> AssertionError: Unexpected input while waiting for receiver to >>> initialize: ==12271== Use of uninitialised value of size 8 >>> >>> Which seems like valgrind detected use of an uninitialised value. >>> I don't know it this is in proton or one of the lib it uses yet. >>> >>> Not sure if FreeBSD is important enough to care too much, but it should >>> work. >>> >>> [so no -1 yet, but investigating. IMO the FreeBSD failures aren't >>> enough to reject the release, but the Ubuntu failures might be] >>> >>> Andrew >>> >>> On Tue, 2015-08-11 at 21:08 +0100, Robbie Gemmell wrote: Hi all, I have put up a third cut for 0.10, please test it and vote accordingly. Since RC2 there have been fixes for PROTON-978, PROTON-975, and PROTON-899. The release archive and sig/checksums can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton/0.10-rc3/ Maven artifacts for the Java bits can be found in a temporary staging repo at: https://repository.apache.org/content/repositories/orgapacheqpid-1042 It is tagged as 0.10-rc3. You may need to fetch the tags explicitly to see it, e.g: "git fetch --tags" Regards, 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 Proton 0.10 (RC3)
I ran the tests under Ubuntu 14.04 (for amd64) running an x86_64 Linux kernel (using Docker). All of the tests, including the SSL tests pass. -Ted On 08/13/2015 09:56 AM, Robbie Gemmell wrote: I have run up a fresh Ubuntu 14.04.3 install didn't see any issues (once I figured out what packages to install to get the tests all running). Can you elaborate on the problem you are seeing? Robbie On 12 August 2015 at 22:41, Andrew Stitcher wrote: I've tested proton-c on ubuntu1404, ubuntu1204 & FreeBSD 10.1p17 Ubuntu 1204 builds and ctests fine. This is our the OS on our travis CI so it's not a surprise it works. Ubuntu 1404 - I'm having problems with the "python" tests and SSL - investigating whether this is my config or something more. This is a little worrying FreeBSD - I'm getting test failures in proton_tests.messenger.SelectableMessengerTest.testSelectable* This might reflect some difference in poll() behaviour. I'm also getting failures in ...*_valgrind with output like this... AssertionError: Unexpected input while waiting for receiver to initialize: ==12271== Use of uninitialised value of size 8 Which seems like valgrind detected use of an uninitialised value. I don't know it this is in proton or one of the lib it uses yet. Not sure if FreeBSD is important enough to care too much, but it should work. [so no -1 yet, but investigating. IMO the FreeBSD failures aren't enough to reject the release, but the Ubuntu failures might be] Andrew On Tue, 2015-08-11 at 21:08 +0100, Robbie Gemmell wrote: Hi all, I have put up a third cut for 0.10, please test it and vote accordingly. Since RC2 there have been fixes for PROTON-978, PROTON-975, and PROTON-899. The release archive and sig/checksums can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton/0.10-rc3/ Maven artifacts for the Java bits can be found in a temporary staging repo at: https://repository.apache.org/content/repositories/orgapacheqpid-1042 It is tagged as 0.10-rc3. You may need to fetch the tags explicitly to see it, e.g: "git fetch --tags" Regards, Robbie - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [VOTE] Release Qpid Proton 0.10 (RC3)
I have run up a fresh Ubuntu 14.04.3 install didn't see any issues (once I figured out what packages to install to get the tests all running). Can you elaborate on the problem you are seeing? Robbie On 12 August 2015 at 22:41, Andrew Stitcher wrote: > I've tested proton-c on ubuntu1404, ubuntu1204 & FreeBSD 10.1p17 > > Ubuntu 1204 builds and ctests fine. > This is our the OS on our travis CI so it's not a surprise it works. > > Ubuntu 1404 - I'm having problems with the "python" tests and SSL - > investigating whether this is my config or something more. This is a > little worrying > > FreeBSD - I'm getting test failures in > proton_tests.messenger.SelectableMessengerTest.testSelectable* > This might reflect some difference in poll() behaviour. > > I'm also getting failures in > ...*_valgrind with output like this... > AssertionError: Unexpected input while waiting for receiver to > initialize: ==12271== Use of uninitialised value of size 8 > > Which seems like valgrind detected use of an uninitialised value. > I don't know it this is in proton or one of the lib it uses yet. > > Not sure if FreeBSD is important enough to care too much, but it should > work. > > [so no -1 yet, but investigating. IMO the FreeBSD failures aren't > enough to reject the release, but the Ubuntu failures might be] > > Andrew > > On Tue, 2015-08-11 at 21:08 +0100, Robbie Gemmell wrote: >> Hi all, >> >> I have put up a third cut for 0.10, please test it and vote >> accordingly. >> >> Since RC2 there have been fixes for PROTON-978, PROTON-975, and >> PROTON-899. >> >> The release archive and sig/checksums can be grabbed from: >> https://dist.apache.org/repos/dist/dev/qpid/proton/0.10-rc3/ >> >> Maven artifacts for the Java bits can be found in a temporary staging >> repo at: >> https://repository.apache.org/content/repositories/orgapacheqpid-1042 >> >> It is tagged as 0.10-rc3. You may need to fetch the tags explicitly >> to >> see it, e.g: "git fetch --tags" >> >> Regards, >> Robbie > > - > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org >
