33We release by uploading the tarball to GitHub and uploading Ubuntu PPAs.
44
55## Creating the release tarball
6+
67You may want to refer to the section about prerequisites.
78
8- * Check whether there are any open issues to fix while you're doing this.
9- * Update ` Changes.md ` to include specify the new version, today's date, and
10- list relevant changes. Commit this.
11- * Create a new branch off of the latest ` main ` for the release.
12- * Run ` ./dev-bin/release.sh ` to update various files in the distro, our
13- GitHub pages, and creates a GitHub release with the tarball.
14- * Check the release looks good on both GitHub and launchpad.net.
15- * Make a pull request against ` main ` with the changes from the release
16- script.
9+ - Check whether there are any open issues to fix while you're doing this.
10+ - Update ` Changes.md ` to specify the new version, today's date, and list
11+ relevant changes. Commit this.
12+ - Create a new branch off of the latest ` main ` for the release.
13+ - Run ` ./dev-bin/release.sh ` to update various files in the distro, our GitHub
14+ pages, and creates a GitHub release with the tarball.
15+ - Check the release looks good on both GitHub and launchpad.net.
16+ - Make a pull request against ` main ` with the changes from the release script.
1717
1818## PPA
1919
@@ -22,56 +22,53 @@ register a GPG key with that account. You also need to be added to the MaxMind
2222team. Ask in the dev channel for someone to add you. See
2323https://help.launchpad.net/Packaging/PPA for more details.
2424
25- The PPA release script is at ` dev-bin/ppa-release.sh ` . Running it should
26- guide you though the release, although it may require some changes to run on
25+ The PPA release script is at ` dev-bin/ppa-release.sh ` . Running it should guide
26+ you though the release, although it may require some changes to run on
2727configurations different than Greg's machine.
2828
29- Check whether any new Ubuntu versions need to be listed in this script
30- before running it.
29+ Check whether any new Ubuntu versions need to be listed in this script before
30+ running it.
3131
3232You should run it from ` main ` .
3333
3434## Homebrew (optional)
3535
36- Releasing to Homebrew is no longer required as the formulas are easily
37- updated by the end-user using a built-in feature in the tool. These
38- directions remain in case there is a more significant change to the
39- build process that may require a non-trivial update to the formula or
40- in the case where we want the Homebrew version updated promptly for
41- some reason.
36+ Releasing to Homebrew is no longer required as the formulas are easily updated
37+ by the end-user using a built-in feature in the tool. These directions remain in
38+ case there is a more significant change to the build process that may require a
39+ non-trivial update to the formula or in the case where we want the Homebrew
40+ version updated promptly for some reason.
4241
43- * Go to https://github.com/Homebrew/homebrew-core/edit/master/Formula/libmaxminddb.rb
44- * Edit the file to update the url and sha256. You can get the sha256 for the
42+ - Go to
43+ https://github.com/Homebrew/homebrew-core/edit/master/Formula/libmaxminddb.rb
44+ - Edit the file to update the url and sha256. You can get the sha256 for the
4545 tarball with the ` sha256sum ` command line utility.
46- * Make a commit with the summary ` libmaxminddb <VERSION> `
47- * Submit a PR with the changes you just made.
46+ - Make a commit with the summary ` libmaxminddb <VERSION> `
47+ - Submit a PR with the changes you just made.
4848
4949# Prerequisites for releasing
5050
51- * Required packages (Ubuntu Artful): vim git-core dput build-essential
52- autoconf automake libtool git-buildpackage libfile-slurp-perl pandoc
53- dirmngr libfile-slurp-tiny-perl libdatetime-perl debhelper dh-autoreconf
51+ - Required packages (Ubuntu Artful): vim git-core dput build-essential autoconf
52+ automake libtool git-buildpackage libfile-slurp-perl pandoc dirmngr
53+ libfile-slurp-tiny-perl libdatetime-perl debhelper dh-autoreconf
5454 libipc-run3-perl libtest-output-perl devscripts
55- * Install [ gh] ( https://github.com/cli/cli/releases ) .
56- * GitHub ssh key (e.g. in ` ~/.ssh/id_rsa ` )
57- * Git config (e.g. ` ~/.gitconfig ` )
58- * Import your GPG secret key (or create one if you don't have a suitable
59- one)
60- * ` gpg --import /path/to/key `
61- * ` gpg --edit-key KEYID ` and trust it ultimately
62- * Ensure it shows with ` gpg --list-secret-keys `
63- * You need to be invited to the launchpad.net MaxMind organization on your
55+ - Install [ gh] ( https://github.com/cli/cli/releases ) .
56+ - GitHub ssh key (e.g. in ` ~/.ssh/id_rsa ` )
57+ - Git config (e.g. ` ~/.gitconfig ` )
58+ - Import your GPG secret key (or create one if you don't have a suitable one)
59+ - ` gpg --import /path/to/key `
60+ - ` gpg --edit-key KEYID ` and trust it ultimately
61+ - Ensure it shows with ` gpg --list-secret-keys `
62+ - You need to be invited to the launchpad.net MaxMind organization on your
6463 launchpad.net account.
65- * You need your GPG key listed on your launchpad.net account
66- * You can add it in the web interface. It wants the output of
64+ - You need your GPG key listed on your launchpad.net account
65+ - You can add it in the web interface. It wants the output of
6766 ` gpg --fingerprint ` .
68- * Part of the instructions involve having your key published on the
69- Ubuntu keyserver:
70- ` gpg --keyserver keyserver.ubuntu.com --send-keys KEYID `
71- * You'll get an email with an encrypted payload that you need to decrypt
72- and follow the link to confirm it.
73- * Ensure ` dch ` knows your name and email. Refer to its man page for how to
74- tell it this. One way is to set the ` DEBFULLNAME ` and ` DEBEMAIL `
75- environment variables. These should match your GPG key's name and email
76- exactly. This is what gets used in the Debian changelog as well as
77- defines what GPG key to use.
67+ - Part of the instructions involve having your key published on the Ubuntu
68+ keyserver: ` gpg --keyserver keyserver.ubuntu.com --send-keys KEYID `
69+ - You'll get an email with an encrypted payload that you need to decrypt and
70+ follow the link to confirm it.
71+ - Ensure ` dch ` knows your name and email. Refer to its man page for how to tell
72+ it this. One way is to set the ` DEBFULLNAME ` and ` DEBEMAIL ` environment
73+ variables. These should match your GPG key's name and email exactly. This is
74+ what gets used in the Debian changelog as well as defines what GPG key to use.
0 commit comments