I think it's a bad idea to just switch the downloads from 1.0 to 1.1 now. We don't even have a release candidate yet, hence 1.1 hasn't seen much testing. 1.1 may be ok for personal use but is it also safe to be deployed on a mission critical system? I'm all for short release cycles, but please don't take such shortcuts. A high quality is really important if we want to support the companies using Pharo and attract new ones.
So the next steps should be: identifying the critical issues (currently there are 179 open issues tagged 1.1!), then fixing them, then we do a first RC. Cheers, Adrian On Jun 8, 2010, at 15:45 , Mariano Martinez Peck wrote: > On Tue, Jun 8, 2010 at 9:46 AM, Niko Schwarz > <[email protected]>wrote: > >> Of course not. Just switch the default download (the big one, all over >> the site) site to 1.1. >> >> I just suggest to switch from 1.0 to 1.1 as stable at the same time >> that we switch from 1.1 to 1.2 for development. > > > I think this is a good idea. > > >> Then we never have 3 >> "current" versions at once. >> >> Cheers, >> >> Niko >> >> -- >> http://scg.unibe.ch/staff/Schwarz >> twitter.com/nes1983 >> Tel: +41 076 235 8683 >> >> _______________________________________________ >> 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 _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
