-
Notifications
You must be signed in to change notification settings - Fork 30
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: Stefan Marr <[email protected]>
- Loading branch information
Showing
1 changed file
with
30 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
Release Checklist | ||
================= | ||
|
||
This list is supposed to make sure we do not forget any important steps during | ||
release. | ||
|
||
1. Check and update issue tracker for issues associated with current milestone | ||
|
||
2. Update CHANGELOG.md with all elements missing | ||
A useful tool is the `github_changelog_generator` | ||
|
||
It can be used like this: | ||
|
||
``` | ||
sudo gem install github_changelog_generator | ||
github_changelog_generator -u smarr -p SOMns --token ${GITHUB_TOKEN} | ||
``` | ||
|
||
3. Make sure all desired changes are part of the `dev` branch. | ||
|
||
4. Prepare a release on GitHub with: https://github.com/smarr/SOMns/releases/new | ||
The content is normally just the last part of the CHANGELOG.md | ||
|
||
5. If everything looks good, tag the release using the GitHub feature | ||
|
||
6. Push the commit that is tagged as release to the `master` branch. | ||
|
||
7. Announce the release | ||
- https://groups.google.com/forum/#!forum/som-dev | ||
- https://twitter.com/SOM_VMs |