summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: d9ce9f5)
raw | patch | inline | side by side (parent: d9ce9f5)
author | Chase Maupin <chase.maupin@ti.com> | |
Fri, 26 Apr 2013 20:55:29 +0000 (15:55 -0500) | ||
committer | Felipe Balbi <balbi@ti.com> | |
Mon, 29 Apr 2013 09:36:55 +0000 (12:36 +0300) |
* Add the requirement for Integration as part of Done so make
sure that we put emphasis on Continuous Integration.
* Update the exceptions section to give examples where this may
not apply since sometimes there is a reason why something will
not make it into the Integration tree and is purely for upstream.
Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
Signed-off-by: Felipe Balbi <balbi@ti.com>
sure that we put emphasis on Continuous Integration.
* Update the exceptions section to give examples where this may
not apply since sometimes there is a reason why something will
not make it into the Integration tree and is purely for upstream.
Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
Signed-off-by: Felipe Balbi <balbi@ti.com>
definition-of-done.tex | patch | blob | history |
diff --git a/definition-of-done.tex b/definition-of-done.tex
index 7f3599c55fca6b1cbbefd0cd974d51c990fb1b83..21cd29a7c4ec1299e0e1bc12a59b6b7215f69310 100644 (file)
--- a/definition-of-done.tex
+++ b/definition-of-done.tex
\item A Backlog item is not Done until it has been Submitted for
integration upstream. For more details see section
\ref{sec:lcpd-definition-submitted}.
+ \item A Backlog item is not Done until it has been Integrated into the
+ TI integration tree for release. For more details see section
+ \ref{sec:lcpd-definition-integrated}.
\end{enumerate}
\paragraph{}
constantly being pushed upstream. More information will be given on this,
including the role of the Product Owner in section \ref{sec:upstreaming}.
+
+\subsection{Integrated}
+\label{lcpd-definition-integrated}
+
+\paragraph{}
+In the LCPD definition of Done an item is not considered Done until it has been
+\textbf{Integrated} into the Integration tree. The purpose is to make sure
+that the work is in a location where it is available for immediate consumption
+by the Business Units to support their customer releases. There are possible
+exceptions to this as detailed in section \ref{sec:exceptions} but the general
+theme is that work done needs to be both upstreamed as well as made available
+within a release to enable customers.
+
\section{Exceptions}
\label{sec:exceptions}
having the developer present a brownbag to the rest of the team about the
new technology area.
+\paragraph{}
+Sometimes a developer may implement a feature in the Integration kernel one
+way but need to change it due to architecture changes or other reasons for
+upstream. In this case the upstream item may not be appropriate for the
+Integration requirement.
+
\paragraph{}
The key point here is that at any time where there is a feeling that one or
more parts of the definition of Done do not apply, this should be agreed by the