Skip to content

Small fixes to RELEASE_PROCEDURE.md #425

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 9, 2016
Merged

Small fixes to RELEASE_PROCEDURE.md #425

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions RELEASE_PROCEDURE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,9 +19,9 @@ The release is prepared as follows:
- In `README.md`, update the version in the Usage section to the new
version.
- Make a pull request.
- Once the PR is merged, tag the merge commit, eg `git tag v0.8.3
- Once the PR is merged, tag the merge commit, e.g. `git tag v0.8.3
$MERGE_COMMIT_SHA1`.
- Push the tag, eg `git push v0.8.3`.
- Push the tag, e.g. `git push origin v0.8.3`.

# Create Release

Expand All @@ -34,7 +34,7 @@ After the release a commit with the following changes is added to the master
branch.

- Add a new Unreleased section header to CHANGELOG.md.
- In `Cargo.toml`, update the version to the next `-dev` version, eg
- In `Cargo.toml`, update the version to the next `-dev` version, e.g.
`v0.8.4-dev`.
- In `Cargo.tml`, revert the libc dependency to its git master branch.
- Commit with a message like "Bump to v0.8.4-dev"
Expand Down