>Hi Dan & co.
>
>Bruce's question about change sets and your response reminded me to ask
>about change set preambles.  Because the change set preamble often contains
>more information about the feature or fix that was included into the
>mainline than the comments in the actual code, I think that some important
>information is lost when the change sets are purged from new images.  Over
>the last year, for example, we have had hundreds of change sets, for a
>variety of features, that have imparted key information about the features
>they introduced/fixed/replaced.
>
>Is there an archive of change set preambles that can be accessed by the
>Squeak community?

Yes, and no, again.

There is certainly an archive of all the changesets -- on the update server itself -- and most of them have preambles.

One could probably just start up a 2.0 image and let it update for a few days until it got to 2.7alpha.  Then you could run the code that appears in the comment to ChangeSet summaryString (something like that), and it would produce a digest of all the preambles.

More importantly, IN THAT IMAGE, you could use all the nice Squeak queries such as 'changeSets including this method', or 'changeSets with conflicting defs'.  This would be more useful than an archive.  Perhaps someone feels like doing this and putting the image out on a server as 'archival.image'.

Anyway, if you seriously want that kind of documentation, that's what I would do.  I frequenlty use an image that dates back to update 900 or so for that purpose.

	- Dan