Yes, it would be great to have a configuration version for each change. But, for some reason, it is hard to have in moose. I spent quite some days trying to fix this
Did you try to do it with versionner? Without a tool this is a hell. Now I think that it will work with versionner. In one click I can release a versionned solution. We tried with some configurations of the moose ecosystems and it look like this is working. So I will continue the experience to see if this is working, snaphotcello is not a good solution (it is what is working) but as mentioned Stefan it flattens and pollutes the configuration.
Now if people shout and I will just fork the configurations. Because this is not acceptable that we cannot reload one version of Moose. We could have a release process as follows
- develop on baseline - release every friday on versions
I do not see why this is not possible.
Stef
Alexandre
Le 27-06-2014 à 16:40, stepharo stepharo@free.fr a écrit :
Hi
today we brainstormed and I will send a sequence of emails to discuss what we decided and started to do.
One of our goal is to check if we can use versionner to manage all the configurations. It looks possible.
The first things we started to do is - make sure that all the configurations of external libraries are correctly defined. In particular we made sure that a version does not depend on a stable one but on a version specific.
- We think that Moose should not depend on baseline of external tools, because we need real reproduceability. - We started to produce configurations with versionner that do not depend on stable but on exact versions. - I will continue to see if we can use Versionner because it would simplify the release.Stef _______________________________________________ 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