Stef, Rio and non-core packages reminds me of #newForWin32, which is missing a #new, so it answers the class instead of an instance. This breaks the installation on Windows, and it also leads to a broken image on Windows if it is not corrected on another OS.
I _think_ I reported it. Bill -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Stéphane Ducasse Sent: Saturday, October 10, 2009 3:02 AM To: Pharo Development Subject: [Pharo-project] Preparing the sprint Hi guys I would like to have several kinds of tasks so that people can pick up Now let me know if you have other points - fixing stuff for 1.0 - integrating pending for 1.1 - OB related UI - fixing more elaborated points for 1.1 - package structure - improving the system (smalllint?) - Popup discard - TextEditor from Squeak/CUIS - ToolBuilder changes - checking squeak fixes - Preparing release candidate - fixing _ - free fonts - Dreaming about the future - filesystem? Rio/ - newcompiler - true package - management of noncore packages - browsers - release/integration process BTW what is costing me most of my time is cleaning the inbox. Can we script that because moving these files is a pain. Syeg _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
