On Jun 18, 2011, at 10:29 PM, Guillermo Polito wrote:
> Hi Stef!
>
> do you mean integrating all them in the Core? Or maybe follow Markus' idea
> of having just one image?
yes
> Maybe that's an important discussion to have too :).
> I can give a hand for the repository stuff. Should we replicate repositories
> + metacello configs in order to be able to freeze them, isn't it?
What we want is to avoid to have two images to maintain.
Now what I would love to have is the following
one configuration for the image
that the build system always load and we get something smaller that the
current dev.
The idea is that core should not be used but there and just as a seed
to build the system
So I would love to see how we could manage update with Metacello because we
would have bootstrap the process
seed1
+ MT1
=> Pharo1
Pharo1 + modifications
=> MT2 + seed2 (optionally)
seed1 or seed2
+ MT2
=> Pharo2
+ modifications
Stef
>
> Guille
>
> On Sat, Jun 18, 2011 at 9:59 AM, Stéphane Ducasse <[email protected]>
> wrote:
> Hi guys
>
> here is a kind of dump of roadmap for 1.4 first level is to make sure that we
> have only one single image.
>
> - load FileSystem
> -> so that we can start to integrate and improve the fileSystem API
>
> - Load shout, Ocompletion, RBEngine (not OB) so that we can change what
> should be changed for RPackage to work
>
> - Ring
> -> so that we can start to integrate it
>
> - Fuel
> -> so that we can deprecate SmartRefStream (there may be a problem
> with mcz (not sure)).
>
> - I want Opal in 1.4 too.
>
> - continue to remove StringHolder hierarchy
>
> - Morphic improvements
>
> Comments are welcomed.
>
> Stef
>
>
>
