From 6c4b2cbde95d0280c8d2fce9e64397523146f245 Mon Sep 17 00:00:00 2001
From: Amine <amine@mouafik.fr>
Date: Wed, 13 May 2020 04:33:34 +0000
Subject: Setup nightly releases deployment pipeline (#730)

---
 README.md | 23 +++++++++++++++++++----
 1 file changed, 19 insertions(+), 4 deletions(-)

(limited to 'README.md')

diff --git a/README.md b/README.md
index 4428babc1..1d68601a5 100644
--- a/README.md
+++ b/README.md
@@ -282,18 +282,33 @@ Deliverables will be available in the `out` folder.
 
 ### Release
 
+Create a new [draft release](https://github.com/getferdi/ferdi/releases/new) that targets the `release` branch, then:
+
+```bash
+$ git checkout develop && git pull
+$ git checkout release
+$ git submodule update --remote --force
+$ git add .
+$ git commit -m "Update submodules"
+$ git merge --no-ff develop
+$ git push
+```
+
+Once the draft release assets are uploaded (13 assets), publish the release. The last commit of the `release` branch will be tagged. You can then merge `release` into `master` and back into `develop` if needed.
+
+#### Nightly
+
 ```bash
 $ git checkout develop && git pull
+$ git checkout nightly
 $ git submodule update --remote --force
 $ git add .
 $ git commit -m "Update submodules"
-$ git checkout master
 $ git merge --no-ff develop
-$ git tag v5.3.4-beta.4
-$ git push --tags
+$ git push
 ```
 
-When pushing a new tag, the CI builds will create a draft GitHub release and upload the deliverables in the draft release assets. Wait for all the assets to be uploaded before publishing the draft release.
+The draft release and assets will be available in [getferdi/nightlies releases](https://github.com/getferdi/nightlies/releases). You need to manually publish the draft release as a pre-release for now.
 
 ## Contributors ✨
 
-- 
cgit v1.2.3-54-g00ecf