Dale I have another question what is the interaction between saying that a given version is stable using a symbolic version and having the development tag in the version? For example I'm migrating merlin and I have stable: spec <symbolicVersion: #'stable'> spec for: #'common' version: '1.5'. development: spec <symbolicVersion: #'development'> spec for: #'common' version: '1.7'. version15: spec <version: '1.5' imports: #('1.0-baseline' )> spec for: #'common' do: [ spec blessing: #'development'. spec description: '1.4 : Replaced PluggableListMorphOfMany by PluggableListMorph'. spec author: 'AlexandreBergel'. spec timestamp: '9/30/2011 09:52'. spec package: 'Merlin' with: 'Merlin-AlexandreBergel.137'. ]. version17: spec <version: '1.7' imports: #('1.0-baseline' )> spec for: #'common' do: [ spec blessing: #'development'. spec description: '1.6 : Removed dependency from BlockContext. Merged with last version'. spec author: 'AlexandreBergel'. spec timestamp: '11/21/2012 08:42'. spec package: 'Merlin' with: 'Merlin-AlexandreBergel.141'. ]. so when do we tag a version as release? because apparently without doing it it still works. Stef