# Production upgrades - correct procedure to follow

**URL:** https://meta.discourse.org/t/production-upgrades-correct-procedure-to-follow/399550
**Category:** Self-hosting
**Created:** [March 30, 2026, 9:27am UTC](https://meta.discourse.org/t/production-upgrades-correct-procedure-to-follow/399550 "2026-03-30T09:27:26Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [March 30, 2026, 10:28am UTC](https://meta.discourse.org/t/production-upgrades-correct-procedure-to-follow/399550/4 "2026-03-30T10:28:34Z")

</div>

> [@stevejr](#):
>
> my understanding is that we should not use the latest of main versions of a release in production as they are still undergoing active development.

Have you read [Understanding Discourse release channels](https://meta.discourse.org/t/understanding-discourse-release-channels/264400) and [Configure a supported tracking branch to get Discourse software updates](https://meta.discourse.org/t/configure-a-supported-tracking-branch-to-get-discourse-software-updates/17014)? I would describe the difference more as having access to the latest changes right away, or receiving them a little later. The latter can be very helpful for custom developments that need to be adapted first. Otherwise, I would prefer access to the latest features and fixes. Of course, this carries a risk of new bugs, but the version that was frozen three weeks ago also contains bugs which might have already been fixed in latest, but usually not significant enough to warrant backporting to the last release.

Also keep in mind that downgrading is not supported, so if you are on a version after the current ESR, you need to wait for the next ESR to be published.

---

_[View the full topic](https://meta.discourse.org/t/production-upgrades-correct-procedure-to-follow/399550)._