# Need a better way to explain what branch to be on, why, and what happens

**URL:** <https://meta.discourse.org/t/need-a-better-way-to-explain-what-branch-to-be-on-why-and-what-happens/240342>\
**Category:** Product Support\
**Created:** [September 28, 2022, 3:29pm UTC](https://meta.discourse.org/t/need-a-better-way-to-explain-what-branch-to-be-on-why-and-what-happens/240342 "2022-09-28T15:29:04Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![khenmu](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/khenmu/32/108976_2.png) [@khenmu](https://meta.discourse.org/u/khenmu)\
**Post date:** [September 28, 2022, 10:18pm UTC](https://meta.discourse.org/t/need-a-better-way-to-explain-what-branch-to-be-on-why-and-what-happens/240342/7 "2022-09-28T22:18:31Z")

</div>

There will always be people out there who decide they want to use e.g. the latest stable release. Not having a guide on how to achieve that in the most intuitive place doesn’t make those people go away; it just makes things a bit less convenient for them - and likely sometimes means them coming here to ask, and others spending time answering the question (again and again).

Probably the stronger argument, though, is that the guide can show them how to do it _correctly_, which means them being able to change back later if they change their mind. If they don’t know, they might end up breaking their install, which will be inconvenient for both them and their community.

If INSTALL-cloud.md has a section on changing branch, it can clarify what the default is and why, making clear that the default is the most widely used, and the easiest to support.

---

_[View the full topic](https://meta.discourse.org/t/need-a-better-way-to-explain-what-branch-to-be-on-why-and-what-happens/240342)._
