v1.5.0

✨ New Features

• 63ac037 - add useful badges to important guide/participant properties (PR #72 by @hardaker)
• 90de1de - add a new guide attribute for whether they are remote or not (PR #74 by @hardaker)
  • ↘️ addresses issue #62 opened by @hardaker
• 829ed6f - allow guides to select gender preferences for participants (PR #77 by @hardaker)
• a9373f2 - add admin notes (PR #75 by @hardaker)

🐛 Bug Fixes

• 72a3720 - added spacing at top of guide/participant matches (PR #73 by @hardaker)

v1.4.2

🐛 Bug Fixes

• faf1701 - add matching text about what to do when failing to connect (PR #70 by @hardaker)

v1.4.1

🐛 Bug Fixes

• 2ce6b93 - safer container re-entry. Remove obviated post-deploy script. (PR #68 by @rjsparks)

v1.4.0

✨ New Features

• d378d24 - django4, rearchitected container (PR #67 by @rjsparks)

(note - there is no v1.3.0 due to a build fumble)

v1.2.2

🐛 Bug Fixes

• 35c6990 - text nits and typos (PR #43 by @ghwood)
• 615f6c4 - a typo (PR #44 by @ghwood)
• d64fbbc - update email text for changes related to IETF114 (PR #47 by @hardaker)

🔧 Chores

• 3929ef4 - remove travis config (PR #45 by @rjsparks)

v1.2.1

Bug Fixes

• a000b5edb6 - text updates for modern list (#37 by @hardaker)

v1.2.0

Improved statistics, template changes for IETF 110

Simplify work for matchers by filtering participants who aren't participating in the next meeting

Merge pull request #32 from hardaker/matcher-attending-view-display

Fix the test suite and code for filtering participants

Add non-attending option

This release adds a "not attending the next ietf meeting" to the Participant model. This is a change in the design of the app, which previously assumed two things:

1. That participating in the guides program required participating in the next meeting (remotely or otherwise), and
2. Participant data would be reset after each meeting.

Django 2.2 and template changes to reflect IETF 108

This release moves the codebase to Django 2.2 and updates the template for email sent when a match is made to match IETF108's conditions.

With the upgrade to Django 2.2, sqlite3 based testing fails. Tests run on mysql (which matches production) succeed. See issue #25.