AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Netbalancer wont open1/6/2023 Read carefully to see if it needs confirmation to remain New or it needs to be changed back to Unconfirmed until it can be reproduced NOTE: Sometimes, reporters mark issues as New without being confirmed by a Mozillian or Community Member. Where it cannot be reproduced, ask the Reporter for additional information or close as Incomplete / WFM The goal is to reduce the Untriaged issues number, by placing them under the correct component. Where a Component is set to something other than Untriaged, leave the bug alone unless asked to do MozRegression or QAWanted Ping Mike for bugs where the Reporter may be difficult and he will take a look into the issueĬlearly mark bug with comments when they later on need to be discussed with Ryanĭifferent actions to be taken for bugs State/Case Information (description, keywords, additional notes.) about the components under Firefox & CORE can be found here Suggested Comments, Contacts & Actions IRC nicknames for contact persons in regards to Bug Triage You can find a list of Bugzilla component ownership for bug decision here Bug Triage Component Selection: Firefox & CORE Manager, Firefox Quality Engineering - Ryan VanderMeulenĬomponents, Contacts and Suggested Comments Bugzilla Component Ownership Intended audience: All team members of Mozilla QA Engineering Team and any third party members interested in this process. This document has the purpose of improving our team’s work quality in regards to Mozilla bug triage process. 2.3.2 Different actions to be taken for bugs. ![]()
0 Comments
Read More
Leave a Reply. |