# HG changeset patch # User Jonathan Davies <[email protected]> # Date 1271664010 -3600 # Node ID ffa1996911197f2677893932ef79fd8c2151ac24 # Parent 6b5fa1fa0edd1201116abd130a3ba1a4ea6a4804 Suggested change to the deprecation policy.
Signed-off-by: Jonathan Davies <[email protected]> diff -r 6b5fa1fa0edd -r ffa199691119 docs/evolution/main.tex --- a/docs/evolution/main.tex Mon Apr 19 09:00:09 2010 +0100 +++ b/docs/evolution/main.tex Mon Apr 19 09:00:10 2010 +0100 @@ -48,7 +48,9 @@ \end{verbatim} where \texttt{<release>} identifies a major release of the software. -\item Every release must be accompanied by a {\em deprecation statement} which lists all fields and messages marked as deprecated in the release. Next to each deprecated item should be an explanation of how to modify a client to avoid using the deprecated field or message. +\item Every release must be accompanied by a {\em deprecation statement} which lists all fields and messages marked as deprecated in the release. +Newly deprecated fields and messages should be clearly highlighted. +Next to each deprecated item should be an explanation of how to modify a client to avoid using the deprecated field or message. \item The deprecation statement shall be prominently displayed in the XenAPI html documentation.
# HG changeset patch # User Jonathan Davies <[email protected]> # Date 1271664010 -3600 # Node ID ffa1996911197f2677893932ef79fd8c2151ac24 # Parent 6b5fa1fa0edd1201116abd130a3ba1a4ea6a4804 Suggested change to the deprecation policy. Signed-off-by: Jonathan Davies <[email protected]> diff -r 6b5fa1fa0edd -r ffa199691119 docs/evolution/main.tex --- a/docs/evolution/main.tex Mon Apr 19 09:00:09 2010 +0100 +++ b/docs/evolution/main.tex Mon Apr 19 09:00:10 2010 +0100 @@ -48,7 +48,9 @@ \end{verbatim} where \texttt{<release>} identifies a major release of the software. -\item Every release must be accompanied by a {\em deprecation statement} which lists all fields and messages marked as deprecated in the release. Next to each deprecated item should be an explanation of how to modify a client to avoid using the deprecated field or message. +\item Every release must be accompanied by a {\em deprecation statement} which lists all fields and messages marked as deprecated in the release. +Newly deprecated fields and messages should be clearly highlighted. +Next to each deprecated item should be an explanation of how to modify a client to avoid using the deprecated field or message. \item The deprecation statement shall be prominently displayed in the XenAPI html documentation.
_______________________________________________ xen-api mailing list [email protected] http://lists.xensource.com/mailman/listinfo/xen-api
