Project

General

Profile

ErrataDesign » History » Version 4

Kyle Baker, 12/04/2014 09:37 AM

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 4 Kyle Baker
--
19 1 Mike McCune
20 2 Kyle Baker
h2. Targeted Persona
21 1 Mike McCune
22 3 Kyle Baker
System Engineer 
23 1 Mike McCune
24 2 Kyle Baker
h2. Status
25 1 Mike McCune
26
h3. User Stories
27 2 Kyle Baker
28 3 Kyle Baker
Owner - David Caplan
29
Status - Finished
30 1 Mike McCune
Blockers - None
31
32
h3. Requirements 
33 2 Kyle Baker
34 3 Kyle Baker
Owner - Mike Mccune / David Caplan
35
Status - Done
36
Blockers  - None
37 1 Mike McCune
38 2 Kyle Baker
h3. Wireframes
39 1 Mike McCune
40 3 Kyle Baker
Owner - Kyle Baker
41
Status - Done
42
Blockers - None
43
Last updated 10/29/2014 - https://dl.dropboxusercontent.com/u/5892944/Errata%20Management-2014-10-29.pdf
44 1 Mike McCune
45
h3. Development Stories
46
47 3 Kyle Baker
Owner - Walden Raines
48
Status - In Progress
49 1 Mike McCune
Expected Delivery - TBD
50
Blockers - None
51
52
h2. Documentation
53
54
h3. User Stories
55
56
* 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.
57
 
58
h3. Requirements
59
60
* User stories will be broken down of the into specific actionable tasks to design and develop against.
61 4 Kyle Baker
62
h3. Development Tasks
63
64
* Errata Management:
65
** http://projects.theforeman.org/projects/katello/issues?query_id=64
66
* Errata Management Email Notifications
67
** http://projects.theforeman.org/projects/katello/issues?query_id=67
68
* Errata Management Environment/Content Views
69
** http://projects.theforeman.org/projects/katello/issues?query_id=68
70
* Errata Management Errata View
71
** http://projects.theforeman.org/projects/katello/issues?query_id=66
72
* Errata Management Host View
73
** http://projects.theforeman.org/projects/katello/issues?query_id=65
74
* Email Features:
75
** http://projects.theforeman.org/projects/katello/issues?query_id=67
76 3 Kyle Baker
77
h3. Impacted
78
79
h3. Future Requirements (specifically not in)
80
81
h3. More Information