+
Skip to content

Compatibility profiles #35650

@stianst

Description

@stianst

Description

We currently have the ability to define different versions of a feature when backwards compatibility is broken; but we don't have a server-wide approach for when it's not wrapped in a feature.

Additionally, anyone that wants to stay on the latest and greatest would need to bump all feature versions.

We should consider introducing something like --feature=compatible|latest|preview, where:

  • Compatible - is guaranteed to not introduce any breaking changes
  • Latest - introduces breaking changes and uses the latest supported versions of a feature
  • Preview - enables all preview features, switches to preview feature versions, etc.

Additionally, some behaviour not wrapped in a feature could use the compatibility profile to change behaviour. We may also want to remove/disable some deprecated capabities in latest.

Basically the aim here is that people can choose whether or not they want to:

  • Stay compatible and not making any changes until upgrading to 27
  • Adopt changes as they come, getting ready early for 27
  • Preview new stuff (not recommended for production ;))

Discussion

No response

Motivation

No response

Details

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      点击 这是indexloc提供的php浏览器服务,不要输入任何密码和下载