Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How does mcl’s versioning scheme work?

MCL Scheme Versioning
0
Posted

How does mcl’s versioning scheme work?

0

The current setup, which I hope to continue, is this. All releases are identified by a date stamp. For example 02-095 denotes day 95 in the year 2002. This date stamp agrees (as of April 2000) with the (differently presented) date stamp used in all manual pages shipped with that release. For example, the date stamp of the FAQ you are reading is 21 Jan 2006, which corresponds with the MCL stamp 06-021. The Changelog file contains a list of what’s changed/added with each release. Currently, the date stamp is the primary way of identifying an mcl release. When asked for its version by using –version, mcl outputs both the date stamp and a version tag (see below). In early 2002 it occurred to me that mcl should, in addition to time stamps, also have something like version numbers, wanting to use those to indicate noteworthy changes. The April 2002 release got version tag 1.001, in order to celebrate the then-recent addition of this FAQ, mcl’s new logging facility –log, and clmimac to the

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.