Skip to content

Making a release

Jump to bottom
Dave Crossland edited this page Mar 12, 2015 · 9 revisions

FontForge's versioning conventions are a bit unconventional right now, following a YYYYMMDD format.

Checkout the sources that you would like to tag as a release add a tag for the name of the release push to the main repository

$ git checkout a7e7ae987;
$ git tag -a 20150210; 
$ git push --tags origin;

Then go to the tags page for FontForge on GitHub, https://github.com/fontforge/fontforge/tags, and add a release note for the new tag.

This release fixes X, Y, Z and adds A, B C.

  • Windows package
  • Mac package
  • Mac Homebrew can also install this release
  • Ubuntu and Debian packages are available from https://launchpad.net/~fontforge/+archive/ubuntu/fontforge
  • Source package fontforge-20150228.tar.gz and fontforge-20150228.spec file below are designed to include all dependencies not available from the standard repositories of the target system since some build platforms block Internet access (but allow local access to package repositories). If the GitHub tarball (or sources from git) compile properly in your target build system, there is no compelling reason to use this release tarball. gnulib is enormous and is available in standard repositories, but included here because the versions available from most package repositories omit certain features that FontForge uses.

Be sure to check the pre-release checkbox, so that these packages can be successfully built and uploaded to the release:

  • Windows installer
  • Mac app
  • self-contained tarball for build systems without net access, and spec file

Then the status can be changed to a full release.

Post-release

After making the release:

Clone this wiki locally