30 Jun
2014
30 Jun
'14
12:20 p.m.
On 30/6/14 11:32, Diego Lont wrote:
Stef,
Just to be sure I understand our goal properly:
We want to create a stable version with versioner at the end of the week. A stable
version is a version that only gets approved changes (where we can have discussion about
when a change gets approved for moose …).
There are two goals (orthogonal in fact)
- how can we reproduce (reload) an exact version of the same
packages regularly (for example every two weeks)
without pain? While supporting the load latest in dev and freeze model.
- how can we provide a modular infrastructure for everybody
building on top of the moose infrastructure:
MooseIDE + synectique tools should reuse extend the same
infrastructure (called mooseEngines by Doru)?
If we want a snapshot (no bug fixes allowed, 100% reproducible), we should not pollute
the configuration with it. And then we need to have a complete list with all packages.
That means: that we need a snapshot of Pharo too.
Yes but let us start to clean
in front of our door and after we
kick the ass of these pharo people :)
I am currently taking a look at versioner and trying to determine if this workflow would
be acceptable. I tried it on Moose and and Glamour. And this is the problems I have:
- The comment on the release button says: create a new version and a new baseline.
Pressing the button does not create a new baseline (this is good), so please fix the
comment here.
Easy
- Pressing the button suggests it resolves all
symbolic dependencies to actual versions. I want more control here. In Moose the correct
version for Grease is currently #’release1.1’. For Magritte3 this should be #’release3.1’.
Yes we were talking about it with Christophe.
- Dialog is way too small: I cannot see the version
number I am creating.
- The suggested version number is incorrect. I.e. for moose it should be 5.0 or 5.0.0.
For glamour it should be 2.9 or 2.9.0.
For me if all the rest work this is
ok :)
- Looking at the version:
when you want to create a stable version, starting at
a development version, it should also "upgrade the references" to used projects
to stable. Either by using the latest stable, or by creating a new stable version is the
current version is newer. This means that each time it encounters a project that is
“dirty” in the sense I described above, I get a dialog asking me if I want to create new
version and what version number this should be.
I do not get the possibility of adding a good description.
In glamour I get 2 common blocks.
- both common blocks define author, timestamp,
blessing and description.
Problably
These problems should be fixed before we can do this.
We should start and give feedback as you are doing it. Tx. I think that people like
clients so we should use versionner
and contact christophe :)
Diego
On 30 Jun 2014, at 10:32, stepharo <stepharo(a)free.fr> wrote:
Hi
I really think that
- everybody should use versionner :) because now that I use it it is really nice.
- we should use baseline for development during development
- we should use stable or versionned for external packages such as XML.
- with versionner we can release at the end of every week or two in probably some
clicks.
(I can ask christophe for some improvements).
So can we agree on that because we can make sure that we have the advantges that now
and have at the end of every week a versionned released?
Stef
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev