Release v3.0.0 #3269
Description
We’re expecting to ship a breaking v3.0.0 release. See the v3.0.0 milestone for a comprehensive view of relevant pull requests and issues.
Major changes
In this release we intend to ship a few breaking changes:
- Changes to the schema to handle redirecting from one ID to one other ID (a feature move) and from one ID to many IDs (a feature split). #3000 for implementation; #3183 for docs)
- Simplifications to the types in the existing schema. Where previously some fields could be a string or an array of strings, in v3.0.0 only arrays of strings are allowed. (#1981 for discussion, #3184 for implementation)
- Removing some features that should not have been created or were minted prematurely (#2341, #2339).
Minor changes
This release will also contain typical updates, such as new features or updated support data for existing features.
Background
Although it’s been mentioned as an intention from time to time in various meetings, issues, and PRs, there’s never been a single place to track the release. This issue is now the home for that.
The main theme of this release is to establish the tools needed to handle the ordinary evolution of the platform. We’re starting with the things needed to handle basic maintenance tasks: splitting too-large features into parts and renaming features (for example, to fix typos).
Some further feature evolution work is expected in the future, such as feature folding or merging. This would come in a future release.