[squeak-dev] [ExperimentalCoreRelease] PharoCore-1.0-10508rc2 vs SL3dot11-9499-alpha

keith keith_hodges at yahoo.co.uk
Fri Mar 12 18:44:30 UTC 2010

>> ong comes a new process which shuts him out from contributing to  
>> squeak, as it has me, and we are told...
> Bullshit.

Ok, question 1, how do I load MC1.5 into trunk? without breaking it?   
I need features of MC1.5.

Question 2, My sources/changes innovation, is going to be produced and  
managed in an external repository, this is where the the code is going  
to develop and evolve.

Trunk doesn't have an integration step, trunk doesn't have a package  
management solution that manages anything external to trunk. Say I  
have 3 experiments going, for different sources/changes history  
mechanisms, how does trunk allow me to publish them and provide them  
as options to users to pick for their image?

I can upload a solution to trunk, but only one solution, and then only  
when it is finished and perfect, but for people like me, my code is  
never finished and perfect so it will be a while. By the time I have  
done it, trunk will have moved on and left me behind.

When my solution is loaded into trunk where is the primary repo for  
managing my code, is it trunk, where anyone could change something? I  
would rather gather a team of interested people around the repo  
externally and have it integrated into a release periodically.

"trunk" is conceptually a repository for one monolithic image, and it  
is not the image I want. If I contribute something it will probably  
not be the image you want, and the trunk process is very fragile, and  
only moves forwards.

When i develop I don't move forwards all the time, it is just not  



More information about the Squeak-dev mailing list