Skip to content

Commit ff56e88

Browse files
committed
Note on developing
1 parent 06d42e7 commit ff56e88

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

DEVELOPING.md

+7-4
Original file line numberDiff line numberDiff line change
@@ -7,12 +7,15 @@ Create a [fork](https://docs.github.com/en/github/getting-started-with-github/fo
77

88
### Branch to work against
99

10-
sbt uses two branches for development:
10+
sbt uses **two or three** branches for development:
11+
Generally the default branch set on Github is what we recommend as the base line for PRs.
1112

12-
- Development branch: `develop` (this is also called "master")
13-
- Stable branch: `1.$MINOR.x`, where `$MINOR` is current minor version (e.g. `1.1.x` during 1.1.x series)
13+
- Next minor branch: `1.$MINOR.x`, where `$MINOR` is next minor version (e.g. `1.9.x` during 1.8.x series)
14+
- Development branch: `develop`
15+
- Stable branch: `1.$MINOR.x`, where `$MINOR` is current minor version (e.g. `1.8.x` during 1.8.x series)
1416

15-
The `develop` branch represents the next major version of sbt. Only new features are pushed to the `develop` branch. This is the branch that you will branch off of to make your changes.
17+
Currently `develop` branch represents the next major version of sbt, i.e. sbt 2.
18+
Next minor branch is where new features can be added as long as it is binary compatible with sbt 1.0.
1619
The `stable` branch represents the current stable sbt release. Only bug fixes are back-ported to the stable branch.
1720

1821
### Instruction to build just sbt

0 commit comments

Comments
 (0)