17 Feb
2011
17 Feb
'11
4:24 p.m.
Another important topic. Now that each version of moose will be made explicit.
How do we integrate them in Hudson?
If there is a guaranty (that we do not have now) that a version recursively depend on
fixed version (and not default), then there is no need to build them.
Cheers,
Alexandre
On 17 Feb 2011, at 11:47, Alexandre Bergel wrote:
Hi!
I am working on using MetacelloBrowser for Moose. The goal is to make explicit all the
versions of Moose and keep a record of them. Each new commit of one of the Moose package
or each new version of a dependent library should produce a new version of Moose. I guess
we all want that. I use this for Mondrian and I am quite happy.
I propose to use a simple version numbering. Something like 4.3.X where X will increment
at each new commit made in one of the packages of Moose.
I have produced version 4.3.1. It loads in the latest Pharo 1.2. However, it contains a
bit of hack. I believe that a Configuration version should not depend on the default
baseline.
It still contains:
spec
project: 'MooseAlgos for Moose' with: '2.2';
project: 'PetitParser for Moose' with: 'default';
project: 'DSM for Moose' with: 'default';
project: 'Glamour for Moose' with: '2.1';
project: 'Mondrian for Moose' with: 'default';
project: 'SmallDude for Moose' with: 'default';
project: 'Merlin' with: '1.0';
project: 'RPackage' with: 'default'.
If you agree with this, I can produce a fix version for each of these package. Does it
goes in the right direction? I already produce Version 2.1 of Glamour.
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.