Thanks, Scott!  Wow.  Who knew?  I didn't :)  But then, I'm ignorant
about *tons* of cool stuff already built into the image.

I have a feeling that we ought to always run those five checks as part
of the "mail to list" ChangeSorter option.  Also might be good to
incorporate in the BFAV and in Doug's UpdateTool. Hmm.....

Cheers,
Brent

P.S. Documentation folks, this would be a good thing to put on the wiki.

-----Original Message-----
From: Scott Wallace [mailto:scott.wallace at squeakland.org] 
Sent: Thursday, November 06, 2003 2:01 PM
To: The general-purpose Squeak developerslist
Subject: Re: Harvesting classes without class comments?!


Most squeakers are probably familiar with the simple change-set-checking
tools that have been available via the "Dual Change Sorter" for years,
but for those who are not...

When preparing a change-set for publication, and also when vetting
someone else's change-set for harvesting, you can point a
DualChangeSorter at the change-set, and then bring up (and *keep up*
with the push-pin) the "more..." branch of the change-set-list menu:

The five "check for" items allow you to explore potential deficiencies
in the change-set; they detect "slips" (e.g. halts and Transcript
references,) messages that have no senders, uncommented methods,
uncommented classes, and uncategorized methods.

If it were agreed that no change-set would be considered a candidate for
harvesting until it had passed all these checks, it would help.