4rkal/monero
1
0
Fork 0
mirror of https://github.com/monero-project/monero.git synced 2025-02-23 10:11:19 +02:00
Code Issues Actions Packages Projects Releases Wiki Activity

docs: remove 'creating stable releases' section

Browse Source
This commit is contained in:
tobtoht 2025-01-27 02:13:58 +01:00
parent 90359e31fd
commit 70d39076e0
No known key found for this signature in database
GPG Key ID: E45B10DD027D2472
1 changed files with 0 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/CONTRIBUTING.md
View File

@ -153,14 +153,6 @@ C4 is meant to provide a reusable optimal collaboration model for open source so
- Any Contributor who has value judgments on a correct patch SHOULD express these via their own patches. - Any Contributor who has value judgments on a correct patch SHOULD express these via their own patches.
- Maintainers MAY commit changes to non-source documentation directly to the project. - Maintainers MAY commit changes to non-source documentation directly to the project.
### Creating stable releases
- The project MUST have one branch ("master") that always holds the latest in-progress version and SHOULD always build.
- The project MUST NOT use topic branches for any reason. Personal forks MAY use topic branches.
- To make a stable release someone MUST fork the repository by copying it and thus become maintainer of this repository.
- Forking a project for stabilization MAY be done unilaterally and without agreement of project maintainers.
- A patch to a stabilization project declared "stable" MUST be accompanied by a reproducible test case.
### Evolution of public contracts ### Evolution of public contracts
- All Public Contracts (APIs or protocols) MUST be documented. - All Public Contracts (APIs or protocols) MUST be documented.