llvmpipe:fix using 32bit rasterization mistakenly, causing overflows

[mesa.git] / docs / releasing.html

diff --git a/docs/releasing.html b/docs/releasing.html
index 2058c1522e47900621c81e7a91b88f7f55ea4db2..99707bee3f5f03f245150a63be18e0231fe997b5 100644 (file)
--- a/docs/releasing.html
+++ b/docs/releasing.html
@@ -24,6 +24,7 @@
 <li><a href="#branch">Making a branchpoint</a>
 <li><a href="#prerelease">Pre-release announcement</a>
 <li><a href="#release">Making a new release</a>
+<li><a href="#calendar">Update the calendar</a>
 <li><a href="#announce">Announce the release</a>
 <li><a href="#website">Update the mesa3d.org website</a>
 <li><a href="#bugzilla">Update Bugzilla</a>
@@ -95,7 +96,14 @@ described in the same section.
 </p>
 
 <p>
-Maintainer is responsible for testing in various possible permutations of
+Nomination happens in the mesa-stable@ mailing list. However,
+maintainer is resposible of checking for forgotten candidates in the
+master branch. This is achieved by a combination of ad-hoc scripts and
+a casual search for terms such as regression, fix, broken and similar.
+</p>
+
+<p>
+Maintainer is also responsible for testing in various possible permutations of
 the autoconf and scons build.
 </p>
 
@@ -118,11 +126,30 @@ Currently Ilia Mirkin and AMD devs have requested "permanent" exception.
 <li>make distcheck, scons and scons check must pass
 <li>Testing with different version of system components - LLVM and others is also
 performed where possible.
+<li>As a general rule, testing with various combinations of configure
+switches, depending on the specific patchset.
 </ul>
 
 <p>
-Achieved by combination of local ad-hoc scripts and AppVeyor plus Travis-CI,
-the latter as part of their Github integration.
+Achieved by combination of local ad-hoc scripts, mingw-w64 cross
+compilation and AppVeyor plus Travis-CI, the latter as part of their
+Github integration.
+</p>
+
+<p>
+For Windows related changes, the main contact point is Brian
+Paul. Jose Fonseca can also help as a fallback contact.
+</p>
+
+<p>
+For Android related changes, the main contact is Tapani
+P&auml;lli. Mauro Rossi is collaborating with android-x86 and may
+provide feedback about the build status in that project.
+</p>
+
+<p>
+For MacOSX related changes, Jeremy Huddleston Sequoia is currently a
+good contact point.
 </p>
 
 <p>
@@ -177,6 +204,12 @@ and llvmpipe drivers</em>
 Currently testing is performed courtesy of the Intel OTC team and their Jenkins CI setup. Check with the Intel team over IRC how to get things setup.
 </p>
 
+<p>
+Installing the built driver from the pre-announced RC branch in the
+system and making some every day's use until the release may be a good
+idea too.
+</p>
+
 
 <h1 id="branch">Making a branchpoint</h1>
 
@@ -427,7 +460,7 @@ Here is one solution that I've been using.
                --enable-glx-tls \
                --enable-gbm \
                --enable-egl \
-               --with-egl-platforms=x11,drm,wayland
+               --with-platforms=x11,drm,wayland,surfaceless
        make -j2 &amp;&amp; DESTDIR=`pwd`/test make -j6 install
        __glxinfo_cmd='glxinfo 2>&amp;1 | egrep -o "Mesa.*|Gallium.*|.*dri\.so"'
        __glxgears_cmd='glxgears 2>&amp;1 | grep -v "configuration file"'
@@ -543,6 +576,13 @@ docs/index.html to add a news entry. Then commit and push:
 </pre>
 
 
+<h1 id="calendar">Update the calendar</h1>
+
+<p>
+Remove the version from the <a href="release-calendar.html" target="_parent">calendar</a>.
+</p>
+
+
 <h1 id="announce">Announce the release</h1>
 
 <p>