anv: fix alignments for uniform buffers

[mesa.git] / docs / releasing.html

diff --git a/docs/releasing.html b/docs/releasing.html
index e5a453799bba5001d99d650f910866ee5477df4a..3d529f889ab0de67d818ec3c1394e1c3486abc7a 100644 (file)
--- a/docs/releasing.html
+++ b/docs/releasing.html
@@ -18,14 +18,14 @@
 <h1>Releasing Process</h1>
 
 <ul>
-<li><a href="#overview">Overview</a>
-<li><a href="#schedule">Release schedule</a>
-<li><a href="#pickntest">Cherry-pick and test</a>
-<li><a href="#stagingbranch">Staging branch</a>
-<li><a href="#branch">Making a branchpoint</a>
-<li><a href="#release">Making a new release</a>
-<li><a href="#announce">Announce the release</a>
-<li><a href="#gitlab">Update Gitlab Issues</a>
+<li><a href="#overview">Overview</a></li>
+<li><a href="#schedule">Release schedule</a></li>
+<li><a href="#pickntest">Cherry-pick and test</a></li>
+<li><a href="#stagingbranch">Staging branch</a></li>
+<li><a href="#branch">Making a branchpoint</a></li>
+<li><a href="#release">Making a new release</a></li>
+<li><a href="#announce">Announce the release</a></li>
+<li><a href="#gitlab">Update Gitlab Issues</a></li>
 </ul>
 
 
@@ -67,17 +67,18 @@ date and other details for individual releases.
 
 <h2>Feature releases</h2>
 <ul>
-<li>Available approximately every three months.
+<li>Available approximately every three months.</li>
 <li>Initial timeplan available 2-4 weeks before the planned branchpoint (rc1)
-on the mesa-announce@ mailing list.
+on the mesa-announce@ mailing list.</li>
 <li>Typically, the final release will happen after 4
 candidates. Additional ones may be needed in order to resolve blocking
-regressions, though.
+regressions, though.</li>
+</ul>
 
 <h2>Stable releases</h2>
 <ul>
-<li>Normally available once every two weeks.
-<li>Only the latest branch has releases. See note below.
+<li>Normally available once every two weeks.</li>
+<li>Only the latest branch has releases. See note below.</li>
 </ul>
 
 <p>
@@ -135,8 +136,8 @@ well contained. Thus it cannot affect more than one driver/subsystem.
 
 <p>Following developers have requested permanent exception</p>
 <ul>
-<li><em>Ilia Mirkin</em>
-<li><em>AMD team</em>
+<li><em>Ilia Mirkin</em></li>
+<li><em>AMD team</em></li>
 </ul>
 
 <p>The gitlab CI must pass.</p>
@@ -190,9 +191,9 @@ Date:   Wed Mar 1 18:11:10 2017 +0100
 <h2>Regression/functionality testing</h2>
 
 <ul>
-<li><em>no regressions should be observed for Piglit/dEQP/CTS/Vulkan on Intel platforms</em>
+<li><em>no regressions should be observed for Piglit/dEQP/CTS/Vulkan on Intel platforms</em></li>
 <li><em>no regressions should be observed for Piglit using the swrast, softpipe
-and llvmpipe drivers</em>
+and llvmpipe drivers</em></li>
 </ul>
 
 <h2 id="stagingbranch">Staging branch</h2>
@@ -281,9 +282,9 @@ So we do a quick 'touch test'
 </p>
 
 <ul>
-<li>meson dist
-<li>scons (from release tarball)
-<li>the produced binaries work
+<li>meson dist</li>
+<li>scons (from release tarball)</li>
+<li>the produced binaries work</li>
 </ul>
 
 <p>
@@ -381,15 +382,14 @@ git cherry-pick -x X.Y~1
 git cherry-pick -x X.Y
 </pre>
 
-<p>Then run the <code>./bin/post_verison.py X.Y.Z</code>, where X.Y.Z is the
-version you just made. This will updated docs/relnotes.html and
-docs/index.html. Remove the new release from docs/release-calendar.html. Then
-commit and push:
+<p>Then run the <pre>./bin/post_version.py X.Y.Z</pre>, where X.Y.Z is the
+version you just made. This will updated docs/relnotes.html,
+docs/index.html, and docs/release-calendar.html. It will then generate
+a git commit automatically. Check that everything looks correct and push:
 </p>
 
 <pre>
-git commit -as -m "docs: update calendar, add news item and link release notes for X.Y.Z"
-git push origin master X.Y
+       git push origin master X.Y
 </pre>
 
 
@@ -408,7 +408,7 @@ series, if that is the case.
 <h2 id="gitlab">Update gitlab issues</h2>
 
 <p>
-Parse through the bugreports as listed in the docs/relnotes/X.Y.Z.html
+Parse through the bug reports as listed in the docs/relnotes/X.Y.Z.html
 document. If there's outstanding action, close the bug referencing the commit
 ID which addresses the bug and mention the Mesa version that has the fix.
 </p>