You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/changelog.rst
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,8 @@
1
1
.. _changelog:
2
2
3
3
Release Notes
4
-
=============
5
-
6
4
- :feature:`orga:sidebar` Renamed CfP to Call for Speakers for clarity
5
+
- :feature:`lang` pretalx now comes with new translations, in Dutch and Italian!
7
6
- :feature:`orga,820` Restricted tracks now link to the page where you can create access codes for that track.
8
7
- :announcement:`admin,1678` Due to its incomplete and complex nature, the ``import_schedule`` admin command has been removed. If you want to import a schedule, despite all the complexities, please use the pretalx-downstream plugin instead.
9
8
- :feature:`orga,1672` The organiser area now has a search box located in the side bar, opened after clicking the event name. It searches all events the current user has full access to (that is, not a limited reviewer account) for events, sessions and speakers.
@@ -36,7 +35,7 @@ Release Notes
36
35
- :feature:`orga:schedule` The schedule editor page can now be printed – page breaks can still occur in odd places, but it's otherwise a very readable schedule (with your selection of rooms).
37
36
- :feature:`dev` Plugins can now inject content into a page's HTML ``<head>`` tag with the ``pretalx.orga.signals.html_head`` signal.
38
37
- :bug:`orga` Answers for URL questions were not included in JSON/CSV exports
39
-
- :announcement:`schedule` The primary URL of widget scripts and widget data has changed. The old URLs will continue until at least the last 2024 release.
38
+
- :announcement:`schedule` The primary URL of widget scripts and widget data has changed. The old URLs will continue to work until at least the last 2024 release.
40
39
- :announcement:`schedule` The old v1 schedule widget, which has been deprecated for a long time, has been removed.
41
40
- :feature:`orga` Tracks and session types in speaker information notes have a better interface, helpful for events with many of either of them.
42
41
- :feature:`orga:review,1462` Reviewers can now remove their reviews (while they can still be edited).
Copy file name to clipboardExpand all lines: doc/maintainer/release.rst
+21-23Lines changed: 21 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,34 +18,32 @@ Boarding checks
18
18
10. Are there any ``@pytest.mark.xfail`` that you have to resolve?
19
19
11. Are the :ref:`changelog` well-phrased and complete?
20
20
12. Are there `open pull requests <https://github.com/pretalx/pretalx/pulls>`_ that you should merge?
21
+
13. Are all tests passing in CI?
22
+
14. Have you written (and not pushed) a blog post? It should contain at least major features and all contributors involved in the release.
21
23
22
24
System checks
23
25
-------------
24
26
25
-
1. Are you in the branch and commit you think you are in?
26
-
2. Are all tests passing?
27
-
3. Have you deployed the release-ready commit to an instance? Did the upgrade work?
28
-
4. Have you written (and not pushed) a blog post? It should contain at least major features and all contributors involved in the release.
29
-
5. Have you told people who may need to know about the release ahead of time? (Plugin developers, clients, self-hosting instances, etc.)
27
+
1. Deploy the release-ready commit to an instance. Check if the upgrade and the instance works.
28
+
2. Clone pretalx into a clean repo: ``git clone git@github.com:pretalx/pretalx pretalx-release && mkvirtualenv pretalx-release && pip install -e .[dev]``
29
+
3. Run ``pytest`` **locally**.
30
+
5. Run ``check-manifest`` **locally**.
30
31
31
32
Take-off and landing
32
33
--------------------
33
34
34
-
1. Clone pretalx into a clean repo: ``git clone git@github.com:pretalx/pretalx pretalx-release && mkvirtualenv pretalx-release && pip install -e .[dev]``
35
-
2. Run ``check-manifest`` **locally**.
36
-
3. Bump version in ``src/pretalx/__init__.py``.
37
-
4. Add the release to the :ref:`changelog`.
38
-
5. Make a commit with the message ``Release vx.y.z``
39
-
6. Tag the commit: ``git tag vx.y.z -m``
40
-
7. Remove old build artefacts: ``rm -rf dist/ build/ pretalx.egg-info``
41
-
8. Build a new release: ``python -m build -n``
42
-
9. Upload the release: ``twine upload dist/pretalx-x.y.z.tar.gz``
43
-
10. Push the release: ``git push && git push --tags``
44
-
11. Install/update the package somewhere.
45
-
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`)
46
-
13. Push the blog post.
47
-
14. Upgrade `the docker repository <https://github.com/pretalx/pretalx-docker>`_ to the current commit **and tag the commit as vx.y.z**.
48
-
15. Increment version number to version+1.dev0 in ``src/pretalx/__init__.py``.
49
-
16. Update version numbers in update checker and deploy.
18. Update any plugins waiting for the new release.
35
+
1. Bump version in ``src/pretalx/__init__.py``.
36
+
2. Add the release to the :ref:`changelog`.
37
+
3. Make a release commit: ``RELEASE=vx.y.z && git commit -am "Release $RELEASE" && git tag $RELEASE -m "Release $RELEASE"``
38
+
4. Build a new release: ``rm -rf dist/ build/ pretalx.egg-info && python -m build -n``
39
+
5. Upload the release: ``twine upload dist/pretalx-x.y.z.tar.gz``
40
+
6. Push the release: ``git push && git push --tags``
41
+
7. Install/update the package somewhere.
42
+
8. 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`)
43
+
9. Publish the blog post.
44
+
10. Upgrade `the docker repository <https://github.com/pretalx/pretalx-docker>`_ to the current commit **and tag the commit as vx.y.z**.
45
+
11. Increment version number to version+1.dev0 in ``src/pretalx/__init__.py``.
46
+
12. Update version numbers in update checker and deploy.
0 commit comments