27 Jun
2014
27 Jun
'14
10:40 p.m.
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
9:20 a.m.
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
11:21 a.m.
So far we (Guillaume, christophe and me) addressed clean the mess and
make sure that we can manage the following configuration with versionner
XMLWriter
XMLParser
Pastell
PhExample
OrderPreserving
BitmapCharacterSet
HashTable
Fame
We will probably ask christophe that versionner on release proposes the
choice to use stable or the version.
I will continue
with
Units
MooseAlgoRubric
SmallDude
MetaNool
Maggrite3
Now I will probably have to fork some configurations if I cannot publish
on the repositories.
Stef
1 Jul
1 Jul
11:27 a.m.
Stef, Guillaume and Christophe,
If you fix configurations, you must fix them properly.
I have reviewed 2 configurations now:
XMLWriter is no longer valid for Pharo1.x
XMLParser is no longer valid for Gemstone and does not have a correct development
version.
So please revert all changes, because the way you do this now, will only create a lot of
upset people.
Regards,
Diego
On 28 Jun 2014, at 11:21, stepharo <stepharo(a)free.fr> wrote:
3942
days inactive
3946
days old
15 comments
4 participants
participants (4)
-
Alexandre Bergel -
Diego Lont -
Guillermo Polito -
stepharo