I'm working on cleaning ECompletion: now it works well in 1.4 So I guess that loading RBEngine and OB should make it. Now people should help.
For 1.5 we will get nautilus. Stef > Ok, but that kind volunteer needs an image built the way they are told to do > so. The convenience factor of having big stuff loaded into an image will > attract users/testers. > > > > > ________________________________________ > From: [email protected] > [[email protected]] on behalf of Frank Shearar > [[email protected]] > Sent: Friday, March 23, 2012 6:25 AM > To: [email protected] > Subject: Re: [Pharo-project] About 1.4 Release... > > On 23 March 2012 09:34, Marcus Denker <[email protected]> wrote: >> Hi, >> >> We were discussing here about the 1.4 release... and my standpoint is: >> >> "What is on the Build Server will be the Release" >> >> For 1.4, this means that this image is the release image: >> >> >> https://ci.lille.inria.fr/pharo/job/Pharo%201.4/lastSuccessfulBuild/artifact/Pharo-1.4.zip >> >> possibly with more bugs fixed. >> >> the list is here: >> http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.4 >> >> It especially means that we will not load additional packages (RB, OB....), >> because then we should >> have used the resulting image already the last months and we did not. >> >> Is that what we want? or will people say "without refactorings, I will not >> use it?" > > I'd say "What is on the Build Server will be the Release" is exactly > the right thing to do, because it's the thing you've been testing. You > can have high confidence that the artifact will be stable, etc. Adding > in extra stuff increases the testing burden. > > Of course, you (you, or some kind volunteer) could have a job that > adds the various extras, and tests that Pharo+(stuff) image. > > frank > >
