英文:
Apache ActiveMQ "Classic" support life cycle
问题
我在寻找有关Apache ActiveMQ "Classic"官方支持生命周期的帮助。
ActiveMQ网站中提到：
一旦Artemis与"Classic"代码库达到足够的功能对等水平，它将成为ActiveMQ的下一个主要版本。
但如何将这个陈述翻译成支持时间表呢？例如，Apache将在未来5年内为ActiveMQ "Classic"提供什么样的支持？是否有ActiveMQ "Classic"的长期支持（LTS）版本？
更新：查看ActiveMQ下载页面，似乎确实存在某种发布策略。该页面显示了两个活跃（我推测目前受支持的）版本：5.17和5.18。较旧的版本（例如5.16）标记为"older release"。此外，5.17的次要版本是在5.18首次发布之后发布的，也就是说，5.17仍然在接收补丁，而较旧的版本（例如5.16）不再接收补丁。这表明Apache AMQ团队内部肯定有关于支持时间表的声明。否则，就不会为5.17发布补丁。
关于这个主题的官方文档/声明的参考将非常有帮助。
英文:
I'm looking for a help with identifying an official support life cycle for Apache ActiveMQ "Classic."
The ActiveMQ web site states:
> Once Artemis reaches a sufficient level of feature parity with the "Classic" code-base it will become the next major version of ActiveMQ.
But how to translate this statement to a support time-frame? For example, what kind of support will Apache provide for the ActiveMQ "Classic" in the next 5 years? Are there LTS versions of ActiveMQ "Classic"?
Update: Looking at the ActiveMQ download page, it seems like some sort of release strategy is definitely in place. The page shows two active (and I presume currently supported) versions: 5.17 and 5.18. The older versions (e.g. 5.16) are marked as "older release". As well, the minor versions of the 5.17 were released after the 5.18 first release, i.e. 5.17 is still getting patches while the older releases (e.g. 5.16 are not patched anymore). This indicates that there is a support timeframe stated somewhere inside the Apache AMQ team. Otherwise, the patches wouldn't be released for 5.17.
A reference to an official document/statement from Apache in regards to this subject would be very helpful.
答案1
得分: 1
最终，“Apache的官方文件/声明”与其提供的每个软件一起发布，即Apache许可证，可以部分概括为：
> 除非适用法律要求或书面同意，根据许可证分发的软件基于“按原样”分发，不提供任何明示或暗示的担保或条件。
此外，ActiveMQ网站上有关支持的具体详细信息。简而言之，如果您需要超出免费志愿者社区支持范围的支持，我建议您考虑商业支持选项。
作为一名提交者和ActiveMQ项目管理委员会的成员，我的个人评估是，由于它已经是事实上的标准JMS服务器实现超过十年，ActiveMQ“经典”部署有一个庞大的基础。许多人已经迁移到ActiveMQ Artemis，但也有许多人愿意永远留在ActiveMQ“经典”上。社区继续发布带有错误修复和内部组件升级的版本（例如，以解决CVE），我想，只要有需求，这种情况将在可预见的将来继续下去。
英文:
Ultimately the "official document/statement from Apache" is shipped with every piece of software that it provides, i.e. the Apache License which can be summarized, in part, as stating:
> Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
Also, the ActiveMQ website has specific details about support. In short, if you need something beyond the community support which is provided for free on a volunteer basis then I recommend you look at a commercial support option.
My individual assessment as a committer and a member of the ActiveMQ Project Management Committee is that there is a large base of ActiveMQ "Classic" deployments given it has been the de facto standard JMS server implementation for well over a decade. Many of these folks have migrated to ActiveMQ Artemis, but many are also perfectly content to stay on ActiveMQ "Classic" forever. The community has continued to produce releases with bug fixes and internal component upgrades (e.g. to address CVEs), and I imagine that will continue for the foreseeable future assuming there is demand.
答案2
得分: 0
ActiveMQ 5.x发布计划正在进行中。将整理JDK LTS、Jakarta和ActiveMQ的发布对齐。正如Justin所提到的，Apache是一个志愿组织，所以这是尽最大努力，但有着如此长久的历史和广泛的用户群体，可以合理地期望用户会继续使用它相当长的时间。
对于稳定的发布对齐计划，请关注：
https://activemq.apache.org/components/classic/download/
https://activemq.apache.org/jms2
要获取商业支持，请查看：
https://activemq.apache.org/support
英文:
The ActiveMQ 5.x release planning is underway. The JDK LTS, Jakarta, and ActiveMQ release alignment will be sorted out. As Justin mentioned, Apache is a volunteer organization, so its all best effort, but with such a long running history and wide user base, it is reasonable to expect users to continue on it for quite some time.
For stable release alignment plans, keep an eye on:
https://activemq.apache.org/components/classic/download/
https://activemq.apache.org/jms2
For commercial support check out:
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论