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…

[画像] mcwumbly: I think the “leading zeroes” suggestion is the only thing that we would be breaking from if we go that route. The OP says that you’re not using leading zeros, if I understand correctly. [画像] david: e.g. the first release of 2026 would be v2026.0, next would be v2026.1, etc…

The point of SemVer is that the version number should communicate some useful information. The only information communicated by your proposed scheme is the earth’s orbit around the sun. That information is not very useful to the consumer of the software. If for some reason I did want to know the da…

[画像] pfaffman: The OP says that you’re not using leading zeros, if I understand correctly. I proposed that a few posts up. [画像] per1234: version number having meaning instead of just being some arbitrary number, as is the case with your proposal. Contrary to semver, the proposed versi…

[画像] Ed_S: have good descriptions of how to perform them as smoothly as possible. Just to emphasize a point that might get lost, I think Discourse does great here. One improvement would be to at least highlight the topics you’ve already written that describe changes and potential breakage wit…

[画像] RGJ: I proposed that a few posts up. Yes, and it’s such a good idea that I think the op should be edited to reflect that!

The leading zeroes and whether or not to aim for synchronization with months more explicitly is being considered. @david will share an update once the group working on this arrives at a decision.

[画像] RGJ: the proposed version numbering scheme makes it immediately clear if a version is still supported That is not the important information for a forum maintainer evaluating a new release. [画像] RGJ: Yes really No, really. You are missing the actual point of SemVer by refusing to …

I think we’re going to have to agree to disagree on this point @per1234 . Here’s a related discussion on the GitHub repository for semver with a response from one of the maintainers : Semver is not really useful for “end-user apps,” it is more useful for libraries that people use as dependencies fo…

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…

RFC：Discourse の新しいバージョン管理戦略

開発

mcwumbly (Dave McClure) 2025 年 9 月 26 日午後 10:16 31

先頭のゼロや、より明確に月との同期を目指すかどうかを検討中です。この件に取り組んでいるグループが決定に至り次第、@david がアップデートを共有します。

トピック		返信	表示
January 2026 Releases Announcements release-notes	15	1755	2026 年 2 月 3 日
July 2026 monthly release Announcements release-notes	13	752	2026 年 7 月 29 日
Stable branch compatibility with discourse_docker and plugins Self-hosting stable	37	3052	2024 年 2 月 3 日
Jumping from 2026.1 ESR to 2026.7 - What I found Product Support	6	439	2026 年 9 月 12 日
Enable updates only to a given release UX	28	3531	2017 年 1 月 25 日

RFC：Discourse の新しいバージョン管理戦略

関連トピック