On May 16, 2010, at 11:17 PM, Mariano Martinez Peck wrote: > > > On Sun, May 16, 2010 at 11:00 PM, Alexandre Bergel > <[email protected]> wrote: > Mariano, > > What is needed for Pharo 1.1? Not much I feel. I produced yesterday a > Pharo1.1 from a core, and it works perfectly, including condenseChange. > > > No, it doesn't work perfectly ;) > All the mails I sent to the mailing list was the "things" I found while > building Pharo 1.1. > We still have problems with network for example.
Where? The ping did not work in 3.9, squeaktrunk, pharo10 and pharo1.1 so :) lukas sent an email last week and we got NO feedback. > Not too much indeed. I need to update a little some configurations. I just > tested with the new vms and today I was testing how to install external > packages like seaside to see if the welcome workspace that explains how to > install them deserves an update. > > What I need is that someone: > > - Integegrate the remaining fixes and crates a PharoCore-11XXX-alpha1.zip and > put it in gforge there are none that are showstoppers > - to create a section in the website specially for 1.1 where we mention we > are in alpha1 blah blah I started and we should continue > - in that section we include new VMs. > - For windows it is the same we have for 1.0: > http://gforge.inria.fr/frs/download.php/26814/PharoVM-Win32-4.0.2-bin.zip > - For linux: > http://squeakvm.org/unix/release/Squeak-4.0.3.2202-linux_i386.tar.gz > - For mac we are waiting a new one from John, but for the moment we > should use: ftp://ftp.smalltalkconsulting.com/Squeak%204.2.4beta1U.app.zip > - Finally we add in that section the Pharo image I build. > > I have updated my build scripts to work with Pharo 1.1 and I build a dev, Excellent > > So...once those points are done, I just create the image and update it to > website. > > But we will need help from people to test it and report bugs, feedback and > all kind of issues. There are still failing and error tests (they are even in > PharoCore). > > Cheers > > Mariano > > > Cheers, > Alexandre > > > On 16 May 2010, at 11:14, Stéphane Ducasse wrote: > > > We are basically ready > > Waiting for feedback on network. > > > > Stef > > > > > > On May 16, 2010, at 3:48 PM, Mariano Martinez Peck wrote: > > > >> We said that for middle May we were going to freeze 1.1. This means, no > >> more new features or refactors. Just bug fixes. So, the next steps can be: > >> > >> - Release a PharoCore1.1 with the last version we have so far tagged as > >> alpha1 (please, put this tag in the zip, .image and .changes). This may > >> be, for example: Pharo-1.1-11360-alpha1.image > >> - Build and release a Pharo 1.1 alpha1 based on such core (now we have > >> almost all dev tools working well in 1.1) > >> - Make publish all new VMs (for each OS) > >> > >> Then the idea is that people/developers start to play with Pharo 1.1. It > >> may be quite unstable as this is the first release for 1.1. People should > >> try to load their own packages, adapt them (if necessary) to 1.1, and > >> report all issues they find (and fixes!!). But they should keep in mind > >> this the first alpha ;) > >> > >> With these, we will be testing: new VMs, PharoCore, PharoDev tools, and > >> external packages (from other people). > >> > >> Pharo team at the same time, continues to work, fixing and integrating. We > >> make new versions as we have been doing so far. When we consider, we > >> release an alpha2....then beta, then RC and finally Pharo 1.1. > >> > >> now...do you think there is an issue that is so important to be > >> fixed/included in the first Pharo1.1 even being a first alpha ? > >> > >> 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 > > _______________________________________________ > 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
