On Mar 16, 2010, at 4:01 51PM, Stéphane Ducasse wrote:
for code 1.1 I would like to be able to remove Preferences.
Stef
Personally, I think it's rather important to have a stable release where both are in, but where the Preferences adding raises deprecations, and the browser removed. Then, in the future, when someone tries to port an old project with Preferences, we can say "Load it into a 1.1 image and fix it there". Without the availability of such a middle step, it'd be somewhat of a leap getting the code up to date. (unless you do it offline, but that's not really the smalltalk way, is it?) Cheers, Henry
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