From 70d39076e01ae895a08aadfb23ebc7802cb4fd2a Mon Sep 17 00:00:00 2001 From: tobtoht Date: Mon, 27 Jan 2025 02:13:58 +0100 Subject: [PATCH] docs: remove 'creating stable releases' section --- docs/CONTRIBUTING.md | 8 -------- 1 file changed, 8 deletions(-) diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md index 606c28fe4..536cdbe45 100644 --- a/docs/CONTRIBUTING.md +++ b/docs/CONTRIBUTING.md @@ -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. - 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 - All Public Contracts (APIs or protocols) MUST be documented.