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 :

Ok. Let's give this a shot. So, we would need versions in all configurations that point to the concrete number or #stable of the other configurations.

Cheers,

Doru

On Sun, Dec 7, 2014 at 2:54 PM, Stephan Eggermont <stephan@stack.nl> wrote:

>No. We will create a stable version of each configuration that will be versioned based on the numbering of each configurations.

Last time I was not so happy with the results of using numbered configurations. The release version stopped being usable about

a week after the release date. With a symbolic name we can fix critical bugs that stop newcomers from using Moose.

Last time we had a development version that didn't work because of significant Pharo3 surgery and a stable version that

couldn't be build because of numbered configurations. If possible I would like to avoid that this time.

Stephan

_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--

www.tudorgirba.com

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev