# RFC: A new versioning strategy for Discourse

**URL:** <https://meta.discourse.org/t/rfc-a-new-versioning-strategy-for-discourse/383536>\
**Category:** Development\
**Tags:** dev-news\
**Created:** [September 23, 2025, 7:55am UTC](https://meta.discourse.org/t/rfc-a-new-versioning-strategy-for-discourse/383536 "2025-09-23T07:55:33Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)\
**Post date:** [September 24, 2025, 10:19pm UTC](https://meta.discourse.org/t/rfc-a-new-versioning-strategy-for-discourse/383536/19 "2025-09-24T22:19:21Z")

</div>

It’s not about when the theme/plugin author pushes a fix, it’s about when Discourse core has a security fix.

Per

> [@david](#):
>
> Approximately every 6 months, declare one of those releases as an Extended Support Release (ESR). ESR versions remain supported for 2 releases after the next ESR is declared.

the only difference between `release` and `esr` is that `esr` gets security fixes for 6 + 2 = 8 months.

---

_[View the full topic](https://meta.discourse.org/t/rfc-a-new-versioning-strategy-for-discourse/383536)._
