diff options
| author | Colin Okay <colin@cicadas.surf> | 2022-08-05 13:07:32 -0500 |
|---|---|---|
| committer | Colin Okay <colin@cicadas.surf> | 2022-08-05 13:07:32 -0500 |
| commit | 88fb5d6074ac4f37ff6cdd4b787db75ec8349850 (patch) | |
| tree | c52d6e502375d1d2648004d431f7ea8df4fa12fd /CONTRIBUTING.org | |
| parent | 94f810da3657b2e53423ed98bc59adca4cf5b88a (diff) | |
[removed] uneeded files
Diffstat (limited to 'CONTRIBUTING.org')
| -rw-r--r-- | CONTRIBUTING.org | 46 |
1 files changed, 0 insertions, 46 deletions
diff --git a/CONTRIBUTING.org b/CONTRIBUTING.org deleted file mode 100644 index cfcfe86..0000000 --- a/CONTRIBUTING.org +++ /dev/null @@ -1,46 +0,0 @@ -* Basic Info - -** Release Schedule - -Prior to 1.0.0, there will be a weekly release each Friday. - -After 1.0.0, a new release schedule will be decided upon. - -At any moment, there are three branches: - -| BRANCH | PURPOSE | -|---------+-----------------------------------------------------------------| -| main | Where stable releases reside. Each taggged with a version. | -|---------+-----------------------------------------------------------------| -| rc | The release candidate branch. Courageous may build and test the | -| | this branch prior to its release. Bugfix patches and PRs | -| | are submitted to rc. | -|---------+-----------------------------------------------------------------| -| develop | Where new features are actively developed. | -|---------+-----------------------------------------------------------------| - - -** Suggesting Features & Reporting Bugs - -To bring something up with the developers, send an email to - - ~cbeo/oneliners.wiki@lists.sr.ht - -To keep up with developments and discuss this tool, join the mailing -list by visiting https://lists.sr.ht/~cbeo/oneliners.wiki and hitting -"subscribe". -** Making code contributions - -If you want to work on a feature, please make a new branch based on -the relevant release candidate branch and develop your features there. - -If the maintainer (me, Colin) has access to your git repo, use the -mailing list to request that your branch be merged into the relevant -release candidate branch. - -If requesting a merge is infeasible because your git repository is -private or local to your machine, you may submit a patch against the -relevant release candidate branch via the mailing list. - - ->>>>>>> develop |