Skip to content

Mention the libc version changes in RELEASE_PROCEDURE.md #419

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 8, 2016
Merged

Mention the libc version changes in RELEASE_PROCEDURE.md #419

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
3 changes: 3 additions & 0 deletions RELEASE_PROCEDURE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,11 +9,13 @@ some Rust versions counts as a breaking change, and requires a major bump.

The release is prepared as follows:

- Ask for a new libc version if, necessary. It usually is.
- Make a commit with a message like "Release v0.8.3" with the following
changes:
- In `CHANGELOG.md`, rename the Unreleased section to the new version
followed by the date of the release.
- In `Cargo.toml`, update the version to the new version.
- In `Cargo.toml`, change the libc dependency to the latest version.
Copy link
Member

@kamalmarhubi kamalmarhubi Sep 8, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add a mention that before committing we should make sure it builds and tests. well I guess this would be picked up by travis when the PR is made.

Copy link
Contributor Author

@fiveop fiveop Sep 9, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had the same idea. It's on my todo list!

- In `README.md`, update the version in the Usage section to the new
version.
- Make a pull request.
Expand All @@ -34,5 +36,6 @@ branch.
- Add a new Unreleased section header to CHANGELOG.md.
- In `Cargo.toml`, update the version to the next `-dev` version, eg
`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"
- Make a pull request.