Congegni
/
libretime
mirror of https://github.com/libretime/libretime.git
7
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

chore: adapt c4 to match our branches and releases requirements

This commit is contained in:
jo 2023-03-15 18:34:46 +01:00 committed by Kyle Robbertze
parent 1d48e47721
commit 22b2d33c4d
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/contribute.md
View File

@ -12,6 +12,9 @@ LibreTime development workflows follow the standardized [C4 development process]
- `7.` A patch commit message MUST follow the [conventional commits specification](https://www.conventionalcommits.org/en/v1.0.0/). - `7.` A patch commit message MUST follow the [conventional commits specification](https://www.conventionalcommits.org/en/v1.0.0/).
- [2.4. Development Process](https://rfc.zeromq.org/spec/42/#24-development-process) - [2.4. Development Process](https://rfc.zeromq.org/spec/42/#24-development-process)
- `16.` Maintainers MAY NOT merge incorrect patches. - `16.` Maintainers MAY NOT merge incorrect patches.
- [2.5. Branches and Releases](https://rfc.zeromq.org/spec/42/#25-branches-and-releases)
- `1.` The project SHALL have a development branch (`main`) that always holds the latest in-progress version and SHOULD always build. The project MAY have a bug fixes only branch (`stable`) that always holds the current stable version and SHOULD always build.
- `3.` To make a stable release a Maintainer shall tag the repository. Stable releases SHALL always be released from the repository `main` or `stable` branches.
## Contribute financially ## Contribute financially