diff options
| author | Andres Gomez <[email protected]> | 2019-01-07 19:04:34 +0200 |
|---|---|---|
| committer | Andres Gomez <[email protected]> | 2019-01-10 15:53:02 +0200 |
| commit | 6c3164cd08ebecfc6a07ec21915072fadf499b12 (patch) | |
| tree | ea2fd4c352ffc653512073d77a15673fe46eda85 /docs/releasing.html | |
| parent | 428164d87f8dc1d378236b4913538803653770c6 (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/releasing.html')
| -rw-r--r-- | docs/releasing.html | 14 |
1 files changed, 12 insertions, 2 deletions
diff --git a/docs/releasing.html b/docs/releasing.html index e4c770f9186..851bbf58670 100644 --- a/docs/releasing.html +++ b/docs/releasing.html @@ -56,9 +56,10 @@ For example: <p> Releases should happen on Wednesdays. Delays can occur although those -should be keep to a minimum. +should be kept to a minimum. <br> -See our <a href="release-calendar.html" target="_parent">calendar</a> for the +See our <a href="release-calendar.html" target="_parent">calendar</a> +for information about how the release schedule is planned, and the date and other details for individual releases. </p> @@ -67,6 +68,9 @@ date and other details for individual releases. <li>Available approximately every three months. <li>Initial timeplan available 2-4 weeks before the planned branchpoint (rc1) on the mesa-announce@ mailing list. +<li>Typically, the final release will happen after 4 +candidates. Additional ones may be needed in order to resolve blocking +regressions, though. <li>A <a href="#prerelease">pre-release</a> announcement should be available approximately 24 hours before the final (non-rc) release. </ul> @@ -84,6 +88,12 @@ Note: There is one or two releases overlap when changing branches. For example: <br> 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. +<br> +This also involves that, as a final release may be delayed due to the +need of additional candidates to solve some blocking regression(s), +the release manager might have to update +the <a href="release-calendar.html" target="_parent">calendar</a> with +additional bug fix releases of the current stable branch. </p> |