28 Jun
2014
28 Jun
'14
9:13 a.m.
On 28/6/14 00:56, Stephan Eggermont wrote:
Steph wrote:
Pressing one button to load one to release and one to commit is not that
complex.
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.
We cannot sign contracts when we maintain deployed systems by just
saving images and preying.
Stef
- 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.
I would recommend against using detailed
numbered versions
for this. That couples you to bug fix patches/updates in the external
libraries and creates a very high versioning effort.
In Seaside we use release3 release30 release31 instead of stable.
Release3 introduced a different packaging, and 31 has some interface
changes. We can now safely promote a new version to stable without
having to update all configurations using seaside.
This reduces the versioning effort, at some loss in reproducibility.
For that, separate snapshots are perfect.
Cheers,
Stephan
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev