19 Jul
2016
19 Jul
'16
11:46 a.m.
Hi,
If we look at the details of Moose we will see that we have very few modifications in the
core components such as Core, Famix, Fame, Glamour, PetitParser. These are highly stable
since years. For example, the proof for that is that I can perfectly load models, parsers
and custom browsers that are more than 5 years old.
Where there is volatility is at the level of Roassal and GT. For the GTInspector, the
public API is stable since about 3 years, and for GTSpotter since 1 year. Roassal also
appears to have reached a stable state since about 1 year at the level of commonly used
builders.
At least from a macroscopic view, things are not so bad, actually. But, perhaps there are
problems in the details. We can address them if they are announced publicly. Let’s find
them and fix them.
Cheers,
Doru
On Jul 19, 2016, at 1:32 AM, Esteban Lorenzano
<estebanlm(a)gmail.com> wrote:
Hi,
Eventually, all systems needs more stability (even Pharo).
Nobody can run a business with a rabbit running away constantly.
Esteban
ps: I think Seaside guys have done a very good job with maintainability and releasing of
products, we should take them as a model to build stable products.
--
www.tudorgirba.com
www.feenk.com
"Be rather willing to give than demanding to get."
On 19 Jul 2016, at 00:09, Stephan Eggermont
<stephan(a)stack.nl> wrote:
On 18/07/16 22:47, stepharo wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev No it does not. Pharo 60 is alpha. Moose does not
have to use an alpha version of Pharo.
That's a choice with advantages and
disadvantages. Seaside moves more slowly
and is used in production systems. That's why it runs on stable releases of Pharo
and is sometimes not up to date with alpha's. You're saying Moose is used by
Synectique in production so needs more stability?
A lot of the visualisation and gui work depends on parts that are supposed to be changing
in
Pharo 6, so we need a way to both move ahead and keep production systems stable.
In Seaside we have several versions available at the same time. That could work for
Moose too, and that has consequences for dependency maintenance. It is just more work,
and someone has to do that work.
Stephan
_______________________________________________
Moose-dev mailing list
Moose-dev(a)list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev