mirror of
https://github.com/libevent/libevent.git
synced 2025-01-31 09:12:55 +08:00
Updated ReleaseChecklist (markdown)
parent
5cac8363dc
commit
38e1a9c396
@ -35,15 +35,15 @@ Once the tarball is tested, it's time to put out the release.
|
||||
* `gpg --detach-sign -a /path/to/.tar.gz`
|
||||
* key should be trusted.
|
||||
* list of contributors (actually it should be not just a list, but contributions itselfs)
|
||||
* This can be done using [`[Generate release notes content for a release](https://docs.github.com/en/rest/releases/releases?apiVersion=2022-11-28#generate-release-notes-content-for-a-release)`](https://docs.github.com/en/rest/releases/releases?apiVersion=2022-11-28#generate-release-notes-content-for-a-release) API
|
||||
* This can be done using [`Generate release notes content for a release`](https://docs.github.com/en/rest/releases/releases?apiVersion=2022-11-28#generate-release-notes-content-for-a-release) API
|
||||
* Add a link on the website and on the old releases page.
|
||||
* Send an announcement to libevent-users (outdated?)
|
||||
* ~~Send an announcement to libevent-users~~
|
||||
* Increment the version in the IRC channel topic by telling chanserv `set #libevent topic Welcome to #libevent! The latest release is ${NEW_TAG}.`
|
||||
|
||||
## Part 4: Right after the distribution is done
|
||||
|
||||
* Increment the versions in `configure.in` and `WIN32-Code/event2/event-config.h` to `${NEW_TAG}-dev`, and increment the version numbers there to `0x02001201`. The "-dev" and "01" mean that we are a development version, not the released version.
|
||||
* Add a new empty section for the next version to the changelog.
|
||||
* Increment the versions in `configure.in` to `${NEW_TAG}-dev`, and increment the version numbers there to `0x02001201`. The "-dev" and "01" mean that we are a development version, not the released version.
|
||||
* Add a new empty section for the next version to the ChangeLog.
|
||||
|
||||
## Reference
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user