-
Notifications
You must be signed in to change notification settings - Fork 427
Making a release
Peter Eisentraut edited this page Dec 12, 2022
·
32 revisions
- Check out the
pgbouncer
andpgbouncer.github.io
repositories next to each other. - Make sure that you can build both pgbouncer and the web site locally.
- Check that Cirrus CI and AppVeyor are building successfully.
- Update libusual if changes are pending.
- Update the following files with new version number and date:
NEWS.md
- version number in
configure.ac
git commit -m 'vX.Y.Z'
git tag pgbouncer_X_Y_Z
- Build the release tarball:
git clean -fdx; ./autogen.sh; ./configure; make dist
- Copy release tarball into a new directory under
downloads/
. (This is the canonical location of the release tarball. The GitHub releases feature is secondary.) -
make doc
(This updates_data/downloads.json
,changelog.md
, and other files, and copies over documentation files from thepgbouncer
repository.) - Write a release post in
_posts
. -
git commit -a -m 'vX.Y.Z'
(no tag) - When satisfied, push all the changes in both repositories.
- Make a GitHub release from the tag. (Copy the already Markdown-formatted part of the changelog from
NEWS.md
. But adjust the line breaks, since GitHub interprets them differently.)
For consistency, announcements should link to the release post on the web site and use the text from the post.