16 Oct
2012
16 Oct
'12
4 p.m.
On Oct 15, 2012, at 8:28 AM, Tudor Girba wrote:
Hi,
We have to think about releasing Moose 4.7 and moving to Pharo 2.0.
There are several reasons why the move to 2.0 would make sense:
1. Athens is coming. We have a major interest in this technology and we need to get on it
as soon as possible.
I passed the mail to igor ;D
He is really pushing athens in this moment.
2. The environment moved to RPackage entirely.
3. Pharo needs users.
oh yes!
Before moving to Pharo 2.0, we need to release a robust 4.7. There are still some open
points:
http://code.google.com/p/moose-technology/issues/list?can=2&q=milestone…
The most pressing ones are:
Issue 799: Editing code in Glamour must be faster
Issue 851: Create a stable version for Moose and all its subparts
With reloader, you can get a list of pair
repository * package versions
that you can reload in 1.4.
I tried it for synectique. If you want I can do it for Moose itself (Moose was included in
the synectique try).
Issue 853: ConfigurationOfMoose should be split to
reflect core vs suite
What do you mean?
What would be good is to revisit the configurations.
Another area to look into is the cleaning of the FAMIX navigation. Right now it's a
mess in there. We should probably remove most of the hardcoded methods and rely on Chef.
Any taker?
My idea is to target a release this year. Input is more than welcome :)
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev