+1
I checked things over as follows:
- Verified the signature and checksum files.
- Checked LICENCE+NOTICE files present in archive.
- Ran mvn apache-rat:check to verify the licence headers.
- Built the router against an install of Proton 0.23.0 and ran all the tests.
- Ran the JMS client
Hi folks,
I have put together a spin for a 0.33.0 Qpid JMS client release,
please give it a test out and vote accordingly.
The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.33.0-rc1/
The maven artifacts are also staged for now at:
+1
I ran my new latency tests (meant to simulate a real customer usage
pattern) on this release as well as the previous release (and corresponding
versions of proton.) No problems with the new release. I may be seeing a
latency slow-down of a few percent, but that is not alarming & seems likely
On 11 June 2018 at 18:32, Robbie Gemmell wrote:
> Hi folks,
>
> I have put together a spin for a 0.33.0 Qpid JMS client release,
> please give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/0.33.0-rc1/
There were 6 binding +1 votes, 2 non-binding +1 votes and no other
votes received. The vote has passed.
I will add the files to the dist release repo and create the final tag
shortly. The website will be updated after the release has had time to
sync to the mirrors.
Thanks to everybody for
On 06/11/2018 01:32 PM, Robbie Gemmell wrote:
Hi folks,
I have put together a spin for a 0.33.0 Qpid JMS client release,
please give it a test out and vote accordingly.
The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.33.0-rc1/
The maven
+1
* checked checksums and signatures of the source and bin distribution,
* ran apache rat-check
* built from source distribution artefact and ran all tests (mvn
verify with Java 1.8.0_171 on Mac OS X 10.11.6)
* ran Broker-J's JMS integration test suite (mvn clean verify
-DskipTests=true
Hi Alex,
Thanks a lot for all these details.
I'll give this a try. Also, your examples look very useful for I've been
using qpid-broker instead of qpid-broker-core to embed the broker.
I've created my sample code a while ago and when trying to migrate to 7.0 I
had troubles getting some
HI,
If I compile QPID (using Proton) on Windows 10 in RELEASE mode, the
application trying to use the QPID client gets aborted by windows when it
tries to create a QPID connection. The abort is called on the last line of
the following piece of code i.e. on the QPID connection creation:
+1
Ran oslo.messaging functional tests and the smoke test.
Looks like the leak was fixed! Good job!
On Thu, Jun 7, 2018 at 5:01 PM, Ganesh Murthy wrote:
> Hello All,
>
> Please cast your vote on this thread to release RC6 as the
> official Qpid Dispatch Router version 1.1.0.
>
>
+1 ... build from source on CentOS7 and used with different AMQP 1.0
clients.
On Thu, Jun 7, 2018 at 11:02 PM Ganesh Murthy wrote:
> Hello All,
>
> Please cast your vote on this thread to release RC6 as the
> official Qpid Dispatch Router version 1.1.0.
>
> RC6 of Qpid Dispatch Router
+1
* Validated signatures and checksums
* Checked for presence of LICENSE and NOTICE files
* Checked README file
* Ran mvn apache-rat:check, no files with missing license headers found.
* Tried to build against Proton 0.22.0 and made sure that the code wont
compile. This version of Dispatch
12 matches
Mail list logo
