On Jan 9, 2010, at 8:39 PM, Miguel Enrique Cobá Martinez wrote:
Hi Mariano,
good job. Some feedback.
The installScript has unused variables and your proxy settings exposed. Maybe this should be deleted from the final build.
Shouldn't be this a RC 2? because there is a new build process and has nothing to do with the RC1?
yes rc2 mariano pharo-rc2 is not a problem
Also, the changes files, shouldn't be compressed for each RC and for the final release?
Yes probably.
Also, the packages.txt file talks about PharoCore1.0 (#10505). Has someone thought about the name shown in System->About:
PharoCore1.0rc1 Latest update: #10505
This is on the todo of marcus to come up with a HUGE list of actions we did in pharo 1.0 :) in a better way than the update cryptic log.
Because this is not a PharoCore image. Shouldn't this read something like
Pharo 1.0 Dev image. Based on PharoCore1.0rc1 Latest update: #10505
What about the disabling of software updates in the Pharo dev/web images? Will this be implemented or a careful update stream will be made in order to not break a dev image with overrides (real difficult I think).
Yeap another interesting point. May be disabling is the easiest solution :)
Maybe all this setup can be put in a post-script in the ConfigurationOfPharo class.
That's all for now. I'm going to use this image to work the following days.
Cheers and keep the good work.
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project