...
Unless otherwise noted, the following assumptions conventions apply to each table:
Stories are indicated with a <number> ID, whereas subtasks to a store are indicated with <parent number>-<child number> ID.
The Blocker field in a story is used to indicate that this story/subtask requires the listed stories/subtasks to be completed before it can be done.
The Story Points field of each subtask contains an initial guess at the appropriate story points for that subtask. Adjust as needed!
When Y appears in one of the OS fields of a story (e.g. EL8) , that story will be replicated for the permutation noted.
When Y appears in one of the OS fields of a subtask, that subtask will be replicated for the permutation noted within the story.
N, -, and a blank entry are all treated as ‘do not replicate’ indicators.
The Notes field will not be included in the ticket and is intended for maintainers or these tables.
...
ID | Ticket Summary (< 100 chars) | Description | Component | Blockers | Story Points | EL7 (Y/N) | EL8 (Y/N) | OEL7 (Y/N) | OEL8 (Y/N) | RH7 (Y/N) | RH8 (Y/N) | Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Release Components | Identify components to be released, verify tests pass, push annotated tags, update SIMP release confluence page. https://simp.readthedocs.io/en/latest/contributors_guide/maintenance/Tagging_and_Releasing_Components.html | - | 3 | ||||||||
1-1 | Identify components to release | - | 1 | |||||||||
1-2 | Release components | 1-1 | 2 | |||||||||
...