-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

On 26/09/15 15:08, Eyal Rozenberg wrote:

What's the relation between the Month+Year release naming scheme (e.g. Jul2015, Oct2014-SP2) and the numeric versions (e.g. 11.19.9)?

The website has a release history page:

https://www.monetdb.org/Documentation/UserGuide/ReleaseNotes

But I haven't found a page discussing the numeric version numbers. I'm not even sure the X.Y.Z format means version.subversion.subsubversion ...

Every time we build a release candidate, we increase the version number before and after. This means that releases are always odd-numbered, and between releases we use even numbers. When we create a new feature release, we increment the middle number and reset the last one to 0 (until the actual build when it is increased to 1). Not all release candidates make it to a release, so the minor numbers don't form a nice sequence of odd numbers. The upshot of this is that if you order the releases on year and month (as is done on the page you pointed to), the middle numbers increase by two for every step. The last number indicates the first and subsequent bug fix releases for that release cycle, but there is no correspondence between SP (from Service Pack) number and the final number in the version number (except that both increase for subsequent releases).

We don't really use the first number. It's been stuck at 11 since 2011.

The rules before 2011 were different and I won't go into them here.

Eyal _______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list

- -- Sjoerd Mullender