Auto-Resolution of UNCO: Yet Another Date

I know we’ve had several attempts at this; here’s another.

Now that Firefox and Thunderbird 1.5beta1 have been released, and so a recent Gecko is available to the general public, the auto-resolution of UNCONFIRMED bugs proposal is going to be put into effect. On Tuesday 27th of September the initial warning will be issued, and on Tuesday 11th of October we’ll be doing the actual resolution of bugs untouched in the previous two weeks.

It will happen in the following products: Core, Toolkit, Firefox, Thunderbird and Mozilla Application Suite.

6 thoughts on “Auto-Resolution of UNCO: Yet Another Date

  1. Will there be any way to restrict people adding the keywords to comments themselves (such as “auto-resolve01”)?

    Products included:

    Firefox
    Thunderbird
    Mozilla Application Suite
    Core
    Toolkit

    Products Excluded:

    Camino
    NSPR
    NSS
    JSS
    PSM

    Possible Products:

    Calendar

    But what about the other 18 products?

    Minimo
    Grendel
    Other Applications

    Directory
    Rhino

    Bugzilla
    Update
    Webtools

    Mozilla Localizations
    Documentation
    Tech Evangelism
    Marketing
    mozilla.org

    CCK

    AUS
    Composer
    Derivatives
    MozillaClassic

  2. Will there be any way to restrict people adding the keywords to comments themselves (such as “auto-resolve01”)?

    No. Does there need to be?

    The other products have either opted out or were not considered suitable. If the
    owners of any of them want to get in touch and say different, that’s great.

  3. “Two weeks later, run a buglist of all bugs where a comment contains the ID used, and which have not changed since the date the comment was added. Do a Change Multiple Bugs, and resolve as the new resolution EXPIRED, using the following comment:

    This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.”

    I was thinking maybe if bogus comments were inserted it would mess up that process and expire some bugs incorrectly… I guess it’s not really going to be a problem though.

  4. dolphinling: you’re looking at two different time periods. The three months is the age of the untouched bugs before we include them in the scheme. The two weeks is the period people have to respond saying “Yes, this bug is still valid, please keep it open”.