24 Mar
2013
24 Mar
'13
9:48 p.m.
Hi doru
I would be a bit cautious.
I would start with a CI job that runs Moose on 30a.
Then I would release Moose much much more often now that we can freeze so that I would
build
stable point of Moose in 2.0.
Then migrate to Pharo3.0 when it makes sense but I would not move on 3.0a right now.
Yes 30 will be good but first I would see how it keeps green tests.
Stef
Moose 4.8 works on Pharo 2.0. The only problem I
noticed is that CMD+s does not work in the text areas anymore.
So, before we start doing major things (such as removing Mondrian, redoing EyeSee on top
of Roassal, adding Athens support, adding Traits into FAMIX, or enhancing GToolkit), I
have a little proposition.
After a bit more testing I would like to release 4.8, and then move Moose 5.0 to Pharo
3.0 as soon as possible.
Here is why:
- Moose can benefit from enhancements from Pharo, and we can only influence and
contribute if we work closely with the Pharo latest version
- Moose should offer tools for Pharo development
- We are a small community that should work more closely together
What do you think?
(If you disagree, please also indicate the amount of effort you would like to invest in
Moose in the near future)
Cheers,
Doru
--
www.tudorgirba.com
"Every successful trip needs a suitable vehicle."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev