From b43078e80efe87fa0f69b7f683a98f958c45ae2e Mon Sep 17 00:00:00 2001 From: Donald Webster Date: Tue, 19 May 2020 16:50:56 -0700 Subject: [PATCH] Updated Release Branches (markdown) --- Release-Branches.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Release-Branches.md b/Release-Branches.md index 6ec1cd9..827c989 100644 --- a/Release-Branches.md +++ b/Release-Branches.md @@ -3,10 +3,10 @@ If you're using Sonarr v2, you can choose between `master` and `develop`. But if ### Sonarr v2 * `master`: Is stable, it has been tested by users on develop branch and it's not known to have any major issues. - * `develop`: The bleeding edge. It is released as soon as code is committed and passes all automated tests. This build may have not been used by us or other users yet. 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.*** + * `develop`: This was the bleeding edge, when development was being done on v2. It is released as soon as code is committed and passes all automated tests. This build may have not been used by us or other users yet. 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.*** ### Sonarr v3 - * `phantom-develop`: The only branch. + * `phantom-develop`: Currently this is the only branch and it is similar to v2's `develop`. It gets updated often, occasionally breaks and is usually fixed quickly w/ the help of users running it and providing useful bug reports. It is released as soon as code is committed and passes all automated tests. ## How to change your branch ##