Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
48 changes: 24 additions & 24 deletions _includes/posts/maintenance-table.md
Original file line number Diff line number Diff line change
@@ -1,24 +1,24 @@
| 31.x | TBA* | after v33.0 | after v34.0 |
| 30.x | 2025-10-10 | after v32.0 | after v33.0 |
| 29.x | 2025-04-14 | after v31.0 | after v32.0 |
| 28.x | 2024-10-02 | 2025-10-10 | after v31.0 |
| 27.x | 2024-04-16 | 2025-04-14 | 2025-10-10 |
| 26.x | 2023-12-06 | 2024-10-02 | 2025-04-14 |
| 25.x | 2023-05-18 | 2024-04-16 | 2024-10-02 |
| 24.x | 2022-11-24 | 2023-12-12 | 2024-04-02 |
| 23.x | 2022-04-25 | 2023-05-18 | 2023-12-01 |
| 22.x | 2021-09-13 | 2022-12-14 | 2023-04-01 |
| 0.21.x | 2021-01-15 | 2022-04-25 | 2022-10-01 |
| 0.20.x | 2020-06-03 | 2021-09-13 | 2022-02-01 |
| 0.19.x | 2019-11-24 | 2021-01-15 | 2021-08-01 |
| 0.18.x | 2019-05-02 | 2020-06-03 | 2021-02-01 |
| 0.17.x | 2018-10-03 | 2019-11-24 | 2020-08-01 |
| 0.16.x | 2018-02-26 | 2019-05-02 | 2020-02-01 |
| 0.15.x | 2017-09-15 | 2018-10-03 | 2019-08-01 |
| 0.14.x | 2017-03-08 | 2018-02-26 | 2019-02-01 |
| 0.13.x | 2016-08-23 | 2017-09-15 | 2018-08-01 |
| 0.12.x | 2016-02-23 | 2017-03-31 | 2018-02-28 |
| 0.11.x | 2015-07-12 | 2016-08-23 | 2017-08-01 |
| 0.10.x | 2015-02-16 | 2016-02-29 | 2017-02-28 |
| 0.9.x | 2014-03-19 | 2015-06-16 | 2016-02-28 |
| 0.8.x | 2013-02-19 | 2014-03-19 | 2015-12-31 |
| 31.x | TBA* | after v34.0 |
| 30.x | 2025-10-10 | after v33.0 |
| 29.x | 2025-04-14 | after v32.0 |
| 28.x | 2024-10-02 | after v31.0 |
| 27.x | 2024-04-16 | 2025-10-10 |
| 26.x | 2023-12-06 | 2025-04-14 |
| 25.x | 2023-05-18 | 2024-10-02 |
| 24.x | 2022-11-24 | 2024-04-02 |
| 23.x | 2022-04-25 | 2023-12-01 |
| 22.x | 2021-09-13 | 2023-04-01 |
| 0.21.x | 2021-01-15 | 2022-10-01 |
| 0.20.x | 2020-06-03 | 2022-02-01 |
| 0.19.x | 2019-11-24 | 2021-08-01 |
| 0.18.x | 2019-05-02 | 2021-02-01 |
| 0.17.x | 2018-10-03 | 2020-08-01 |
| 0.16.x | 2018-02-26 | 2020-02-01 |
| 0.15.x | 2017-09-15 | 2019-08-01 |
| 0.14.x | 2017-03-08 | 2019-02-01 |
| 0.13.x | 2016-08-23 | 2018-08-01 |
| 0.12.x | 2016-02-23 | 2018-02-28 |
| 0.11.x | 2015-07-12 | 2017-08-01 |
| 0.10.x | 2015-02-16 | 2017-02-28 |
| 0.9.x | 2014-03-19 | 2016-02-28 |
| 0.8.x | 2013-02-19 | 2015-12-31 |
2 changes: 1 addition & 1 deletion _posts/en/meetings/2018-05-17-meeting.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ getting quite long.
## 0.16.1

**Background:** Bitcoin Core developers have begun preparing a new
0.16.1 [maintenance release](/en/lifecycle/#maintenance-releases) with
0.16.1 [maintenance release](/en/lifecycle/#versioning) with
bugfixes and backports of important features.

**Discussion
Expand Down
2 changes: 1 addition & 1 deletion _posts/en/meetings/2018-05-24-meeting.md
Original file line number Diff line number Diff line change
Expand Up @@ -237,7 +237,7 @@ sentences. If you believe any quote was taken out of context, please
and we will correct the mistake.

[current high-priority PRs]: https://github.com/bitcoin/bitcoin/projects/8
[maintenance release]: /en/lifecycle/#maintenance-releases
[maintenance release]: /en/lifecycle/#versioning
[key-value database]: https://en.wikipedia.org/wiki/Key-value_database
[UHF model]: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-May/015967.html

Expand Down
2 changes: 1 addition & 1 deletion _posts/en/meetings/2018-07-12-meeting.md
Original file line number Diff line number Diff line change
Expand Up @@ -216,7 +216,7 @@ and we will correct the mistake.
[log coin selection]: {{log}}#l-194

[last meeting]: /en/meetings/2018/07/05/
[maintenance releases]: /en/lifecycle/#maintenance-releases
[maintenance releases]: /en/lifecycle/#versioning
[backport]: https://en.wikipedia.org/wiki/Backporting
[docs repo]: https://github.com/bitcoin-core/docs
[srd]: /en/meetings/2018/06/21/#coin-selection
Expand Down
2 changes: 1 addition & 1 deletion _posts/en/meetings/2018-07-26-meeting.md
Original file line number Diff line number Diff line change
Expand Up @@ -176,7 +176,7 @@ and we will correct the mistake.
[bcco #581]: https://github.com/bitcoin-core/bitcoincore.org/issues/581
[alt meet time]: /en/meetings/2018/07/05/#alternating-meeting-time
[time poll results]: https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_a80f9a69d20aab2a
[maintenance release]: /en/lifecycle/#maintenance-releases
[maintenance release]: /en/lifecycle/#versioning
[tag 0.17]: https://github.com/bitcoin/bitcoin/milestone/33

{% include link-to-issues.md issues="13426" %}
38 changes: 14 additions & 24 deletions _posts/en/pages/2016-01-15-lifecycle.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,44 +16,33 @@ This document describes the life-cycle of the Bitcoin Core software package rele

Bitcoin Core releases are versioned as follows: MAJOR.MINOR, and release candidates are suffixed with rc1, rc2 etc.

## Major releases
We aim to make a major release every 6 months. These will be numbered 29.0, 30.0 etc.

We aim to make a major release every 6-7 months.

These will be numbered 22.0, 23.0 etc.

## Maintenance releases

We will provide maintenance "minor releases" that fix bugs within the major releases. As a general rule we do not introduce major new features in a maintenance release (except for consensus rules). However, we may add minor features where necessary, and we will back-port consensus rule changes such as soft forks.

Minor releases will be numbered 22.1, 22.2, 23.1, 23.2 etc.
We will provide minor ("maintenance") releases that fix bugs (security and otherwise) for each major release. These
will be numbered 29.3, 30.1, etc. We will not introduce major new features in maintenance releases (besides consensus
rules change, see below).

## Consensus rules

Proposals to change consensus rules are always shipped first in maintenance versions such as 22.2, 23.1 etc. This makes it easier for enterprise users to assess and test the proposal because of its smaller changeset compared to a major release. It also allows users who follow a more conservative upgrade path to adopt consensus rule changes in a more timely manner.

## Maintenance period

We maintain the major versions until their "Maintenance End". We generally maintain the current and previous major release.
For example, if the current release is 23.0, then 22.0 is also considered maintained.
Once 24.0 is released, then 22.0 would be considered at its "Maintenance End".
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.
Once software has reached the "Maintenance End" period, it will only receive critical security fixes until the End-of-Life (EOL) date.
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.
Generally, it is recommended to run the latest maintenance release (point release) of the current or previous major version.

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.
We always maintain the latest three major versions. When a new major version is released, the oldest one falls out of
the maintenance window and becomes "End of Life". For example, if the last major release is 30.0, then 29.x and 28.x are
also considered maintained. Once 31.0 is released, 28.x becomes "End of Life". The threshold for backporting a change
to an older major version increases as it ages.

For example, major version 22.0 was released on 2021-09-13 and we provided maintenance fixes (point releases) until 2022-12-14.
Critical security issues would still be continued to be fixed until the EOL date of 2023-04-01.
However, to take advantage of bug fixes, you would have to upgrade to a later major version.
Major versions that are "End of Life" do not generally receive security fixes. For more about our policy on security
fixes, see our [security advisories][] page. We recommend running the latest maintenance release of the most recent
major version you are able to upgrade to.

## Schedule

Once EOL is reached, you will need to upgrade to a newer version.

| Version | Release Date | Maintenance End | End of Life |
|---------|--------------|-----------------|-------------|
| Version | Release Date | End of Life |
|---------|--------------|-------------|
{% include posts/maintenance-table.md %}

\* _We aim to make a major release every 6-7 months_
Expand Down Expand Up @@ -82,3 +71,4 @@ For this reason, Bitcoin Core deviates from SemVer for changes to consensus rule

[SemVer]: https://semver.org/
[bitcoin-transifex-link]: https://explore.transifex.com/bitcoin/bitcoin/
[security advisories]: /en/security-advisories
2 changes: 1 addition & 1 deletion _posts/en/posts/2018-06-15-release-0.16.1.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,4 +45,4 @@ our best to help you.
[release notes]: /en/releases/0.16.1/
[IRC]: https://en.bitcoin.it/wiki/IRC_channels
[download page]: /en/download
[maintenance release]: /en/lifecycle/#maintenance-releases
[maintenance release]: /en/lifecycle/#versioning
2 changes: 1 addition & 1 deletion _posts/en/posts/2018-07-29-release-0.16.2.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ our best to help you.
[release notes]: /en/releases/0.16.2/
[IRC]: https://en.bitcoin.it/wiki/IRC_channels
[download page]: /en/download
[maintenance release]: /en/lifecycle/#maintenance-releases
[maintenance release]: /en/lifecycle/#versioning
[tx-as-internal-node]: https://bitslog.wordpress.com/2018/06/09/leaf-node-weakness-in-bitcoin-merkle-tree-design/

{% include references.md %}
2 changes: 1 addition & 1 deletion _posts/ja/pages/2016-01-15-lifecycle.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ Bitcoin CoreはMAJOR.MINORという形式でバージョン管理され、その

メジャーリリースには、22.0、23.0といった番号が付けられます。

## メンテナンスリリース {#maintenance-releases}
## メンテナンスリリース {#versioning}

メジャーリリースのバグを修正するメンテンナンスの「マイナーリリース」を提供します。一般的なルールとして、メンテナンスリリースでは(コンセンサスルールを除いて)重要な新しい機能を導入していません。ただし、必要に応じてマイナーな機能を追加したり、ソフトフォークなどによるコンセンサスルールの変更をバックポートすることがあります。

Expand Down
2 changes: 1 addition & 1 deletion _posts/ja/posts/2018-06-15-release-0.16.1.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,4 +33,4 @@ opcodeが使われている場合、そのトランザクションのリレー
[リリースノート]: /ja/releases/0.16.1/
[IRC]: https://en.bitcoin.it/wiki/IRC_channels
[ダウンロードページ]: /ja/download
[メンテナンスリリース]: /en/lifecycle/#maintenance-releases
[メンテナンスリリース]: /en/lifecycle/#versioning
2 changes: 1 addition & 1 deletion _posts/ja/posts/2018-07-29-release-0.16.2.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ Bitcoin Coreバージョン0.16.2が[ダウンロード][ダウンロードペ
[リリースノート]: /ja/releases/0.16.2/
[IRC]: https://en.bitcoin.it/wiki/IRC_channels
[ダウンロードページ]: /ja/download
[メンテナンスリリース]: /en/lifecycle/#maintenance-releases
[メンテナンスリリース]: /en/lifecycle/#versioning
[tx-as-internal-node]: https://bitslog.wordpress.com/2018/06/09/leaf-node-weakness-in-bitcoin-merkle-tree-design/

{% include references.md %}