~jan0sch/smederee

Showing details for patch fecc79c1daa62b51d9038c4cfcfbeac81c9972ad.
2024-02-01 (Thu), 6:04 PM - Jens Grassel - fecc79c1daa62b51d9038c4cfcfbeac81c9972ad

Contributing: Simplify release guide for updating changelog.

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-13 05:57:51.948470029 +0000
+++ new-smederee/CONTRIBUTING.md	2025-01-13 05:57:51.948470029 +0000
@@ -87,11 +87,9 @@
 
 #### 3.5.1 Release guide
 
-Before releasing a new version a Maintainer SHALL update the [CHANGELOG](CHANGELOG.md) file and add the changes which are subject to the release. The changes SHOULD be written into the `Unreleased` section of the file and the commit message SHALL be titled "CHANGELOG: Update with changes since the last release."
-
 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`.
 
-IMMEDIATELY BEFORE the release, the changes in the section `Unreleased` in the [CHANGELOG](CHANGELOG.md) file MUST be moved to a section named after the release and a new empty `Unreleased` section MUST be created. The commit message for these changes MUST be titled "Prepare RELEASE NAME" e.g. "Prepare RELEASE v1.2.3"
+Before releasing a new version a Maintainer SHALL update the [CHANGELOG](CHANGELOG.md) file and add the changes which are subject to the release under a section named after the release. The commit message for these changes MUST be titled "Prepare RELEASE NAME" e.g. "Prepare RELEASE v1.2.3"
 
 A release SHALL be accompanied by an annotated tag (`darcs tag --edit-long-comment NAME`) that holds a description of the changes that are included in the release. This description SHOULD be same as in the CHANGELOG.