Commit 1e2795fd authored by Bob Obara's avatar Bob Obara

DOC: Adding Release Issue Template to SMTK's GitLab

parent c64e3eb0
<!--
This template is for tracking a release of SMTK. Please replace the
following strings with the associated values:
- `VERSION`
- `MAJOR`
- `MINOR`
Please remove this comment.
-->
# Preparatory steps
- Update SMTK guides
- Assemble release notes into `doc/release/notes/SMTK-VERSION`.
- [ ] Get positive review and merge.
# Update SMTK
Keep the relevant items for the kind of release this is.
If making a first release candidate from master, i.e., `vMAJOR.MINOR.0-RC1`:
- [ ] Update `master` branch for **smtk**
```
git fetch origin
git checkout master
git merge --ff-only origin/master
```
- [ ] Update `version.txt` and tag the commit
```
git checkout -b update-to-vVERSION
echo VERSION > version.txt
git commit -m 'Update version number to VERSION' version.txt
git tag -a -m 'SMTK VERSION' vVERSION HEAD
```
- Integrate changes to `master` branch
- [ ] Create a merge request targeting `master` (do *not* add `Backport: release`)
- [ ] Get positive review
- [ ] `Do: merge`
- Integrate changes to `release` branch
- [ ] `git push origin update-to-vVERSION:release vVERSION`
- [ ] Update kwrobot with the new `release` branch rules (@ben.boeckel)
# Post-release
- [ ] Write and publish blog post with release notes.
- [ ] Post an announcement in the Announcements category on
[discourse.smtk.org](https://discourse.kitware.com/c/smtk/).
/cc @ben.boeckel
/cc @bob.obara
/cc @tjcorona
/cc @dcthomp
/label ~"priority:required"
<!--
This template is for tracking a release of SMTK. Please replace the
following strings with the associated values:
- `VERSION`
- `MAJOR`
- `MINOR`
Please remove this comment.
-->
# Preparatory steps
- Update SMTK guides
- Assemble release notes into `doc/release/notes/SMTK-VERSION`.
- [ ] Get positive review and merge.
# Update SMTK
If making a release from the `release` branch, e.g., `vMAJOR.MINOR.0-RC2 or above`:
- [ ] Update `release` branch for **smtk**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
```
- [ ] Update `version.txt` and tag the commit
```
git checkout -b update-to-vVERSION
echo VERSION > version.txt
git commit -m 'Update version number to VERSION' version.txt
git tag -a -m 'SMTK VERSION' vVERSION HEAD
```
- Integrate changes to `master` branch
- [ ] Create a merge request targeting `master` (do *not* add `Backport: release`)
- [ ] Get positive review
- [ ] `Do: merge`
- Integrate changes to `release` branch
- [ ] `git push origin update-to-vVERSION:release vVERSION`
# Post-release
- [ ] Write and publish blog post with release notes.
- [ ] Post an announcement in the Announcements category on
[discourse.smtk.org](https://discourse.kitware.com/c/smtk/).
/cc @ben.boeckel
/cc @bob.obara
/cc @tjcorona
/cc @dcthomp
/label ~"priority:required"
<!--
This template is for tracking a release of SMTK. Please replace the
following strings with the associated values:
- `VERSION`
- `MAJOR`
- `MINOR`
Please remove this comment.
-->
# Preparatory steps
- Update SMTK guides
- Assemble release notes into `doc/release/notes/SMTK-VERSION`.
- [ ] Get positive review and merge.
# Update SMTK
If making a release from the `release` branch, e.g., `vMAJOR.MINOR.0-RC2 or above`:
- [ ] Update `release` branch for **smtk**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
```
- [ ] Update `version.txt` and tag the commit
```
git checkout -b update-to-vVERSION
echo VERSION > version.txt
git commit -m 'Update version number to VERSION' version.txt
git tag -a -m 'SMTK VERSION' vVERSION HEAD
```
- Integrate changes to `master` branch
- [ ] Create a merge request targeting `master` (do *not* add `Backport: release`)
- [ ] Get positive review
- [ ] `Do: merge`
- Integrate changes to `release` branch
- [ ] `git push origin update-to-vVERSION:release vVERSION`
- Update documentation page
- [ ] See `https://github.com/Kitware/paraview-docs/blob/gh-pages/versions.json`
# Upload documentation
- [ ] Verify documentation is uploaded and is correct
# Post-release
- [ ] Write and publish blog post with release notes.
- [ ] Post an announcement in the Announcements category on
[discourse.smtk.org](https://discourse.kitware.com/c/smtk/).
- [ ] Update release notes
(https://www.paraview.org/Wiki/ParaView_Release_Notes)
- [ ] Move unclosed issues to next release milestone in GitLab
/cc @ben.boeckel
/cc @bob.obara
/cc @tjcorona
/cc @dcthomp
/label ~"priority:required"
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment