Re: Re[2]: .doc -> crash

From: Mark Gilbert (
Date: Tue Apr 01 2003 - 18:01:50 EST

  • Next message: Alan G Isaac: "Re[4]: .doc -> crash"

    On Tue, 2003-04-01 at 15:14, Dom Lachowicz wrote:
    > The practice is to file bugs/crashes in bugzilla
    > (assuming it's not a duplicate of another bug), and
    > then let QA and the developers handle it from there.
    > Files sent to mailing lists get lost, mishandled,
    > forgotten about, ignored, or simply don't reach
    > developers attentions. Bugzilla is the only fool-proof
    > way to go about this sort of thing. If you'd like to
    > see if any other users can confirm your bug (this
    > moving it into the "CONFIRMED" bugzilla state, and
    > thus getting more developers' attentions) please do.
    > But please do so after filing your bug in bugzilla.

    Our states were reverted a wbile back so that now, he should file it UNCONFIRMED, and it gets confirmed if someone else moves it to NEW.
    UNCONFIRMED - Unconfirmed, initial state of bug report
    NEW - Someone besides the reporter confirmed it
    ASSIGNED - Some developer or qa manager accepted the bug
    RESOLVED - A resolution has been committed/decided/etc and is pending verification
    VERIFIED - Verified, the resolution works.
    CLOSED - This state is only for use by developers and qa personnel, indicating a bug which, for whatever reason, does not even belong in the db.

    Best regards

    To unsubscribe from this list, send a message to with the word
    unsubscribe in the message body.

    This archive was generated by hypermail 2.1.4 : Tue Apr 01 2003 - 18:11:00 EST