aboutsummaryrefslogtreecommitdiffstats
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorLibravatar Drew DeVault <sir@cmpwn.com>2016-09-05 12:11:39 -0400
committerLibravatar Drew DeVault <sir@cmpwn.com>2016-09-05 12:11:39 -0400
commita89105e62d95ccb8871ff27ef9661c698257e792 (patch)
tree63c5c7e5afdcec4ed3928c8062b7804e65361a34 /CONTRIBUTING.md
parentDocument release cycle in CONTRIBUTING.md (diff)
downloadsway-a89105e62d95ccb8871ff27ef9661c698257e792.tar.gz
sway-a89105e62d95ccb8871ff27ef9661c698257e792.tar.zst
sway-a89105e62d95ccb8871ff27ef9661c698257e792.zip
Minor cleanup on CONTRIBUTING.md
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md23
1 files changed, 11 insertions, 12 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 1c671126..05b259ad 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -7,24 +7,23 @@ your plans.
7 7
8## Release Cycle 8## Release Cycle
9 9
10There are three stages of a sway release. Say the current stable version is 10The master branch of sway is always working towards becoming the next release.
110.7. The master branch of sway is working towards becoming the 0.8 release. 0.8 11That release will go through each of these three stages:
12will go through each of these three stages:
13 12
14**In development**: during this time 0.8 lives in the master branch and is 13**In development**: during this time the release lives in the master branch and
15considered unstable. All pull requests merged during this time will land in sway 14is considered unstable. All pull requests merged during this time will land in
160.8. 15this version. Only developers are encouraged to run this version.
17 16
18**Release candidate**: at some point (usually when development is fairly quiet), 17**Release candidate**: at some point (usually when development is fairly quiet),
19@SirCmpwn will announce an upcoming release candidate (often 2 weeks in 18SirCmpwn will announce an upcoming release candidate (often 2 weeks in
20advance). When the two weeks are up, a branch is cut (i.e. 0.8-rc1) and from 19advance). When the two weeks are up, a branch is cut (i.e. 0.8-rc1) and from
21that point only bugfix pull requests land in this branch. Each morning, if 20that point only bugfix pull requests land in this branch. Each morning, if
22bugfixes landed in 0.8 during the previous day, a new RC is cut. During the RC 21bugfixes landed during the previous day, a new RC is cut. During the RC phase,
23phase, more adventurous users are encouraged to upgrade and start looking for 22more adventurous users are encouraged to upgrade and start looking for and
24and reporting bugs (especially in new features). 23reporting bugs (especially in new features).
25 24
26**Stable release**: when no substantial changes are merged into an RC for 1 25**Stable release**: when no substantial changes are merged into an RC for one
27week, it's released as a new stable version of Sway. At this point, all users 26week, it's released as a new stable version of sway. At this point, all users
28are encouraged to upgrade. 27are encouraged to upgrade.
29 28
30## Pull Requests 29## Pull Requests