GitHub/libevent
1
0
Fork 0
mirror of https://github.com/libevent/libevent.git synced 2025-01-31 09:12:55 +08:00
Code Issues Packages Projects Releases Wiki Activity

Updated ReleaseChecklist (markdown)

Azat Khuzhin 2022-11-21 00:38:52 +03:00
parent ae474f2cdc
commit 9ed559592c
1 changed files with 0 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
ReleaseChecklist.md

@ -19,7 +19,6 @@ I wrote up this document as a checklist of stuff to do before putting out a Libe
* Generate the changelog using [`changelog.py`](https://github.com/libevent/libevent/blob/master/extra/release/changelog.py)
* Update the credits using [`update-contributors.sh`](https://github.com/libevent/libevent/blob/master/extra/release/update-contributors.sh)
* Increment the version number and version string in configure.in. The next version should be 2.0.18-stable; the numeric version should be `0x02001200` (That is, 02 00 12 00 : the first three bytes are the version number, and the final 00 byte means that this is the actual release of 2.0.18, not some development version between 2.0.18 and 2.0.19.)
* Increment the version number and string in `WIN32-Code/nmake/event2/event-config.h`. (These are not automatically changed by configure.in, since we don't use `autoconf` with `nmake`.)
* Increment the `libtool` VERSION_INFO in `Makefile.am`. See `Makefile.am` for full instructions on what to do in other cases.
* Increment the versions in `CMakeLists.txt`.
* Run `make distcheck` again to make sure nothing above messed us up. Do this one on the system with the most up-to-date autotools you have.