From e0f7d25cf02cff33589e66dbe46f9e43b2656d31 Mon Sep 17 00:00:00 2001 From: Andres Gomez Date: Mon, 27 Mar 2017 21:48:10 +0300 Subject: [PATCH] docs/releasing: format/style homogenization Signed-off-by: Andres Gomez Cc: Emil Velikov Reviewed-by: Emil Velikov --- docs/releasing.html | 35 +++++++++++++++++++++++++++++++---- 1 file changed, 31 insertions(+), 4 deletions(-) diff --git a/docs/releasing.html b/docs/releasing.html index 15df022e5f6..2058c1522e4 100644 --- a/docs/releasing.html +++ b/docs/releasing.html @@ -14,6 +14,7 @@
+

Releasing process

+

Overview

@@ -48,6 +50,7 @@ For example: Mesa 12.0.2 - 12.0 branch, bugfix +

Release schedule

@@ -82,12 +85,14 @@ The final release from the 12.0 series Mesa 12.0.5 will be out around the same time (or shortly after) 13.0.1 is out.

+

Cherry-picking and testing

Commits nominated for the active branch are picked as based on the criteria as described in the same section. +

Maintainer is responsible for testing in various possible permutations of @@ -104,33 +109,38 @@ release. This is made only with explicit permission/request, and the patch must be very well contained. Thus it cannot affect more than one driver/subsystem.

+

Currently Ilia Mirkin and AMD devs have requested "permanent" exception.

-
  • make distcheck, scons and scons check must pass
  • Testing with different version of system components - LLVM and others is also performed where possible.
+

Achieved by combination of local ad-hoc scripts and AppVeyor plus Travis-CI, the latter as part of their Github integration.

+

Note: If a patch in the current queue needs any additional fix(es), then they should be squashed together.
The commit messages and the cherry picked from tags must be preserved.

+

This should be noted in the pre-announce email. +

+ 
     git show b10859ec41d09c57663a258f43fe57c12332698e
 
     commit b10859ec41d09c57663a258f43fe57c12332698e
-    Author: Jonas Pfeil <pfeiljonas@gmx.de>
+    Author: Jonas Pfeil <pfeiljonas@gmx.de>
     Date:   Wed Mar 1 18:11:10 2017 +0100
 
         ralloc: Make sure ralloc() allocations match malloc()'s alignment.
@@ -149,7 +159,6 @@ This should be noted in the pre-announce email.
 
         (cherry picked from commit ff494fe999510ea40e3ed5827e7818550b6de126)
-

Regression/functionality testing

@@ -157,11 +166,13 @@ This should be noted in the pre-announce email. Less often (once or twice), shortly before the pre-release announcement. Ensure that testing is redone if Intel devs have requested an exception, as per above.

+
  • no regressions should be observed for Piglit/dEQP/CTS/Vulkan on Intel platforms
  • no regressions should be observed for Piglit using the swrast, softpipe and llvmpipe drivers
+

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.

@@ -205,15 +216,18 @@ To setup the branchpoint: Now go to Bugzilla and add the new Mesa version X.Y.

+

Check that there are no distribution breaking changes and revert them if needed. For example: files being overwritten on install, etc. Happens extremely rarely - we had only one case so far (see commit 2ced8eb136528914e1bf4e000dea06a9d53c7e04).

+

Proceed to release -rc1.

+

Pre-release announcement

@@ -227,18 +241,22 @@ release is made.

Terminology used

+
  • Nominated
+

Patch that is nominated but yet to to merged in the patch queue/branch.

  • Queued
+

Patch is in the queue/branch and will feature in the next release. Barring reported regressions or objections from developers.

  • Rejected
+

Patch does not fit the criteria and @@ -344,6 +362,7 @@ AUTHOR (NUMBER): Reason: ... +

Making a new release

@@ -351,18 +370,21 @@ These are the instructions for making a new Mesa release.

Get latest source files

+

Ensure the latest code is available - both in your local master and the relevant branch.

Perform basic testing

+

Most of the testing should already be done during the cherry-pick and pre-announce stages. - So we do a quick 'touch test' +

+
  • make distcheck (you can omit this if you're not using --dist below)
  • scons (from release tarball) @@ -455,6 +477,7 @@ be empty (TBD) at this point.

    Two scripts are available to help generate portions of the release notes: +

     	./bin/bugzilla_mesa.sh
@@ -471,6 +494,7 @@ to be included in the release notes.
 
    
 Commit these changes and push the branch.
 
    
+
 
     	git push origin HEAD
 
    
@@ -481,6 +505,7 @@ Commit these changes and push the branch.
 
    
 Start the release process.
 
    
+
 
     	../relative/path/to/release.sh . # append --dist if you've already done distcheck above
 
    
@@ -519,6 +544,7 @@ docs/index.html to add a news entry. Then commit and push:
 
 
 
    Announce the release
    
+
 
    
 Use the generated template during the releasing process.
 
    
@@ -531,6 +557,7 @@ As the hosting was moved to freedesktop, git hooks are deployed to update the
 website. Manually check that it is updated 5-10 minutes after the final git push
 
    
 
+
 
    Update Bugzilla
    
 
 
    
-- 
2.30.2