I don't know much about why we stop at RESOLVED, but what is most likely the preferred path would be to have some sort of QA team that goes through all RESOLVED bugs, tests them, and marks them as VERIFIED accordingly. Then finally it can be closed.
*--* *Tyler Romeo* Stevens Institute of Technology, Class of 2015 Major in Computer Science www.whizkidztech.com | [email protected] On Thu, Aug 2, 2012 at 9:35 PM, Al Snow <[email protected]> wrote: > > Hi - I'm Al Snow. > Applied for the Bug Wrangler position a week ago. Started today setting up > accounts and reading about the internals. Also did some archaeology on > Bugzilla and have some questions.Appears CLOSED status is not used much - > do we stop at RESOLVED or VERIFIED status? How about PRIORITY? See lots of > UNPRIORITIZED that have a active (ACTIVE, RESOLVED) status. Will > double-check docs, but unclear how DUPLICATE tickets are set to CLOSED.How > long does a ticket stay in one status before we need to flag it? > Created a couple of personal Bugzilla monitors (whiners), but any help > with bug triage dashboard/graphs/reports/wizards/extensions would be > appreciated. > Also saw reference to Bug Squad in 2012-2013 Goals. (Thanks - Julian) > ......................................................................My > bug triage ideas, beside the Bug Squad, include looking into:Semi-automatic > detection of duplicates (see Bugzilla e-group)Semi-automatic assignment of > Assignee (saw some external references)Create wizard to improve bug > creation (similar to Google's BITE project ;>) > Wrestle that bug to the ground!Al > PS. Today's notes - if you have questions about what I found in the last > several days. > > > > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
