# Introducing releases.discourse.org **URL:** https://meta.discourse.org/t/introducing-releases-discourse-org/392712 **Category:** Announcements **Created:** [January 6, 2026, 3:27pm UTC](https://meta.discourse.org/t/introducing-releases-discourse-org/392712 "2026-01-06T15:27:56Z") **Posts on this page:** 1 **Showing post:** 8
### Author: ![SkyeDragon](https://avatars.discourse-cdn.com/v4/letter/s/3e96dc/32.png) [@SkyeDragon](https://meta.discourse.org/u/SkyeDragon) #### Post date: [January 10, 2026, 9:22pm UTC](https://meta.discourse.org/t/introducing-releases-discourse-org/392712/8 "2026-01-10T21:22:18Z")
This is awesome, really helps to quickly see at a glance what version I’m on and when I need to plan for moving to the next one! Big fan of this page 👏 👏 I love that security fixes and big features are highlighted! I hope breaking changes will be similarly featured as well. Also, I would suggest ESRs should ideally be supported for just a little bit more time (maybe a month or two), so that people can switch from one ESR to another while they’re both in non-active development but support period. Otherwise communities basically need to decide between waiting and being out of support briefly, or going early and being in-support but having to take more in-dev updates. Having a small overlap gives a branch a chance to become more stable. This is pretty common for ESR lifecycles, ex for mediawiki: ![image](https://global.discourse-cdn.com/meta/original/4X/8/e/7/8e783c8603372371e74d45941d100d2bb2ec7282.png) This doesn’t need to be anything particularly fancy, just high-priority security fixes for an extra month or two on the older ESR branch Thanks regardless though, this really helps clear a lot of things up ^.^ --- _[View the full topic](https://meta.discourse.org/t/introducing-releases-discourse-org/392712)._