summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDylan Baker <[email protected]>2019-09-20 10:37:14 -0700
committerDylan Baker <[email protected]>2019-09-25 10:46:59 -0700
commitc8fa996dcfa9c7c31baaec2eb32b1f78f8286c8c (patch)
tree6d74327c2d3ece5d723f00ee022311c8e35aa607
parent666a5a22305c3db027cfab900496688493f19653 (diff)
release: Push 19.3 back two weeks
The main reason to do this is that 19.2 has slipped by two weeks, and such the 19.3 branch is due to happen extremely close to the release of 19.2.0. I think it would be better to have a little more time between releases for developers and for packagers. This would still have the 19.3 release out before December, even if it slips by 1 week. Acked-By: Karol Herbst <[email protected]> Acked-by: Juan A. Suarez <[email protected]>
-rw-r--r--docs/release-calendar.html8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/release-calendar.html b/docs/release-calendar.html
index 8df86f44e94..2711371a005 100644
--- a/docs/release-calendar.html
+++ b/docs/release-calendar.html
@@ -90,25 +90,25 @@ if you'd like to nominate a patch in the next stable release.
</tr>
<tr>
<td rowspan="4">19.3</td>
-<td>2019-10-15</td>
+<td>2019-10-30</td>
<td>19.3.0-rc1</td>
<td>Dylan Baker</td>
<td>
</tr>
<tr>
-<td>2019-10-22</td>
+<td>2019-11-06</td>
<td>19.3.0-rc2</td>
<td>Dylan Baker</td>
<td>
</tr>
<tr>
-<td>2019-10-29</td>
+<td>2019-11-13</td>
<td>19.3.0-rc3</td>
<td>Dylan Baker</td>
<td>
</tr>
<tr>
-<td>2019-11-05</td>
+<td>2019-11-20</td>
<td>19.3.0-rc4</td>
<td>Dylan Baker</td>
<td>Last planned RC/Final release</td>