Skip to content

Version compatibility discussion #156

@aftersnow

Description

@aftersnow

Feature request:

so far, newly added fields have been optional, and the value ranges of fields have only been extended. This generally allows us to maintain forward compatibility.

However, if we encounter changes in the future that unavoidably break forward compatibility, should we establish a formal version management and compatibility strategy?

Use case:

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions