Publishing on Monticello
stéphane ducasse
ducasse at iam.unibe.ch
Sat Sep 17 07:35:23 UTC 2005
> Monticello is designed to allow precisely this style of
> development. You just merge your version with the official version
> and you're done. As a developer you should of course enable the
> #upgradeIsMerge preference.
Bert what is that preference exactly
>> As long as you are developing a master image, it is the right way
>> to create modified versions of original packages. They immediately
>> become the new originals;) This kind of work is wonderfully
>> supported by Monticello with its many merging facilities.
>> Nonetheless, if you want to develop a second master *partly*
>> synchronized with another master line, there will be much work
>> waiting for you, accumulating over time...
>
> This is a false assertion. Did you actually try? I regularily have
> private changes to "official" packages. Upgrading them works great.
Do not forget to publish the one that make sense to be published in
3.9 :)
Stef
More information about the Squeak-dev
mailing list
|