[PUP-5776] Master Theme: Working with Themes and Epics in the Puppet Project Created: 2016/01/29 Updated: 2018/11/30
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
As a user of Jira focusing on the PUP project, I want to know about existing Epics, and how they should be applied. When we make released I want to know what needs to be done to ensure we have the relevant Epics defined.
I expect the PUP folks to update this story with links to the available Themes. And that this description is updated with an overall description of how Themes and Epics work.
DESCRIPTION OF THEMES AND EPICS
A Theme represents an activity that stretched over many releases; e.g. "Performance". We use an Epic to describe such themes. They are always named with a prefix of "Theme:". An example is PUP-5775 "Theme: Performance" Epic.
For each release series, there is an Epic that contains the tickets that directly implements something in that theme. Other tickets may also support that Epic. As an example PUP-5773 "4.x Performance" is an Epic that supports "Theme: Performance".
(This construct is used since Jira does not support the notion of Theme).
RELESE SERIES EPICS
Release series epics are named Nx <name_of_theme> e.g. "4.x Performance". Such themes are created lazily when there is going to be work on that theme for a release series.
If there is a need to create an Epic that is closed with a specific release, it should be given a concrete version name e.g. "4.4 Performance", and this ticket should support "4.x Performace". which in turn supports "Theme: Performance".