REL: preparing release

CHANGELOG.md

@@ -9,6 +9,20 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Added ###
 
+### Changed ###
+
+### Deprecated ###
+
+### Removed ###
+
+### Fixed ###
+
+### Security ###
+
+## [0.4.1] 2021-02-10 ##
+
+### Added ###
+
 * Versioning support (experimental). The version db.Version class can
   represents particular entity versions and also the complete history of an
   entity.

DEPENDENCIES.md

+Python 3.5 or later
+pip 20.0.2 or later
+
+Any other dependencies are being installed via pip

RELEASE_GUIDELINES.md

@@ -16,21 +16,27 @@ guidelines of the CaosDB Project
 1. Create a release branch from the dev branch. This prevents further changes
    to the code base and a never ending release process. Naming: `release-<VERSION>`
 
-2. Check all general prerequisites.
+2. Update CHANGELOG.md
 
-3. Prepare [setup.py](./setup.py): Update the `MAJOR`, `MINOR`, `MICRO`, `PRE`
+3. Check all general prerequisites.
+
+4. Prepare [setup.py](./setup.py): Check the `MAJOR`, `MINOR`, `MICRO`, `PRE`
    variables and set `ISRELEASED` to `True`. Use the possibility to issue
    pre-release versions for testing.
 
-4. Merge the release branch into the master branch.
+5. Merge the release branch into the master branch.
 
-5. Tag the latest commit of the master branch with `v<VERSION>`.
+6. Tag the latest commit of the master branch with `v<VERSION>`.
 
-6. Delete the release branch.
+7. Delete the release branch.
 
-7. Remove possibly existing `./dist` directory with old release.
+8. Remove possibly existing `./dist` directory with old release.
 
-8. Publish the release by executing `./release.sh` with uploads the caosdb
+9. Publish the release by executing `./release.sh` with uploads the caosdb
    module to the Python Package Index [pypi.org](https://pypi.org).
 
-9. Merge the master branch back into the dev branch.
+10. Merge the master branch back into the dev branch.
+
+11. After the merge of master to dev, start a new development version by
+    setting `ISRELEASED` to `False` and by increasing at least the `MIRCO`
+    version in [setup.py](./setup.py)

setup.py

@@ -49,7 +49,7 @@ MAJOR = 0
 MINOR = 4
 MICRO = 1
 PRE = ""  # e.g. rc0, alpha.1, 0.beta-23
-ISRELEASED = False
+ISRELEASED = True
 
 if PRE:
     VERSION = "{}.{}.{}-{}".format(MAJOR, MINOR, MICRO, PRE)