From bd8537fa71a8f1d7e6300f60da07bf458b3ac9ac Mon Sep 17 00:00:00 2001 From: Andres Gomez Date: Fri, 19 Jan 2018 00:29:08 +0200 Subject: [PATCH] docs: add a notice whenever a release is the final in a series Cc: Emil Velikov Cc: Juan A. Suarez Romero Signed-off-by: Andres Gomez Reviewed-by: Eric Engestrom Reviewed-by: Juan A. Suarez Reviewed-by: Emil Velikov --- docs/releasing.html | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/docs/releasing.html b/docs/releasing.html index c7f5dfe5d2b..f65d6d4173d 100644 --- a/docs/releasing.html +++ b/docs/releasing.html @@ -272,6 +272,11 @@ It is followed by a brief period (normally 24 or 48 hours) before the actual release is made.

+

+Be aware to add a note to warn about a final release in a series, if +that is the case. +

+

Terminology used

  • Nominated
@@ -311,6 +316,10 @@ The candidate for the Mesa X.Y.Z is now available. Currently we have: - NUMBER nominated (outstanding) - and NUMBER rejected patches +[If applicable: +Note: this is the final anticipated release in the SERIES series. Users are +encouraged to migrate to the NEXT_SERIES series in order to obtain future fixes.] + BRIEF SUMMARY OF CHANGES Take a look at section "Mesa stable queue" for more information. @@ -594,7 +603,8 @@ Something like the following steps will do the trick:

Also, edit docs/relnotes.html to add a link to the new release notes, -edit docs/index.html to add a news entry, and remove the version from +edit docs/index.html to add a news entry and a note in case of the +last release in a series, and remove the version from docs/release-calendar.html. Then commit and push:

@@ -610,6 +620,11 @@ docs/release-calendar.html. Then commit and push: Use the generated template during the releasing process.

+

+Again, pay attention to add a note to warn about a final release in a +series, if that is the case. +

+

Update the mesa3d.org website

-- 2.30.2