diff options
Diffstat (limited to 'docs/releasing.html')
| -rw-r--r-- | docs/releasing.html | 24 |
1 files changed, 12 insertions, 12 deletions
diff --git a/docs/releasing.html b/docs/releasing.html index 2dbd03bc6f3..d4aa37a3681 100644 --- a/docs/releasing.html +++ b/docs/releasing.html @@ -2,7 +2,7 @@ <html lang="en"> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> - <title>Releasing process</title> + <title>Releasing Process</title> <link rel="stylesheet" type="text/css" href="mesa.css"> </head> <body> @@ -15,7 +15,7 @@ <div class="content"> -<h1>Releasing process</h1> +<h1>Releasing Process</h1> <ul> <li><a href="#overview">Overview</a> @@ -31,7 +31,7 @@ </ul> -<h1 id="overview">Overview</h1> +<h2 id="overview">Overview</h2> <p> This document uses the convention X.Y.Z for the release number with X.Y being @@ -52,7 +52,7 @@ For example: </pre> -<h1 id="schedule">Release schedule</h1> +<h2 id="schedule">Release schedule</h2> <p> Releases should happen on Wednesdays. Delays can occur although those @@ -97,7 +97,7 @@ additional bug fix releases of the current stable branch. </p> -<h1 id="pickntest">Cherry-picking and testing</h1> +<h2 id="pickntest">Cherry-picking and testing</h2> <p> Commits nominated for the active branch are picked as based on the @@ -223,7 +223,7 @@ system and making some every day's use until the release may be a good idea too. </p> -<h1 id="stagingbranch">Staging branch</h1> +<h2 id="stagingbranch">Staging branch</h2> <p> A live branch, which contains the currently merge/rejected patches is available @@ -243,7 +243,7 @@ Notes: </ul> -<h1 id="branch">Making a branchpoint</h1> +<h2 id="branch">Making a branchpoint</h2> <p> A branchpoint is made such that new development can continue in parallel to @@ -293,7 +293,7 @@ Proceed to <a href="#release">release</a> -rc1. </p> -<h1 id="prerelease">Pre-release announcement</h1> +<h2 id="prerelease">Pre-release announcement</h2> <p> It comes shortly after outstanding patches in the respective branch are pushed. @@ -445,7 +445,7 @@ Reason: The patch was reverted shortly after it was merged. </pre> -<h1 id="release">Making a new release</h1> +<h2 id="release">Making a new release</h2> <p> These are the instructions for making a new Mesa release. @@ -599,7 +599,7 @@ docs/release-calendar.html. Then commit and push: </pre> -<h1 id="announce">Announce the release</h1> +<h2 id="announce">Announce the release</h2> <p> Use the generated template during the releasing process. @@ -611,7 +611,7 @@ series, if that is the case. </p> -<h1 id="website">Update the mesa3d.org website</h1> +<h2 id="website">Update the mesa3d.org website</h2> <p> As the hosting was moved to freedesktop, git hooks are deployed to update the @@ -619,7 +619,7 @@ website. Manually check that it is updated 5-10 minutes after the final <code>gi </p> -<h1 id="bugzilla">Update Bugzilla</h1> +<h2 id="bugzilla">Update Bugzilla</h2> <p> Parse through the bugreports as listed in the docs/relnotes/X.Y.Z.html |