Skip to content

Commit 828defb

Browse files
committed
uncomited changes
1 parent bbc490f commit 828defb

16 files changed

+993
-0
lines changed
Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
---
2+
title: Sobre
3+
name: about
4+
permalink: /pt_br/about/
5+
type: pages
6+
layout: page
7+
lang: pt_br
8+
version: 3
9+
10+
---
11+
12+
## Sobre nós
13+
14+
Bitcoin Core é um projeto de [código aberto](https://opensource.org/) o qual mantém e lança um software cliente Bitcoin chamado de "Bitcoin Core".
15+
16+
É um descendente direto do código cliente Bitcoin lançado por Satoshi Nakamoto após ele ter publicado o famoso whitepaper do Bitcoin
17+
18+
[Bitcoin Core](https://github.com/bitcoin/bitcoin) consiste em ambos "nó-completo" software para validar completamente a cadeia de blocos tanto como uma carteira bitcoin. O projeto também mantém softwares relacionados como a biblioteca de criptografia [libsecp256k1](https://github.com/bitcoin-core/secp256k1) e outros localizados no [GitHub](https://github.com/bitcoin-core).
19+
20+
Qualquer um pode [contribuir com o Bitcoin Core](/pt_BR/contribute/).
21+
22+
## Team
23+
24+
The Bitcoin Core project has a large open source developer community with many casual contributors to the codebase.
25+
There are many more who contribute research, peer review, testing, documentation, and translation.
26+
27+
### Maintainers
28+
29+
Project maintainers have commit access and are responsible for merging patches from contributors. They perform a janitorial role merging patches that the team agrees should be merged. They also act as a final check to ensure that patches are safe and in line with the project goals. The maintainers' role is by agreement of project contributors.
30+
31+
### Contributors
32+
33+
Everyone is free to propose code changes and to test, review and comment on open Pull Requests.
34+
Anyone who contributes code, review, test, translation or documentation to the Bitcoin Core project is considered a contributor.
35+
The release notes for each Bitcoin Core software release contain a credits section to recognize all those who have contributed to the project over the previous release cycle.
36+
A list of code contributors can be found on [Github][github-contributors].
37+
38+
{% include references.md %}

_posts/pt_BR/pages/2016-01-01-blog.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
---
2+
layout: post-index
3+
title: Blog
4+
name: blog
5+
permalink: /en/blog/
6+
type: pages
7+
lang: en
8+
version: 1
9+
---
10+
11+
Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
---
2+
title: How Can I Contribute?
3+
name: contribute
4+
id: en-contribute
5+
permalink: /en/contribute/
6+
type: pages
7+
layout: page
8+
lang: en
9+
version: 5
10+
redirect_from:
11+
- /zh_TW/contribute/
12+
---
13+
14+
You are welcome to contribute to the project!
15+
Our main source code repository is [hosted on GitHub](https://github.com/bitcoin/bitcoin/) and there are several aspects you can help on:
16+
17+
- Improving our documentation (see [README.md][README.md] and [doc folder][doc])
18+
- [Translations][translation_process.md]
19+
- Testing code, testing releases
20+
- Participate on the mailing lists
21+
- Improving our UIs
22+
- Coding (fix open issues or implement new features)
23+
24+
Feel free to report [issues][issues] and open [pull requests][pulls], but please check the [contribution guidelines](/en/faq/contributing-code) to understand our workflow.
25+
26+
**Discussion**
27+
28+
Most Bitcoin Core related discussion happens in the following IRC channels on irc.libera.chat:
29+
30+
- [#bitcoin-core-dev] - Main discussion
31+
- [#bitcoin-core-builds] - Build system and release discussion
32+
- [#bitcoin-core-gui] - Graphical User Interface discussion
33+
34+
There is also a mailing list for Bitcoin protocol discussion [bitcoin-dev][].
35+
36+
**Contribute to this website**
37+
38+
You can also translate or contribute to this [website][website-contrib].
39+
40+
[README.md]: https://github.com/bitcoin/bitcoin/blob/master/README.md
41+
[doc]: https://github.com/bitcoin/bitcoin/tree/master/doc
42+
[translation_process.md]: https://github.com/bitcoin/bitcoin/blob/master/doc/translation_process.md
43+
[website-contrib]: https://github.com/bitcoin-core/bitcoincore.org/blob/master/CONTRIBUTING.md
44+
45+
{% include references.md %}
Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
layout: home
3+
type: pages
4+
lang: en
5+
title: Bitcoin
6+
name: index
7+
permalink: /
8+
version: 2
9+
tags: [bitcoin, bitcoin core]
10+
translated: false
11+
---
12+
13+
Bitcoin
Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
---
2+
type: pages
3+
layout: page
4+
lang: en
5+
title: IRC Meetings
6+
name: meetings
7+
permalink: /en/meetings/
8+
version: 4
9+
---
10+
The project holds several recurring meetings in the `#bitcoin-core-dev` IRC
11+
channel on Libera Chat ([webchat][bitcoin-core-dev-IRC-webchat]). Everyone is welcome to attend. Logs and
12+
automatically-generated meeting minutes may be found [here][erisian] and [here][schnelli].
13+
14+
Current meeting schedules are available on the developer wiki:
15+
16+
- General developer meeting: https://github.com/bitcoin-core/bitcoin-devwiki/wiki/General-IRC-meeting
17+
- Wallet developer meeting: https://github.com/bitcoin-core/bitcoin-devwiki/wiki/Wallet-Current-Priorities-and-IRC-meetings
18+
19+
Meeting times are also listed on [this Google calendar][meeting
20+
calendar].
21+
22+
[Here as ical format][meeting calendar ical] to subscribe via a calendar app.
23+
24+
If you have any questions about the date or time of an upcoming meeting,
25+
please ask in the IRC channel.
26+
27+
Anyone interested in contributing to Bitcoin Core is also
28+
encouraged to attend the weekly Bitcoin Core PR Review Club meetings,
29+
which are held in a different chatroom. See [the review club
30+
website][review club] for details.
31+
32+
Summaries of old meetings from 2015 to 2018 are now [listed on a
33+
separate page][summaries].
34+
35+
[bitcoin-core-dev-IRC-webchat]: https://web.libera.chat/#bitcoin-core-dev
36+
[erisian]: https://www.erisian.com.au/bitcoin-core-dev/
37+
[schnelli]: https://bitcoin.jonasschnelli.ch/ircmeetings/logs/bitcoin-core-dev/
38+
[meeting calendar]: https://calendar.google.com/calendar?cid=MTFwcXZkZ3BkOTlubGliZjliYTg2MXZ1OHNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ
39+
[meeting calendar ical]: https://calendar.google.com/calendar/ical/11pqvdgpd99nlibf9ba861vu8s%40group.calendar.google.com/public/basic.ics
40+
[review club]: https://bitcoincore.reviews/
41+
[summaries]: /en/meeting-summaries/
Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
type: pages
3+
layout: page
4+
lang: en
5+
title: Releases
6+
name: releases
7+
permalink: /en/releases/
8+
version: 1
9+
---
10+
{% include releases.html %}
Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
title: Bitcoin Core Supported BIPs
3+
name: supported-bips
4+
type: pages
5+
layout: page
6+
lang: en
7+
permalink: /en/bips/
8+
version: 2
9+
redirect_from:
10+
- /zh_TW/bips/
11+
---
12+
Bitcoin Core supports the following [BIPs][BitcoinCoreDocBips].
13+
14+
{% include references.md %}
Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,84 @@
1+
---
2+
title: Software Life Cycle
3+
name: software-life-cycle
4+
id: en-software-life-cycle
5+
permalink: /en/lifecycle/
6+
layout: page
7+
type: pages
8+
lang: en
9+
version: 2
10+
---
11+
{% include toc.html %}
12+
13+
This document describes the life-cycle of the Bitcoin Core software package released by the Bitcoin Core project. It is in line with standard maintenance policy across commercial software.
14+
15+
## Versioning
16+
17+
Bitcoin Core releases are versioned as follows: MAJOR.MINOR, and release candidates are suffixed with rc1, rc2 etc.
18+
19+
## Major releases
20+
21+
We aim to make a major release every 6-7 months.
22+
23+
These will be numbered 22.0, 23.0 etc.
24+
25+
## Maintenance releases
26+
27+
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.
28+
29+
Minor releases will be numbered 22.1, 22.2, 23.1, 23.2 etc.
30+
31+
## Consensus rules
32+
33+
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.
34+
35+
## Maintenance period
36+
37+
We maintain the major versions until their "Maintenance End". We generally maintain the current and previous major release.
38+
For example, if the current release is 23.0, then 22.0 is also considered maintained.
39+
Once 24.0 is released, then 22.0 would be considered at its "Maintenance End".
40+
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.
42+
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.
43+
Generally, it is recommended to run the latest maintenance release (point release) of the current or previous major version.
44+
45+
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.
46+
47+
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.
49+
However, to take advantage of bug fixes, you would have to upgrade to a later major version.
50+
51+
## Schedule
52+
53+
Once EOL is reached, you will need to upgrade to a newer version.
54+
55+
| Version | Release Date | Maintenance End | End of Life |
56+
|---------|--------------|-----------------|-------------|
57+
{% include posts/maintenance-table.md %}
58+
59+
\* _We aim to make a major release every 6-7 months_
60+
61+
_TBA: to be announced_
62+
63+
## Protocol versioning
64+
65+
The description above only describes Bitcoin Core software releases. Many other parts of the Bitcoin system contain their own versions. A few examples:
66+
67+
- Every **transaction** contains a version number.
68+
- The **P2P network protocol** uses version numbers to allow nodes to announce what features they support.
69+
- Bitcoin Core's **built-in wallet** has its own internal version number.
70+
71+
These version numbers are deliberately decoupled from Bitcoin Core's version number as the Bitcoin Core project either has no direct control over them (as is the case with blocks and transactions), or tries to maintain compatibility with other projects (as is the case with the network protocol), or allows for the possibility that no major changes will be made in some releases (as is sometimes the case with the built-in wallet).
72+
73+
The consensus protocol itself doesn't have a version number.
74+
75+
## Relationship to SemVer
76+
77+
Bitcoin Core software versioning does not follow the [SemVer][] optional versioning standard, but its release versioning is superficially similar. SemVer was designed for use in normal software libraries where individuals can choose to upgrade the library at their own pace, or even stay behind on an older release if they don't like the changes.
78+
79+
Parts of Bitcoin, most notably the consensus rules, don't work that way. In order for a new consensus rule to go into effect, it must be enforced by some number of miners, full nodes, or both; and once it has gone into effect, software that doesn't know about the new rule may generate or accept invalid transactions (although upgrades are designed to prevent this from happening when possible).
80+
81+
For this reason, Bitcoin Core deviates from SemVer for changes to consensus rules and other updates where network-wide adoption is necessary or desirable. Bitcoin Core releases these changes as maintenance releases (`x.y`) instead of as major releases (`x.0`); this minimizes the size of the patch in order to make it easy for as many people as possible to inspect it, test it, and deploy it. It also makes it possible to backport the same patch to multiple previous major releases, further increasing the number of users who can easily upgrade, although there are not always enough volunteers to manage this.
82+
83+
[SemVer]: https://semver.org/
84+
[bitcoin-transifex-link]: https://www.transifex.com/bitcoin/bitcoin/

0 commit comments

Comments
 (0)