mirror/pretalx
1
0
Fork 0
mirror of https://github.com/MatomoCamp/pretalx.git synced 2024-09-09 05:13:44 +02:00
Code Releases Activity

Clarify support

Browse source
This commit is contained in:
Tobias Kunze 2021-12-26 00:59:17 +01:00
parent 6be7167db9
commit b31665fa16
2 changed files with 19 additions and 23 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
SECURITY.md
View file

@ -2,12 +2,9 @@
## Supported Versions
We can currently only support the current version. At least our support matrix is simple!
| Version | Supported |
| ------- | --------- |
| ≥ 2.3.0 | ✅ |
| < 2.3.0 | ❌ |
Due to limited development bandwidth, only the [most recent release](https://pypi.org/project/pretalx/#history) is
currently supported. If you need support for previous releases, please contact
[support@pretalx.com](mailto:support@pretalx.com).
## Reporting a Vulnerability

33
doc/maintainer/release.rst
View file

@ -31,20 +31,19 @@ Take-off and landing
--------------------
1. Bump version in ``src/pretalx/__init__.py``.
2. Update the supported version in ``SECURITY.md`` if the release is not just a patch release.
3. Update the translation percentages from `here <https://translate.pretalx.com/projects/pretalx/pretalx/#translations>`_.
4. Add the release to the :ref:`changelog`.
5. Make a commit with the message ``Release vx.y.z``
6. Tag the commit: ``git tag -u F0DAD3990F9C816CFD30F8F329C085265D94C052 vx.y.z -m 'Release vx.y.z'``
7. Remove old build artefacts: ``rm -rf dist/ build/ pretalx.egg-info``
8. Build a new release: ``python -m build``
9. Sign the release: ``gpg --default-key F0DAD3990F9C816CFD30F8F329C085265D94C052 --detach-sign -a dist/pretalx-x.y.z.tar.gz``
10. Upload the release: ``twine upload dist/pretalx-x.y.z.tar.gz dist/pretalx-x.y.z.tar.gz.asc``
11. Push the release: ``git push && git push --tags``
12. Install/update the package somewhere.
13. Add the release on `GitHub <https://github.com/pretalx/pretalx/releases>`_ (upload the archive you uploaded to PyPI, and add a link to the correct section of the :ref:`changelog`)
14. Push the blog post.
15. Upgrade `the docker repository <https://github.com/pretalx/pretalx-docker>`_ to the current commit **and tag the commit as vx.y.z**.
16. Switch to ``main`` branch
17. Copy release note to changelog and increment version number.
18. Update version numbers in update checker and deploy.
2. Update the translation percentages from `here <https://translate.pretalx.com/projects/pretalx/pretalx/#translations>`_.
3. Add the release to the :ref:`changelog`.
4. Make a commit with the message ``Release vx.y.z``
5. Tag the commit: ``git tag -u F0DAD3990F9C816CFD30F8F329C085265D94C052 vx.y.z -m 'Release vx.y.z'``
6. Remove old build artefacts: ``rm -rf dist/ build/ pretalx.egg-info``
7. Build a new release: ``python -m build``
8. Sign the release: ``gpg --default-key F0DAD3990F9C816CFD30F8F329C085265D94C052 --detach-sign -a dist/pretalx-x.y.z.tar.gz``
9. Upload the release: ``twine upload dist/pretalx-x.y.z.tar.gz dist/pretalx-x.y.z.tar.gz.asc``
10. Push the release: ``git push && git push --tags``
11. Install/update the package somewhere.
12. Add the release on `GitHub <https://github.com/pretalx/pretalx/releases>`_ (upload the archive you uploaded to PyPI, and add a link to the correct section of the :ref:`changelog`)
13. Push the blog post.
14. Upgrade `the docker repository <https://github.com/pretalx/pretalx-docker>`_ to the current commit **and tag the commit as vx.y.z**.
15. Switch to ``main`` branch
16. Copy release note to changelog and increment version number.
17. Update version numbers in update checker and deploy.