>> First, what is the "Squeak-Version" package about?  Is it merely to
>> declare which update number we're at?  I didn't see where this has any
>> bearing on the actual update processing.
>
> It's only there to keep the "update number" increasing monotonically.

Ah, got it; to keep it increasing from the older versions of Squeak;
from before this update process...  A comment somewhere would have
helped!

>> I've copied the update-ar.1.mcm configuration to the new 4.2
>> repository, but I don't see whether any further change is needed.
>
> You should instead take the latest trunk update map, update it with the actual release packages, and then save to the release repo.

Ok, did that.

>> Then there is MCMcmUpdater's "LastUpdateMap" class variable.  This
>> gives us the minVersion update number for a particular repository but,
>> in my image, both #'s (for 'trunk' and for '4.1') are very low.
>
> Those numbers are unrelated. One is a sequential number of MCMs, the other the sum of all package version numbers.

Ok, just verifying no entry is needed for 4.2.

 - Chris