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…

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 diff…

[이미지] 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 t…

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

Hi, I used to use the beta tag and am now trying to update my scripts to use the new setup. Here’s how the repository looks as far as I can tell: * b541e99ea2 (origin/tests-passed, origin/main, origin/latest) DEV: Exclude new table in IntermediateDB config * 02dfb651ae DEV: Add support for convert…

Hi @simonk , thanks for raising those points! We’ve actually been discussing both those things today internally. The old beta and latest-release tags should be aliases of release release should be tracking the latest commit of release/2025.11 Working on getting that fixed up right now.

Those three tags have now been moved to the correct commit manually. Will make sure that the automated tooling is updated to keep them in the right place going forward. * commit 48167b94d63faf8a41b9c8193ec5dd3e4e9f498e (HEAD -> release/2025.11, tag: release, tag: latest-release, tag: beta, origin/r…

RFC: Discourse를 위한 새로운 버전 관리 전략

개발

RGJ (Richard - Communiteq) 11월 26, 2025, 11:57오전 43

정말 멋진데요

지금 3.5.3으로의 안정적 업데이트가 없으며, 이것이 우연한 일치일 수도 있다는 뜻으로 이해하면 맞나요?

글		댓글	조회수
January 2026 Releases Announcements release-notes	15	1443	2월 3, 2026
July 2026 monthly release Announcements release-notes	13	592	7월 29, 2026
Jumping from 2026.1 ESR to 2026.7 - What I found Support	5	270	7월 29, 2026
Stable branch compatibility with discourse_docker and plugins Self-hosting stable	37	2892	2월 3, 2024
Enable updates only to a given release UX	28	3405	1월 25, 2017

RFC: Discourse를 위한 새로운 버전 관리 전략

Related topics