life-cycle-of-story: Add creation of upstream stories

* Add another item that discussed the creation of the stories
  for addressing maintainer feedback and tracking the merge of
  patches into the maintainer tree.

Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>

diff --git a/life-cycle-of-story.tex b/life-cycle-of-story.tex
index adac185ce63a062a16056b4cec34fdd61ef51b8f..099fb633c45287ebf088f6a6300a38f9ea4e0e98 100644 (file)
--- a/life-cycle-of-story.tex
+++ b/life-cycle-of-story.tex
@@ -159,6 +159,18 @@ Done within the tool.
           determined to be done then it can be \textbf{Closed} which will move
           it to the \textit{Accepted} state and close all the tasks within
           that backlog item as well.
+    \item For any items that had an \textbf{Upstream} component there should
+          be the following stories created:
+        \begin{itemize}
+            \item A story should be created to address maintainer feedback.
+                  ideally the patches have been submitted early enough that
+                  you will know if there will be maintainer feedback prior
+                  to the next sprint planning.
+            \item A story must be created indicating the \textbf{Merged} item.
+                  This story should be added to the backlog and assigned into
+                  the proper epic to allow tracking of the merge of the patches
+                  into the upstream tree.
+        \end{itemize} 
 \end{enumerate}
 
 \paragraph{}