diff options
-rw-r--r-- | life-cycle-of-story.tex | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/life-cycle-of-story.tex b/life-cycle-of-story.tex index adac185..099fb63 100644 --- a/life-cycle-of-story.tex +++ b/life-cycle-of-story.tex | |||
@@ -159,6 +159,18 @@ Done within the tool. | |||
159 | determined to be done then it can be \textbf{Closed} which will move | 159 | determined to be done then it can be \textbf{Closed} which will move |
160 | it to the \textit{Accepted} state and close all the tasks within | 160 | it to the \textit{Accepted} state and close all the tasks within |
161 | that backlog item as well. | 161 | that backlog item as well. |
162 | \item For any items that had an \textbf{Upstream} component there should | ||
163 | be the following stories created: | ||
164 | \begin{itemize} | ||
165 | \item A story should be created to address maintainer feedback. | ||
166 | ideally the patches have been submitted early enough that | ||
167 | you will know if there will be maintainer feedback prior | ||
168 | to the next sprint planning. | ||
169 | \item A story must be created indicating the \textbf{Merged} item. | ||
170 | This story should be added to the backlog and assigned into | ||
171 | the proper epic to allow tracking of the merge of the patches | ||
172 | into the upstream tree. | ||
173 | \end{itemize} | ||
162 | \end{enumerate} | 174 | \end{enumerate} |
163 | 175 | ||
164 | \paragraph{} | 176 | \paragraph{} |