You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by Matt Pavlovich <ma...@apache.org> on 2026/07/29 13:28:55 UTC
[Discuss] Release branch support planning (was End of Life timeline for 5.x)
On the heels of the v6.3.0 release, it is now a good time to revisit community supported release stream branch planning.
The previous thread focused on end-of-life for 5.19.x, but I think it also makes sense to talk about 6.2.x and perhaps even a general strategy on community supported releases.
I think until we are free of Spring as the primary bootstrap for the broker, we should consider aligning the support branches by Spring version support timeline (which naturally brings a JDK version alignment). Jetty doesn’t publish a community support timeline, but is less slightly less critical as many run a broker without the UI or http/ws transports.
A couple of other points to consider (these also tend to be in natural conflict with one another):
0. ActiveMQ is a volunteer project
1. ActiveMQ is infrastructure system, and users are sometimes tied to old JDKs and APIs for a long time (outside their control)
2. Spring 5.x and 6.x fix releases no longer released as open source
3. Jetty 9.x and 11.x fix releases no longer released as open source
A few discussion notes:
a. In other threads there had been mention about doing a bit longer support on 5.19.x instead of providing an activemq-client-javax client in the 6.3.x series
b. ActiveMQ 6.2.x had a disjointed EE alignment, so directing folks to 6.3.x should be an improvement all around
Thanks,
Matt
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@activemq.apache.org
For additional commands, e-mail: dev-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
Re: [Discuss] Release branch support planning (was End of Life timeline for 5.x)
Posted by Matt Pavlovich <ma...@apache.org>.
Hi Benjamin-
Please open a an issue on Github to report any issues with the 6.3.0 release.
A bug or issue in 6.3.0 is readily fixable. The challenge with continuing active releases and development on 6.2.x (and older) are that the other dependencies are inactive and have open security vulnerabilities that require an extended support contract to get the fixed releases.
Matt
> On Jul 30, 2026, at 1:01 PM, Benjamin Graf <be...@gmx.net> wrote:
>
> Hi all,
>
> 6.3.0 has been released just a few days ago. Therefor IMHO it is quite a bit early to set 6.2.x out of maintenance. I would suggest to keep it active until 6.3.x will be as mature as 6.2.x is today. As far as I know there is at least one major incident in 6.3.0 (https://github.com/apache/activemq/issues/1717) and by the way a broker that does start by default with WARN logging messages is not very nice!
>
> 2026-07-30 19:59:11,693 | WARN | BaseResource file:///c:/xxx/apache-activemq-6.3.0/bin/../webapps/admin/ <file:///c:/xxx/apache-activemq-6.3.0/webapps/admin/> is aliased to file:///C:/xxx/apache-activemq-6.3.0/webapps/admin/ in oeje11w.WebAppContext@49c17ba4{/admin,/admin,b=file:///c:/xxx/apache-activemq-6.3.0/bin/../webapps/admin/,a=STOPPED,h=oeje11s.SessionHandler@43e065f2 <fi...@43e065f2>{STOPPED}}. May not be supported in future releases. | org.eclipse.jetty.ee11.servlet.ServletContextHandler | main
> 2026-07-30 19:59:12,686 | WARN | The XML schema [XMLSchema.dtd] could not be found. This is very likely to break XML validation if XML validation is enabled. | org.apache.tomcat.util.descriptor.DigesterFactory | main
> 2026-07-30 19:59:12,686 | WARN | The XML schema [datatypes.dtd] could not be found. This is very likely to break XML validation if XML validation is enabled. | org.apache.tomcat.util.descriptor.DigesterFactory | main
> 2026-07-30 19:59:12,688 | WARN | The XML schema [xml.xsd] could not be found. This is very likely to break XML validation if XML validation is enabled. | org.apache.tomcat.util.descriptor.DigesterFactory | main
> 2026-07-30 19:59:13,003 | WARN | BaseResource file:///c:/xxx/apache-activemq-6.3.0/bin/../webapps/api/ <file:///c:/xxx/apache-activemq-6.3.0/webapps/api/> is aliased to file:///C:/xxx/apache-activemq-6.3.0/webapps/api/ in oeje11w.WebAppContext@66e17eff{/api,/api,b=file:///c:/xxx/apache-activemq-6.3.0/bin/../webapps/api/,a=STOPPED,h=oeje11s.SessionHandler@4bb1b96b <fi...@4bb1b96b>{STOPPED}}. May not be supported in future releases. | org.eclipse.jetty.ee11.servlet.ServletContextHandler | main
> 2026-07-30 19:59:13,548 | WARN | Base Resource should not be an alias | org.eclipse.jetty.server.handler.ResourceHandler | main
> Regards,
>
> Benjamin
>
> On 30.07.2026 07:20, Jean-Baptiste Onofré wrote:
>> Hi Matt,
>>
>> As previously discussed, End of Life (EOL) doesn't strictly apply to
>> Apache projects, as we can always cut a release on any branch if the
>> community requires it.
>>
>> That being said, I believe we agreed to only maintain the latest 6.x
>> series. Moving forward, we should focus our efforts on 6.3.x and stop
>> focusing on 6.2.x. The same should eventually apply to 5.19.x.
>>
>> While I fully agree with encouraging users to upgrade to 6.3.x (point
>> b), I don't see the need to maintain focus on 5.19.x, even for the
>> javax client. The latest changes in the 5.19.x series were primarily
>> on the broker side, not the client. Since all previous releases in the
>> 6.2.x and 5.19.x series will remain available, users can migrate at
>> their own pace.
>>
>> Therefore, I propose that we mark 6.2.x as "not active" on the website
>> and focus solely on 6.3.x. I suggest we take the same approach for
>> 5.19.x in the near future.
>>
>> Regards,
>> JB
>>
>> On Wed, Jul 29, 2026 at 3:29 PM Matt Pavlovich <ma...@apache.org> <ma...@apache.org> wrote:
>>> On the heels of the v6.3.0 release, it is now a good time to revisit community supported release stream branch planning.
>>>
>>> The previous thread focused on end-of-life for 5.19.x, but I think it also makes sense to talk about 6.2.x and perhaps even a general strategy on community supported releases.
>>>
>>> I think until we are free of Spring as the primary bootstrap for the broker, we should consider aligning the support branches by Spring version support timeline (which naturally brings a JDK version alignment). Jetty doesn’t publish a community support timeline, but is less slightly less critical as many run a broker without the UI or http/ws transports.
>>>
>>> A couple of other points to consider (these also tend to be in natural conflict with one another):
>>>
>>> 0. ActiveMQ is a volunteer project
>>> 1. ActiveMQ is infrastructure system, and users are sometimes tied to old JDKs and APIs for a long time (outside their control)
>>> 2. Spring 5.x and 6.x fix releases no longer released as open source
>>> 3. Jetty 9.x and 11.x fix releases no longer released as open source
>>>
>>> A few discussion notes:
>>>
>>> a. In other threads there had been mention about doing a bit longer support on 5.19.x instead of providing an activemq-client-javax client in the 6.3.x series
>>> b. ActiveMQ 6.2.x had a disjointed EE alignment, so directing folks to 6.3.x should be an improvement all around
>>>
>>> Thanks,
>>> Matt
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@activemq.apache.org <ma...@activemq.apache.org>
>>> For additional commands, e-mail: dev-help@activemq.apache.org <ma...@activemq.apache.org>
>>> For further information, visit: https://activemq.apache.org/contact
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@activemq.apache.org <ma...@activemq.apache.org>
>> For additional commands, e-mail: dev-help@activemq.apache.org <ma...@activemq.apache.org>
>> For further information, visit: https://activemq.apache.org/contact
>>
>>
Re: [Discuss] Release branch support planning (was End of Life timeline for 5.x)
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi
Again, the purpose is not EoL or end of maintance: it's never actually happen.
It's just the effort we put on 6.2.x. Updating the dependency and
fixes can still happen on 6.2.x, but all new features will happen on
main and backported to 6.3.x.
The purpose is also to accelerate on 6.4.0, 6.5.0, etc.
Regards
JB
On Thu, Jul 30, 2026 at 8:01 PM Benjamin Graf <be...@gmx.net> wrote:
>
> Hi all,
>
> 6.3.0 has been released just a few days ago. Therefor IMHO it is quite a bit early to set 6.2.x out of maintenance. I would suggest to keep it active until 6.3.x will be as mature as 6.2.x is today. As far as I know there is at least one major incident in 6.3.0 (https://github.com/apache/activemq/issues/1717) and by the way a broker that does start by default with WARN logging messages is not very nice!
>
> 2026-07-30 19:59:11,693 | WARN | BaseResource file:///c:/xxx/apache-activemq-6.3.0/bin/../webapps/admin/ is aliased to file:///C:/xxx/apache-activemq-6.3.0/webapps/admin/ in oeje11w.WebAppContext@49c17ba4{/admin,/admin,b=file:///c:/xxx/apache-activemq-6.3.0/bin/../webapps/admin/,a=STOPPED,h=oeje11s.SessionHandler@43e065f2{STOPPED}}. May not be supported in future releases. | org.eclipse.jetty.ee11.servlet.ServletContextHandler | main
> 2026-07-30 19:59:12,686 | WARN | The XML schema [XMLSchema.dtd] could not be found. This is very likely to break XML validation if XML validation is enabled. | org.apache.tomcat.util.descriptor.DigesterFactory | main
> 2026-07-30 19:59:12,686 | WARN | The XML schema [datatypes.dtd] could not be found. This is very likely to break XML validation if XML validation is enabled. | org.apache.tomcat.util.descriptor.DigesterFactory | main
> 2026-07-30 19:59:12,688 | WARN | The XML schema [xml.xsd] could not be found. This is very likely to break XML validation if XML validation is enabled. | org.apache.tomcat.util.descriptor.DigesterFactory | main
> 2026-07-30 19:59:13,003 | WARN | BaseResource file:///c:/xxx/apache-activemq-6.3.0/bin/../webapps/api/ is aliased to file:///C:/xxx/apache-activemq-6.3.0/webapps/api/ in oeje11w.WebAppContext@66e17eff{/api,/api,b=file:///c:/xxx/apache-activemq-6.3.0/bin/../webapps/api/,a=STOPPED,h=oeje11s.SessionHandler@4bb1b96b{STOPPED}}. May not be supported in future releases. | org.eclipse.jetty.ee11.servlet.ServletContextHandler | main
> 2026-07-30 19:59:13,548 | WARN | Base Resource should not be an alias | org.eclipse.jetty.server.handler.ResourceHandler | main
>
> Regards,
>
> Benjamin
>
> On 30.07.2026 07:20, Jean-Baptiste Onofré wrote:
>
> Hi Matt,
>
> As previously discussed, End of Life (EOL) doesn't strictly apply to
> Apache projects, as we can always cut a release on any branch if the
> community requires it.
>
> That being said, I believe we agreed to only maintain the latest 6.x
> series. Moving forward, we should focus our efforts on 6.3.x and stop
> focusing on 6.2.x. The same should eventually apply to 5.19.x.
>
> While I fully agree with encouraging users to upgrade to 6.3.x (point
> b), I don't see the need to maintain focus on 5.19.x, even for the
> javax client. The latest changes in the 5.19.x series were primarily
> on the broker side, not the client. Since all previous releases in the
> 6.2.x and 5.19.x series will remain available, users can migrate at
> their own pace.
>
> Therefore, I propose that we mark 6.2.x as "not active" on the website
> and focus solely on 6.3.x. I suggest we take the same approach for
> 5.19.x in the near future.
>
> Regards,
> JB
>
> On Wed, Jul 29, 2026 at 3:29 PM Matt Pavlovich <ma...@apache.org> wrote:
>
> On the heels of the v6.3.0 release, it is now a good time to revisit community supported release stream branch planning.
>
> The previous thread focused on end-of-life for 5.19.x, but I think it also makes sense to talk about 6.2.x and perhaps even a general strategy on community supported releases.
>
> I think until we are free of Spring as the primary bootstrap for the broker, we should consider aligning the support branches by Spring version support timeline (which naturally brings a JDK version alignment). Jetty doesn’t publish a community support timeline, but is less slightly less critical as many run a broker without the UI or http/ws transports.
>
> A couple of other points to consider (these also tend to be in natural conflict with one another):
>
> 0. ActiveMQ is a volunteer project
> 1. ActiveMQ is infrastructure system, and users are sometimes tied to old JDKs and APIs for a long time (outside their control)
> 2. Spring 5.x and 6.x fix releases no longer released as open source
> 3. Jetty 9.x and 11.x fix releases no longer released as open source
>
> A few discussion notes:
>
> a. In other threads there had been mention about doing a bit longer support on 5.19.x instead of providing an activemq-client-javax client in the 6.3.x series
> b. ActiveMQ 6.2.x had a disjointed EE alignment, so directing folks to 6.3.x should be an improvement all around
>
> Thanks,
> Matt
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@activemq.apache.org
> For additional commands, e-mail: dev-help@activemq.apache.org
> For further information, visit: https://activemq.apache.org/contact
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@activemq.apache.org
> For additional commands, e-mail: dev-help@activemq.apache.org
> For further information, visit: https://activemq.apache.org/contact
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@activemq.apache.org
For additional commands, e-mail: dev-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
Re: [Discuss] Release branch support planning (was End of Life timeline for 5.x)
Posted by Benjamin Graf <be...@gmx.net>.
Hi all,
6.3.0 has been released just a few days ago. Therefor IMHO it is quite a bit
early to set 6.2.x out of maintenance. I would suggest to keep it active until
6.3.x will be as mature as 6.2.x is today. As far as I know there is at least
one major incident in 6.3.0 (https://github.com/apache/activemq/issues/1717) and
by the way a broker that does start by default with WARN logging messages is not
very nice!
2026-07-30 19:59:11,693 | WARN | BaseResource
file:///c:/xxx/apache-activemq-6.3.0/bin/../webapps/admin/ is aliased to
file:///C:/xxx/apache-activemq-6.3.0/webapps/admin/ in
oeje11w.WebAppContext@49c17ba4{/admin,/admin,b=file:///c:/xxx/apache-activemq-6.3.0/bin/../webapps/admin/,a=STOPPED,h=oeje11s.SessionHandler@43e065f2{STOPPED}}.
May not be supported in future releases. |
org.eclipse.jetty.ee11.servlet.ServletContextHandler | main 2026-07-30
19:59:12,686 | WARN | The XML schema [XMLSchema.dtd] could not be found. This
is very likely to break XML validation if XML validation is enabled. |
org.apache.tomcat.util.descriptor.DigesterFactory | main 2026-07-30 19:59:12,686
| WARN | The XML schema [datatypes.dtd] could not be found. This is very likely
to break XML validation if XML validation is enabled. |
org.apache.tomcat.util.descriptor.DigesterFactory | main 2026-07-30 19:59:12,688
| WARN | The XML schema [xml.xsd] could not be found. This is very likely to
break XML validation if XML validation is enabled. |
org.apache.tomcat.util.descriptor.DigesterFactory | main 2026-07-30 19:59:13,003
| WARN | BaseResource file:///c:/xxx/apache-activemq-6.3.0/bin/../webapps/api/
is aliased to file:///C:/xxx/apache-activemq-6.3.0/webapps/api/ in
oeje11w.WebAppContext@66e17eff{/api,/api,b=file:///c:/xxx/apache-activemq-6.3.0/bin/../webapps/api/,a=STOPPED,h=oeje11s.SessionHandler@4bb1b96b{STOPPED}}.
May not be supported in future releases. |
org.eclipse.jetty.ee11.servlet.ServletContextHandler | main 2026-07-30
19:59:13,548 | WARN | Base Resource should not be an alias |
org.eclipse.jetty.server.handler.ResourceHandler | main
Regards,
Benjamin
On 30.07.2026 07:20, Jean-Baptiste Onofré wrote:
> Hi Matt,
>
> As previously discussed, End of Life (EOL) doesn't strictly apply to
> Apache projects, as we can always cut a release on any branch if the
> community requires it.
>
> That being said, I believe we agreed to only maintain the latest 6.x
> series. Moving forward, we should focus our efforts on 6.3.x and stop
> focusing on 6.2.x. The same should eventually apply to 5.19.x.
>
> While I fully agree with encouraging users to upgrade to 6.3.x (point
> b), I don't see the need to maintain focus on 5.19.x, even for the
> javax client. The latest changes in the 5.19.x series were primarily
> on the broker side, not the client. Since all previous releases in the
> 6.2.x and 5.19.x series will remain available, users can migrate at
> their own pace.
>
> Therefore, I propose that we mark 6.2.x as "not active" on the website
> and focus solely on 6.3.x. I suggest we take the same approach for
> 5.19.x in the near future.
>
> Regards,
> JB
>
> On Wed, Jul 29, 2026 at 3:29 PM Matt Pavlovich<ma...@apache.org> wrote:
>> On the heels of the v6.3.0 release, it is now a good time to revisit community supported release stream branch planning.
>>
>> The previous thread focused on end-of-life for 5.19.x, but I think it also makes sense to talk about 6.2.x and perhaps even a general strategy on community supported releases.
>>
>> I think until we are free of Spring as the primary bootstrap for the broker, we should consider aligning the support branches by Spring version support timeline (which naturally brings a JDK version alignment). Jetty doesn’t publish a community support timeline, but is less slightly less critical as many run a broker without the UI or http/ws transports.
>>
>> A couple of other points to consider (these also tend to be in natural conflict with one another):
>>
>> 0. ActiveMQ is a volunteer project
>> 1. ActiveMQ is infrastructure system, and users are sometimes tied to old JDKs and APIs for a long time (outside their control)
>> 2. Spring 5.x and 6.x fix releases no longer released as open source
>> 3. Jetty 9.x and 11.x fix releases no longer released as open source
>>
>> A few discussion notes:
>>
>> a. In other threads there had been mention about doing a bit longer support on 5.19.x instead of providing an activemq-client-javax client in the 6.3.x series
>> b. ActiveMQ 6.2.x had a disjointed EE alignment, so directing folks to 6.3.x should be an improvement all around
>>
>> Thanks,
>> Matt
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:dev-unsubscribe@activemq.apache.org
>> For additional commands, e-mail:dev-help@activemq.apache.org
>> For further information, visit:https://activemq.apache.org/contact
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:dev-unsubscribe@activemq.apache.org
> For additional commands, e-mail:dev-help@activemq.apache.org
> For further information, visit:https://activemq.apache.org/contact
>
>
Re: [Discuss] Release branch support planning (was End of Life timeline for 5.x)
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Matt,
As previously discussed, End of Life (EOL) doesn't strictly apply to
Apache projects, as we can always cut a release on any branch if the
community requires it.
That being said, I believe we agreed to only maintain the latest 6.x
series. Moving forward, we should focus our efforts on 6.3.x and stop
focusing on 6.2.x. The same should eventually apply to 5.19.x.
While I fully agree with encouraging users to upgrade to 6.3.x (point
b), I don't see the need to maintain focus on 5.19.x, even for the
javax client. The latest changes in the 5.19.x series were primarily
on the broker side, not the client. Since all previous releases in the
6.2.x and 5.19.x series will remain available, users can migrate at
their own pace.
Therefore, I propose that we mark 6.2.x as "not active" on the website
and focus solely on 6.3.x. I suggest we take the same approach for
5.19.x in the near future.
Regards,
JB
On Wed, Jul 29, 2026 at 3:29 PM Matt Pavlovich <ma...@apache.org> wrote:
>
> On the heels of the v6.3.0 release, it is now a good time to revisit community supported release stream branch planning.
>
> The previous thread focused on end-of-life for 5.19.x, but I think it also makes sense to talk about 6.2.x and perhaps even a general strategy on community supported releases.
>
> I think until we are free of Spring as the primary bootstrap for the broker, we should consider aligning the support branches by Spring version support timeline (which naturally brings a JDK version alignment). Jetty doesn’t publish a community support timeline, but is less slightly less critical as many run a broker without the UI or http/ws transports.
>
> A couple of other points to consider (these also tend to be in natural conflict with one another):
>
> 0. ActiveMQ is a volunteer project
> 1. ActiveMQ is infrastructure system, and users are sometimes tied to old JDKs and APIs for a long time (outside their control)
> 2. Spring 5.x and 6.x fix releases no longer released as open source
> 3. Jetty 9.x and 11.x fix releases no longer released as open source
>
> A few discussion notes:
>
> a. In other threads there had been mention about doing a bit longer support on 5.19.x instead of providing an activemq-client-javax client in the 6.3.x series
> b. ActiveMQ 6.2.x had a disjointed EE alignment, so directing folks to 6.3.x should be an improvement all around
>
> Thanks,
> Matt
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@activemq.apache.org
> For additional commands, e-mail: dev-help@activemq.apache.org
> For further information, visit: https://activemq.apache.org/contact
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@activemq.apache.org
For additional commands, e-mail: dev-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact