🌟 Release Checklist for TIDES v2.0

[chrisyamas]

This issue tracks outstanding items that must be completed before declaring the v2.0 release.

Remaining Issues from Milestone

Requirements from Versioning Policy

• Each release MUST contain one or more changes to normative content which have been approved through the change-making process.
• Each release MUST be reviewed and approved in GitHub by 2+ members of the Board – or their designees – for accuracy and consistency with the changes' intent.
• Each release MUST be tagged with its version number.
• Each release MUST have documentation available.
• Each release MUST have an entry in CHANGELOG.md.
• Each release MUST be specified as a release on Github.
• Each release MUST be noticed to any TIDES mailing lists or discussion groups.
• Each release SHOULD have sample datasets (real or exemplary) which cover the normative changes in the release.

Constituent v2.0 changes (PRs to develop)

• Add vehicle_crew supporting table #246 – add vehicle_crew supporting table
• Update event_type enum values to snake_case #247 – update event_type enum values to snake_case
• Clarify event_count usage and APC data guidance #248 – clarify event_count usage and APC data guidance
• Rename duration fields with explicit suffix #249 – rename duration fields with explicit suffix
• Add new vehicle_label field to vehicles table #250 – add vehicle_label field to vehicles table
• Rename passenger_events to device_events with expanded scope #251 – rename passenger_events to device_events with expanded scope
• Add device_status table for tracking device availability #253 – add device_status table for tracking device availability

Potential / under consideration

Not yet confirmed for v2.0; pending the Issues Working Group decision on whether they proceed to a PR for this release.

• 📄🚀 – Modify handling of vehicle attributes and vehicles consists #269 – vehicle attributes / vehicle consists (Issues Working Group)
• 🐛📄 – Stop Visits departure_load minimum: 0 biases aggregations #270 – stop_visits departure_load minimum bias

Each box is checked when its change is merged into develop. Final release merges develop to main with 2+ Board approvals per the versioning policy.

[chrisyamas]

Just a note that the "documentation available" for this release should include a migration guide to help TIDES implementers appropriately migrate from prior version (1.0).