-
Notifications
You must be signed in to change notification settings - Fork 10
Home
TomMaullin edited this page Aug 7, 2018
·
26 revisions
Welcome to the SnPM-devel wiki!
- Create a new branch called
new_release_{{Version number}}
out ofmaster
, where{{Version number}}
is replaced with the version number of SnPM you intend on making a release for. - Merge in all the unmerged updates that will be part of the release using
git merge BRANCH_NAME
whereBRANCH_NAME
is replaced by the name of the branch to be added to that release.
- Create a pull request from the
new_release
branch and document all the changes as an itemized list in the top comment. Note: the list of commits between thenew_release
branch and a given tag can be obtained withgit log --pretty=oneline new_release...SnPMxx.x.x
whereSnPMxx.x.x
must be replaced by the actual tag name. Please use one of the following prefixes for each item:-
fix:
for updates that fix an error and -
enh:
for other enhancements, -
dev:
for fixes that only impact the GitHub repository and the development process (e.g. pull request templates).
-
- Run the tests as specified in doc: Non-regression testing and copy the test report in a comment in the pull request.
- If any test fails, update the code and iterate 3-4 until all tests pass.
- Increment SnPM version number in line 52 of
snpm.m
, as well as on lines 1, 22 and 23 ofCITATION.CFF
, and add/commit/push this update. - Change the title of the pull request into
Release SnPM X.X.X
where X.X.X if the number of the version to be released. - Merge the pull request into
master
. - Go to https://github.com/SnPM-toolbox/SnPM-devel/releases
- Click
Draft a new release
and fill in:
- Tag version: SnPMX.X.X (where `X.X.X is the actual version)
- Target: master (keep default value)
- Release title: SnPM X.X.X (where `X.X.X is the actual version)
- Describe this release: copy/paste the itemized list from the corresponding merged PR.
- Click on
Publish release
- Modify link to the
zip
on SnPM website.