what are the exact problems with the network? lukas' email said that the resolver behaviour had changed positively, not that there was an issue. or did i miss read?
thanks, Mike On Mon, May 17, 2010 at 9:21 AM, Stéphane Ducasse <[email protected]> wrote: > So what do you suggest > beta for two three weeks > then rc1 > > Stef > > On May 17, 2010, at 10:00 AM, Mariano Martinez Peck wrote: > >> >> >> On Mon, May 17, 2010 at 9:29 AM, Stéphane Ducasse >> <[email protected]> wrote: >> Unstable is alpha. We called it that way so that people do not start to use >> it :) >> >> Ok, we can tag it beta then. >> >> But now we should go beta=releaseCandidate1 >> >> >> No, I don't agree. That's not the same. One thing is beta and another thing >> is a release candidate. >> >> >> Stef >> >> On May 16, 2010, at 11:18 PM, Mariano Martinez Peck wrote: >> >> > >> > >> > On Sun, May 16, 2010 at 11:16 PM, Stéphane Ducasse >> > <[email protected]> wrote: >> > check the network problem. >> > But we can release rc1 anytime now. >> > >> > >> > No, please. We are not in a RC yet. We should first go as alpha, then beta >> > and finally RC. >> > We cannot go in a RC with the first build ever. >> > >> > Cheers >> > >> > Mariano >> > >> > >> > Stef >> > >> > On May 16, 2010, at 11:00 PM, Alexandre Bergel 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. >> > > >> > > 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 >> >> >> _______________________________________________ >> 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
