[squeak-dev] Re: Bug in object finalization?

Norbert Hartl norbert at hartl.name
Thu Jun 19 09:02:49 UTC 2008


On Wed, 2008-06-18 at 16:23 -0700, Michael Rueger wrote:
> But, while we are on it:
> what could we do to make it easier -meaning not imposing even more
> stress/work on top of release stress etc- for the different "forks"
> (Croquet, Sophie, Pharo, Seaside, etc) to make fixes
> available/accessible?

> The semaphore fixes back then got me thinking about this, but I'm
> still not sure what a solution would be.
> Basically one would need to be able to easily see changes across a
> variety of repository and image versions. A central source database
> maybe?

I would see it the other way round. The forks forked as there wasn't
a way to do it centralized. Every measure that takes this approach
is IMHO suspect to fail :) What id needed at least is that every release
team has a public changelog and source repository. This way a release
team of one fork could easily see what others have done and incorporate
it in the own fork.

I could image some sort of centralized notification about accepted
fixes. This could be a wiki page with a table where each release 
team enters the accepted fixes as a row and the forks are the 
columns

             squeak     croquet    pharo
fixThat.2      +          X 
fixThis.1      X          +          -

So fixThis.1 is a patch from squeak (X). the croquet team accepted
and incorporated the change (+) and the pharo (you rebels!!) declined
it (-). fixThat.2 is a fix from croquet that squeak accepted and pharo
didn't do anything until now.

This may sound like a cheesy solution but it is easy to do and it 
doesn't depend on a common external system or common source code loaded
as prerequisite

Norbert




More information about the Squeak-dev mailing list