Correct issues with the releasing guide
This commit is contained in:
parent
d496e27628
commit
45b2dc69b6
10
Releasing.md
10
Releasing.md
@ -1,8 +1,8 @@
|
||||
# HTTPure Releasing Guide
|
||||
|
||||
1. Check out the branch you will be releasing (generally `master`, but sometimes
|
||||
an older release series branch). Ensure all relevant commits and PRs have
|
||||
been merged.
|
||||
1. Check out the release series branch (or `master` if you are releasing the
|
||||
next major/minor version). Ensure all relevant commits and PRs have been
|
||||
merged.
|
||||
2. Update [History.md](History.md) by changing "unreleased" to the new
|
||||
version/date. Example diff:
|
||||
```diff
|
||||
@ -11,8 +11,8 @@
|
||||
+1.0.0 / 2017-07-10
|
||||
+==================
|
||||
```
|
||||
3. Commit your update to [History.md](History.md). Use the message "Release
|
||||
notes for v<new version number>".
|
||||
3. Commit your update to [History.md](History.md). Use the message `Release
|
||||
notes for v<new version number>`.
|
||||
4. Run `pulp version` in the project root. This will check the project for any
|
||||
issues and create a new version tag and empty checkpoint commit.
|
||||
5. Push the release notes and version commit and version tag.
|
||||
|
Loading…
Reference in New Issue
Block a user