Folks,

Okay, so I'm using the BFAV and figuring out how to help get rid of the
changes backlog.

The BFAV apparently manages a lot more things than just bug fixes. That's
okay, but it seems to me that bugs are the things that ask most strongly for
changes in the distribution image, and it seems most useful to devote my
attention to getting rid of pending bug fixes before looking at anything
else.

So, in the BFAV I set "*[FIX]*" as the pattern to filter the topics by
subject line, and sure enough, I get a list of about 15 topics which all
have [FIX] in the subject line.

I go to the oldest item, it is called "[FIX] CollectionFixes". I click on
it, and read

Subject:  [FIX] CollectionFixes (  Not sure that there was a bug )
Date Posted: 5 October 2003
Comments: This topic has 1 posts.

Okay, this doesn't help me a lot, let's click on the second line associated
with the topic. I read:

Subject:  [FIX] CollectionFixes (  Not sure that there was a bug )
Author:  ducasse at iam.unibe.ch
Date Posted: 5 October 2003
Comments:
The intention was nice but in VW this is the same as in Squeak
collect: on any subclasses of Set return a Set and not an instance of
the class.

Andrew could you tell us what bug you were fixing exactly.

Stef

I'm lost once again. I know who Stef is, but who is Andrew? Where is the
code? How can something be a fix if it doesn't have code? How can something
be a fix when there isn't at least the claim of an associated bug? What is
the status of this topic?

I don't understand Stef's comment at all Why would he be asking "Andrew" for
explanation about Stef's own bug fix?

Or wait a minute. Maybe Stef isn't the author of the fix. Maybe Stef is the
author of the e-mail, and he has nothing to do with the fix itself. That
would make sense. However, there is nothing to be seen in the BFAV from any
"Andrew" regarding this fix. This is all very confusing.

[BTW, of course it is a bug for #collect: on a Set to return another Set -
the result of #collect: should have the same size as the receiver (note -
the ANSI spec disagrees with me). Something similar happens with
SortedCollection - we can't return a SortedCollection because we can't know
what its sortBlock should be].

I wonder, am I so stupid, or am I discovering, step by step, elements of the
answer to Marcus' question why people don't submit reviews at a higher
frequency?

Thanks in advance for any suggestions to help me along...

Peter