-
Notifications
You must be signed in to change notification settings - Fork 51
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge remote-tracking branch 'pretalx/main'
- Loading branch information
Showing
142 changed files
with
39,363 additions
and
11,852 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,36 @@ | ||
| name: Strings | ||
|
|
||
| on: | ||
| push: | ||
| branches: [ main ] | ||
| paths: | ||
| - 'src/pretalx/locale/**' | ||
| pull_request: | ||
| branches: [ main ] | ||
| paths: | ||
| - 'src/pretalx/locale/**' | ||
|
|
||
| concurrency: | ||
| group: ${{ github.workflow }}-${{ github.head_ref || github.run_id }} | ||
| cancel-in-progress: true | ||
|
|
||
| jobs: | ||
| compile: | ||
| runs-on: ubuntu-latest | ||
| name: Check that translation files compile | ||
| steps: | ||
| - uses: actions/checkout@v4 | ||
| - name: Set up Python ${{ matrix.python-version }} | ||
| uses: actions/setup-python@v5 | ||
| with: | ||
| python-version-file: ".github/workflows/python-version.txt" | ||
| cache: "pip" | ||
| - name: Install system dependencies | ||
| run: | | ||
| sudo apt update | ||
| sudo apt install gettext | ||
| - name: Install Python dependencies | ||
| run: python -m pip install -e ".[dev]" | ||
| - name: Compile locales | ||
| run: python manage.py compilemessages | ||
| working-directory: ./src |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -82,12 +82,12 @@ jobs: | |
| - name: Run checks | ||
| run: python manage.py check --deploy | ||
| working-directory: ./src | ||
| - name: Compile locales | ||
| - name: Run checks | ||
| run: python manage.py compilemessages | ||
| working-directory: ./src | ||
| - name: Run tests | ||
| working-directory: ./src | ||
| run: python -m pytest -nauto -p no:sugar --reruns 3 tests | ||
| run: python -m pytest -nauto -p no:sugar --reruns 3 --cov-report=term-missing:skip-covered tests | ||
| env: | ||
| PRETALX_CONFIG_FILE: 'tests/ci_${{ matrix.database }}.cfg' | ||
| - name: Show coverage as build info | ||
|
|
@@ -103,19 +103,6 @@ jobs: | |
| python -m coverage report | ||
| if: matrix.database == 'postgres' && matrix.python-version == '3.10' | ||
|
|
||
| - name: Create HTML report if tests failed. | ||
| id: html_report | ||
| working-directory: ./src | ||
| run: python -m coverage html | ||
| if: ${{ failure() }} && matrix.database == 'postgres' && matrix.python-version == '3.10' | ||
|
|
||
| - name: Upload HTML report if tests failed. | ||
| uses: actions/upload-artifact@v4 | ||
| with: | ||
| name: html-report | ||
| path: ./src/htmlcov | ||
| if: ${{ failure() }} && steps.html_report.conclusion != "skipped" | ||
|
|
||
| - name: "Make badge" | ||
| uses: schneegans/[email protected] | ||
| with: | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -4,6 +4,19 @@ Release Notes | |
| ============= | ||
|
|
||
| - :feature:`orga:sidebar` Renamed CfP to Call for Speakers for clarity | ||
| - :feature:`orga,820` Restricted tracks now link to the page where you can create access codes for that track. | ||
| - :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. | ||
| - :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. | ||
| - :feature:`orga:review,1633` Resources uploaded or linked by speakers are now shown in the review view (unless anonymous reviews are used, as resources can currently not be anonymised). | ||
| - :feature:`orga:review,1675` In order to make large events more manageable, the review dashboard is now by default paginated to 100 sessions per page. The page size can be adjusted up to showing all sessions as before (and the page size is remembered on a per-user basis). | ||
| - :feature:`orga` The default page size for paginated pages has been increased to 50. | ||
| - :feature:`orga:review` Reviewers can now review all proposals at the same time in bulk, as an alternative to reviewing them one by one. | ||
| - :feature:`orga` Organisers can now upload question options in bulk, which is particularly handy for questions with many options, like country lists. | ||
| - :feature:`orga:email,1351` pretalx now provides two new email placeholders, ``speaker_schedule_new`` (all talks changed in the current schedule, like in the notification email generated on schedule release) and ``speaker_schedule_full`` (a list of **all** scheduled sessions for that user). | ||
| - :bug:`schedule,1666` When building the social media preview card, pretalx would display a session's description rather than its abstract. | ||
| - :bug:`cfp,1660` When setting character limits on text questions, pretalx would count line breaks as two characters. | ||
| - :bug:`orga:submission,1613` The session page dropdown would sometimes include the "public link" even though it wasn't public yet. This has been fixed, and in the case of accepted or confirmed proposals that don't have a public page yet (e.g. because they're not scheduled yet), the link is marked as "public link (not public yet)". | ||
| - :bug:`cfp` When rendering email addresses in Markdown, shorter TLDs won out against longer ones (e.g. .co instead of .com, or .ro instead of .rocks). This was already fixed for normal links, just not for email addresses. Until you update to include this fix, you can instead turn emails into a link yourself: ``[[email protected]](mailto:[email protected])``. | ||
| - :feature:`orga,1619` Organisers can now add new team members in bulk instead of one by one. | ||
| - :feature:`orga:schedule,1587` A hint now shows when users click the "New break" box, informing them that they have to drag it to the schedule instead. | ||
| - :feature:`orga:schedule` Breaks now also show their start time and duration in the schedule editor. | ||
|
|
@@ -50,7 +63,7 @@ Release Notes | |
| - :bug:`admin,1579` There was a bug in the `pretalx init` command, and also too verbose output. | ||
| - :bug:`orga,1577` The printable proposal cards showed broken characters for anything outside latin1. | ||
| - :bug:`orga` Reordering questions while some of them were inactive could lead to 404 errors. | ||
| - :bug:`orga:submission` pretalx wasn't able to filter out pending state changes from the organiser proposal list. | ||
| - :bug:`orga:submission` pretalx wasn't able to filter pending state changes from the organiser proposal list. | ||
| - :bug:`lang` The schedule editor was not operational with some languages, particularly with different language code versions (pt-BR vs pt_br). | ||
| - :bug:`orga:schedule` The schedule editor would not show some specific time selectors when people expanded the timeline to see five-minute steps. | ||
| - :release:`2023.1.0 <2023-08-30>` | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -6,44 +6,46 @@ You are a pretalx maintainer and want to release a new version? Hold on to your | |
| Boarding checks | ||
| --------------- | ||
|
|
||
| 1. Are there pending migrations from `Weblate <https://translate.pretalx.com/projects/pretalx/pretalx/#repository>`_? Merge them. | ||
| 2. Are the translation files up to date? | ||
| 3. Are there pending checks for bad translations on Weblate? | ||
| 4. If new translations were added, add new fullcalendar locales (you have to download the `release archive <https://github.com/fullcalendar/fullcalendar/releases/download/v6.1.5/fullcalendar-6.1.5.zip>`_) and extract the locales from there), and make sure that flags (in input fields) for the new locale are shown. | ||
| 5. Are there warnings about missing migrations? | ||
| 6. Any blockers to see `here <https://github.com/pretalx/pretalx/issues?q=is%3Aopen+is%3Aissue+label%3A%22type%3A+bug%22+>`_? | ||
| 7. Are there any TODOs that you have to be resolve? | ||
| 8. Are there any ``@pytest.mark.xfail`` that you have to resolve? | ||
| 9. Are the :ref:`changelog` well-phrased and complete? | ||
| 10. Are there `open pull requests <https://github.com/pretalx/pretalx/pulls>`_ that you should merge? | ||
| 1. Are the translation files up to date? | ||
| 2. Are there pending checks for bad translations on Weblate? | ||
| 3. Are there pending translations from `Weblate <https://translate.pretalx.com/projects/pretalx/pretalx/#repository>`_? Merge them. | ||
| 4. Are all locales with more than 75% coverage included in the release? | ||
| 5. Update the translation percentages from `translate.pretalx.com <https://translate.pretalx.com/projects/pretalx/pretalx/#translations>`_. | ||
| 6. If new translations were added, add new fullcalendar locales (you have to download the `release archive <https://github.com/fullcalendar/fullcalendar/releases/download/v6.1.5/fullcalendar-6.1.5.zip>`_) and extract the locales from there), and make sure that flags (in input fields) for the new locale are shown. | ||
| 7. Are there warnings about missing migrations? | ||
| 8. Any blockers to see `in our issues <https://github.com/pretalx/pretalx/issues?q=is%3Aopen+is%3Aissue+label%3A%22type%3A+bug%22+>`_? | ||
| 9. Are there any TODOs that you have to resolve? | ||
| 10. Are there any ``@pytest.mark.xfail`` that you have to resolve? | ||
| 11. Are the :ref:`changelog` well-phrased and complete? | ||
| 12. Are there `open pull requests <https://github.com/pretalx/pretalx/pulls>`_ that you should merge? | ||
|
|
||
| System checks | ||
| ------------- | ||
|
|
||
| 1. Are you in the branch and commit you think you are in? | ||
| 2. Are all tests passing? | ||
| 3. Have you deployed the release-ready commit to an instance? Did the upgrade work? | ||
| 4. Have you written (and not pushed) a blog post? It should contain at least major features and all contributors involved in the release. ``git shortlog -ns vx.y.z..main``. | ||
| 4. Have you written (and not pushed) a blog post? It should contain at least major features and all contributors involved in the release. | ||
| 5. Have you told people who may need to know about the release ahead of time? (Plugin developers, clients, self-hosting instances, etc.) | ||
| 6. Is your virtualenv active? | ||
|
|
||
| Take-off and landing | ||
| -------------------- | ||
|
|
||
| 1. Clone pretalx into a clean repo: ``git clone [email protected]:pretalx/pretalx pretalx-release && workon pretalx`` | ||
| 1. Clone pretalx into a clean repo: ``git clone [email protected]:pretalx/pretalx pretalx-release && mkvirtualenv pretalx-release && pip install -e .[dev]`` | ||
| 2. Run ``check-manifest`` **locally**. | ||
| 3. Bump version in ``src/pretalx/__init__.py``. | ||
| 4. Update the translation percentages from `here <https://translate.pretalx.com/projects/pretalx/pretalx/#translations>`_. | ||
| 5. Add the release to the :ref:`changelog`. | ||
| 6. Make a commit with the message ``Release vx.y.z`` | ||
| 7. Tag the commit: ``git tag vx.y.z -m`` | ||
| 8. Remove old build artefacts: ``rm -rf dist/ build/ pretalx.egg-info`` | ||
| 9. Build a new release: ``python -m build -n`` | ||
| 10. Upload the release: ``twine upload dist/pretalx-x.y.z.tar.gz`` | ||
| 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. Increment version number to version+1.dev0 in ``src/pretalx/__init__.py``. | ||
| 17. Update version numbers in update checker and deploy. | ||
| 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 vx.y.z -m`` | ||
| 7. Remove old build artefacts: ``rm -rf dist/ build/ pretalx.egg-info`` | ||
| 8. Build a new release: ``python -m build -n`` | ||
| 9. Upload the release: ``twine upload dist/pretalx-x.y.z.tar.gz`` | ||
| 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. Increment version number to version+1.dev0 in ``src/pretalx/__init__.py``. | ||
| 16. Update version numbers in update checker and deploy. | ||
| 17. ``rm -rf pretalx-release && deactivate && rmvirtualenv pretalx-release`` | ||
| 18. Update any plugins waiting for the new release. | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.