docs/releasing: further explain the build/check testing process

The build/check test should be done with an appropriate combination of
flags, depending on the changes introduced by the patch set.

Also, mention to cross compile with mingw-w64 for Windows.

Signed-off-by: Andres Gomez <agomez@igalia.com>
Cc: Emil Velikov <emil.velikov@collabora.com>
Reviewed-by: Emil Velikov <emil.velikov@collabora.com>

diff --git a/docs/releasing.html b/docs/releasing.html
index f5c1cc78125739d05f5c525d5f671ef75ea8ee3a..cdc19413dbd3c8fa38eccbf75a1d7c34a40cd9ba 100644 (file)
--- a/docs/releasing.html
+++ b/docs/releasing.html
@@ -125,11 +125,14 @@ 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>