summaryrefslogtreecommitdiffstats
path: root/docs/release-calendar.html
diff options
context:
space:
mode:
authorAndres Gomez <[email protected]>2019-01-07 19:04:34 +0200
committerAndres Gomez <[email protected]>2019-01-10 15:53:02 +0200
commit6c3164cd08ebecfc6a07ec21915072fadf499b12 (patch)
treeea2fd4c352ffc653512073d77a15673fe46eda85 /docs/release-calendar.html
parent428164d87f8dc1d378236b4913538803653770c6 (diff)
docs: complete the calendar and release schedule documentation
As suggested by Emil Velikov. Cc: Dylan Baker <[email protected]> Cc: Juan A. Suarez <[email protected]> Cc: Emil Velikov <[email protected]> Signed-off-by: Andres Gomez <[email protected]> Acked-by: Dylan Baker <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
Diffstat (limited to 'docs/release-calendar.html')
-rw-r--r--docs/release-calendar.html10
1 files changed, 10 insertions, 0 deletions
diff --git a/docs/release-calendar.html b/docs/release-calendar.html
index afef899b0e0..3f4e1e9d8b9 100644
--- a/docs/release-calendar.html
+++ b/docs/release-calendar.html
@@ -23,6 +23,16 @@ Mesa provides feature/development and stable releases.
The table below lists the date and release manager that is expected to do the
specific release.
<br>
+Regular updates will ensure that the schedule for the current and the
+next two feature releases are shown in the table.
+<br>
+In order to keep the whole releasing team up to date with the tools
+used, best practices and other details, the member in charge of the
+next feature release will be in constant rotation.
+<br>
+The way the release schedule works is
+explained <a href="releasing.html#schedule" target="_parent">here</a>.
+<br>
Take a look <a href="submittingpatches.html#criteria" target="_parent">here</a>
if you'd like to nominate a patch in the next stable release.
</p>