+1 (binding)

* Validated signatures and checksums
* Verified license and notice files in archives
* Checked source license headers with 'mvn apache-rat:check'
* Built from source and ran through several tests
* Ran the broker from the binary archive and exercised the web console

On Fri, Feb 13, 2026 at 12:17 PM Francois Papon <
[email protected]> wrote:

> +1 (non-binding)
>
> Thanks for the release!
>
> François
> [email protected]
> [email protected]
>
> Le 12/02/2026 à 18:11, Jean-Baptiste Onofré a écrit :
> > Hi folks,
> >
> > Here's the vote for the Apache ActiveMQ 6.2.1 release.
> >
> > This is a maintenance release on the 6.2.x series.
> > It includes 9 fixes and several dependencies updates, especially:
> > - running Docker container with non root user
> > - fix on environment variables propagation in the Docker container
> > - additional validation on MQTT control packets
> > - fix incorrect QueueSize if Non-Persistent messages with TTL is used
> > - fix KahaDBStore ackAndPreparedMap is not properly cleared when
> recovered
> > acks are removed
> > - fix ManagementContext unregister race condition
> >
> > You can take a look on the Release Notes for details:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12356338
> >
> > Staging Maven Repository:
> >
> https://repository.apache.org/content/repositories/orgapacheactivemq-1471/
> >
> > Staging Dist Repository:
> > https://dist.apache.org/repos/dist/dev/activemq/activemq/6.2.1/
> >
> > Git tag:
> > activemq-6.2.1
> >
> > Please vote to approve this release:
> > [ ] +1 Approve the release
> > [ ] 0 I don't care
> > [ ] -1 Don't approve the release (please provide specific comment)
> >
> > This vote will be open for at least 72 hours.
> >
> > Thanks!
> > Regards
> > JB
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> For further information, visit: https://activemq.apache.org/contact
>
>
>

Reply via email to