X-Git-Url: https://git.libre-soc.org/?a=blobdiff_plain;f=docs%2Freleasing.html;h=14315e7a8e4e05bdf9c882a89b8ae5509458bc9a;hb=05fb2f88ecf46809648230bcdd2c1563b317a188;hp=e588435e81318c70623a0f841935bd40c2b81d59;hpb=5ccbac8e04b5225ec51cfb994bcb09bfacef5314;p=mesa.git diff --git a/docs/releasing.html b/docs/releasing.html index e588435e813..14315e7a8e4 100644 --- a/docs/releasing.html +++ b/docs/releasing.html @@ -54,8 +54,8 @@ For example:
-Releases should happen on Fridays. Delays can occur although those should be keep
-to a minimum.
+Releases should happen on Wednesdays. Delays can occur although those
+should be keep to a minimum.
See our calendar for the
date and other details for individual releases.
@@ -96,7 +96,7 @@ described in the same section.
Nomination happens in the mesa-stable@ mailing list. However, -maintainer is resposible of checking for forgotten candidates in the +maintainer is responsible 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.
@@ -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. +
+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:
@@ -600,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. +
+