[HarfBuzz] harfbuzz: Branch 'master' - 3 commits

Behdad Esfahbod behdad at kemper.freedesktop.org
Mon Oct 23 17:10:39 UTC 2017 

 RELEASING.md  |   69 +++++++++++++++++++++++++++++++++++++++++-----------------
 harfbuzz.doap |    2 -
 2 files changed, 50 insertions(+), 21 deletions(-)

New commits:
commit 61d1c60a1c555c58205964df4e449ee57125a739
Author: Behdad Esfahbod <behdad at behdad.org>
Date:   Mon Oct 23 13:10:21 2017 -0400

    [RELEASING] Format

diff --git a/RELEASING.md b/RELEASING.md
index 8fd8a33e..83302c7f 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -1,37 +1,66 @@
 HarfBuzz release walk-through checklist:
 
 1. Open gitk and review changes since last release.
-   * `git diff $(git describe | sed 's/-.*//').. src/*.h` prints all public API changes.
 
-     Document them in NEWS,  All API and API semantic changes should be clearly
-     marked as API additions, API changes, or API deletions.
-     If there's a backward-incompatible API change (including deletions for API used anywhere),
-     that's a release blocker.  Do NOT release.  Document deprecations.
-2. Based on severity of changes, decide whether it's a minor or micro release number bump,
+   * `git diff $(git describe | sed 's/-.*//').. src/*.h` prints all public API
+     changes.
+
+     Document them in NEWS.  All API and API semantic changes should be clearly
+     marked as API additions, API changes, or API deletions.  Document
+     deprecations.
+
+     If there's a backward-incompatible API change (including deletions for API
+     used anywhere), that's a release blocker.  Do NOT release.
+
+2. Based on severity of changes, decide whether it's a minor or micro release
+   number bump,
+
 3. Make sure you have correct date and new version at the top of NEWS file,
+
 4. Bump version in configure.ac line 3,
+
 5. Do "make distcheck", if it passes, you get a tarball.
    Otherwise, fix things and commit them separately before making release,
-6. "make release-files". Enter your GPG password again.  This creates a sha256 hash and signs it.
-7. Now that you have a tarball built, commit NEWS and configure.ac changes.  The commit message
-   is simply the release number.  Eg. "1.4.7"
-8. Tag the release and sign it: Eg. "git tag -s 1.4.7 -m 1.4.7".  Enter your GPG password.
+
+6. "make release-files".  Enter your GPG password.  This creates a sha256 hash
+   and signs it.
+
+7. Now that you have release files built, commit NEWS and configure.ac changes.
+   The commit message is simply the release number.  Eg. "1.4.7"
+
+8. Tag the release and sign it: Eg. "git tag -s 1.4.7 -m 1.4.7".  Enter your
+   GPG password again.
+
 9. Build win32 bundle.
-   1. Put contents of [this](https://drive.google.com/open?id=0B3_fQkxDZZXXbWltRGd5bjVrUDQ) on your `~/.local/i686-w64-mingw32`
-   2. Run `./MING32 --with-uniscribe` script (available below) to config harfbuzz with mingw
-   3. make
-   4. `./UPDATE.sh` (available below)
-10. Copy all artefacts to users.freedesktop.org and move them into `/srv/www.freedesktop.org/www/software/harfbuzz/release`
-    There should be four files.  Eg.:
+
+   a. Put contents of [this](https://drive.google.com/open?id=0B3_fQkxDZZXXbWltRGd5bjVrUDQ) on your `~/.local/i686-w64-mingw32`,
+
+   b. Run `./MING32 --with-uniscribe` script (available below) to configure harfbuzz with mingw in a subdirector (eg. winbuild/),
+
+   c. make
+
+   d. Back in the parent directory, run `./UPDATE.sh` (available below) to build win32 bundle.
+
+10. Copy all artefacts to users.freedesktop.org and move them into
+    `/srv/www.freedesktop.org/www/software/harfbuzz/release` There should be four
+    files.  Eg.:
  ```
 -rw-r--r--  1 behdad eng 1592693 Jul 18 11:25 harfbuzz-1.4.7.tar.bz2
 -rw-r--r--  1 behdad eng      89 Jul 18 11:34 harfbuzz-1.4.7.tar.bz2.sha256
 -rw-r--r--  1 behdad eng     339 Jul 18 11:34 harfbuzz-1.4.7.tar.bz2.sha256.asc
 -rw-r--r--  1 behdad eng 2895619 Jul 18 11:34 harfbuzz-1.4.7-win32.zip
 ```
-11. While doing that, quickly double-check the size of the .tar.bz2 and .zip files against their previous releases to make sure nothing bad happened.  They should be in the ballpark, perhaps slightly larger.  Sometimes they do shrink, that's not by itself a stopper.
-12. Push the commit and tag out: "git push --follow-tags".  Make sure it's pushed both to freedesktop repo and github.
-13. Go to GitHub release page [here](https://github.com/behdad/harfbuzz/releases), edit the tag, upload artefacts and NEWS entry and save.
+
+11. While doing that, quickly double-check the size of the .tar.bz2 and .zip
+    files against their previous releases to make sure nothing bad happened.
+    They should be in the ballpark, perhaps slightly larger.  Sometimes they
+    do shrink, that's not by itself a stopper.
+
+12. Push the commit and tag out: "git push --follow-tags".  Make sure it's
+    pushed both to freedesktop repo and github.
+
+13. Go to GitHub release page [here](https://github.com/behdad/harfbuzz/releases),
+    edit the tag, upload artefacts and NEWS entry and save.
 
 
 ## MING32
commit 6a2e1649debd992211bf96ef80d075d2d04a49ed
Author: Behdad Esfahbod <behdad at behdad.org>
Date:   Mon Oct 23 13:01:34 2017 -0400

    [doap] Switch to github issues
    
    https://github.com/behdad/harfbuzz/pull/575#issuecomment-338514596

diff --git a/harfbuzz.doap b/harfbuzz.doap
index d2896ebe..1e3e9abc 100644
--- a/harfbuzz.doap
+++ b/harfbuzz.doap
@@ -13,7 +13,7 @@
   <!--download-page
   rdf:resource=""/-->
   <bug-database
-  rdf:resource="http://bugs.freedesktop.org/enter_bug.cgi?product=harfbuzz"/>
+  rdf:resource="https://github.com/behdad/harfbuzz/issues" />
 
   <maintainer>
     <foaf:Person>
commit 8a898c1929cf7ffc9b0011461b34281ecc98705c
Author: Behdad Esfahbod <behdad at behdad.org>
Date:   Mon Oct 23 13:00:36 2017 -0400

    [RELEASING] Minor
    
    https://github.com/behdad/harfbuzz/pull/575

diff --git a/RELEASING.md b/RELEASING.md
index db50ed94..8fd8a33e 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -31,7 +31,7 @@ HarfBuzz release walk-through checklist:
 ```
 11. While doing that, quickly double-check the size of the .tar.bz2 and .zip files against their previous releases to make sure nothing bad happened.  They should be in the ballpark, perhaps slightly larger.  Sometimes they do shrink, that's not by itself a stopper.
 12. Push the commit and tag out: "git push --follow-tags".  Make sure it's pushed both to freedesktop repo and github.
-13. Create a GitHub release [here](https://github.com/behdad/harfbuzz/releases), upload artefacts and NEWS entry on it also.
+13. Go to GitHub release page [here](https://github.com/behdad/harfbuzz/releases), edit the tag, upload artefacts and NEWS entry and save.
 
 
 ## MING32
@@ -57,7 +57,7 @@ export LDFLAGS=-L$HOME/.local/$target/lib
 export PKG_CONFIG_LIBDIR=$HOME/.local/$target/lib/pkgconfig
 export PATH=$HOME/.local/$target/bin:$PATH
 
-../configure --build=`~/script/config.guess` --host=$target --prefix=/home/behdad/.local/$target "$@"
+../configure --build=`../config.guess` --host=$target --prefix=$HOME/.local/$target "$@"
 ```
 
 ## UPDATE.sh

More information about the HarfBuzz mailing list