third_party_mesa3d/docs/release-calendar.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html lang="en">
<head>
  <meta http-equiv="content-type" content="text/html; charset=utf-8">
  <title>Release Calendar</title>
  <link rel="stylesheet" type="text/css" href="mesa.css">
</head>
<body>

<div class="header">
  The Mesa 3D Graphics Library
</div>

<iframe src="contents.html"></iframe>
<div class="content">

<h1>Release Calendar</h1>

<h2>Overview</h2>

<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.
</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>

<h2 id="calendar">Calendar</h2>

<table border="1">

<tr>
<th>Branch</th>
<th>Expected date</th>
<th>Release</th>
<th>Release manager</th>
<th>Notes</th>
</tr>
<tr>
<td rowspan="1">20.0</td>
<td>2020-05-27</td>
<td>20.0.8</td>
<td>Dylan Baker</td>
<td>Last planned release of the 20.0 series</td>
</tr>
<tr>
<td rowspan="8">20.1</td>
<td>2020-06-10</td>
<td>20.1.1</td>
<td>Eric Engestrom</td>
<td></td>
</tr>
<tr>
<td>2020-06-24</td>
<td>20.1.2</td>
<td>Eric Engestrom</td>
<td></td>
</tr>
<tr>
<td>2020-07-08</td>
<td>20.1.3</td>
<td>Eric Engestrom</td>
<td></td>
</tr>
<tr>
<td>2020-07-22</td>
<td>20.1.4</td>
<td>Eric Engestrom</td>
<td></td>
</tr>
<tr>
<td>2020-08-05</td>
<td>20.1.5</td>
<td>Eric Engestrom</td>
<td></td>
</tr>
<tr>
<td>2020-08-19</td>
<td>20.1.6</td>
<td>Eric Engestrom</td>
<td></td>
</tr>
<tr>
<td>2020-09-02</td>
<td>20.1.7</td>
<td>Eric Engestrom</td>
<td></td>
</tr>
<tr>
<td>2020-09-16</td>
<td>20.1.8</td>
<td>Eric Engestrom</td>
<td>Last planned release of the 20.1 series</td>
</tr>
</table>

</div>
</body>
</html>
docs: add release calendar page and references to it Add a page that has information which release is expected when and associated information. Reference to it from the "Releasing process" and "Release notes" pages. v2: - Add Andres for 17.0.5 - Rework table format to include the branch (Eric) Signed-off-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Eric Engestrom <eric.engestrom@imgtec.com> 2017-04-24 17:22:19 +01:00			`<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">`
			`<html lang="en">`
			`<head>`
			`<meta http-equiv="content-type" content="text/html; charset=utf-8">`
docs: renumber headings It's generally frowned upon to have multiple H1 headings in HTML4. So let's make sure each article has a primary heading for the article, and that that heading is the title that is used in the sidebar. While we're at it, let's update the title in the articles to match the title from the sidebar as well. Signed-off-by: Erik Faye-Lund <erik.faye-lund@collabora.com> Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> 2019-05-06 12:57:15 +02:00			`<title>Release Calendar</title>`
docs: add release calendar page and references to it Add a page that has information which release is expected when and associated information. Reference to it from the "Releasing process" and "Release notes" pages. v2: - Add Andres for 17.0.5 - Rework table format to include the branch (Eric) Signed-off-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Eric Engestrom <eric.engestrom@imgtec.com> 2017-04-24 17:22:19 +01:00			`<link rel="stylesheet" type="text/css" href="mesa.css">`
			`</head>`
			`<body>`

			`<div class="header">`
docs: drop h1 in header It's generally frowned upon to have more than one H1 per document in HTML4. So let's put the text directly inside the header. This means we can drop the flex-based centering, which makes things a bit easier. We also need to change the padding to rem instead of em, because the em has now changed. Signed-off-by: Erik Faye-Lund <erik.faye-lund@collabora.com> Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> 2019-05-06 13:26:47 +02:00			`The Mesa 3D Graphics Library`
docs: add release calendar page and references to it Add a page that has information which release is expected when and associated information. Reference to it from the "Releasing process" and "Release notes" pages. v2: - Add Andres for 17.0.5 - Rework table format to include the branch (Eric) Signed-off-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Eric Engestrom <eric.engestrom@imgtec.com> 2017-04-24 17:22:19 +01:00			`</div>`

			`<iframe src="contents.html"></iframe>`
			`<div class="content">`

docs: renumber headings It's generally frowned upon to have multiple H1 headings in HTML4. So let's make sure each article has a primary heading for the article, and that that heading is the title that is used in the sidebar. While we're at it, let's update the title in the articles to match the title from the sidebar as well. Signed-off-by: Erik Faye-Lund <erik.faye-lund@collabora.com> Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> 2019-05-06 12:57:15 +02:00			`<h1>Release Calendar</h1>`

			`<h2>Overview</h2>`
docs: add release calendar page and references to it Add a page that has information which release is expected when and associated information. Reference to it from the "Releasing process" and "Release notes" pages. v2: - Add Andres for 17.0.5 - Rework table format to include the branch (Eric) Signed-off-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Eric Engestrom <eric.engestrom@imgtec.com> 2017-04-24 17:22:19 +01:00
			`<p>`
			`Mesa provides feature/development and stable releases.`
			`</p>`
docs: do not use br-tag for non-significant breaks According to the W3C, we shouldn't use the br-tag unless the line-break is part of the content: https://www.w3.org/TR/2011/WD-html5-author-20110809/the-br-element.html All of these instances are for non-content usage, and is as such technically out-of-spec. So let's either remove them, or split paragraphs, based on how related the content are. Signed-off-by: Erik Faye-Lund <erik.faye-lund@collabora.com> Reviewed-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> 2019-06-03 18:30:23 +02:00
docs: add release calendar page and references to it Add a page that has information which release is expected when and associated information. Reference to it from the "Releasing process" and "Release notes" pages. v2: - Add Andres for 17.0.5 - Rework table format to include the branch (Eric) Signed-off-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Eric Engestrom <eric.engestrom@imgtec.com> 2017-04-24 17:22:19 +01:00			`<p>`
			`The table below lists the date and release manager that is expected to do the`
			`specific release.`
docs: do not use br-tag for non-significant breaks According to the W3C, we shouldn't use the br-tag unless the line-break is part of the content: https://www.w3.org/TR/2011/WD-html5-author-20110809/the-br-element.html All of these instances are for non-content usage, and is as such technically out-of-spec. So let's either remove them, or split paragraphs, based on how related the content are. Signed-off-by: Erik Faye-Lund <erik.faye-lund@collabora.com> Reviewed-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> 2019-06-03 18:30:23 +02:00			`</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>.`
docs: remove pointless, stray newline Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3443> 2020-01-16 21:03:08 +01:00			`</p>`
docs: do not use br-tag for non-significant breaks According to the W3C, we shouldn't use the br-tag unless the line-break is part of the content: https://www.w3.org/TR/2011/WD-html5-author-20110809/the-br-element.html All of these instances are for non-content usage, and is as such technically out-of-spec. So let's either remove them, or split paragraphs, based on how related the content are. Signed-off-by: Erik Faye-Lund <erik.faye-lund@collabora.com> Reviewed-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> 2019-06-03 18:30:23 +02:00			`<p>`
docs: add release calendar page and references to it Add a page that has information which release is expected when and associated information. Reference to it from the "Releasing process" and "Release notes" pages. v2: - Add Andres for 17.0.5 - Rework table format to include the branch (Eric) Signed-off-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Eric Engestrom <eric.engestrom@imgtec.com> 2017-04-24 17:22:19 +01:00			`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>`

docs: renumber headings It's generally frowned upon to have multiple H1 headings in HTML4. So let's make sure each article has a primary heading for the article, and that that heading is the title that is used in the sidebar. While we're at it, let's update the title in the articles to match the title from the sidebar as well. Signed-off-by: Erik Faye-Lund <erik.faye-lund@collabora.com> Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> 2019-05-06 12:57:15 +02:00			`<h2 id="calendar">Calendar</h2>`
docs: add release calendar page and references to it Add a page that has information which release is expected when and associated information. Reference to it from the "Releasing process" and "Release notes" pages. v2: - Add Andres for 17.0.5 - Rework table format to include the branch (Eric) Signed-off-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Eric Engestrom <eric.engestrom@imgtec.com> 2017-04-24 17:22:19 +01:00
			`<table border="1">`

			`<tr>`
			`<th>Branch</th>`
			`<th>Expected date</th>`
			`<th>Release</th>`
			`<th>Release manager</th>`
			`<th>Notes</th>`
docs: add 18.0.5 in the release calendar Mesa 18.1 series has not been released yet, so let's extend 18.0 lifetime. v2: Add missing closing TR tags (Eric Engestrom) CC: Andres Gomez <agomez@igalia.com> CC: Emil Velikov <emil.l.velikov@gmail.com> Reviewed-by: Andres Gomez <agomez@igalia.com> 2018-05-14 16:17:38 +02:00			`</tr>`
docs: update 17.3 and 18.0 cycles for the release calendar Cc: Emil Velikov <emil.velikov@collabora.com> Cc: Juan A. Suarez Romero <jasuarez@igalia.com> Signed-off-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Juan A. Suarez <jasuarez@igalia.com> Reviewed-by: Emil Velikov <emil.velikov@collabora.com> 2017-12-18 21:31:23 +02:00			`<tr>`
docs: update calendar, add news item, and link releases notes for 20.0.7 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5041> 2020-05-14 10:14:53 -07:00			`<td rowspan="1">20.0</td>`
docs/release-calendar: Add calendar for 20.1 Release candidates It's time to start getting the calendar going for 20.1 so that everyone is clear on when the close date for new features is. Eric Engstrom has agreed to help out with the 20.1 series, and will be the primary point, he's also helping out with a few of the 20.0.x point releases. Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Acked-by: Eric Engestrom <eric@engestrom.ch> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4077> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4077> 2020-03-05 15:48:42 -08:00			`<td>2020-05-27</td>`
docs: update calendar, add news item, and link releases notes for 20.0.4 Note that the next 20.0.x releases numbers have been shifted as this was not one of the planned releases. Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4428> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4428> 2020-04-03 13:12:10 +02:00			`<td>20.0.8</td>`
docs/release-calendar: Add calendar for 20.1 Release candidates It's time to start getting the calendar going for 20.1 so that everyone is clear on when the close date for new features is. Eric Engstrom has agreed to help out with the 20.1 series, and will be the primary point, he's also helping out with a few of the 20.0.x point releases. Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Acked-by: Eric Engestrom <eric@engestrom.ch> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4077> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4077> 2020-03-05 15:48:42 -08:00			`<td>Dylan Baker</td>`
			`<td>Last planned release of the 20.0 series</td>`
			`</tr>`
			`<tr>`
docs: update calendar, add news item, and link releases notes for 20.1.0 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5234> 2020-05-27 22:27:17 +02:00			`<td rowspan="8">20.1</td>`
			`<td>2020-06-10</td>`
			`<td>20.1.1</td>`
			`<td>Eric Engestrom</td>`
			`<td></td>`
			`</tr>`
			`<tr>`
			`<td>2020-06-24</td>`
			`<td>20.1.2</td>`
			`<td>Eric Engestrom</td>`
			`<td></td>`
			`</tr>`
			`<tr>`
			`<td>2020-07-08</td>`
			`<td>20.1.3</td>`
			`<td>Eric Engestrom</td>`
			`<td></td>`
			`</tr>`
			`<tr>`
			`<td>2020-07-22</td>`
			`<td>20.1.4</td>`
			`<td>Eric Engestrom</td>`
			`<td></td>`
			`</tr>`
			`<tr>`
			`<td>2020-08-05</td>`
			`<td>20.1.5</td>`
			`<td>Eric Engestrom</td>`
			`<td></td>`
			`</tr>`
			`<tr>`
			`<td>2020-08-19</td>`
			`<td>20.1.6</td>`
			`<td>Eric Engestrom</td>`
			`<td></td>`
			`</tr>`
			`<tr>`
			`<td>2020-09-02</td>`
			`<td>20.1.7</td>`
			`<td>Eric Engestrom</td>`
			`<td></td>`
			`</tr>`
			`<tr>`
			`<td>2020-09-16</td>`
			`<td>20.1.8</td>`
docs/release-calendar: Add calendar for 20.1 Release candidates It's time to start getting the calendar going for 20.1 so that everyone is clear on when the close date for new features is. Eric Engstrom has agreed to help out with the 20.1 series, and will be the primary point, he's also helping out with a few of the 20.0.x point releases. Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Acked-by: Eric Engestrom <eric@engestrom.ch> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4077> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4077> 2020-03-05 15:48:42 -08:00			`<td>Eric Engestrom</td>`
docs: update calendar, add news item, and link releases notes for 20.1.0 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5234> 2020-05-27 22:27:17 +02:00			`<td>Last planned release of the 20.1 series</td>`
docs/release-calendar: Add calendar for 20.1 Release candidates It's time to start getting the calendar going for 20.1 so that everyone is clear on when the close date for new features is. Eric Engstrom has agreed to help out with the 20.1 series, and will be the primary point, he's also helping out with a few of the 20.0.x point releases. Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Acked-by: Eric Engestrom <eric@engestrom.ch> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4077> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4077> 2020-03-05 15:48:42 -08:00			`</tr>`
docs: add release calendar page and references to it Add a page that has information which release is expected when and associated information. Reference to it from the "Releasing process" and "Release notes" pages. v2: - Add Andres for 17.0.5 - Rework table format to include the branch (Eric) Signed-off-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Eric Engestrom <eric.engestrom@imgtec.com> 2017-04-24 17:22:19 +01:00			`</table>`

			`</div>`
			`</body>`
			`</html>`