-
Notifications
You must be signed in to change notification settings - Fork 15
Checklist for new releases
Carlchristian Eckert edited this page Feb 11, 2015
·
2 revisions
- check if the milestone is fulfilled
- move unfinished items to new milestone, if appropriate
- bump version information
- check the years in the license
- If the API changed, check files like README.md and Usage.md to be up-to-date
- edit changelog
- release date must match the current day
- check if the referenced milestone is correct
- check if the referenced compare-view is correct
- merge all these changes to the
dev
branch - merge the
dev
branch intomaster
(Using another Pull-request?) - draft a new release from the newly merged
master
branch - write nice description, similar to the already existing ones
- do the release-dance
- hit the release-button
- fetch the DOI from Zenodo (should be auto-generated?)
- add the DOI to the release description