On Thu, Dec 22, 2005 at 11:26:40AM -0800, Chris Muller wrote:
Hi, I have also been thinking about this. While there is a #magmaVersion which returns simply an Integer, this is used primarily to check against legacy files. i.e., if there is no format change for a new release, I don't increment it.
It would seem useful to have another human-consumable versionString. To this end I have considered
"1.0" to be the functionality included right now "1.1" (real soon now) which interfaces to the security module and "1.2" (vaporware) to be the one which includes security AND the import/export replication feature
It would be real great if these could be file-compatible with each other but I don't know whether that will be possible yet.
Also, as incremental enhancements/bug fixes, each of these would be suffixed with "r1", "r2", etc.
If you want to get fancy about it, Craig Latta's naming convention for versions is worth a read. It seems sensible to me, and has held up well over time.
http://netjam.org/smalltalk/versions.html
Dave