Mirrors/monero
1
0
Fork 0
mirror of https://github.com/monero-project/monero.git synced 2025-12-10 09:01:28 +09:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #9737

Browse Source 
70d3907 docs: remove 'creating stable releases' section (tobtoht)
This commit is contained in:
luigi1111 2025-10-07 15:40:24 -04:00
commit 46d794f98e
No known key found for this signature in database
GPG Key ID: F4ACA0183641E010
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

@ -147,14 +147,6 @@ C4 is meant to provide a reusable optimal collaboration model for open source so
- Maintainers SHOULD ask for improvements to incorrect patches and SHOULD reject incorrect patches if the Contributor does not respond constructively. - Maintainers SHOULD ask for improvements to incorrect patches and SHOULD reject incorrect patches if the Contributor does not respond constructively.
- 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.
### 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.