On Mon, 21 Oct 2024 at 20:08, Justin Bertram <jbert...@apache.org> wrote:
>
> I would like to propose an Apache ActiveMQ Artemis 2.38.0 release.
>
> Highlights include:
>
> - WebSocket compression is now supported. This compression can be used
> transparently for AMQP, STOMP, or MQTT when communication is over
> WebSockets.
> - The ActiveMQServerMessagePlugin now has a messageMoved() callback.
> - Core bridge configuration now supports client-id which will make it much
> easier to identify bridge connections on remote brokers.
> - The consumer CLI command now supports consuming messages "forever."
> - The authentication & authorization caches now have detailed debug logging.
> - There’s been a handful of updates to broker management including:
>     - The documentation has been improved with more examples for Jolokia
> and a new sub-section on management method option syntax.
>     - It’s now possible to pass empty "options" to the management methods
> that accept them.
>     - The management methods which return paged results can now return all
> the results together by specifying -1 for either the page or the pageSize.
>     - The management method option syntax now supports the NOT_EQUALS
> operator for greater flexibility with filtering results of management
> operations.
>     - Configuration for diverts created via management can now be done via
> JSON.
>
> The release notes can be found here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315920&version=12355013
>
> Ths git commit report is here:
> https://activemq.apache.org/components/artemis/download/commit-report-2.38.0
>
> Source and binary distributions can be found here:
> https://dist.apache.org/repos/dist/dev/activemq/activemq-artemis/2.38.0/
>
> The Maven staging repository is here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1412
>
> If you would like to validate the release:
> https://activemq.apache.org/components/artemis/documentation/hacking-guide/#validating-releases
>
> It is tagged in the git repo as <version>
>
> [ ] +1 approve this release
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> This is a re-spin of a previously proposed release. To be clear, no source
> code has changed in this re-spin. The only changes are to the binaries and
> the signatures. The source archive is exactly the same as it was before.
> The change was necessary to fix a build-repeatability issue related to file
> permissions in the binaries.
>
> Here's my +1
>
>
> Justin

+1

I checked things over as follows:
- Verified the signature + checksum files.
- Diffed the source archives + checksums with the previous candidate
  to verify they had not changed at all.
- Diffed the binary archives with the previous candidate to verify only
  the console war files had changed (but only the pom details permissions).
- Gave the broker a start and loaded the web console.
- Ran the Qpid JMS 2.6.1 HelloWorld against a broker from the binary
archive on JDK 17.
- Verified the build reproducibility using the tooling at Reproducible
Central, which passed.

Robbie

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@activemq.apache.org
For additional commands, e-mail: dev-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact


Reply via email to