Add release information to readme
This commit is contained in:
parent
9bb71512ed
commit
5e49918625
27
README.md
27
README.md
|
|
@ -69,7 +69,7 @@ Production Build
|
|||
|
||||
`heroku run python server/manage.py <command> --app <appname>`
|
||||
|
||||
### Rollabck
|
||||
### Rollback
|
||||
|
||||
After doing a rollback under https://data.heroku.com/
|
||||
|
||||
|
|
@ -121,3 +121,28 @@ Change bucket `Permissions` / `Bucket Policy`
|
|||
}
|
||||
|
||||
```
|
||||
|
||||
## Release
|
||||
|
||||
### Pushing to Production
|
||||
|
||||
Whenever you want to do a release, just merge develop into master and push to origin.
|
||||
The current master will always be deployed in the evening, if there are new commits that are not yet on Heroku.
|
||||
|
||||
### Tagging
|
||||
|
||||
Whenever you do a new release, please tag the current commit after merging with the current date:
|
||||
|
||||
git tag -a release/v2019-09-10
|
||||
|
||||
`git tag -a` creates an annotated tag, which must have a release message (like a commit message). For now, just repeat the current date, like:
|
||||
|
||||
Release to production on 2019-09-10
|
||||
|
||||
You can and should then push the tag to the repo
|
||||
|
||||
git push origin release/v2019-09-10
|
||||
|
||||
You can later see the metadata of the tag with
|
||||
|
||||
git show release/v2019-09-10
|
||||
|
|
|
|||
Loading…
Reference in New Issue