Peter Jeremy wrote:
> On 2009-Nov-02 13:35:05 +0000, "Dr. David Kirkby" <david.kir...@onetel.net> 
> wrote:
>> I would suggest a pull-down on the track where one could select from
>>
>> 1) N/A - Not an upstream bug.
>> 2) Not yet reported upstream, but should be.
>> 3) Reported upstream.
>> 4) Fixed upstream
> 
> Sounds good to me.

Great, that is two people that think it is useful.

>> In the case of #3, the trac ticket should give further details of how the 
>> bug 
>> was reported. Such as
> ...
>> In case #4, the trac ticket should state if the fix is in
>> * A stable upstream release
>> * CVS
>> * Alpha/beta release
> [and presumably the version with the fix in it]

Yes, whatever information is needed to get the fix.

> Do you see these as being special fields or just the general trac body?

I think whether a fix is in a stable upstream release, CVS, a particular alpha 
release or similar should just be described in the trac ticket. There are just 
too many combinations otherwise. If someone knows of an upstream bug fix, they 
should just put the information as text.

> The only downside I can see is that tickets won't be updated from case
> 3 to case 4 - but that's still going to be a vast improvement over what
> we have now.

There is no reason a trac ticket could not be updated from case 3 to case 4, 
but 
clearly that is not going to happen automatically.


Dave


--~--~---------~--~----~------------~-------~--~----~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to