[Feature]: Allow organisers to configure which of the default CfP fields to request and require. Please check your settings after updating, as the migration is not guaranteed to work as expected.

[Feature]: Schedules now feature a sidebar navigation to jump directly to a selected day.

[Feature]: Schedules now contain a search bar to filter talks by title or speaker.

[Feature]: For organisers, the submission/talk API endpoints now contain the question answers given by the speakers.

[Feature]: Instead of setting a flag somewhere, pretalx now has an explicit “go live” button. There is also a corresponding signal plugins can listen to (please refer to the plugin documentation for further information).

[Bug]#501:: When a speaker held more than two talks, their related talks were not linked correctly.

[Bug]:: When a submission was removed that contained an answered (multiple-) choice question, the selected answer option was removed, too.

[Support]: We now have tests to make sure all config options and plugin hooks are documented.

[Support]: pretalx now doesn’t support usernames any longer – as email addresses were already required for accounts, they are now the only means of logging in. This may confuse a few users – as an administrator, you can look up users’ email addresses if they don’t remember them, or change them, if necessary.

[Support]: All manage commands available in pretalx are now included in the documentation.

[Support]: The URLs for schedule exports have changed from /myevent/schedule/export?exporter=exportername to /myevent/schedule/export/exportername – if you have hardcoded links to schedule exporters, please update them accordingly.

[Bug]: A one-character-oversight led to issues with the new navigation search with certain user permissions.

[Bug]: The new read-only links for submissions received the same secret token when migrating the database. No data was leaked as this made using the read-only links impossible. When upgrading to the next release, all read-only link addresses will be reset.

[Feature]#93: Organisers can provide room-based information for speakers, which will be provided in emails about talk scheduling.

[Feature]#340: Organisers can now decide if reviewers should be required to submit a score or a text with their review.

[Feature]: pretalx now features a Plugin API, allowing to install custom plugins. Plugins can add their own exporters, and hook into various plugin hooks to be expanded over the course of this year. Plugins can be enabled or disabled per event. Documentation can be found here: https://docs.pretalx.org/en/latest/developer/plugins/index.html

[Bug]: The orga view now always uses the event timezone.

[Bug]#300: The Docker setup was broken. It is fixed, and a notice of limited support was added to the documentation.

[Bug]: Upgrading the privileges of an existing user did not result in an email, since no invitation was required.

[Bug]: Unconfirmed talks showed up as empty boxes in the schedule editor.

[Bug]: Documentation fix: The environment variable for database passwords is PRETALX_DB_PASS, not PRETALX_DB_PASSWORD.

[Bug]: In the <title> tag, the event was displayed twice, once properly and once in a technical representation.

[Bug]#333: Users could not see (instead not change) their submissions after CfP end, until they were either rejected or accepted.

[Feature]: A read only REST API was introduced. At the moment, it only supports resources for events and submissions.

[Feature]#156: You can assign “override votes” to reviewers, which function like vetos (both positive and negative), on an individual basis.

[Feature]#171: You can now configure a custom domain to use with your event, in case you have an event specific domain for each of your events.

[Feature]#78: We moved to a new permission system that allows for more flexible roles. Please report any bugs that may relate to incorrect permissions.

[Feature]#233: Questions may now be marked as ‘answers contain personal data’. Answers of these questions are deleted when users delete their accounts.

[Feature]#207: Question answers now receive a nice evaluation, aggregating all given answers.

[Feature]: A rebuild command was introduced that recompiles all static assets.

[Feature]#38: pretalx can now be configured to run with celery (an asynchronous task scheduler) for long running tasks and tasks like email sending. A new config section was added, and usage has been documented.

[Feature]#210:, [Feature]#195: The review interface has been rewritten to include fewer pages with more information relevant to the user, dependent on event stages and their role in the event.

[Feature]#209: Speakers can now upload files which will be shown on their talk page.

[Feature]#208: You can now ask questions that take an uploaded file as an answer.

[Feature]#215: Mail template placeholders are now validated so that templates including invalid placeholders cannot be saved at all.

[Feature]#126: You can now choose to hide the public schedule (including talk pages and speaker pages, but excluding feedback pages and the schedule.xml export)

[Feature]#159: E-mails are now sent with a multipart/HTML version, featuring the mail’s text in a box, styled with the event’s primary color.

[Bug]#287: The default submission type was not, in fact, suggested by default.

[Bug]: The event stage display could show several conflicting phases as active.

[Bug]: In some places, gravatar images of the visiting user were shown instead of the speaker.

[Bug]: Inactive questions (questions not shown to speakers) could not be edited.

[Bug]: When removing the custom event color, and then adding it again, caching issues could be encountered.

[Bug]: If an account was configured to be both an orga member and a reviewer, it encountered access rights issues.

[Bug]: When building absolute URLs for exports, emails, and RSS feeds, ‘localhost’ was used instead of the actual configured URL.

[Bug]#304: pretalx crashed when an incorrect invite key was used, now it shows a 404 page.

[Bug]: The default value for email SSL usage is now False, permitting the default configuration of localhost:25 to work on more machines out of the box.