Version numbering


#1

Until now new versions have been released when they’re ready. Trying to decide what makes it in and when that happens has been very arbitrary.

The new plan is to release a new version on the second Monday of every month. Whatever fixes are in by then, and new features which are ready to go will make it in.

We try to stick to Semantic Versioning (since we have no public APIs sometimes there’s a bit of leniency). Typically a new feature will increase the minor version, e.g 2.16.0 to 2.17.0, and bug fixes will increase the patch version, e.g. 2.16.0 to 2.16.1. Any major changes and we’ll go from 2.x to 3.x.

With a regular release schedule though, we’re considering jumping on the band wagon and going for time based version numbers, like Avid have recently done, e.g. 2018.5 for May 2018. Any additional patches in a month would be 2018.5.1.

Any thoughts (he asks talking into the breeze)?