Question:
If ToolBuilder has its own repository, and changes to ToolBuilder are done at separate repository at squeaksource.com/DeltaStreams, then also put into the trunk repository, then it is found in trunk that a small fix is required to ToolBuilder, where would the be fix be stored? If done just locally to trunk,  how would it ever be possible to keep ToolBuilder in its separately loadable repository in sync?

Similarly for MC. I've seen the following go by:
At 3:36 AM +0000 8/31/09, commits at source.squeak.org apparently wrote:
>Andreas Raab uploaded a new version of Monticello to project The Trunk:
>http://source.squeak.org/trunk/Monticello-ar.321.mcz

Yet it is clear that at the public repository for MC at http://www.squeaksource.com/mc/, that Monticello is already at at least version 492. How does the Andreas 321 change relate to the 492 version in the public MC repository?

What are the plans for keeping versions of separately loadable modules like Monticello, or ToolBuilder in sync?

Or if forking Monticello, shouldn't it have a different name?

Or am I missing something?

Are the planned work items for trunk documented anywhere?

Ken G. Brown

At 6:51 AM -0700 9/7/09, Igor Stasenko apparently wrote:
>Matthew made some enhancements to ToolBuilder, which currently held in
>separate repository at
>squeaksource.com/DeltaStreams under the ToolBuilder-Kernel cat.
>
>Some of the changes would be really nice to integrate in trunk, like
>
>- renamed PluggableListSpec>>size to listSize
>- added PluggableListSpec>>listItem, as an optimization to only fetch
>items in view rather than the whole list, when scrolling
>
>or maybe i'm not aware, and they are already in trunk?
>I just want to ask anyone who is interested to make an overview of
>changes and decide if its safe to push them to trunk image (or
>official ToolBuilder repository).
>
>--
>Best regards,
>Igor Stasenko AKA sig.