@@ -14,6 +14,8 @@ The release is prepared as follows:
14
14
changes:
15
15
- In ` CHANGELOG.md ` , rename the Unreleased section to the new version
16
16
followed by the date of the release.
17
+ - Add a new Unreleased section header to ` CHANGELOG.md ` with the four
18
+ Added, Changed, Fixed, and Removed sections added.
17
19
- In ` Cargo.toml ` , update the version to the new version.
18
20
- In ` Cargo.toml ` , change the libc dependency to the latest version.
19
21
- In ` README.md ` , update the version in the Usage section to the new
@@ -30,11 +32,7 @@ The release is prepared as follows:
30
32
31
33
# After Release
32
34
33
- After the release make a pull request with the following changes:
34
-
35
- - Add a new Unreleased section header to ` CHANGELOG.md ` .
36
- - In ` Cargo.toml ` , update the version to the nextversion, e.g.
37
- ` v0.8.4 ` .
38
- - In ` Cargo.toml ` , revert the libc dependency to its git master branch.
39
- - Make a commit of the above changes with a message like "[ skip ci] Bump to v0.8.4"
40
- - This skips continuous integration testing on the build bots and Travis CI
35
+ Once a release is done, all that's left is to change the ` libc ` version
36
+ back to using the version from git. So make a pull request containing a
37
+ simple commit entitled "Start the next dev cycle" that changes the ` libc `
38
+ dependency in ` Cargo.toml ` to using it from git master.
0 commit comments