diff options
| author | Colin Okay <okay@toyful.space> | 2022-03-05 18:10:56 -0600 |
|---|---|---|
| committer | Colin Okay <okay@toyful.space> | 2022-03-05 18:10:56 -0600 |
| commit | 72978b2739038bf3525c08abe92d55e61aba719e (patch) | |
| tree | 3d25dd230c6993986d2c42380a287ed97057bc24 | |
| parent | 704e1a8e3d492406ec3f29706bf185abda4683d0 (diff) | |
Updated CONTRIBUTING.org
| -rw-r--r-- | CONTRIBUTING.org | 9 |
1 files changed, 2 insertions, 7 deletions
diff --git a/CONTRIBUTING.org b/CONTRIBUTING.org index c242b1d..9d896ee 100644 --- a/CONTRIBUTING.org +++ b/CONTRIBUTING.org @@ -9,13 +9,8 @@ After 1.0.0, a new release schedule will be decided upon. Each release is developed in a branch called rc-<major>.<minor>, referring to the major and minor versions in semver. -These branches are based off of the dev branch, meaning that any one -of them should be able to merge dev at any point - merge conflicts -from dev into an rc branch are not allowed. - When a release candidate is "accepted", it will be merged into main -and the commit will be tagged with the version. At that point dev -should also be updated from main. +and the commit will be tagged with the version. ** Suggesting Features & Reporting Bugs @@ -34,7 +29,7 @@ by starting the subject line with one of the following: ** Branch based collaboration If you want to work on a feature, please make a new branch based on -dev and develop your features there. +the relevant release candidate branch and develop your features there. If the maintainer (me, Colin) has access to your git repo, simply request that your branch be merged into the relevant release candidate |