# Major upgrade -- best practices?

**URL:** <https://meta.discourse.org/t/major-upgrade-best-practices/380545>\
**Category:** Self-hosting\
**Created:** [August 27, 2025, 3:35pm UTC](https://meta.discourse.org/t/major-upgrade-best-practices/380545 "2025-08-27T15:35:07Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![opcourdis](https://avatars.discourse-cdn.com/v4/letter/o/45deac/32.png) [@opcourdis](https://meta.discourse.org/u/opcourdis)\
**Post date:** [August 28, 2025, 11:03pm UTC](https://meta.discourse.org/t/major-upgrade-best-practices/380545/6 "2025-08-28T23:03:09Z")

</div>

Best practice? Keep a checklist somewhere, you can add one in the UI\>admin\>update by adding this CSS to your theme(../admin/customize/themes/ edit\>css) if someday you or someone would have the idea to update too quickly :

`.admin-contents.update .d-nav-submenu::before {content:“Update checklist” : Backup done?" ; “Last month meta announcement read? ; last months most important bugs from Meta checked? Essential plugin compatibility checked? Postgres/Redis compatibility version checked? Right timing for the update checked? Troubleshooting Workforce Availability in case of update failure checked?” }`

---

_[View the full topic](https://meta.discourse.org/t/major-upgrade-best-practices/380545)._