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: [email protected] For additional commands, e-mail: [email protected] For further information, visit: https://activemq.apache.org/contact
