On 04/13/2018 03:03 PM, Robbie Gemmell wrote:
Hi folks,
I have put together a spin for a Qpid Proton-J 0.27.0 release, please
test it and vote accordingly.
The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.27.0-rc1/
The maven artifacts
I would prefer to keep the feature enforced as it is now. I was one who
was surprised to have a sender whose message is settled by the router
only to find out that it was not delivered anywhere.
The document
https://qpid.apache.org/releases/qpid-dispatch-1.0.0/book/book.html#routing-patterns
+1
I checked things out as follows:
- Verified the signature and checksum files.
- Checked the LICENCE and NOTICE files in the archives.
- Used mvn apache-rat:check to verify licence headers in the source archive.
- Ran the source build and tests.
- Used the staging repo with the Qpid JMS client
I don't have an issue with this, I didn't originally like the default
being to reject unsettled deliveries when the ability was added,
particularly given the congestion handling for pre-settled, but also
due to the likely need for clients to jump hoops to use the
multicasting vs not.
The
Hi folks,
I have put together a spin for a Qpid Proton-J 0.27.0 release, please
test it and vote accordingly.
The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.27.0-rc1/
The maven artifacts are staged for now at:
