|
| 1 | +# Releasing New Rez Versions |
| 2 | + |
| 3 | +If you are a collaborator and have push access to master, these are the steps to |
| 4 | +follow to release a new version: |
| 5 | + |
| 6 | +1. Make sure that the version in `utils/_version.py` is updated appropriately. |
| 7 | + Rez uses [semantic versioning](https://semver.org/). |
| 8 | +1. Before pushing your branch, update `CHANGELOG.md` to describe the changes. Follow |
| 9 | + the existing structure. The PR for the merge appears in square brackets in the |
| 10 | + title (eg `[#552]`); since this PR doesn't exist yet, just leave `[#XXX]` as a |
| 11 | + placeholder. |
| 12 | +2. Push your changes, and create a PR to master. In that PR's description, copy |
| 13 | + the markdown you added to the changelog for this release. Change only the title |
| 14 | + - just put the version number there. |
| 15 | +3. Once approved, merge to master. |
| 16 | +4. In master, go back to `CHANGELOG.md` and update the PR number appropriately. |
| 17 | +5. Run tag.sh. This tags the git repo with the version in `utils/_version.py`. |
| 18 | +6. Do a `git push` to push changelog update, and a `git push --tags` to push the |
| 19 | + new tag. |
| 20 | +7. Goto [https://github.com/nerdvegas/rez/releases] and create a new release. Use |
| 21 | + the changelog markdown as the starting point, and format appropriately (look |
| 22 | + at existing release notes to see what to do). |
| 23 | + |
| 24 | +## Example Changelog Entry |
| 25 | + |
| 26 | +``` |
| 27 | +## 1.2.3 [[#000](https://github.com/nerdvegas/rez/pull/456)] Release Title Here |
| 28 | +
|
| 29 | +#### Addressed Issues |
| 30 | +
|
| 31 | +* [#000](https://github.com/nerdvegas/rez/issues/000) some thing is broken |
| 32 | +* [#001](https://github.com/nerdvegas/rez/issues/001) some other thing is broken |
| 33 | +
|
| 34 | +#### Merged PRs |
| 35 | +
|
| 36 | +* [#002](https://github.com/nerdvegas/rez/pull/002) fixed the floober |
| 37 | +* [#003](https://github.com/nerdvegas/rez/pull/003) added missing flaaber |
| 38 | +
|
| 39 | +#### Notes |
| 40 | +
|
| 41 | +Notes about the new release go here. These should add any info that isn't |
| 42 | +necessarily obvious from the linked issues. |
| 43 | +
|
| 44 | +#### COMPATIBILITY ISSUE! |
| 45 | +
|
| 46 | +Put any notes here in the unfortunate case where some form of backwards |
| 47 | +incompatibility is unavoidable. This is rare. |
| 48 | +``` |
0 commit comments