It's hard to think this one through without use cases… On the positive, it may be better to mark every numbered version as #'release' and then use semantic versioning to update if you run into trouble (i.e. release 2.0 and if you have to adjust the packages, 2.0.1). Because now that we have stable versions, there seem to be two competing systems - the tag of the numbered version and the symbolic version. In practice, it looks like a lot of numbered versions never get updated (i.e. versions that are symbolic #'stable' are not #'release' in the version spec)
----- Cheers, Sean -- View this message in context: http://forum.world.st/pharo-3-0-versionner-and-creating-a-development-version-tp4742756p4742849.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
