From Fedora Project Wiki
(Created page with "* communications * coordination baton holder * releng requirements — pushes and stuff * do we need to respin images? * do we need to use the urgent-fixes repo? * infrastruct...") |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
This needs to be de-duped against the already existing [[Urgent updates policy]]. | |||
* communications | * communications | ||
** announcement(s) to ML(s)? | |||
** Fedora Magazine article | |||
* coordination baton holder | * coordination baton holder | ||
** q.v. [http://infrastructure.fedoraproject.org/csi/security-policy/en-US/html-single/ CSI docs]? | |||
* releng requirements — pushes and stuff | * releng requirements — pushes and stuff | ||
* do we need to respin images? | * do we need to respin images? | ||
| Line 11: | Line 16: | ||
** does the package still function right | ** does the package still function right | ||
** is the flaw fixed | ** is the flaw fixed | ||
* and getting testers lined up | |||
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
- q.v. CSI docs?
- 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