This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [Bugzilla] Missing option to go from WAITING to UNCONFIRMED?



On Thursday, July 10, 2003, at 9:11 AM, Steven Bosscher wrote:


It is now possible to go from WAITING to NEW, but sometimes a bug cannot
be confirmed until feedback is received (missing .i files, specs, the
usual requirements to attempt to reproduce the problem).
And it should be waiting until the feedback is received, at which time it becomes NEW or invalid.
So I suppse we
should have an option to go from WAITING to UNCONFIRMED...?
Why?
We just went through this on bugzilla-masters.
We can't go from WAITING to UNCONFIRMED.
WAITING is both an unconfirmed, and a confirmed, state (IE you can transition a confirmed bug to waiting, and an unconfirmed bug to waiting. There is also a separate flag in Bugzilla's database tracking whether the bug was ever confirmed or not that)
In the unconfirmed state (ie the bug was never confirmed prior to being in WAITING), there is no need for a transition because it's *already* unconfirmed. Thus, the only reasonable transition is to NEW or RESOLVED/<something like INVALID>.
In the confirmed state (Ie the bug was confirmed prior to being in WAITING), you run into the same problems you would trying to transition from NEW to UNCONFIRMED. It's not as simple as changing the status, and doesn't make sense anyway.
Thus, WAITING->UNCONFIRMED is an invalid transition.
The solution is not to confirm bugs until they are ready to be confirmed, not allowing bad transitions.




Gr. Steven


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]