Versioner cannot currently be used to make the switch from Pharo 3 to Pharo 4. It also cannot be used to maintain Moose versions for both. If you want to be able to maintain versions delivered to customers, you'll need the platform support and need to be able to DRY configurations. The delivered configuration is unlikely to load in a current Pharo image, so it needs a dependency on a ConfigurationOfPharo version Stephan