From Fedora Project Wiki
No edit summary
No edit summary
 
Line 1: Line 1:
This needs to be de-duped against the already existing [[Urgent updates policy]].
* communications
* communications
** announcement(s) to ML(s)?  
** announcement(s) to ML(s)?  

Latest revision as of 19:59, 17 October 2014

This needs to be de-duped against the already existing Urgent updates policy.

  • communications
    • announcement(s) to ML(s)?
    • Fedora Magazine article
  • coordination baton holder
  • releng requirements — pushes and stuff
  • do we need to respin images?
  • do we need to use the urgent-fixes repo?
  • infrastructure consuming the fixes early/first
  • any package rebuilds needed beyond the flawed one?
    • and do any package _builders_ need to be found?
  • coordination of patches - how do we know what to apply
  • test cases... two aspects
    • does the package still function right
    • is the flaw fixed
  • and getting testers lined up