On 28/6/14 11:22, Stephan Eggermont wrote:
Steph wrote:
If necessary we will build a tool that does is automatically. Releasing a real fixed version is important. I'm sorry stefan but we want FULL reproducibility.
A snapshot is a separate concept from a configuration. Building a separate tool to create snapshots is a good idea. A snapshot should know about a configuration but not the other way around.
The problem we run into is that we use configuration A that depends on version B1 of a configuration, and another configuration C that depends on version B2. So we need to create a new configuration version of A, even though A is not interested in C.
I know that.
To make that work dependent configurations would need to change at the sum of change rate of all the configurations they are depending on. As long as we don't have global flow (in the lean sense) that is unworkable.
this is what we will see. Again there is a difference between development and release. When you develop you want to always get the latest (and certainly not on project you have no control over). When you version clicking on a tool like versionner should work.
Stef
We cannot sign contracts when we maintain deployed systems by just saving images and preying.
Yes. Make snapshots. And a good experiment to get tools improved would be to add a ConfigurationOfPharo build that creates a version for each build. I suspect some scalability issues.
Stephan _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev