Update readme
This commit is contained in:
parent
9139aa80b7
commit
f7370a7cdc
14
README.md
14
README.md
|
|
@ -181,7 +181,7 @@ The current master will always be deployed in the evening, if there are new comm
|
|||
|
||||
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 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:
|
||||
|
||||
|
|
@ -189,12 +189,22 @@ Whenever you do a new release, please tag the current commit after merging with
|
|||
|
||||
You can and should then push the tag to the repo
|
||||
|
||||
git push origin release/v2019-09-10
|
||||
git push origin v2019-09-10
|
||||
|
||||
You can later see the metadata of the tag with
|
||||
|
||||
git show release/v2019-09-10
|
||||
|
||||
or
|
||||
|
||||
git tag -ln
|
||||
|
||||
NB: If there are two releases on the same day, use the pattern `v2020-03-01.x` eg. `v2020-03-01.1` for the subsequent releases
|
||||
|
||||
#### Hotfixes
|
||||
|
||||
Please use the pattern `v2020-03-01.hotfix` for hotfix releases
|
||||
|
||||
|
||||
## Testing
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue