[Lazarus] Moderating the bugtracker
Bart
bartjunk64 at gmail.com
Wed Aug 24 11:06:31 CEST 2011
Hi,
I have a question on moderating the bugtracker, more specifically on
when I should assign (and unassign) issues to myself.
In the Lazarus bugtracker, I have the "status" (don't know how it is
called) of developer.
I do however not have commit rights (nor do I aspire to get them) on svn.
In the past I was told I could assign issues to myself, if I thought I
could fix them, and unassign them if it turned out I wasn't able to
fix it after all.
I have done so for quite a while now, but recently when I assigned an
issue to myself and fixed it, I was asked why I assigned it to myself,
since I didn't have commit rights.
It was suggested to me that I should unassign the issue as soon as I
had fixed it and set a relevant target.
I must admit that a little bit of vanity comes into play here as well:
if an issue assigned to me (and fixed by me) gets resoved (without
changing the assignment) it'll be reflected in the bugtracker
statistics.
But putting that aside, what should be the general guidline for this
scenario, where one has assigned an issue to oneself and then fixed
it, but one doesn't have commit rights?
I can see several options:
1. Notify someone with commit rights a patch is available (the
bugtracker doesn't offer such functionality)
2. Move the issue to "Patches", do not change the assignment (for me ,
and probably others, this has the drawback that in "Patches" I am
"reporter", so I cannot move the issue back, or unassign if needed)
3. Set the target and just wait until someone commits the patch (this
is what I did in the past)
4. Set the target and unassign the issue.
5. Never assign issues to you if you do not have commit rights.
The wiki article about moderating the bugtracker
(http://wiki.freepascal.org/Moderating_the_bug_tracker) does not
describe this situation, so it might be a good idea to update it?
B.t.w. Is it OK to set the current trunk (currently 0.9.31) as target?
Bart
More information about the Lazarus
mailing list