The problem with Collection appears to go back to 4.2, at least.  The
method in question looks related to some of the finalization
registry..

FlexibleVocabularies too - dirty in the 4.2 release (after checking changes).

For Monticello, it looks like this alpha image was saved after having
run the test cases.  *We should not do that* because we can't trust
that there aren't / won't be extranneous objects left around after
running the tests which shouldn't be put into a deployment image
(alpha, release or otherwise).

For deploying new alpha images, how about we keep using
ReleaseBuilderTrunk.  We can enhance it if necessary of course, more
importantly it serves as good "documentation" about how the image was
deployed.



On Wed, Jul 13, 2011 at 9:57 AM, Bert Freudenberg <bert at freudenbergs.de> wrote:
> Hi all,
>
> I ran the snippet below in a freshly downloaded trunk image. It found a couple of differences:
>
> - Monticello is dirty because of the Mock category
> - FlexibleVocabularies is dirty because its empty -Info category was removed
> - Collections is dirty because there is an unpackaged method, WeakRegistry class>>migrateOldRegistries
>
> These discrepancies should be corrected before the release, but does anybody have an idea why this happened?
>
> MCWorkingCopy allManagers
>        do: [:wc |
>                wc ancestors size = 1 ifTrue: [
>                        | parent changes |
>                        parent := wc repositoryGroup versionWithInfo: wc ancestors first.
>                        changes := wc package snapshot patchRelativeToBase: parent snapshot.
>                        wc modified: changes isEmpty not]]
>        displayingProgress: 'Checking packages'.
>
>
> - Bert -
>
>
>