ErrataDesign » History » Revision 2
Revision 1 (Mike McCune, 10/28/2014 12:23 AM) → Revision 2/10 (Kyle Baker, 12/03/2014 02:45 PM)
h1. Errata Management Design h2. Summary Issues/Trackers 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. Management: h2. Targeted Release http://projects.theforeman.org/projects/katello/issues?query_id=64 Foreman 0.0 / Katello 0.0 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 Design -- h2. Status h3. User Stories Owner - John Doe Status - Not Started Expected Delivery - TBD Blockers - None h3. Requirements Owner - John Doe Status - Not Started Expected Delivery - TBD Blockers - Waiting on User Stories h3. Wireframes Owner - John Doe Status - Not Started Blockers - Waiting on User Stories & Requirements Last updated TBD - Link to wireframes h3. Development Stories Owner - Foreman (TBD) Katello (TBD) Status - Not Started Expected Delivery - TBD Blockers - Waiting on Wireframes 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.