We’re planning to introduce a new versioning system for Discourse. Our goal is to provide more choice & predictability for community administrators, while maintaining our development velocity. We’re also adjusting some terminology to align better with other software. This document will evolve as we…

It does not really matter if it is a library or larger application. A semantic versioning scheme (like semver) works perfectly well for large application. It can even be used for a collection of applications bundled into a platform, but here it becomes quite difficult to tackle. The main question i…

[图片] elmuerte: If you often have breaking changes sticking to semver adds little value. Yes, this is where things effectively are today, especially with the flexible theme system. So I think you’re spot on here: [图片] elmuerte: “But then you have x.y.z which is semver”. Well no, it looks…

This discussion doesn’t look good. I can see a decision from the development team to embrace a new versioning system that make sense for them, and others who suddenly seem to consider that Discourse version was following semantic versioning… which it was not. It’s always been a rolling release, at l…

Before answering your other questions, I want to first clarify that our intended release frequency isn’t changing with this proposal. For the past 3 years, we’ve been making “stable” releases approximately every 6 months, targeting these releases for the end of each January and July, with a bit of…

Thank you for your thorough explanation @mcwumbly ! [图片] mcwumbly: With that in mind, do you feel like your other questions about too many settings are still related to this proposal? Or are they independent concerns that would be better to discuss in a separate topic? Indeed, this is a diffe…

[图片] hellekin: Customizing the admin using a plugin would be useful for making tests about what it could look like. Any ongoing work regarding such an approach? Not specifically this, but we’ve been investing quite a bit in improving the admin UI over the past year. If you want to dig into th…

This is a great change (I especially like overlapping ESRs) Feedback: I would like to see that lifecycle graph on a centralized page so I can easily check on it, ideally with a EOL table so I can easily tell what is in and out of support at any given time and plan accordingly (at least for ESRs)…

Today we’ve taken another step towards implementing this RFC - the latest version of Discourse is numbered as v2025.11.0, and we’ve now begun work on v2025.12.0-latest on the latest branch :tada: [图片] Release v2025.11.0: AI translations improvements, chat search, new review …

That’s pretty cool :+1: Do I understand correctly that there is no stable update to 3.5.3 now, possibly coincidentally?

Yeah, just a coincidence. We didn’t have any security fixes to release this month. Stable 3.5 is still fully supported

RFC：Discourse 的新版本策略

开发

mcwumbly (Dave McClure) 2025 年10 月 1 日 02:10 39

并非专门针对此，但我们在过去一年中投入了相当多的精力来改进管理员界面。如果您想更深入地研究这些问题，可以开启一个新主题，并阐述您想进一步讨论的一些问题和/或想法？

话题		回复	浏览量
January 2026 Releases Announcements release-notes	15	1450	2026 年2 月 3 日
July 2026 monthly release Announcements release-notes	13	598	2026 年7 月 29 日
Jumping from 2026.1 ESR to 2026.7 - What I found Support	5	274	2026 年7 月 29 日
Stable branch compatibility with discourse_docker and plugins Self-hosting stable	37	2895	2024 年2 月 3 日
Enable updates only to a given release UX	28	3406	2017 年1 月 25 日

RFC：Discourse 的新版本策略

相关话题