# Better commit messages for the changelog

**URL:** https://meta.discourse.org/t/better-commit-messages-for-the-changelog/39107
**Category:** Development
**Created:** [2016年二月5日 17:37 UTC](https://meta.discourse.org/t/better-commit-messages-for-the-changelog/39107 "2016-02-05T17:37:44Z")
**Posts on this page:** 1
**Showing post:** 14

<div class="post-metadata">

### Author: ![wesochuck](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/wesochuck/32/108706_2.png) [@wesochuck](https://meta.discourse.org/u/wesochuck)
#### Post date: [2016年二月5日 19:27 UTC](https://meta.discourse.org/t/better-commit-messages-for-the-changelog/39107/14 "2016-02-05T19:27:25Z")

</div>

> [@wesochuck](#):
>
> It’s possible that you may have to wait until the next major point release before you can switch to stable.

Confirmed that it looks like you need to wait till the stable release that would put you ahead of your current beta release:

> [@Downgrade to stable?](https://meta.discourse.org/t/downgrade-to-stable/33729/4):
>
> To move between channels you got to ensure you are running forward. So… you are safe to move to “tests-passed” to “stable” just as we release a new “stable” release. Meaning, if you are on “tests-passed” now, all you can do is move to “beta” next time we cut a beta. Process for moving channels is the same… Stop upgrading Discourse Wait for a new release on channel Amend app.yml to point at channel Rebuild We cut new betas weekly, so its easy to get on that train. To get on stable you are …

---

_[View the full topic](https://meta.discourse.org/t/better-commit-messages-for-the-changelog/39107)._
