<html> <head> <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> <div class="moz-cite-prefix">On 23-09-13 16:16, Dave Crossland wrote: </div> <blockquote cite="mid:CAEozd0ye+=hADr2O-tRSyLiecL+gn7xYtzWGFW7SpHd7QU8Ldg@mail.gmail.com" type="cite"> <pre wrap="">On 23 September 2013 15:52, Eric Schrijver <a class="moz-txt-link-rfc2396E" href="mailto:eric@authoritism.net"><eric@authoritism.net></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">How do other Open Source font projects deal with their version numbers? Any best practices? </pre> </blockquote> <pre wrap=""> semver.org </pre> </blockquote> I’m aware of semver.org—that’s where I picked up the terminology Major, Minor, Patchversion. At the same time, actually following semver is rather difficult because I’m not sure its software concepts are easy mappable to fonts: <meta http-equiv="content-type" content="text/html; charset=UTF-8"> <ol style="margin: 0px; padding: 0px 0px 0px 1.5em; color: rgb(0, 0, 0); font-family: Arial; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 21px; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"> <li>MAJOR version when you make incompatible API changes,</li> <li>MINOR version when you add functionality in a backwards-compatible manner, and</li> <li>PATCH version when you make backwards-compatible bug fixes.</li> </ol> *Any* change to a font could be considered an incompatible API change (i.e. incompatible with existing designs that use the font). Of course there are some additions that could be considered to be backwards-compatible, like adding extra glyphs… But I think what version numbers mean need to be a bit reimagined for fonts. Like I said, for me it would be more like: 1. MAJOR version constitutes a coherent set of design goals 2. MINOR version constitutes a discrete goal obtained in pursuing these design goals 3. PATCH version constitutes incremental progress toward design goals I can expand on this, of course :) But what I’m interested in is—what kind of versioning systems are people using in the wild? Are you actually using SEMVER with Google, Dave? </body> </html>