[Pharo-project] About 1.2

Norbert Hartl norbert at hartl.name
Sun Feb 27 01:06:33 CET 2011

Why do you think the break of 1.1 build  is xml related? To me it appears either a PharoSound or metacello problem. The build is unable to load Collections-Arithmetic. Either it is missing from the package-cache or erronously pulled in via dependency that is not right.


Am 25.02.2011 um 21:50 schrieb Stéphane Ducasse <stephane.ducasse at inria.fr>:

> Hi guys
> 1.2 should go out. Marcus and me should spend their time on 1.3, OPAL and the rest.
> Now for PharoDev we want to remove packages that are not about tools.
> If you want XML, openDBX... help us using Metacello to build distributions = something that will work in 1.2 when 
> we will be in Pharo 10. Right now this is not normal that a problem in XML in 1.2 impacts the builds in 1.1.
> Proposing bloated images DOES NOT HELP US. Why? Because the goal is to have an INFRASTRUCTURE to take 
> a small image with a metacello description repository and load whatever we want. In the future we want to use 
> metacello to manage core and not to have a distinction between core and dev. We should be able to load all the time
> RBEngine and use it all the time to fix the system. 
> Right now we are LOSING TIME on fixing 1.2 configs while we should invest in the infrastructure that will enable 
> to be agile and load whatever configuration we/you will develop.
> So can we be focus on the infrastructure? The concept and tools that we will make us be really powerful in the 
> future?
> So if the community does not hear our call, we the board will take actions. We do not want to do that but if this
> is necessary we will do it because we want 1.2 to get out.
> Stef

More information about the Pharo-project mailing list