Permalink
Fetching contributors…
Cannot retrieve contributors at this time
205 lines (202 sloc) 21.6 KB

Release Notes

  • :feature:`538` The sneak peek view will only feature talks that have been accepted.
  • :feature:`440` Organisers can now follow an RSS feed to see new submissions – you'll have to provide your authentication token in the RSS request header to authenticate.
  • :feature:`-` You can now set the default pretalx system wide time zone and locale (defaulting to UTC and en).
  • 🐛`544` Organisers could see the titles of speaker information notes of all events, not just the currently active one (they could not see the details or edit them).
  • :feature:`504` The schedule page is now better printable.
  • 🐛`-` A bug <https://github.com/celery/celery/issues/4878> in celery could make running pretalx with asynchronous workers impossible. We've pinned an earlier celery version that doesn't show this problem.
  • :support:`-` A new pretalx plugin adds media.ccc.de as a recording provider – this plugin replaces the previously inbuilt capacity of pretalx to provide recording iframes. (This functionality was never directly exposed and only accessible via the pretalx shell. It is now deprecated and will be removed in a later version.)
  • :feature:`-` Plugins can now provide recording iframes (via the new register_recording_provider signal and other mixins).
  • :feature:`-` The new nav_event_settings plugin signal allows plugins to integrate their own settings pages next to the pretalx core pages.
  • :feature:`-` pretalx now presents a colorpicker for your event primary color, including a hint on color suitability.
  • :feature:`-` The new /api/me endpoint shows name, email address, locale, and timezone of the logged in user.
  • :feature:`-` The nav_event plugin signal has changed to expect a list instead of a dictionary response. The dictionary response will be supported for one more version, and raises a deprecation warning.
  • :feature:`-` The API now provides a /rooms endpoint – this endpoint is public, so upgrading will publish which rooms you have configured in your conferences!
  • :feature:`530` The API now provides a /reviews endpoint.
  • 🐛`529` When trying to review their own submission, a user would see a 404 not found error instead of an explanation that this was a forbidden action.
  • 🐛`-` The password reset form told users if they had already tried to reset their password in the last 24 hours. While this is helpful, it also allows user discovery via password reset. Instead, the user now sees a more generic message.
  • :feature:`-` While filling out the submission form wizard, submitters see a top bar telling them where they are in the submission process.
  • 🐛`-` The event dashboard showed a wrong countdown towards the CfP end while the CfP end was between three and one day away.
  • :feature:`-` The new event dropdown helps you find your event, even if you have access to many events.
  • 🐛`-` The organiser login page did not strip whitespace from login credentials.
  • 🐛`524` Review settings contained the setting "Force data entry" twice, referring to the score and text, respectively.
  • 🐛`522` If a speaker did not check a mandatory checkbox, they could not submit the form (as intended), but could see no feedback explaining the issue.
  • :feature:`` The rebuild command now comes with a lot more build output for ease of debugging. You can disable the build output with the new --silent/-s flag.
  • :feature:`476` Administrators can now delete both events and organisers.
  • :feature:`493` Speaker email addresses are now available via the API for users with access permissions.
  • 🐛`515` Under rare circumstances, the pretalx database could reach a state pretalx couldn't cope with due to duplicate schedule versions.
  • :feature:`512` You can now configure if speakers should provide their availability during talk submission.
  • :support:`-` Due to an updated Django version, pretalx has dropped support for PostgreSQL 9.3 and MySQL 5.5.
  • :release:`0.8.0 <2018-09-23>`
  • 🐛`-` When a user removed a submission containing an answered choice question, pretalx removed the selected answer option, too.
  • 🐛`501` When a speaker held more than two talks, their related talks did not show up.
  • 🐛`505` Custom CSS may now also include media queries.
  • 🐛`500` Display of times could be off in the static HTML export.
  • :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.
  • :feature:`213` A human-readable time until the CfP closes now shows up next to the end time.
  • 🐛`503` Not all current TLDs did end up included as URLs when processing markdown input to build links.
  • 🐛`-` The schedule import in the organiser backend never worked (while the manage command for administrators did work).
  • :feature:`454` As an organizer, it's now possible to send an email to all reviewers in the Compose Mail section.
  • :feature:`492` In exports, HTTP Etags are now supported to allow for more aggressive caching on clients.
  • 🐛`-` If a review question was mandatory while submission questions were active, they would block the submission process.
  • :feature:`-` Organisers can now also reset the password for the speakers they have access to.
  • 🐛`488` The HTML export contained media files (not other content) from all conferences on an instance, instead of the exported conference.
  • :feature:`-` Present a public list of talks and a list of speakers.
  • 🐛`478` The behaviour of pressing enter in multi-step forms was unintuitive in some places.
  • :feature:`-` The submission list now includes a graph of submissions over time.
  • :feature:`-` You can now see the sneak peek / is_featured flag in the submissions and talk API endpoints.
  • :feature:`-` You can now use your authentication token to access all pages you have access to, as you already could for the API. This makes integration of exports much easier.
  • :support:`-` All manage commands available in pretalx are now included in the documentation.
  • :feature:`240` When using paper cards to build a schedule, each card comes with a QR code link to a quick scheduling form for that submission.
  • :feature:`-` You can now see warnings and what the public changelog will look like before releasing a new schedule.
  • :feature:`214` The schedule editor shows warnings on scheduling conflicts, including live feedback on where you can schedule a talk.
  • :feature:`474` The review dashboard now features the same search and filter options as the submission list.
  • 🐛`473` Following the revamp of team permissions, override votes were missing from the settings. We re-introduced the settings, and improved the general handling of override votes.
  • :support:`-` pretalx now doesn't support usernames any longer – as all users had to have email addresses already, you will now have to provide an email address to log in. This may confuse users – as an administrator, you can look up users' email addresses if they don't remember them, or change them, if necessary.
  • 🐛`-` You could make questions inactive, but not delete them.
  • :feature:`408` You can now add length restrictions to abstracts, descriptions, speaker biographies, and all text-based questions.
  • :feature:`-` When linking to a talk on social media, those pages will show the talk image.
  • :feature:`-` French translation
  • :feature:`-` The event logo shows up larger and up to the full width of the document below. Please check that your event still looks as intended after upgrading.
  • :feature:`149` Allow to order rooms manually.
  • :feature:`149` Allow to order questions manually.
  • :support:`-` We now have tests to make sure all config options and plugin hooks are part of our documentation.
  • :feature:`-` Instead of setting a flag somewhere, pretalx now has an explicit "go live" button. Plugins can listen to the corresponding signal (please refer to the plugin documentation for further information).
  • 🐛`463` Don't show a 404 error if a reviewer tries to review their own submission, but show an error message instead.
  • :feature:`-` For organisers, the submission/talk API endpoints now contain the question answers given by the speakers.
  • :feature:`-` Schedules now contain a search bar to filter talks by title or speaker.
  • :feature:`-` Schedules now feature a sidebar navigation to jump directly to a selected day.
  • :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:`-` Prevent organisers from adding a non-localhost mail server without transport level security to make sure our Privacy Policy holds true.
  • :feature:`415` Allow organisers to trigger a password reset for team members.
  • 🐛`451` Don't crash during pretalx init if no conference organiser slug is present.
  • :release:`0.7.1 <2018-06-19>`
  • 🐛`-` The new read-only links for submissions received the same secret token when migrating the database. pretalx leaked no data, as this made using the read-only links impossible. When upgrading to the next release, all read-only link addresses will be reset.
  • 🐛`-` A one-character-oversight led to issues with the new navigation search with certain user permissions.
  • :release:`0.7.0 <2018-06-19>`
  • :feature:`430` To maintain compatability with frab xml exports, the schedule xml export now contains a <url> tag.
  • 🐛`-` When trying to register a user with a nick that already existed in a different capitalization, pretalx failed to show a clear error message.
  • :feature:`128` An event's schedule is now available even if the browser has no internet connection, provided it has opened the schedule before.
  • :support:`-` Provide better upgrade documentation for administrators.
  • :support:`-` Add clever release notes.
  • 🐛`443` (UI) The button colors when changing submission states were unintuitive.
  • :feature:`-` You can now configure the configuration file with the PRETALX_CONFIG_FILE environment variable.
  • :feature:`-` Some more context sensitive dashboard tiles include for example a countdown to the CfP end.
  • :feature:`-` A navigation search allows you to go directly to a range of useful pages.
  • 🐛`444` If two organisers set a submission to 'accepted' at the same time, two acceptance emails would show up in the outbox.
  • 🐛`-` Removing a speaker from a submission could be impossible if their nick contained special characters.
  • :feature:`-` Submitters can share a submission via a read-only link.
  • :feature:`-` Organisers can configure a list of talks as "sneak peek" before they release the first schedule.
  • 🐛`446` If an event had a custom domain configured, absolute urls would still use the instance's default domain.
  • 🐛`441` The "Mark speaker arrived" button is now visible during and slightly before the event, but not during other times.
  • 🐛`-` The API always showed the speaker biography as empty.
  • 🐛`-` When accessing a confirmation link unauthenticated, a 404 page was visible instead of a login page.
  • :feature:`-` The API now exports links to submission images and speaker avatars.
  • 🐛`-` HTML exports failed if a speaker had canceled their talk.
  • 🐛`-` Sometimes, empty HTML reports showed up with all talks missing.
  • :release:`0.6.1 <2018-05-15>`
  • 🐛`-` The "Copy to draft" button was missing when viewing a sent email.
  • 🐛`431` Accepted, but unconfirmed talks showed up as "Other talks" on the public schedule once the speaker had confirmed one talk.
  • :release:`0.6.0 <2018-05-06>`
  • :feature:`-` New plugin hook: pretalx.submission.signals.submission_state_change will trigger on any state change by a submission.
  • :feature:`-` The frab compatible xml now uses UUIDs, and includes an XML comment with a pretalx version string.
  • :feature:`-` pretalx has a better general look and feel and colorscheme.
  • :feature:`-` Organisers can make more changes to speaker profiles and submissions to ease event administration.
  • :feature:`-` pretalx now has a concept of organisers and teams.
  • :feature:`-` To avoid running into issues when uploading custom CSS, and ensuring smooth operations, custom colors and CSS is not used in the organiser area anymore.
  • :feature:`-` You can now send mails from templates and use shortcuts from submissions to send mails to specific speakers.
  • :feature:`-` Since different events have different needs, organisers can now choose if speakers have to provide submission abstracts, descriptions, and speaker biographies during the CfP.
  • 🐛`375` Speakers could see their submission in the orga backend, but could access no information they did not put there themselves.
  • 🐛`-` The API showed talks to organisers if no schedule was present yet. It did not show the information to unauthorised users.
  • 🐛`-` There was no possibility to reset a user's API token.
  • 🐛`-` If an organiser changed a speaker's email address, they could assign an address already in use in the pretalx instance, resulting in buggy behaviour all around.
  • :release:`0.5.0 <2018-03-07>`
  • :feature:`-` pretalx now features a Plugin API, allowing to install custom plugins. Plugins can add their own exporters, and hook into plugin hooks. You can enable or disable plugins per event. You can find the plugin developer documentation: https://docs.pretalx.org/en/latest/developer/plugins/index.html
  • :feature:`340` Organisers can now decide if reviewers should have to submit a score or a text with their review.
  • :feature:`93` Organisers can provide room-based information for speakers, and send it automatically in the emails about talk scheduling.
  • :feature:`318` The list of submissions is now better searchable.
  • :feature:`294` Speakers can now upload an image that will show up next to their talk information.
  • :feature:`-` Reviewers can now also answer custom questions during their review, with all capabilities that speaker questions have.
  • :feature:`352` There are now optional review deadlines, preventing users from adding, modifying or removing reviews after a certain date.
  • :feature:`-` Individual directories for logs, media, and static files can now take their values from environment variables.
  • :feature:`348` Organisers can now show information snippets to submitters, or speakers.
  • :feature:`-` Allow to filter question statistics by speaker status.
  • 🐛`344` In the dashboard, reviewers would see an incorrect link to add new reviewers.
  • 🐛`341` The "save" button was missing on the mail settings page.
  • 🐛`333` Users could not see (instead not change) their submissions after CfP end, until they were either rejected or accepted.
  • 🐛`-` In the <title> tag, the event showed up twice, once properly and once in a technical representation.
  • 🐛`-` Documentation fix: The environment variable for database passwords is PRETALX_DB_PASS, not PRETALX_DB_PASSWORD.
  • 🐛`-` Unconfirmed talks showed up as empty boxes in the schedule editor.
  • 🐛`-` Upgrading the privileges of an existing user did not result in an email, since it required no new account.
  • 🐛`300` The Docker setup was non-functional. The documentation includes a notice of limited support.
  • 🐛`-` The orga view now always uses the event timezone.
  • :release:`0.4.1 <2018-02-05>`
  • 🐛`335` CfP was uneditable due to missing "Save" button.
  • 🐛`336` Organisers couldn't add new questions.
  • :release:`0.4.0 <2018-02-04>`
  • :feature:`-` A page in the organiser area lists and links all possible data exports in one export page.
  • :feature:`322` You may now import XML files to release a new schedule.
  • :feature:`292` We added a new team management interface to manage all team members and permissions in one place.
  • :feature:`-` The new init command for project setup adds the initial user, but in time it should ask for basic configuration, aswell.
  • :feature:`-` The rebuild command now supports a --clear flag to remove all static assets before rebuilding them.
  • :feature:`-` You can choose a pattern for the header hero strip in your event color.
  • :feature:`320` You can now choose different deadlines per submission type, overriding the default deadline.
  • :feature:`325` All forms are instantly editable if you have edit permissions, and disabled otherwise. No more need to click "Edit"!
  • 🐛`-` The schedule export could change project settings, requiring pretalx restart to reset the settings. Unchecking the "Generate HTML export on schedule release" settings was a workaround for this bug.
  • 🐛`259` When running pretalx as (in-application) superuser, permission issues could arise. pretalx now warns and offers to migrate the account to an administrator account.
  • 🐛`-` Frontend password validation was non-functional, and never displayed interactive password statistics. This was a display issue.
  • 🐛`327` We removed the unused max_duration property of submission types.
  • 🐛`329` Users always saw the default submission type instead of their chosen one.
  • :release:`0.3.1 <2018-01-18>`
  • 🐛`-` Make 404 errors more helpful.
  • 🐛`-` Re-introduce support for the documented PRETALX_DATA_DIR environment variable.
  • 🐛`-` Leaving an optional choice question empty resulted in a server error.
  • :release:`0.3.0 <2018-01-17>`
  • :feature:`243` Organisers can mark speakers as "arrived".
  • :feature:`67` Visitors can download an ical file containing all talks of a single speaker.
  • :feature:`-` We have a new API for speakers.
  • :feature:`-` The speaker biography is now visible in submissions in the API endpoint.
  • 🐛`-` Non-superusers could not access the email sending form.
  • 🐛`-` More than one event stage could be visible as active.
  • 🐛`-` If a user without active log-in looked at entered submissions, they triggered a server error instead of a 404.
  • 🐛`-` If notifications about new submissions were active, pretalx sent the mails to the submitter instead of the organizer.
  • :release:`0.2.2 <2017-12-11>`
  • 🐛`-` Reviewers could not view speaker pages.
  • 🐛`-` Inviting somebody twice did not issue a second invitation object.
  • 🐛`-` Somebody who was reviewer first could not join the organizer team.
  • :release:`0.2.1 <2017-12-06>`
  • :feature:`122` All HTML contains better meta tags, which leads to better display in social media.
  • 🐛`289` Organisers could not delete inactive questions (making them active first worked as a workaround).
  • 🐛`288` Organisers could not delete choice questions as long as they still had answer options.
  • 🐛`-` Review team invitations sometimes failed, resulting in useless invitation objects.
  • 🐛`-` Clicking the "Save & next" button when reviewing could result in an internal error, without any data loss.
  • 🐛`-` Organisers could not remove reviewers from teams.
  • 🐛`-` Absolute URLs always included 'localhost' as their host.
  • 🐛`-` When adding a submission in the orga backend with an orga user as speaker, the orga user did not receive a speaker profile.
  • :release:`0.2.0 <2017-12-01>`
  • 🐛`-` 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.
  • :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.
  • :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:`215` pretalx validates mail template placeholders, and prevents organisers from saving templates including invalid placeholders.
  • :feature:`208` You can now ask questions that take an uploaded file as an answer.
  • :feature:`209` Speakers can now upload files which will be visible on their talk page.
  • :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:`38` pretalx can now run with celery (an asynchronous task scheduler) for long running tasks and tasks like email sending. The new config section is part of our documentation.
  • :feature:`-` The new rebuild command recompiles all static assets.
  • :feature:`207` Question answers now receive a nice evaluation, aggregating all given answers.
  • :feature:`233` Organisers can mark questions as 'answers contain personal data'. When users delete their accounts, they also delete answers of these questions.
  • :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:`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:`156` You can assign "override votes" to reviewers, which function like vetos (both positive and negative), on an individual basis.
  • :feature:`-` The new read-only REST API supports resources for events and submissions.
  • 🐛`304` pretalx crashed with incorrect invite keys, now it shows a 404 page.
  • 🐛`-` When building absolute URLs for exports, emails, and RSS feeds, pretalx used 'localhost' instead of the actual configured URL.
  • 🐛`-` If a user was both an orga member and a reviewer, they could encounter access rights issues.
  • 🐛`-` When removing the custom event color, and then adding it again, caching issues could occur.
  • 🐛`-` Inactive questions (questions not visible to speakers) were not editable.
  • 🐛`-` In some places, gravatar images of the visiting user were visible instead of the speaker.
  • 🐛`-` The event stage display could show conflicting phases as active.
  • 🐛`287` The default submission type was not, in fact, suggested by default.
  • :release:`0.1.0 <2017-11-01>`