+1 I checked things out as follows: - Verified the signature + checksum files. - Checked for LICENCE + NOTICE files in the archives. - Checked licence headers in the source archive by running: "mvn apache-rat:check" - 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. - Ran the source build and the AMQP integration tests on JDK 17 with a fresh local repo using: "mvn clean install -DskipTests && cd tests/integration-tests/ && mvn -Ptests -Dtest=org.apache.activemq.artemis.tests.integration.amqp.** test"
Robbie On Mon, 16 Dec 2024 at 16:23, Justin Bertram <jbert...@apache.org> wrote: > > Correction...The link to the Maven staging repository is: > > https://repository.apache.org/content/repositories/orgapacheactivemq-1415 > > > Justin > > On Mon, Dec 16, 2024 at 10:19 AM Justin Bertram <jbert...@apache.org> wrote: > > > I would like to propose an Apache ActiveMQ Artemis 2.39.0 release. > > > > Highlights include: > > > > - Java 17 is now required. support for Java 11 has been dropped. > > The main reason for this change is that the version of Jetty we were > > embedding in previous versions (i.e. 10) will officially reach its > > end-of-life on January 1, 2025 [1] and will therefore no longer be > > receiving any fixes - including security fixes. Security is critical for us > > and most of our users so we therefore need to upgrade to Jetty 12 - the > > only version of Jetty now supported. Jetty 12 requires Java 17 so we must > > also move to Java 17 and drop support for Java 11. > > Please note that after upgrading the broker to Java 17 it will be > > backwards compatible with all previous clients. > > - AMQP federation and broker connections have new management controls. > > - The Core client (including the Core JMS client) supports a configurable > > timeout for onMessage invocations when closing/stopping a connection. > > - Datasource configuration is now available when configuring the broker > > via properties. > > - Failure conditions for CLI commands (e.g. artemis check) now > > specifically return an exit code of 1 which means they can be more reliably > > incorporated into other scripts, etc. > > - The binary distribution is almost 8MB smaller than 2.38.0 due to > > reduced dependencies. > > - Lots of fixes for various flaky tests. This reduces spurious test > > failures improving the experience for developers building the broker and > > running the test-suite. > > > > * Full release notes: > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315920&version=12355167 > > > > * Commit report: > > > > https://activemq.apache.org/components/artemis/download/commit-report-2.39.0 > > > > * Source and binary distributions: > > https://dist.apache.org/repos/dist/dev/activemq/activemq-artemis/2.39.0/ > > > > * Maven staging repository: > > https://repository.apache.org/content/repositories/orgapacheactivemq-1414 > > > > * How to validate the release: > > > > https://activemq.apache.org/components/artemis/documentation/hacking-guide/#validating-releases > > > > It is tagged in the source repo as <version> > > > > [ ] +1 approve this release > > [ ] +0 no opinion > > [ ] -1 disapprove (and reason why) > > > > Here's my +1 > > > > > > Justin > > > > [1] https://github.com/jetty/jetty.project/issues/10485 > > --------------------------------------------------------------------- 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
