Created Release Branches (markdown)

Release-Branches.md

@@ -0,0 +1,30 @@
+- **develop (Default/Stable):** It has been tested by users on nightly branch and it's not known to have any major issues.
+
+
+- **nightly (Nightly):** The bleeding edge. Released as soon as code is committed and passed all automated tests, this build may have not been used by us or other users. ***Use this branch only if you know what you are doing and are willing to get your hands dirty to recover a failed update.***
+
+- **aphrodite (V3 Alpha):** Aphrodite is in early alpha phase, changes are pushed often with little testing. There is no guarantee that it will even run in some cases. ***Use this branch only if you know what you are doing and are willing to get your hands dirty to recover a failed update.***
+
+## How to change your branch ##
+
+#### For Built-In Updater ####
+
+1. Go to Settings and then the General tab and show advanced settings (use the toggle by the save button).
+
+2. Under the Development section change the branch name to `develop`
+
+3. Save
+
+_This will not install the bits from that branch immediately, it will happen during the next update._
+
+## Installing a newer version ##
+
+1. Go to System and then the Updates tab
+
+2. Newer versions that are not yet installed will have an update button next to them, clicking that button will install the update.
+
+## Can I switch from nightly back to develop? ##
+We don't recommend manually switching back to develop, since other branches are commonly running newer code which might not be compatible with the older code in develop.
+
+## Can I switch from aphrodite back to develop? ##
+No, significant database migrations have been made which mean you should make a backup of your v0.2 database if you want to go back.