summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEdward Thomson <ethomson@edwardthomson.com>2018-06-09 18:24:27 +0100
committerEdward Thomson <ethomson@edwardthomson.com>2018-06-09 18:24:27 +0100
commit5e53f216dc33fd102d1acdef496b0972fb6d75df (patch)
tree3a59e8cdc4c5a6ebfdc965c35001613024e68929
parent5cd5f7bd3c5bf8c0d0124e2bdc9b02a27c77b2eb (diff)
downloadlibgit2-5e53f216dc33fd102d1acdef496b0972fb6d75df.tar.gz
docs: update release steps to include clib manifest
We've introduced a manifest for the clib version system that includes a version number; we should update it at release time to correspond with the version number in the header.
-rw-r--r--docs/release.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/release.md b/docs/release.md
index 42f032b12..9c5b6a7ca 100644
--- a/docs/release.md
+++ b/docs/release.md
@@ -10,7 +10,8 @@ We aim to release once every six months. We start the process by opening an issu
Let's release v0.X, codenamed: <something witty>
- - [ ] Bump the versions in the headers
+ - [ ] Bump the versions in the headers (`include/git2/version.h`)
+ - [ ] Bump the versions in the clib manifest (`package.json`)
- [ ] Make a release candidate
- [ ] Plug any final leaks
- [ ] Fix any last-minute issues
@@ -27,6 +28,7 @@ Preparing the first release candidate includes updating the version number of li
- CHANGELOG.md
- include/git2/version.h
+- package.json
As soon as the pull request is merged, the merge commit shall be tagged with a lightweight tag.