ErrataDesign » History » Version 3
Kyle Baker, 12/03/2014 02:57 PM
| 1 | 2 | Kyle Baker | h1. Errata Management |
|---|---|---|---|
| 2 | 1 | Mike McCune | |
| 3 | 2 | Kyle Baker | h2. Summary |
| 4 | 1 | Mike McCune | |
| 5 | 2 | Kyle Baker | 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. |
| 6 | 1 | Mike McCune | |
| 7 | 2 | Kyle Baker | For these requirements we use these definitions: |
| 8 | * Applicable: An errata will be applied if the host runs yum update |
||
| 9 | * Available: An errata has been synced, but not promoted to where a host can consume it |
||
| 10 | * Present: An errata has been synced, but would never be applied to a host by yum update. |
||
| 11 | 1 | Mike McCune | |
| 12 | 2 | Kyle Baker | h2. Targeted Release |
| 13 | 1 | Mike McCune | |
| 14 | 3 | Kyle Baker | Foreman 1.8 / Katello 2.2 |
| 15 | 1 | Mike McCune | |
| 16 | 2 | Kyle Baker | h2. Trackers |
| 17 | 1 | Mike McCune | |
| 18 | 2 | Kyle Baker | * Errata Management: |
| 19 | ** http://projects.theforeman.org/projects/katello/issues?query_id=64 |
||
| 20 | * Errata Management Email Notifications |
||
| 21 | ** http://projects.theforeman.org/projects/katello/issues?query_id=67 |
||
| 22 | * Errata Management Environment/Content Views |
||
| 23 | ** http://projects.theforeman.org/projects/katello/issues?query_id=68 |
||
| 24 | * Errata Management Errata View |
||
| 25 | ** http://projects.theforeman.org/projects/katello/issues?query_id=66 |
||
| 26 | * Errata Management Host View |
||
| 27 | ** http://projects.theforeman.org/projects/katello/issues?query_id=65 |
||
| 28 | * Email Features: |
||
| 29 | ** http://projects.theforeman.org/projects/katello/issues?query_id=67 |
||
| 30 | 1 | Mike McCune | |
| 31 | 2 | Kyle Baker | h2. Targeted Persona |
| 32 | 1 | Mike McCune | |
| 33 | 3 | Kyle Baker | System Engineer |
| 34 | 1 | Mike McCune | |
| 35 | 2 | Kyle Baker | h2. Status |
| 36 | 1 | Mike McCune | |
| 37 | h3. User Stories |
||
| 38 | 2 | Kyle Baker | |
| 39 | 3 | Kyle Baker | Owner - David Caplan |
| 40 | Status - Finished |
||
| 41 | 1 | Mike McCune | Blockers - None |
| 42 | |||
| 43 | h3. Requirements |
||
| 44 | 2 | Kyle Baker | |
| 45 | 3 | Kyle Baker | Owner - Mike Mccune / David Caplan |
| 46 | Status - Done |
||
| 47 | Blockers - None |
||
| 48 | 1 | Mike McCune | |
| 49 | 2 | Kyle Baker | h3. Wireframes |
| 50 | 1 | Mike McCune | |
| 51 | 3 | Kyle Baker | Owner - Kyle Baker |
| 52 | Status - Done |
||
| 53 | Blockers - None |
||
| 54 | Last updated 10/29/2014 - https://dl.dropboxusercontent.com/u/5892944/Errata%20Management-2014-10-29.pdf |
||
| 55 | 1 | Mike McCune | |
| 56 | h3. Development Stories |
||
| 57 | |||
| 58 | 3 | Kyle Baker | Owner - Walden Raines |
| 59 | Status - In Progress |
||
| 60 | 1 | Mike McCune | Expected Delivery - TBD |
| 61 | 3 | Kyle Baker | Blockers - None |
| 62 | 2 | Kyle Baker | |
| 63 | h2. Documentation |
||
| 64 | |||
| 65 | h3. User Stories |
||
| 66 | |||
| 67 | * 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. |
||
| 68 | |||
| 69 | h3. Requirements |
||
| 70 | |||
| 71 | * User stories will be broken down of the into specific actionable tasks to design and develop against. |
||
| 72 | 3 | Kyle Baker | |
| 73 | h3. Impacted |
||
| 74 | |||
| 75 | h3. Future Requirements (specifically not in) |
||
| 76 | |||
| 77 | h3. More Information |