Requirements for 1.0

[foolip]

What do we need to settle before releasing 1.0?

[foolip]

Specific issues to consider for 1.0:

• Validate any valid spec URL #84
• Consider handling feature identifier changes or aliases #91
• Feature parent relationships #217
• Support notes #557
• What's the earliest baseline_low_date? #623
• Add a group field? #648 (and snapshots)
• Burndowns for BCD, MDN, and Caniuse #666 (how much do we burn down?)
• Release the schema files in the the GitHub Release #715
• Publish descriptions #736

[foolip]

Why should we eventually release a 1.0? Only so that consumers can better use our version numbers to know when there are breaking changes.

[foolip]

In GoogleChrome/webstatus.dev#509 webstatus.dev was affected by our schema change when introducing groups and features. In order to be able to signal such breaking changes going forward, I'd like to release 1.0.0 ASAP and then proceed with semver like any project.

I had been "saving" 1.0 for something special, but I think the practical need to signal breaking changes is here right now. There are major versions after 1 that we can use for special events.