Skip to content

Commit 1b6fb55

Browse files
committed
doc: clarify process for patch releases
1 parent 7b7503d commit 1b6fb55

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

doc/release-process.md

+4-2
Original file line numberDiff line numberDiff line change
@@ -16,8 +16,10 @@ This process also assumes that there will be no minor releases for old major rel
1616

1717
1. Open a PR to the master branch with a commit (using message `"release: prepare for $MAJOR.$MINOR.$PATCH"`, for example) that
1818
* finalizes the release notes in [CHANGELOG.md](../CHANGELOG.md) (make sure to include an entry for `### ABI Compatibility`),
19-
* updates `_PKG_VERSION_*` and `_LIB_VERSION_*` and sets `_PKG_VERSION_IS_RELEASE` to `true` in `configure.ac`, and
20-
* updates `project(libsecp256k1 VERSION ...)` and `${PROJECT_NAME}_LIB_VERSION_*` in `CMakeLists.txt`.
19+
* sets `_PKG_VERSION_IS_RELEASE` to `true` in `configure.ac`, and
20+
* if this is not a patch release
21+
* updates `_PKG_VERSION_*` and `_LIB_VERSION_*` in `configure.ac` and
22+
* updates `project(libsecp256k1 VERSION ...)` and `${PROJECT_NAME}_LIB_VERSION_*` in `CMakeLists.txt`.
2123
2. After the PR is merged, tag the commit and push it:
2224
```
2325
RELEASE_COMMIT=<merge commit of step 1>

0 commit comments

Comments
 (0)