diff options
author | Bowon Ryu <bowon.ryu@samsung.com> | 2019-02-14 17:33:09 +0900 |
---|---|---|
committer | Bowon Ryu <bowon.ryu@samsung.com> | 2019-02-14 17:33:09 +0900 |
commit | 1baac414088e430483b85f702898c8448083bfc2 (patch) | |
tree | 59799dda277ac726617ff1b6ffb4747e775f551a /RELEASING.md | |
parent | b9f425ddd6223cd82b3d35f13fbd060d3c0c0e38 (diff) | |
download | harfbuzz-1baac414088e430483b85f702898c8448083bfc2.tar.gz harfbuzz-1baac414088e430483b85f702898c8448083bfc2.tar.bz2 harfbuzz-1baac414088e430483b85f702898c8448083bfc2.zip |
Imported Upstream version 2.3.1upstream/2.3.1
Diffstat (limited to 'RELEASING.md')
-rw-r--r-- | RELEASING.md | 11 |
1 files changed, 9 insertions, 2 deletions
diff --git a/RELEASING.md b/RELEASING.md index 0aef610..1fd8365 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -8,7 +8,8 @@ HarfBuzz release walk-through checklist: Document them in NEWS. All API and API semantic changes should be clearly marked as API additions, API changes, or API deletions. Document deprecations. Ensure all new API / deprecations are in listed correctly in - docs/harfbuzz-sections.txt + docs/harfbuzz-sections.txt. If release added new API, add entry for new + API index at the end of docs/harfbuzz-docs.xml. If there's a backward-incompatible API change (including deletions for API used anywhere), that's a release blocker. Do NOT release. @@ -25,11 +26,17 @@ HarfBuzz release walk-through checklist: 6. Do "make distcheck", if it passes, you get a tarball. Otherwise, fix things and commit them separately before making release, + Note: Check src/hb-version.h and make sure the new version number is + there. Sometimes, it does not get updated. If that's the case, + "touch configure.ac" and rebuild. Also check that there is no hb-version.h + in your build/src file. Typically it will fail the distcheck if there is. + That's what happened to 2.0.0 going out with 1.8.0 hb-version.h... So, that's + a clue. 7. "make release-files". Enter your GPG password. This creates a sha256 hash and signs it. -8. Now that you have release files built, commit NEWS and configure.ac changes, +8. Now that you have release files, commit NEWS, configure.ac, and src/hb-version.h, as well as any REPLACEME changes you made. The commit message is simply the release number. Eg. "1.4.7" |