dev:bug_wrangler:faq
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
dev:bug_wrangler:faq [2013/04/22 17:37] – yboston | dev:bug_wrangler:faq [2024/04/22 15:02] (current) – Added section to link to UI Accessibility Checklist lhernandez | ||
---|---|---|---|
Line 15: | Line 15: | ||
* What you expected to happen. | * What you expected to happen. | ||
- | Frequently, users have questions regarding the different statuses and importance values assigned to bugs on Launchpad. | + | Frequently, users have questions regarding the different statuses and importance values assigned to bugs on Launchpad. |
===== Bug Status Definitions ===== | ===== Bug Status Definitions ===== | ||
Line 24: | Line 24: | ||
* **Invalid** - Bug is unreproducible by multiple users, other than the submitter. | * **Invalid** - Bug is unreproducible by multiple users, other than the submitter. | ||
* **Won' | * **Won' | ||
- | * **Confirmed** - Bug is confirmed by one or more users, other than the submitter. | + | * **Confirmed** - Bug is confirmed by one or more users, other than the submitter. |
* **Triaged** - Bug has been acknowledged. It isn't new or confirmed, but we'll assign a real status later. | * **Triaged** - Bug has been acknowledged. It isn't new or confirmed, but we'll assign a real status later. | ||
* **In Progress** - A developer is actively working on a solution to this bug, or may be awaiting commit/ | * **In Progress** - A developer is actively working on a solution to this bug, or may be awaiting commit/ | ||
Line 44: | Line 44: | ||
When you have finished either writing or reviewing the code, please remove your assignment from a bug. If you were reviewing code and you have questions for the programmer, you may reassign the bug to them as a signal that the code still needs work. If you do this, you should also add a comment to the bug explaining why you think the code needs more work or asking your questions. | When you have finished either writing or reviewing the code, please remove your assignment from a bug. If you were reviewing code and you have questions for the programmer, you may reassign the bug to them as a signal that the code still needs work. If you do this, you should also add a comment to the bug explaining why you think the code needs more work or asking your questions. | ||
===== Milestones ===== | ===== Milestones ===== | ||
- | //Needs expansion// | + | |
+ | NOTE: The following examples are based on the 2 series of Evergreen and use 2.7 terminology to give some substance to how milestones may operate. | ||
+ | |||
+ | Milestones for wishlist bugs for new features may be assigned to the next release for future review before they are fully finished. | ||
+ | |||
+ | Bug reports and fixes may be assigned to the actual milestone where we plan to include the fix. These normally only get specific milestones now when there is working code to test and there is a " | ||
+ | |||
+ | ===== Tags ===== | ||
+ | |||
+ | Look for the " | ||
+ | |||
+ | There are a few tags that we use in a special way: | ||
+ | |||
+ | * **pullrequest**: | ||
+ | * **needsrepatch**: | ||
+ | * **signedoff**: | ||
+ | * **needstest**: | ||
+ | * **needsreleasenote**: | ||
+ | * **bitesize**: | ||
+ | |||
+ | A list of tag definitions in use as of 2020 can be seen [[dev: | ||
+ | |||
+ | ===== Accessibility Testing Tools ===== | ||
+ | |||
+ | Use the [[accessibility: |
dev/bug_wrangler/faq.txt · Last modified: 2024/04/22 15:02 by lhernandez