harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geir Magnusson Jr." <g...@pobox.com>
Subject Re: [jira][general] Good issue resolution guideline update
Date Tue, 06 Feb 2007 15:38:10 GMT

On Feb 6, 2007, at 3:28 AM, Alex Blewitt wrote:

> On 06/02/07, Yang Paulex <paulex.yang@gmail.com> wrote:
>>
>> I also had some thoughts to keep the patch history, recently I  
>> reviewed and
>> commented some patches, and then the contributor submitted new
>> patches(thanks!), but they removed the old ones from JIRA.  
>> Sometimes it
>> makes me confused, because the patches' names are same but they  
>> are actually
>> a new version, further, it makes the former discussion on the JIRA  
>> invalid
>> because they are based on the old patches. So I'd like to propose  
>> this for
>> discussion:
>>
>> 5. if for any reasons, someone needed to submit a new patch for  
>> some issue,
>> don't delete the old one, but named the new ones with version number.
>
> Yeah, one of the annoying things is that JIRA doesn't tell you which
> patch(es) are current or not, so it's a bit difficult to know if it's
> just the last one or a combination of the above. I guess there's no
> way of configuring JIRA to show up 'obsoleted' patches on a bug, is
> there, thus allowing them to be kept but displayed differently
> somehow?

You can see the time of submission, so you can at least order them  
that way.

I think that being sure to give them a unique name, like

     foo_patch_20070201.txt

or such, and then provide a comment in the JIRA specifically naming  
that patch...

geir

>
> Alex.


Mime
View raw message