Skip to content

Commit 6d1d883

Browse files
committed
Merge #1036: Backfill lifecycle table
0b15471 Introduce EOL abbreviation on first use (Murch) 1f90a79 Backfill lifecycle table (Murch) Pull request description: - Reverse order to put newest version at the top - Put "after version MAJOR.0" for all maintenance end and EOL dates - Backfill all dates up to version 0.8.x from file’s history in repository ACKs for top commit: achow101: ACK 0b15471 sipa: ACK 0b15471 Tree-SHA512: f0ab8ba2faa3a7184b35c98c69e814b63b49fe0bca6ed8515161aced6c16133ebd4151e0308f2a420cfd2330a544650356ecacf3b8ee97ee88d32697a64a0f21
2 parents c4add50 + 0b15471 commit 6d1d883

File tree

2 files changed

+23
-6
lines changed

2 files changed

+23
-6
lines changed

_includes/posts/maintenance-table.md

Lines changed: 21 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,21 @@
1-
| 25.x | 2023-05-18 | 2024-04-16 | TBA |
2-
| 26.x | 2023-12-06 | after v28.0 | TBA |
3-
| 27.x | 2024-04-16 | after v29.0 | TBA |
4-
| 28.x | TBA* | TBA | TBA |
1+
| 28.x | TBA* | after v30.0 | after v31.0 |
2+
| 27.x | 2024-04-16 | after v29.0 | after v30.0 |
3+
| 26.x | 2023-12-06 | after v28.0 | after v29.0 |
4+
| 25.x | 2023-05-18 | 2024-04-16 | after v28.0 |
5+
| 24.x | 2022-11-24 | 2023-12-12 | 2024-04-02 |
6+
| 23.x | 2022-04-25 | 2023-05-18 | 2023-12-01 |
7+
| 22.x | 2021-09-13 | 2022-11-24 | 2023-04-01 |
8+
| 0.21.x | 2021-01-15 | 2022-04-25 | 2022-10-01 |
9+
| 0.20.x | 2020-06-03 | 2021-09-13 | 2022-02-01 |
10+
| 0.19.x | 2019-11-24 | 2021-01-15 | 2021-08-01 |
11+
| 0.18.x | 2019-05-02 | 2020-06-03 | 2021-02-01 |
12+
| 0.17.x | 2018-10-03 | 2019-11-24 | 2020-08-01 |
13+
| 0.16.x | 2018-02-26 | 2019-05-02 | 2020-02-01 |
14+
| 0.15.x | 2017-09-15 | 2018-10-03 | 2019-08-01 |
15+
| 0.14.x | 2017-03-08 | 2018-02-26 | 2019-02-01 |
16+
| 0.13.x | 2016-08-23 | 2017-09-15 | 2018-08-01 |
17+
| 0.12.x | 2016-02-23 | 2017-03-31 | 2018-02-28 |
18+
| 0.11.x | 2015-07-12 | 2016-08-23 | 2017-08-01 |
19+
| 0.10.x | 2015-02-16 | 2016-02-29 | 2017-02-28 |
20+
| 0.9.x | 2014-03-19 | 2015-06-16 | 2016-02-28 |
21+
| 0.8.x | 2013-02-19 | 2014-03-19 | 2015-12-31 |

_posts/en/pages/2016-01-15-lifecycle.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,14 +38,14 @@ We maintain the major versions until their "Maintenance End". We generally maint
3838
For example, if the current release is 23.0, then 22.0 is also considered maintained.
3939
Once 24.0 is released, then 22.0 would be considered at its "Maintenance End".
4040
As a major release ages, issues have to be increasingly critical to be backported to it, and an increasing amount or severity of issues is required to warrant a new minor release.
41-
Once software has reached the "Maintenance End" period it will only receive critical security fixes until the EOL date.
41+
Once software has reached the "Maintenance End" period, it will only receive critical security fixes until the End-of-Life (EOL) date.
4242
After EOL, users must upgrade to a later version to receive security updates, even though the community may provide fixes for critical issues on a best effort basis.
4343
Generally, it is recommended to run the latest maintenance release (point release) of the current or previous major version.
4444

4545
Please note that minor versions get bugfixes, translation updates, and soft forks. Translation on [Transifex][bitcoin-transifex-link] is only open for the last two major releases.
4646

4747
For example, major version 22.0 was released on 2021-09-13 and we provided maintenance fixes (point releases) until 2022-11-15.
48-
Critical security issues would still be continued to be fixed until the End-Of-Life "EOL" date of 2024-04-01.
48+
Critical security issues would still be continued to be fixed until the EOL date of 2024-04-01.
4949
However, to take advantage of bug fixes, you would have to upgrade to a later major version.
5050

5151
## Schedule

0 commit comments

Comments
 (0)