> > There are SEVERAL reasons, but I don't have time to answer correctly. I will > let the board to answer, but I will to a summary: > > - Because of marketing > - Because to give visibility to outside > - People that are waiting to build stuff because they won't do it until have > a "stable release" > - Companies may not move on a propject that doesn't have yet a stable > release
> - Having two branches requieres time and effort Am I understanding this correctly? Am I to believe that Pharo doesn't have both a development and production branch, or have I misunderstood? > - We need to progress in 1.1 > - Because people won't believe in us anymore. We said that the 1.0 release > was going to be one year ago. > > If you want to continue this discussion, please open another thread. > > Cheers > > Mariano > >> >> Bill >> >> >> >> ________________________________ >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Mariano >> Martinez Peck >> Sent: Friday, January 22, 2010 9:32 AM >> To: Pharo Development >> Subject: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2 >> >> Hi folks. This is 1.0 RC2. Please, look at this image in a nice way >> because it is very likely that if there is no big issue, it will be 1.0 >> official. We need to release 1.0. >> >> Issues fixed: In addition to the fixes from the PharoCore, we have: 1033, >> 1182, 1826, 1862. >> >> Big changes: >> >> - Now we use OB from Lukas Renggli repository and we have ALL TESTS >> GREEN!!! Thanks Lukas! >> - O2 loads again in the image without breaking OB. Read the workspace to >> see how to install it. Thanks David and Alexandre! >> - We have almost (only one failing here) ALL TESTS of the PharoDev image >> in green. They are more than 8800. >> >> Smaller changes: >> >> - Fixed the problem with Metacello and OCompletion. No more overrides. >> - System -> About now shows the real Pharo name, not the core. I am also >> being "compatible" with the new SystemVersion that we have in 1.1 :) >> Thanks Michael and Miguel! >> - I didn't left again my proxy settings. I fixed this in my build scripts. >> It should be clean :) >> - Mercury bar is back again. If you want to disable: Preferences disable: >> #mercuryPanel. >> - Added a lot of cleanups after creating the image, including condensing >> .changes >> - Added Refactoring-Spelling again. Thanks Stan! >> - I wrote a ConfigurationOfNile instead of Nile-All and depends on >> Monticello dependencies. >> - New welcome workspaces. Also getting started workspace and another >> workspace explaining how to load external packages like Seaside (2.8 and 3), >> Magritte, Pier, Moose, GetTools, O2, etc. Finally it is also added a link to >> the new ProfStef :) >> Do you think that with this we are able to close issue1479 ? >> - Background with Pharo picture. This was a joke. It looked nice :) I >> promise I don't put it again if you don't like. To remove it evaluate: >> World color: Color white. >> - Enable the preference fastDragWindowForMorphic. Sorry, but it most >> computers this works REALLY slow. If you want them back, just disable it. >> - When installing Seaside now doesn't ask for user and password ( >> admin/seaside ). In addition, the Seaside Control Panel is only isntalled if >> OB is installed. This means that yu can install it in core or dev. Thanks >> Dale! >> - Disable of System Update for Dev images as it is not working properly. >> >> >> The link is: >> https://gforge.inria.fr/frs/download.php/25397/Pharo1.0-10508-rc2dev10.01.2.zip >> >> Cheers >> >> Mariano >> >> >> >> _______________________________________________ >> 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
