~jan0sch/smederee

Showing details for patch 23fe340430400907eb22a68178640afe7c7ee928.
2024-06-29 (Sat), 9:01 PM - Jens Grassel - 23fe340430400907eb22a68178640afe7c7ee928

CONTRIBUTING: Remove TODO and rephrase minimal about forks and branches.

Summary of changes
1 files modified with 1 lines added and 3 lines removed
  • CONTRIBUTING.md with 1 added and 3 removed lines
diff -rN -u old-smederee/CONTRIBUTING.md new-smederee/CONTRIBUTING.md
--- old-smederee/CONTRIBUTING.md	2025-01-11 11:48:59.542732054 +0000
+++ new-smederee/CONTRIBUTING.md	2025-01-11 11:48:59.542732054 +0000
@@ -78,13 +78,11 @@
 
 ### 3.5 Branches and Releases
 
-In darcs, each repository is a branch. Therefore what you would consider a fork in other systems like git, is considered a branch in darcs.
+In darcs, each repository is a branch. Therefore what you would consider a *fork* in other systems (e.g. git), is considered a *branch* in darcs.
 
 1. The project SHALL have one main branch that always holds the latest in-progress version and SHOULD always build.
 2. To make a stable release a Maintainer SHALL prepare the CHANGELOG file and tag the repository. Stable releases SHALL always be released from the main branch.
 
-TODO: Adjust releases and tagging to having multiple modules inside the mono repository.
-
 #### 3.5.1 Release guide
 
 The release `NAME` SHALL follow the specification described in the CHANGELOG file e.g. `major`.`minor`.`patchlevel` prefixed with a lower case `v`, for example: `v1.0.3`.