maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Osipov <micha...@apache.org>
Subject Re: [DISCUSS] Idle bug handling approach
Date Sun, 23 Nov 2014 21:54:22 GMT
Am 2014-11-23 um 22:32 schrieb Stephen Connolly:
> On 23 November 2014 at 19:48, Kristian Rosenvold <
> kristian.rosenvold@gmail.com> wrote:
>
>> I think this is a very good idea. But I have seen this mis-used a few
>> times in other projects, and I think we want to avoid this scenario:
>>
>> There are some bugs that have very well written bug reports with
>> detailed descriptions on reproduction and/or quite a few watchers too.
>> I've seen this "rule" misused; some committer comes along and requests
>> some kind of additional information - sometimes the request can border
>> on the silly and maybe the committer does not really even understand
>> the problem (half of us really don't half the time - that's just the
>> way triaging works sometimes). So the issue gets closed because the
>> people who are familiar with the bug think it's a silly request to
>> make (and they might not even know its a committer making it - we have
>> no special distinctions in jira) and we basically piss off users.
>>
>> So I think it's a good strategy for half-baked, potentially old and
>> half-clear issues (which there are a LOT of!). A hundred years ago
>> someone taught me that if one person reports something it can be
>> ignored, but when the second person reports it it's most likely a bug.
>> So any issue with just one "user" watcher should be pretty harmless (
>> I may sometimes watch issues but I really don't want to be counted as
>> a watcher...)
>>
>> I just fixed/triaged well over a hundred bugs in maven-assembly-plugin
>> and out of the 56 remaining bugs there's probably 20-30 I'd want to
>> close this way.
>>
>> I was about to create some heuristic about when to be careful with
>> such a rule, but I basically changed my mind :)
>>
>> Actually maybe we should just say that after >30 days, we add an
>> additional message
>>
>> "this issue will be closed as incomplete in 10 days unless the
>> requested information is supplied"
>
>
> or a response seeking clarification on the exact information required, etc

+1

This is exactly what I am trying to do sometimes, even if I am not able 
to solve the ticket. Others might be if they get better information on 
the issue.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Mime
View raw message