harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oliver Deakin <oliver.dea...@googlemail.com>
Subject Re: Example of providing a good issue resolution Was: [jira] Closed: (HARMONY-2077) [doc] Good issue resolution guideline
Date Fri, 01 Dec 2006 10:36:31 GMT
Alexei Fedotov wrote:
> Alexey, all,
>
> Let me attract your attention to a resolution of issue [1]. If you
> follow Ivan's comments you will see how an elegant one-line solution
> springs up from a nowhere.
>
> Why I'm asking you to spend your time on investigating resolved issue?
>> From my perspective it is very good example of how a good issue should
> evolve. It definitely worth effort to document intermediate steps,
> because
> * Writing down the facts orders them and builds the whole picture.
> * Reading through comments makes a patch review and understanding much 
> easier.
> * Someone who is interested in resolution could join at any time.
>
> That is why I asked to add regular reports on issue progress to the
> guidelines. From this example we can extract a good rate for
> commenting: a comment per hour.

I'm not sure we can put a time limit on this - one comment an hour is pretty
impressive! I do agree though that keeping a bug updated with your
current progress while debugging or preparing a fix is important. It keeps
anyone interested up to speed, allows anyone who may recognise the symptoms
of the bug to jump in at any point and offer help, and also lets others
see that there is still activity on that bug, so they do not duplicate 
effort
trying to solve it themselves.

Regards,
Oliver


>
> [1] http://issues.apache.org/jira/browse/HARMONY-2228
>
> Best regards,
>
> On 11/15/06, Alexey Petrenko (JIRA) <jira@apache.org> wrote:
>>     [ http://issues.apache.org/jira/browse/HARMONY-2077?page=all ]
>>
>> Alexey Petrenko closed HARMONY-2077.
>> ------------------------------------
>>
>>    Resolution: Won't Fix
>>
>> Closed by submitter request.
>>
>> > [doc] Good issue resolution guideline
>> > -------------------------------------
>> >
>> >                 Key: HARMONY-2077
>> >                 URL: http://issues.apache.org/jira/browse/HARMONY-2077
>> >             Project: Harmony
>> >          Issue Type: Improvement
>> >          Components: Website/Documentation
>> >            Reporter: Alexei Fedotov
>> >         Assigned To: Alexey Petrenko
>> >            Priority: Minor
>> >         Attachments: get-involved.patch
>> >
>> >
>> > Added a thread about desired JIRA resolution communication style to 
>> the web site.
>>
>> -- 
>> This message is automatically generated by JIRA.
>> -
>> If you think it was sent incorrectly contact one of the 
>> administrators: http://issues.apache.org/jira/secure/Administrators.jspa
>> -
>> For more information on JIRA, see: 
>> http://www.atlassian.com/software/jira
>>
>>
>>
>
>

-- 
Oliver Deakin
IBM United Kingdom Limited


Mime
View raw message