Maybe you could use Versionner for that. If your configuration depends on a #stable version, Versionner can resolve this (check box activated by default) when releasing a new version. Versioner do not have a deep release functionality but it should not be difficult to do if needed; At a time, I created the VSConfigurationGeneratorCommand (in Versionner repo in SH) that follows all the dependencies of a project. Christophe Le 7 déc. 2014 à 21:21, Tudor Girba a écrit :

Le 8 déc. 2014 à 11:09, Tudor Girba a écrit : In Versionner, I assume that the development version is a baseline. If it not, I create a new baseline that becomes the new development version (understand, the current, not yet released version, I work on). Once Versionner has this baseline version, it resolves all kind of symbolic versions to the numbered versions for the release (but still keep the symbolic version in the baseline to use for dev version and next releases). ok, so it should be easy. Versionners uses a command pattern so I assume you could call the ReleaseVersion Command on all the configurations without clicking on the Versionner UI. In this case, the only thing is to check that Versionner is happy with the current configuration. Here is a snippet of code that you can try: | config project | config := ConfigurationOfVersionner. project := MTProject newFromVersion: config project development inConfiguration: config. (VSReleaseDevelopmentVersionCommand target: project devWorkflow for: nil) execute