diff options
author | Andreas Boll <[email protected]> | 2012-10-02 13:37:34 +0200 |
---|---|---|
committer | Andreas Boll <[email protected]> | 2012-10-02 15:44:00 +0200 |
commit | f07784d9badfdbb5dc8d26d1c1cbd355216307c8 (patch) | |
tree | 9825ec1db3cebb5ced276c074639c6c3394d73d2 /docs | |
parent | e00abb00f058f7476d21ee4be74df59a3a9782b9 (diff) |
docs: document how to mark a candidate for a stable branch
Reviewed-by: Brian Paul <[email protected]>
Diffstat (limited to 'docs')
-rw-r--r-- | docs/devinfo.html | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/docs/devinfo.html b/docs/devinfo.html index 90752b750e8..a52a11ea656 100644 --- a/docs/devinfo.html +++ b/docs/devinfo.html @@ -156,6 +156,22 @@ src/mesa/state_tracker/st_glsl_to_tgsi.cpp can serve as examples. </p> +<h2>Marking a commit as a candidate for a stable branch</h2> + +<p> +If you want a commit to be applied to a stable branch, +you should add an appropriate note to the commit message. +</p> + +<p> +Here are some examples of such a note: +</p> +<ul> + <li>NOTE: This is a candidate for the 9.0 branch.</li> + <li>NOTE: This is a candidate for the 8.0 and 9.0 branches.</li> + <li>NOTE: This is a candidate for the stable branches.</li> +</ul> + <h2>Making a New Mesa Release</h2> <p> |