[Monetdb-developers] Re: [MonetDB-users] MonetDB Bug-Etiquette
sjoerd at acm.org
Mon Nov 21 11:45:35 CET 2005
Fabian Groffen wrote:
> On 21-11-2005 02:38:01 +0100, Stefan Manegold wrote:
>>Since both the user who submits a bug report and the developer(s) who
>>take(s) care of fixing a bug are by definition very familiar with the
>>details of a bug report, it seems more than obvious that they should share
>>the task of adding a test script to the CVS repository while dealing with
>>the respective bug, i.e., *before* closing the bug report.
> It is not obvious that the submitter knows the problem very well to me.
> Hence, I'd like to reduce the 'options' here, and let the developer add
> the script when (s)he closes the bug.
I guess it depends on the submitter. For some it is (almost) trivial to
create a test script, and in any case, it helps the developper
enormously if a small test can be made that shows the problem. In fact
I would go so far as to say that for all real bugs (i.e. not compilation
issues and typos and such) a small test is essential. I do think it is
the developper's responsibility that the test gets added to the test web
(that doesn't mean the developper has to do it, it means the developper
must make sure it is done).
>>- Please fill in Category and Group.
>>- Feel free to set the Priority if you think the default is no appropriate.
> not appropriate
>>- Please provide a detailed description how to repeat the bug you report, or
>> even a concise test script to do so. Preferably, the test script should
>> also be added to the standard test-suite (in the CVS repository; see
>> "Adding test scripts" below for more details!).
> I strongly suggest to drop the CVS thing. Many users don't have it, and
> it's confusing and more work for devs, see below.
I'm sort of with Fabian here. Maybe the "preferably" should be changed
in "if possible".
>>- Please feel free to close your bug report, in case you notice it does not
>> occur any more (your test script in the standard test-suite is your
>> free-of-charge monitor; simply check our "TestWeb" at
>> http://monetdb.cwi.nl/Development/TestWeb/ ;-)).
>> See "Closing bug reports" below for more details!
> This is weird. So a bug can suddenly vanish? Yes it can, but then the
> exact cause of the bug was not found, so it can be gone just by
> coincidence, which is *not* good. Submitters should only close their
> bug if they think they made a mistake and that their bug is invalid.
Bugs do sometimes disappear because of fixes that were made for some
other reason. It is appropriate that the report gets closed in that
case. The resolution should then be "Out of Date".
>>- Once a developer closes your bug report, please double-check whether the
>> solution indeed works for you (simply check the status of your test script
>> in our "TestWeb" at http://monetdb.cwi.nl/Development/TestWeb/ ;-)).
>> If is does not work for you, feel free to re-open the bug report,
>> or file a new one. In either case, please give a detailed description
>> of the remaining or new problem!
> Why not let the developer *always* add the test script before closing
> the bug. Checking that a bug is already there (hoping it complies to
> the naming conventions as pointed out below) is just some extra hassle.
> Besides that, IMHO it's just more well organised if the dev adds the
> script once (s)he fixes the problem and as such the correct output can
> be determined as well as the test possibly made somewhat more extensive
> to cover more possible problems. The dev that fixes the problem should
> ideally have the best knowledge on why something went wrong.
As I mentioned above, it is the developer's responsibility. That
doesn't mean the developer must do it, and if the submitter can create
and check in a test script, I would encourage that.
> Just my e0.02
> This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
> Register for a JBoss Training Course. Free Certification Exam
> for All Training Attendees Through End of 2005. For more info visit:
> Monetdb-developers mailing list
> Monetdb-developers at lists.sourceforge.net
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 369 bytes
Desc: OpenPGP digital signature
More information about the developers-list