From: Earnie B. <ea...@us...> - 2009-07-21 14:33:42
|
Quoting "Aaron W. LaFramboise" <aar...@aa...>: > 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 |