Moose, including Mondrian and Spy load well in Pharo 1.1. No big effort were needed for this. I haven't seen that many problems in porting applications to 1.1. The only thing I bumped into so far, are initialExtent (but apparently this was fixed) and tool registration. Alexandre On 16 Mar 2010, at 07:50, Stéphane Ducasse wrote:
+ 1 end of march for a code freeze would be great. Stef
On Mar 16, 2010, at 10:19 AM, Marcus Denker wrote:
Hi,
Now with 1.0 done, I think we should think about freezing 1.1.
The main reason of course is that 1.1 is *far more pleasent* to use than 1.0. The other thing is that 1.1 did change quite some things that have impact on external code (Preferences, as an example).
So I think we should
-> start slowing down on 1.1 (Stef suggested that already) -> start polishing (tests...) -> start to look at the Dev image. -> Official code freeze end of March. -> Release if possible end of April (this of course depends on the state of things).
Any reasons against?
Marcus
-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.