From e9ede5d78f009e98207aec75326c798b6ee77f5c Mon Sep 17 00:00:00 2001 From: Philipp Matthias Schaefer Date: Thu, 8 Sep 2016 21:22:17 +0200 Subject: [PATCH] Mention the libc version changes in RELEASE_PROCEDURE.md --- RELEASE_PROCEDURE.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/RELEASE_PROCEDURE.md b/RELEASE_PROCEDURE.md index 80972d5b04..ba107cb558 100644 --- a/RELEASE_PROCEDURE.md +++ b/RELEASE_PROCEDURE.md @@ -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. - In `README.md`, update the version in the Usage section to the new version. - Make a pull request. @@ -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.