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 The Libevent Release Checklist (markdown)

nmathewson 2012-02-10 21:51:04 -08:00
parent cb5c8628a0
commit 28ee6ce193
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ReleaseChecklist.md

@ -27,8 +27,8 @@ TEST!
* Generate the credits. I like to use " git log ${LAST_TAG}..HEAD --pretty='format:%an' > names " for everybody whose name is on a commit, then " git log ${LAST_TAG}..HEAD | perl -ne 'if (/([A-Z]\w* [A-Z]\w*)/) { print "$1\n"; }' >> names " to get all the namelike sequences in the log. Then I use a sort -k2 | uniq pipeline to sort and uniqueify them. These names get stuck in the list in the README, and in the announcement. {NOTE: The perl snippet above is }
* 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/event2/event-config.h. (These are not automatically changed by configure.in, since we don't use autoconf with msvc.)
* Increment the libtool VERSION_INFO in Makefile.am See Makefile.am for full instructions on what to do in other cases.
* Run "make distcheck" again to make sure nothing above messed us up.
* Increment the libtool VERSION_INFO in Makefile.am. See Makefile.am for full instructions on what to do in other cases.
* 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.
* Upload the resulting tarball somewhere volatile; tell people to try it out.
## Part 3: The point of no return