unisonweb/unison
1
0
Fork 0
mirror of https://github.com/unisonweb/unison.git synced 2024-10-04 05:37:14 +03:00
Code Issues Projects Releases Wiki Activity

Update release-steps.md

Browse Source
This commit is contained in:
Paul Chiusano 2021-09-27 12:55:26 -05:00 committed by GitHub
parent 0711e35fde
commit 2125e78e41
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/release-steps.md
View File

@ -11,7 +11,8 @@ Create and push the tag to github. This will trigger the build. To determine the
git fetch
git checkout series/M2
git merge origin/trunk
git tag -a $RELEASE_NAME -m "release"
git tag -a release/$RELEASE_NAME -m "release"
git push origin release/$RELEASE_NAME
```
__2__
@ -20,11 +21,11 @@ Wait for the release to show up on [the releases page](https://github.com/unison
__3__
Create a release notes draft issue, following [this template](https://github.com/unisonweb/unison/issues/2342).
Create a release notes draft issue, following [this template](https://github.com/unisonweb/unison/issues/2342) and updating the output of PRs merged and contributors to the release.
__4__
Update trunk of `base` to include any new builtins added since last release. Suggestion for how to do this: look through the release notes draft to find the PRs merged since last release.
Update trunk of `base` to include any new builtins added since last release. Suggestion for how to do this: look through the release notes draft to find the PRs merged since last release. @runarorma does this usually.
```
git log --oneline release/M2h...release/M2i | grep 'Merge pull request #'
@ -34,7 +35,7 @@ Then just use `alias.term ##Nat.newBuiltin Nat.someName` and/or `alias.type ##So
__5__
Cut a release of base.
Cut a release of base. @runarorama does this usually.
```
.> pull https://unisonweb/base basedev.release