ErrataDesign » History » Revision 4
Revision 3 (Kyle Baker, 12/03/2014 02:57 PM) → Revision 4/10 (Kyle Baker, 12/04/2014 09:37 AM)
h1. Errata Management h2. Summary Errata Management should be improved so that a user can know when new errata have been brought down, and can view the relationship between errata and hosts. Errata Notifications should be simplified so that customers recieve fewer coarse grained emails, rather then more fine grained emails. For these requirements we use these definitions: * Applicable: An errata will be applied if the host runs yum update * Available: An errata has been synced, but not promoted to where a host can consume it * Present: An errata has been synced, but would never be applied to a host by yum update. h2. Targeted Release Foreman 1.8 / Katello 2.2 h2. Trackers -- * Errata Management: ** http://projects.theforeman.org/projects/katello/issues?query_id=64 * Errata Management Email Notifications ** http://projects.theforeman.org/projects/katello/issues?query_id=67 * Errata Management Environment/Content Views ** http://projects.theforeman.org/projects/katello/issues?query_id=68 * Errata Management Errata View ** http://projects.theforeman.org/projects/katello/issues?query_id=66 * Errata Management Host View ** http://projects.theforeman.org/projects/katello/issues?query_id=65 * Email Features: ** http://projects.theforeman.org/projects/katello/issues?query_id=67 h2. Targeted Persona System Engineer h2. Status h3. User Stories Owner - David Caplan Status - Finished Blockers - None h3. Requirements Owner - Mike Mccune / David Caplan Status - Done Blockers - None h3. Wireframes Owner - Kyle Baker Status - Done Blockers - None Last updated 10/29/2014 - https://dl.dropboxusercontent.com/u/5892944/Errata%20Management-2014-10-29.pdf h3. Development Stories Owner - Walden Raines Status - In Progress Expected Delivery - TBD Blockers - None h2. Documentation h3. User Stories * Please include a story describing how the user would transverse this feature including the workflow. This story ideally would include what their actions would be before and after completion of the task. h3. Requirements * User stories will be broken down of the into specific actionable tasks to design and develop against. h3. Development Tasks * Errata Management: ** http://projects.theforeman.org/projects/katello/issues?query_id=64 * Errata Management Email Notifications ** http://projects.theforeman.org/projects/katello/issues?query_id=67 * Errata Management Environment/Content Views ** http://projects.theforeman.org/projects/katello/issues?query_id=68 * Errata Management Errata View ** http://projects.theforeman.org/projects/katello/issues?query_id=66 * Errata Management Host View ** http://projects.theforeman.org/projects/katello/issues?query_id=65 * Email Features: ** http://projects.theforeman.org/projects/katello/issues?query_id=67 h3. Impacted h3. Future Requirements (specifically not in) h3. More Information