Skip to content
Snippets Groups Projects
Commit cd0505c2 authored by Florian Spreckelsen's avatar Florian Spreckelsen
Browse files

REL: Add release documentation files

parent 31d77b93
No related branches found
No related tags found
1 merge request!53Release 0.1
Pipeline #29215 passed with warnings
......@@ -38,9 +38,9 @@ The original authors of this package are:
# License
Copyright (C) 2021 Research Group Biomedical Physics, Max Planck Institute for
Copyright (C) 2021-2022 Research Group Biomedical Physics, Max Planck Institute for
Dynamics and Self-Organization Göttingen.
Copyright (C) 2021 IndiScale GmbH
Copyright (C) 2021-2022 IndiScale GmbH
All files in this repository are licensed under a [GNU Affero General Public
License](LICENCE) (version 3 or later).
# Release Guidelines for the CaosDB Python Client Library
This document specifies release guidelines in addition to the general release
guidelines of the CaosDB Project
([RELEASE_GUIDELINES.md](https://gitlab.com/caosdb/caosdb/blob/dev/RELEASE_GUIDELINES.md))
## General Prerequisites
* 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.
* dependencies in `setup.cfg` are up-to-date.
## Steps
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. Update CHANGELOG.md
3. Check all general prerequisites.
4. Update the version:
- `version` variables in `src/doc/conf.py`
- Version in [setup.cfg](./setup.cfg): Check the `MAJOR`, `MINOR`, `MICRO`, `PRE` variables and set
`ISRELEASED` to `True`. Use the possibility to issue pre-release versions for testing.
5. Merge the release branch into the main branch.
6. Tag the latest commit of the main branch with `v<VERSION>`.
7. Delete the release branch.
8. Remove possibly existing `./dist` directory with old release.
9. Publish the release by executing `./release.sh` with uploads the caosdb
module to the Python Package Index [pypi.org](https://pypi.org).
10. Merge the main branch back into the dev branch.
11. After the merge of main to dev, start a new development version by
increasing at least the micro version in [setup.cfg](./setup.cfg) and
preparing CHANGELOG.md.
12. Create releases on gitlab.com and gitlab.indiscale.com that contain (at
least) the most recent section of the CHANGELOG as the description and link
to the PyPi package.
#!/bin/bash
rm -rf dist/ build/ .eggs/
python setup.py sdist bdist_wheel
python -m twine upload -s dist/*
[metadata]
name = caoscrawler
version = 0.1
version = 0.1.0
author = Alexander Schlemmer
author_email = alexander.schlemmer@ds.mpg.de
description = A new crawler for caosdb
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment