Releases: TabbycatDebate/tabbycat
Releases · TabbycatDebate/tabbycat
2.5.2
2.5.1
Nebelung (2.5.0)
- Added a preference to allow dedicated reply speaker. Thanks to Miha Frangež for the PR! (#1584)
- Private URL submissions now store the participant whose link was used rather than just their IP address (#1586)
- Added selectors for adjudicator positions in draw emails (#1423)
- Implemented debate postponement, allowing debates to be marked as "postponed" in the results page. Postponed debates do not block draw generation, contrary to unconfirmed debates. (#1563)
- Added round weights so that team points can be pondered between rounds, implementing tapered scoring. Weights only affect the sum of team points. (#1512)
- Optimisations to the database
- Adjudicator Feedback choices and draw flags are stored with PostgreSQL-specific arrays (#1525)
- Optimised database queries to create all debates in a draw at once (#1376)
- Optimised deletion of team private URLs (#1618)
- Reduced number of database queries in sending notifications (#1592)
- Delegated the calculation of team and speaker rankings to database functions where available, with metrics using the same query. (#1617)
- Improvements to the API, including
- Added URL field from the Room model to the Venues API endpoints as 'external URL'
- The Institution API endpoints show institutions' regions as their name, and regions can be created
- Breaks are now explorable and manipulable through the API.
- Overhauled the results framework to allow for more types of ballots
- BP finals now nominate only one team winning (#527)
- There are now settings to allow tied-point and low-point wins, with declared winners (#643)
- Two-team formats can now have scoreless ballots, and winner ballots are not restricted to elimination rounds (#1003)
- Results are now discoverable through the API.
- Added new translations and features to help translators
- Thanks to Pascal Alfadian for his work on an Indonesian translation!
- Added in-context translation through Crowdin enabling translations to be made directly on Tabbycat (#1664)
- Removed the simulated annealing adjudicator allocator. (#1619)
- Fixed issue with Sentry integration preventing some debugging info from being included in error reports
- Improved handling of multiple current rounds in record pages, and prevented data leakage
2.4.7
2.4.6
2.4.5
- Fixed the display of room URLs on private URL pages (thanks Viran for the report)
- Preformed panels with a bracket range now sort more sensibly (thanks Zachary for the report)
- Fixed manual sorting of preformed panels in general
- Improved sorting of feedback table when sorting 'difference between base score and current score' (thanks Zachary for the report)
- Fixed issue where the last saved counter was not updating on normal tables
2.4.4
- Fixed colours associated with adjudicators' scores not showing
- Showed validation errors when using API with invalid field names
- Prevented Tabbycat from creating default conflicts with the API if already specified in the request
- Fixed eligibility API endpoints when a list of participants is not present
- Fixed speaker category eligibility API endpoint not accepting speakers
- Allowed updating teams, excluding speakers, through the team detail API endpoint
- Added date and time formats for Malay
2.4.3
2.4.2
2.4.1
- Fixed issue where redundant check-ins would crash (#1513)
- Require round sequence numbers to be nonnegative (#1514)
- This change may cause upgrades of existing sites to fail with an
IntegrityError
if they have a negative round sequence number. Please change all round sequence numbers to positive numbers (or 0) before upgrading. Negative round numbers cause most Tabbycat pages to fail anyway, so functioning existing sites shouldn't have this problem.
- This change may cause upgrades of existing sites to fail with an
- Adjust display of team names in registration cards (#1511)
- Fixed bug causing main action item not to appear in languages other than English
- Allowed null values for emoji and code names in Teams' API
- Enforced use of null values where field is undetermined yet cannot be blank in API
- Improved performance of certain database pages
- Fixed issue where null points caused an error in current standings
- Fixed issue preventing the creation of speakers in teams through API
- Little updates and clarifications to the documentation