docs: add MD5 checksums for 9.2.2 files

[mesa.git] / docs / release-calendar.html

diff --git a/docs/release-calendar.html b/docs/release-calendar.html
index c98676b58829bb4c164f597c0bb367e3c6b41a67..70ed01125763f351c71288d99cb9329bc783776a 100644 (file)
--- a/docs/release-calendar.html
+++ b/docs/release-calendar.html
@@ -21,20 +21,29 @@
 <p>
 Mesa provides feature/development and stable releases.
 </p>
+
 <p>
 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>
+</p>
+
+<p>
+Regular updates will ensure that the schedule for the current and the next two
+feature releases are shown in the table.
+</p>
+
+<p>
+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.
+</p>
+
+<p>
+The way the release schedule works is explained
+<a href="releasing.html#schedule" target="_parent">here</a>.
+</p
+>
+<p>
 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>
@@ -51,19 +60,7 @@ if you'd like to nominate a patch in the next stable release.
 <th>Notes</th>
 </tr>
 <tr>
-<td rowspan="3">19.0</td>
-<td>2019-05-07</td>
-<td>19.0.4</td>
-<td>Dylan Baker</td>
-<td>
-</tr>
-<tr>
-<td>2019-05-21</td>
-<td>19.0.5</td>
-<td>Dylan Baker</td>
-<td>
-</tr>
-<tr>
+<td rowspan="1">19.0</td>
 <td>2019-06-04</td>
 <td>19.0.6</td>
 <td>Dylan Baker</td>