You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+29-5Lines changed: 29 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,12 @@ and this project adheres to the versioning scheme outlined in the [README.md](RE
7
7
8
8
## [Unreleased]
9
9
10
-
- Added support for Clarity 3
10
+
## [3.0.0.0.0]
11
+
12
+
### Added
13
+
14
+
-**Nakamoto consensus rules, activating in epoch 3.0 at block 867,867** (see [SIP-021](https://github.com/stacksgov/sips/blob/main/sips/sip-021/sip-021-nakamoto.md) for details)
15
+
- Clarity 3, activating with epoch 3.0
11
16
- Keywords / variable
12
17
-`tenure-height` added
13
18
-`stacks-block-height` added
@@ -16,10 +21,29 @@ and this project adheres to the versioning scheme outlined in the [README.md](RE
Copy file name to clipboardExpand all lines: SECURITY.md
+14-53Lines changed: 14 additions & 53 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
4
4
## Supported Versions
5
-
Please see [Releases](https://github.com/stacks-network/stacks-blockchain/releases). It is recommended to use the [most recently released version](https://github.com/stacks-network/stacks-blockchain/releases/latest).
5
+
Please see [Releases](https://github.com/stacks-network/stacks-core/releases). It is recommended to use the [most recently released version](https://github.com/stacks-network/stacks-core/releases/latest).
6
6
7
7
8
8
## Reporting a vulnerability
@@ -21,61 +21,22 @@ You may also contact us with any questions or to report a vulnerabilty using the
Copy file name to clipboardExpand all lines: docs/SIPS.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,4 +4,4 @@ Stacks improvement proposals (SIPs) are aimed at describing the implementation o
4
4
5
5
See [SIP 000](https://github.com/stacksgov/sips/blob/main/sips/sip-000/sip-000-stacks-improvement-proposal-process.md) for more details.
6
6
7
-
The SIPs now located in the [stacksgov/sips](https://github.com/stacksgov/sips) repository as part of the [Stacks Community Governance organization](https://github.com/stacksgov).
7
+
The SIPs are located in the [stacksgov/sips](https://github.com/stacksgov/sips) repository as part of the [Stacks Community Governance organization](https://github.com/stacksgov).
The following is a slightly modified version of the gitflow branching strategy described in <https://nvie.com/posts/a-successful-git-branching-model/>
4
+
5
+
## Main Branches
6
+
7
+
-**master** - `master` is the main branch where the source code of HEAD always reflects a production-ready state.
8
+
-**develop** - `develop` is the branch where the source code of HEAD always reflects a state with the latest delivered development changes for the next release.
9
+
-**next** - `next` may contain consensus-breaking changes for a future release.
10
+
-**release/X.Y.Z.A.n** is the release branch.
11
+
12
+
When the source code in the develop branch reaches a stable point and is ready to be released, a release branch is created as `release/X.Y.Z.A.n` (see [release-process.md](./release-process.md)).
13
+
After release, the following will happen:
14
+
15
+
-`release/X.Y.Z.A.n` branch is merged back to `master`.
16
+
-`master` is then merged into `develop`, and development continues in the `develop` branch.
17
+
-`develop` is then merged into `next`.
18
+
19
+
## Supporting Branches
20
+
21
+
Branch names should use a prefix that conveys the overall goal of the branch.
22
+
All branches should be based off of `develop`, with the exception being a hotfix branch which may be based off of `master`.
23
+
24
+
-`feat/some-fancy-new-thing`: For new features.
25
+
-`fix/some-broken-thing`: For hot fixes and bug fixes.
26
+
-`chore/some-update`: Any non code related change (ex: updating CHANGELOG.md, adding comments to code).
27
+
-`docs/something-needs-a-comment`: For documentation.
28
+
-`ci/build-changes`: For continuous-integration changes.
29
+
-`test/more-coverage`: For branches that only add more tests.
30
+
-`refactor/formatting-fix`: For refactors of the codebase.
31
+
32
+
The full branch name **must**:
33
+
34
+
- Have a maximum of 128 characters.
35
+
- Only includes ASCII lowercase and uppercase letters, digits, underscores, periods and dashes.
0 commit comments