Update release docs (#1468)

Author: sophialittlejohn

.github/README.md

@@ -13,14 +13,10 @@ It's also recommended to run Prettier automatically in your editor, e.g. using [
 
 ## Preparing Envs (e.g when the dev chain data is reset)
 
-### Frontend
-
-1. Create pools for initial data
-
-### Faucet
+### Faucet (only available in demo and dev)
 
 1. Add a valid seed hex to `faucet-api/env-vars/demo.secrets`
-2. Fund the account wallet with aUSD and DEVEL/DEMO
+2. Fund the account wallet with all availabe pool currencies and the native currency
 
 ### Onboarding API
 
@@ -32,7 +28,7 @@ Setup pure proxy to sign transactions (whitelisting & transfer tokens).
 4. Add the pure_proxy_address to the env variable `MEMBERLIST_ADMIN_PURE_PROXY` in the onboarding api and `REACT_APP_MEMBERLIST_ADMIN_PURE_PROXY` in the centrifuge-app env variables.
 5. Make sure secure_wallet_B is funded with both aUSD and the Native currency.
 
-Note: onboarding must be manually enabled for each tranche in the issuer settings.
+> onboarding must be manually enabled for each tranche in the issuer settings.
 
 ### Asset Originator POD Access
 
@@ -107,14 +103,57 @@ To set a pool into maintenance mode, add the pool id to the environment variable
 
 To make sure repository admins can control the full workflow of our apps to production safely this repository provides the following flow:
 
-- When you open a PR a new cent-app will be deployed with your PR number on the URL such as: app-prXXX.k-f.dev
+- Opening a new PR will deploy cent-app using the PR number to app-prXXX.k-f.dev - There should be a comment with these links in your PR after deployment. Forks do not trigger a PR deployment
+
+- Merging code into `main` will deploy buckets and functions pointing to: app-dev.k-f.dev
+
+- Demo deployments must be [manually triggered](https://github.com/centrifuge/apps/actions/workflows/demo-deploys.yml). They are not required for the release process.
+
+- Catalyst deployments are triggered by pushing a tag containing `rc` in the tag name.
 
-- After code is merged to main you can see the changes in: app-dev.k-f.dev
+- Altair and staging are triggered by creating a `pre-release` [on the Github repository](https://github.com/centrifuge/apps/releases/new) 
 
-- When a repository admin creates a `centrifuge-app/v*` tag it will will trigger a deployment to [altair.centrifuge.io](https://altair.centrifuge.io). The release needs to FIRST be marked as `prerelease`.
+- Centrifuge is deployed by editing [an existing release](https://github.com/centrifuge/apps/releases) and unmarking `pre-release` to fully release it, it will promote the staging artifacts to app.centrifuge.io 
 
-  > Draft releases or tags other than the one above will not trigger any deployments.
+- Using the github release manager the pre-release can be promoted to production ([app.centrifuge.io](https://app.centrifuge.io)) using the artifacts generated in the pre-release. The production release must be approved by a reviewer.
 
-- Once ready, you can edit your pre-release and untick the "pre-release" setting to fully publish a release, this will trigger a refresh of our code in app.centrifuge.io and app.ipfs.centrifuge.io (coming soon)
+(Coming soon: release web-bundle to IPFS)
+
+You can follow your deployments by going to [the Actions section](https://github.com/centrifuge/apps/actions/workflows/centrifuge-app.yml) of the github repo
+
+HackMD docs: https://centrifuge.hackmd.io/MFsnRldyQSa4cadx11OtVg?view
+
+## More info
 
 More info on our release process rationale can be found in [our HackMD](https://centrifuge.hackmd.io/MFsnRldyQSa4cadx11OtVg?view) (Private link, only k-f contributors)
+
+## Releasing to staging, Altair, and Prod/Centrifuge
+
+### 1. Create a release and mark it as a pre-Release 
+-> Deploys to pp.staging.centrifuge.io) and app.altair.centrifuge.io
+
+Navigate to create a new [pre-release](https://github.com/centrifuge/apps/releases/new). Make sure to tick the `pre-release` option.
+
+1. Use an existing tag `rc` created to release Catalyst or create a new `centrifuge-app-vX.YY` tag on the release screen. Only tags starting with `rc*` or `centrifuge-app-v*` will meet the requirements for deployments
+   - Major version: release includes new features/improvments
+   - Minor version: release only includes bug fixes
+2. Name the release `CentrifugeApp vX.X`
+3. Generate the release notes
+4. Tick the `Set as a pre-release` checkbox
+5. Click `Publish release` to trigger the build. You can follow progress on the [Actions dashboard](https://github.com/centrifuge/apps/actions/workflows/staging-deploy.yml)
+6. Once the build is complete, a reviewer must approve the release to trigger a deployment
+
+When the deployment is finished a notification will be sent to the #eng-apps channel on Slack.
+
+### 2. Create a production Release 
+-> Deploys to app.centrifuge.io
+
+> The deployment to staging from point 1. needs to have been finished first. The production deployment uses the artifacts generated in the pre-release.
+
+Navigate to the [release summary](https://github.com/centrifuge/apps/releases) and select the pre-release you want to publish.
+
+1. Untick the `Set as a pre-release` checkbox and then tick the `Set as the latest release` checkbox
+2. Click `Update release` to trigger the prod deployment. As with the pre-release, the production release must be approved by a reviewer.
+3. Follow your prod deployment in the  [Actions dashboard](https://github.com/centrifuge/apps/actions/workflows/prod-deploy.yml)
+
+When the deployment is finished a notification will be sent to the #eng-apps channel on Slack.