REL: prepare next release cycle

CHANGELOG.md

@@ -4,6 +4,22 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [Unpublished]
+
+### Added (for new features, dependecies etc.)
+
+### Changed (for changes in existing functionality)
+
+### Deprecated (for soon-to-be removed features)
+
+### Removed (for now removed features)
+
+### Fixed (for any bug fixes)
+
+### Security (in case of vulnerabilities)
+
+### Documentation (for notable additions or changes of the documentation)
+
 ## [0.4.2] - 2021-12-06
 
 ### Added (for new features, dependecies etc.)

RELEASE_GUIDELINES.md

-# Release Guidelines for the CaosDB MySQL Backend
+# Release Guidelines for the CaosDB Web Interface
 
 This document specifies release guidelines in addition to the generel release
 guidelines of the CaosDB Project
@@ -8,7 +8,7 @@ guidelines of the CaosDB Project
 
 * All tests are passing.
 * FEATURES.md is up-to-date and a public API is being declared in that document.
-* CHANGELOG.md is up-to-date.
+* CHANGELOG.md is up-to-date (insert version number and remove unpublished)
 * DEPENDENCIES.md is up-to-date.
 
 ## Steps
@@ -25,3 +25,5 @@ guidelines of the CaosDB Project
 5. Delete the release branch.
 
 6. Merge the main branch back into the dev branch.
+
+7. Prepare CHANGELOG for next release cycle.