From Fedora Project Wiki
(New page: = Ongoing = # Monitor '''all open''' bugs for releases which are no longer maintained and have reached End of Life (EOL). #* These can usually be closed with a comment from here: [https://...)
 
m (internal link cleaning)
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
= Ongoing =
= Ongoing =
# Monitor '''all open''' bugs for releases which are no longer maintained and have reached End of Life (EOL).
# Monitor '''all open''' bugs for releases which are no longer maintained and have reached End of Life (EOL).
#* These can usually be closed with a comment from here: [https://fedoraproject.org/wiki/BugZappers/StockBugzillaResponses#EOL standard EOL response]
#* These can usually be closed with a comment from here: [[BugZappers/StockBugzillaResponses#EOL|standard EOL response]]
# Monitor and triage all bugs for currently maintained and rawhide releases:
# Monitor and triage all bugs for currently maintained and rawhide releases:
#* Status == NEW  
#* Status == NEW  
Line 7: Line 7:
# Keep an eye out for bugs that need to be fixed before the next major release (blockers) and should be added to the applicable release [[BugZappers/HouseKeeping/Trackers| tracker]].
# Keep an eye out for bugs that need to be fixed before the next major release (blockers) and should be added to the applicable release [[BugZappers/HouseKeeping/Trackers| tracker]].


{{Admon/note | ''More information'' See [[BugZappers/BugStatusWorkFlow|  bug life cycle]] for more information and policies about how the bug states work.}}
{{Admon/note | More information | See [[BugZappers/BugStatusWorkFlow|  bug life cycle]] for more information and policies about how the bug states work.}}

Latest revision as of 21:31, 17 September 2016

Ongoing

  1. Monitor all open bugs for releases which are no longer maintained and have reached End of Life (EOL).
  2. Monitor and triage all bugs for currently maintained and rawhide releases:
    • Status == NEW
    • NEEDINFO reporter for greater than thirty (30) days.
  3. Keep an eye out for bugs that need to be fixed before the next major release (blockers) and should be added to the applicable release tracker.
Note.png
More information
See bug life cycle for more information and policies about how the bug states work.