Releases correspond to Git tags. Changes between releases are described below with the following tags indicating the components affected:
UI
refers the user interfaceAPI
refers to the server componentINFRA
refers to infrastructure changes such as Docker, HTTPD configuration, etc.TOOLING
refers to changes to tooling that falls outside the UI or API, such as the RLA export.
- Fix timing bug in standardization process
- Make standardization process more robust
- Fix unchecked list index access during report generation
- Fix CVR export indicator not correctly showing up
- API - allow report to run before any audit submissions
- API - Affirmation text on the county report has more room
- UI - Prevent choice and contest names from growing too long
- API - Allow spaces in canonical choice names
- UI - Remove spinners on CVR upload error
- API - fix weird issue in reports where there are no contestCVRIds
- UI - Update DoS dashboard to handle multiple audit boards
- API - don't set auditStatus if hand counting
- UI - Immediately show deleted files on the DOS dashboard
- API - Ensure BMI and CVR deletions are reflected in the ASM
- API - Ensure contests are deleted
- UI - style updates
- UI - Fix slow-to-appear upload spinner
- UI - indicate upload in progress rather than an error
- API - Delete file as the state
- API - fast contest delete
- API - Throw error on invalid ballot manifests
- API - Fix infinite round loop under certain circumstances
- UI - simple change to remove warning about breadcrumbs
- UI - Add two new statuses to the state dashboard
- UI - Result on cdb
- UI - Remove manifest and CVR export matcher
- API - update reports sql using uf.computed_hash
- UI - spinner for delete file
- UI - Re-style file download widget
- API - add equals to Result - fixes concurrent update bug
- UI - UI Refresh - new look and feel on login and on the state dashboard
- API - File fails - file upload failures show better error messages
- API - Improved CVR import performance
- UI - Remove audit detail section from the county dashboard
- API - fix previously audited showing up in final review page
- UI - Hand count button requires confirmation
- UI - hide submit until valid seed entered
- API - Make the hand count button safe to use
- API - Don't show negative numbers of estimated samples
- INFRA - smoketest to use python3
- API - some debug logging removed
- UI - update instruction text
- UI - Fix bad audit board regex that caught just a single digit
- API - Correctly identify overvotes submitted by an audit board
- API - Database host should be configurable
- API - change meaning of ballotsRemainingInCurrentRound
- INFRA - add dashboard polling load test script
- UI - Prevent text selection on audit buttons
- API - Adjust where discrepancies appear in the DoS dashboard
- UI - Add CDOS contact info
- UI - Remove 'Vote for X' text from data entry and review screens
- API - Show signatories from all rounds on the affirmation sheet
- API - select CVRs in bulk, add uri concept for fast selection
- API - Specify column types for map serialization
- API - Show all audit board members on the affirmation sheet
- API - When a county runs out of ballots, we can only terminate single county audits
- API - (phantom-record) add ballotType to State report
- API - A CVR counts as an audited sample if it was selected for an audit
- UI - Fix ballot count pluralization on the county dashboard
- UI - Move "next card" button on the review screen
- UI - Only require no-consensus consent if we are checking the box
This release contained significant API-level and application-level changes, and represents over six weeks of sustained development effort.
- API - Log on phantom CVR creation
- UI - Fix a bug where standardized contests would sometimes not display on first run
- INFRA - Always pull new base Docker images when building
- TOOLING - Better debugging for smoketest main.py
- API - Handle phantom records
- TOOLING - Generate test files for RLAtool
The bulk of the changes since the last release are wrapped up in the following PR:
The sprint beginning on 7/18/2018 and ending on 7/31/2018
Fixes bugs from 1.3.0 and 1.3.2 releases
- unauditable contests becoming auditable
- large decimal in risk limit display
- fixed issue where no canonical contests file is uploaded
- removed 0 from range of random numbers
The sprint beginning on 7/18/2018 and ending on 7/31/2018
- Random ballot selection is driven by ballot manifests (#23) see the wiki for details. Some attributes still come from the CVR data(imprintedID for one). We hope to change that in the future.
- Add support for standardizing contest names (#24 and #25)
- API - Fix the "freeze" bug preventing Alamosa from completing their audit
- UI - Challenge response separates coordinates
This represents the two sprints beginning on 6/19/2018 and ending on 7/17/2018
- Documentation Updates
- UI - Lowercase username parameter to login2F
- remove parameter name constraint
- INFRA - Add support for running in virtual environments
- UI/API - Incorporate CDOS changes made between 2017 F&F delivery and Colorado's 2017 General Election
- UI - All audit info editable
- UI - Add selected contests to review page
- UI - Use a single input field for 2FA challenge
- UI - Usernames need to be lowercase
- API - Ballot Manifest can use strings for Batch IDs
- API - Ballot Manifest objects store their effective start / end sequence numbers
This is FreeAndFair's most recent tag.