Bug Triage/Projects/Bug Handling/Bug Husbandry: Difference between revisions
Jump to navigation
Jump to search
(→Update affecteds: notes) |
(→Release Cycle Queries and Activities: branch day) |
||
| Line 15: | Line 15: | ||
== Release Cycle Queries and Activities == | == Release Cycle Queries and Activities == | ||
=== 1 week to | === 1 week to branch === | ||
==== Move fix-optionals ==== | ==== Move fix-optionals ==== | ||
| Line 26: | Line 26: | ||
Leave them marked as affected for upcoming release. | Leave them marked as affected for upcoming release. | ||
=== Branch day === | |||
* Update versions, milestones, tracking, and status | |||
* Add status and tracking for nightly+1 but restrict to release drivers | |||
Revision as of 23:40, 16 January 2018
Bug Farming
Automated cleanup of bugs is handled by the bug-husbandry-bot, under which regular and ad-hoc queries run.
Current Regular Queries
Intermittent Test Failure Cleanup
Closes bugs filed from Orange Factor for intermittent test failures. Intermittent test failure bugs which have had no new failures in 21 days (as measured by comment count) and have not been reopened in the past week are closed.
Other Requests
File a bug in the Bulk Bug Edit Requests component.
Release Cycle Queries and Activities
1 week to branch
Move fix-optionals
Mark all unfixed, fix-optionals for upcoming release (beta) as wontfix and mark as ? for next release unless that status is set (nightly) (Query)
Update affecteds
Mark all unfixed, affected bugs for upcoming release (beta) as ? for next release unless that status is set (nightly) (Query)
Leave them marked as affected for upcoming release.
Branch day
- Update versions, milestones, tracking, and status
- Add status and tracking for nightly+1 but restrict to release drivers