# Why don't Stable Versions and Release Notes match?

**URL:** <https://meta.discourse.org/t/why-dont-stable-versions-and-release-notes-match/165297>\
**Category:** Product Support\
**Created:** [September 25, 2020, 12:24am UTC](https://meta.discourse.org/t/why-dont-stable-versions-and-release-notes-match/165297 "2020-09-25T00:24:12Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![jomaxro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jomaxro/32/126216_2.png) [@jomaxro](https://meta.discourse.org/u/jomaxro)\
**Post date:** [September 25, 2020, 3:06am UTC](https://meta.discourse.org/t/why-dont-stable-versions-and-release-notes-match/165297/6 "2020-09-25T03:06:49Z")

</div>

Jeff is correct, I don’t write release notes for stable releases. The email you received is a standard email, shared by all Discourse instances. It doesn’t know what branch you’re on.

Stable point releases only include critical bug fixes and security patches. Unlike our normal releases, which contain hundreds of changes, stable point releases generally have less than 10, many times far less.

You can see all the changes at [https://github.com/discourse/discourse/commits/stable](https://github.com/discourse/discourse/commits/stable). Look for “Version bump to v{current version}” and “Version bump to v{previous version}”. Anything between that is the changes. In the case of v2.5.2 there are 7 changes. 3 security, 2 follow ups to the security changes, and 2 critical performance fixes.

---

_[View the full topic](https://meta.discourse.org/t/why-dont-stable-versions-and-release-notes-match/165297)._