Results of the Apache ActiveMQ 5.15.2 vote:
Vote passes with 3 +1 binding votes.
The following votes were received:
Binding:
+1 Timothy Bish
+1 Christopher Shannon
+1 Gary Tully
Non-Binding
+1 Jean-Baptiste Onofré
+1 Robbie Gemmell
+1 Bruce D
I'll start pushing out the release bundles and
+1 (non-binding)
Upgraded from 5.15.1 to 5.15.2 in our staging environment; no issues, but
then again 5.15.1 was also working fine for us. Using the auto transport.
Clients tested were an ActiveMQ 5.14.1 Java client and a C# client using
NMS ActiveMQ 1.7.2. The NMS client sometimes takes up to 30
+1 (binding)
Regards
JB
On Oct 18, 2017, 12:56, at 12:56, Robbie Gemmell
wrote:
>On 17 October 2017 at 15:37, Christopher Shannon
> wrote:
>> Hi Everyone,
>>
>> I have created the ActiveMQ 5.15.2 release and it's ready for a vote.
>>
On 17 October 2017 at 15:37, Christopher Shannon
wrote:
> Hi Everyone,
>
> I have created the ActiveMQ 5.15.2 release and it's ready for a vote.
>
> The list of resolved issues is here:
>
+1
On Tue, 17 Oct 2017 at 21:49 Timothy Bish wrote:
> +1
>
> * Checked each archive to License and Notice files
> * Validated signatures and checksums
> * Ran the binary broker build on linux, checked web console and sent
> some messages using Qpid JMS example
> * Built
+1
* Checked each archive to License and Notice files
* Validated signatures and checksums
* Ran the binary broker build on linux, checked web console and sent
some messages using Qpid JMS example
* Built from source and ran the sanity test profile tests
* Built Qpid JMS using the staged bits
Hi Everyone,
I have created the ActiveMQ 5.15.2 release and it's ready for a vote.
The list of resolved issues is here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12341669
You can get the release artifacts here: