On 23.02.2009, at 20:45, Adrian Lienhard wrote:
> Hi all,
>
> Marcus, Stef and I have been meeting today and we discussed how to
> proceed for the first release (version 1.0).
One note to everyone who submitted a bugreport... no, note at the end of
the mail. First a story.
In Squeak, people submitted lots of improvements and bugs, first with
the funky [TAGS] to the
list, later via the bugtracker. But then, a curious thing happened:
they never, ever, looked
at that bug-report again. Maybe the image side code changed, and the
submission
needed a trivial change so that the changeset could be loaded. Or
there was some
question posted by a harvester. Or after 1000 applied changesets,
there might be
the possibility that a bug is already fixed. Kind of obvious, that the
submitter
of a report can help a lot in these situations. But they don't. I have
*no clue* why.
In the end, I closed lots (really lots!) of entries in Squeak over the
years
after a question to the original submitter was not anwered after 1
year(!) of waiting.
I really wonder what the problem was... the submitter cared a lot when
submitting the bug
or improvement in the first place. But then, just answering a question
or re-do a changeset
(maybe 30min of work for the original author) was too much... a mystery.
Thus: As we are nearing 1.0, I kindly ask everyone who submitted
something to look at the
report. Maybe you can make it easier to have it integrated? e.g.
exactly describing the action
needed is better than making it a riddle (some people think that it is
a sign of intelligence
to not give the solution to a problem after describing the cause). A
changeset (or mcz) is
the best. Even for a one-line triviality.
You reported a bug half a year ago? Try to recreate it and add a
comment: This is still a problem
in #10243 and the way I re-created the problem is this.
In the end, the question is: If you don't care, why should we?
Marcus
-
Marcus Denker -- [email protected]
http://www.marcusdenker.de
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
