[squeak-dev] Urgent, Spur users please read, was: The Inbox: Kernel-kfr.858.mcz

Chris Muller asqueaker at gmail.com
Mon Jun 16 15:06:43 UTC 2014


>>>>    This shows us something we have to be /very/ careful about!  KFR's commit is from Spur and includes all the Spur changes to e.g. the allInstances machinery (look at the diff).  So there are many more changes than the one the checkin comment describes and those changes _will break_ non-spur trunk images.   So...
>>>>
>>>> a) we need an inbox for Spur packages
>>>> b) anyone committing a version of Collections Kernel or System needs to commit to the right place, spur or trunk/inbox
>>>>
>>>> This situation is temporary while we shake down Spur.
>>>> Perhaps I made a mistake and should have named the Spur packages differently, i.e. Collections.spur Kernel.spur or System.spur?  Then when we accept Spur we could change the package names back to Collections Kernel or System and fix the history somehow.  Thoughts?
>>>
>>> Using a branch name sounds good to me.
>>
>> Isn't that rather overkill?  I think we should not set a new precedent
>> in the complexity of our namespace unless we absolutely have to.  The
>> Inbox is for just cherry-picking individual contributions, not an
>> on-going development ancestry.  Wouldn't simply "documenting" each
>> submission for "spur" in the version-comments (instead of the
>> version-name!) be sufficient for Inbox purposes?
>
> What new precedent? We've used branches in the Inbox before. The Inbox
> has never been for cherry-picking individual contributions.

"Never?"  I have no idea what you mean.  What do you think the Inbox
is for if not cherry-picking individual contributions?

The only "branch" we have in Inbox right now is the "-quasiquote"
stuff from Eliot, which I guess is integrated now anyway and so should
be moved to Treated..?


More information about the Squeak-dev mailing list