Is it possible to add more statuses to the tracker?

View: New views
2 Messages — Rating Filter:   Alert me  

Is it possible to add more statuses to the tracker?

by Aaron W. LaFramboise-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

A big barrier to going through the bug tracker is the sheer amount of
time and effort required to investigate each issue.  I think it might be
easier if I had more states to work with.

I think the workflow for a real GCC bug should go like this:

Open -> Confirmed -> Analyzed -> Closed

(This is roughly the workflow that FSF GCC uses on their Bugzilla.)

This reflects the reality that I may be able to confirm a bug, but I may
not be able to immediately analyze it, or I might be able to analyze it,
but its not obvious how to fix it.  Or some bugs may require some time
investment to even confirm, if they're something fairly strange.

I think it would be really helpful to be able to triage and sort bugs in
this manner, with the immediate goal of getting bugs into 'confirmed'
state or closed, and ultimately delegate all appropriate bugs to the GCC
bug tracker where they stand a chance of being fixed.



------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
MinGW-dvlpr mailing list
MinGW-dvlpr@...
https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr

Re: Is it possible to add more statuses to the tracker?

by Earnie :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Quoting "Aaron W. LaFramboise" <aaron77thyme@...>:

> A big barrier to going through the bug tracker is the sheer amount of
> time and effort required to investigate each issue.  I think it might be
> easier if I had more states to work with.
>
> I think the workflow for a real GCC bug should go like this:
>
> Open -> Confirmed -> Analyzed -> Closed
>
> (This is roughly the workflow that FSF GCC uses on their Bugzilla.)
>
> This reflects the reality that I may be able to confirm a bug, but I may
> not be able to immediately analyze it, or I might be able to analyze it,
> but its not obvious how to fix it.  Or some bugs may require some time
> investment to even confirm, if they're something fairly strange.
>
> I think it would be really helpful to be able to triage and sort bugs in
> this manner, with the immediate goal of getting bugs into 'confirmed'
> state or closed, and ultimately delegate all appropriate bugs to the GCC
> bug tracker where they stand a chance of being fixed.
>

We can do something like this with our NetworkRedux cloud and the  
Drupal software.  Again if anyone is willing to help focus on  
replacing SF please let me know.

--
Earnie


------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
MinGW-dvlpr mailing list
MinGW-dvlpr@...
https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr