[Monetdb-developers] Re: [MonetDB-users] MonetDB Bug-Etiquette
Fabian.Groffen at cwi.nl
Mon Nov 21 12:58:09 CET 2005
On 21-11-2005 12:45:48 +0100, Stefan Manegold wrote:
> Users and developers should not be "eminies" blaming each other, rather they
> should work together, and support each other as good as possible to solve
> bug with minimal overhead. The user know how to trigger the bug, hence (s)he
> should provide the developer with as much information as possible to
> resproduce the bug and thus check whether her/his fixed indeed solve the
Sure. We misunderstood each other I think.
> Both user and developer share the reposibility of verifying that the
> provided solution indeed solved the problem permanently.
A user should be 'stimulated' to produce a test script. He/She shouldn't
be responsible for in any way if you want to have some decent QA IMHO.
Devs are responsible for it to get into CVS and that it is correct.
Users are most welcome to help working out such script.
> > > 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".
> Exactly. ;-)
Then it is a dev that decides that a bug is out of date. Which was my
point. I don't think a (regular) user (not a dev reporting a bug to
another dev!) should be the one responsible for closing a bug. QA
> > 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.
> This (c|sh)ould have been my words ;-)
I think my second mail should make clear that I wanted to say exactly
the same thing.
More information about the developers-list