On a slightly different topic, Alistair Grant ran into a bug involving Metacello and how it semantic version numbers[7] a couple

months ago and this release includes a bug fix ... the bug was related to the fact that the parser was too lenient and did throw an

error for some forms of invalid Semantic version numbers ... with this fix an error is thrown ... of course it is entirely possible that there are ConfigurationOfs out in the wild that "depend upon the old behavior" so if you get an "invalid version number" error while working with a configuration and discover that it is not practical to redefine the version numbers to conform to the semantic version number format then you can add the following method to the ConfigurationOf and the old, buggy version of the parser will be used:

�� versionNumberClass
������ ^ MetacelloOldSemanticVersionNumber