|
1 |
| -# Release steps |
2 | 1 |
|
3 |
| -* Update version constants (find them by running `git grep [VERSION_NUMBER]`) |
4 |
| -* Create changelog entry (edit CHANGELOG.md with a one-liner for each closed issue going in the release) |
5 |
| -* Commit and push changes to master with the message: "Version Bump to v[VERSION_NUMBER]" |
6 |
| -* Make sure your `upstream` repo is set |
| 2 | + |
| 3 | +# Versions |
| 4 | + |
| 5 | +This project follows the Major.Minor.Revision versioning system. Fixes, and minor additions would increment Revision. Large changes and additions would increment Minor, and anything that would be a "Breaking" change, or redesign would be an increment of Major. |
| 6 | + |
| 7 | +# Changelog |
| 8 | + |
| 9 | +When doing a release, the Changelog format should be as follows: |
| 10 | + |
| 11 | +```markdown |
| 12 | + |
| 13 | +## [Version] - YYYY-MM-DD |
| 14 | +https://github.com/softlayer/softlayer-python/compare/v5.9.0...v5.9.1 |
| 15 | + |
| 16 | +#### New Command |
| 17 | +- `slcli new command` #issueNumber |
| 18 | + |
| 19 | +#### Improvements |
| 20 | +- List out improvements #issueNumber |
| 21 | +- Something else that changed #issueNumber |
| 22 | + |
| 23 | +#### Deprecated |
| 24 | +- List something that got removed #issueNumber |
| 25 | + |
| 26 | +``` |
| 27 | + |
| 28 | +# Normal Release steps |
| 29 | + |
| 30 | +A "release" of the softlayer-python project is the current state of the `master` branch. Any changes in the master branch should be considered releaseable. |
| 31 | + |
| 32 | + |
| 33 | +1. Create the changelog entry, us this to update `CHANGELOG.md` and as the text for the release on github. |
| 34 | +2. Update the version numbers in these files on the master branch. |
| 35 | + - `SoftLayer/consts.py` |
| 36 | + - `setup.py` |
| 37 | +3. Make sure the tests for the build all pass |
| 38 | +4. [Draft a new release](https://github.com/softlayer/softlayer-python/releases/new) |
| 39 | + - Version should start with `v` followed by Major.Minor.Revision: `vM.m.r` |
| 40 | + - Title should be `M.m.r` |
| 41 | + - Description should be the release notes |
| 42 | + - Target should be the `master` branch |
| 43 | +5. The github automation should take care of publishing the release to [PyPi](https://pypi.org/project/SoftLayer/). This may take a few minutes to update. |
| 44 | + |
| 45 | +# Manual Release steps |
| 46 | + |
| 47 | +1. Create the changelog entry, us this to update `CHANGELOG.md` and as the text for the release on github. |
| 48 | +2. Update the version numbers in these files on the master branch. |
| 49 | + - `SoftLayer/consts.py` |
| 50 | + - `setup.py` |
| 51 | +3. Commit your changes to `master`, and make sure `softlayer/softlayer-python` repo is updated to reflect that |
| 52 | +4. Make sure your `upstream` repo is set |
| 53 | + |
7 | 54 | ```
|
8 | 55 | git remote -v
|
9 | 56 | upstream [email protected]:softlayer/softlayer-python.git (fetch)
|
10 | 57 | upstream [email protected]:softlayer/softlayer-python.git (push)
|
11 | 58 | ```
|
12 |
| -* Push tag and PyPi `python fabfile.py 5.7.2`. Before you do this, make sure you have the organization repository set up as upstream remote, also make sure that you have pip set up with your PyPi user credentials. The easiest way to do that is to create a file at `~/.pypirc` with the following contents: |
| 59 | + |
| 60 | +5. Create and publish the package |
| 61 | + - Make sure you have `twine` installed, this is what uploads the pacakge to PyPi. |
| 62 | + - Before you do this, make sure you have the organization repository set up as upstream remote, also make sure that you have pip set up with your PyPi user credentials. The easiest way to do that is to create a file at `~/.pypirc` with the following contents: |
13 | 63 |
|
14 | 64 | ```
|
15 | 65 | [server-login]
|
16 | 66 | username:YOUR_USERNAME
|
17 | 67 | password:YOUR_PASSWORD
|
18 | 68 | ```
|
| 69 | + |
| 70 | + - Run `python fabfile.py 5.7.2`. Where `5.7.2` is the `M.m.r` version number. Don't use the `v` here in the version number. |
| 71 | + |
| 72 | + |
| 73 | +*NOTE* PyPi doesn't let you reupload a version, if you upload a bad package for some reason, you have to create a new version. |
| 74 | + |
0 commit comments