Please sign in to comment.
'rake release' creates font with generated version number ♫
When a designer uses a font, it is critical that she or he can identify the particular version unambigously. We also want to make sure that designers can use our development snapshots. That’s why for every commit there needs to be a potential version number. We could, theoretically, use git hashes as identifiers. However, they look cryptic to end users, and they don’t provide information about the chronology of versions. Taking cues from the semver.org spec, our version number takes a form X.Y.Z., where X is the major version, Y the minor version, and Z the patch version. Minor versions have a defined set of goals, and get tagged in Git, we started with 0.0.0 and we are now working towards 0.1.0. Our patch versions, are built from the source tree after each commit. So from the first commit after 0.1.0 we can build 0.1.1. To do a release, we use the ''git describe'' command to tell us the last tag and the number of commits since that tag, whereupon we base a version number that we bake into the ufo and thus into the generated font.
- Loading branch information...