Skip to content

Update breaking changes documentation #337

@labo-flg

Description

@labo-flg

Clarify the strategy :

  • our first intention is to never break an API unless it's mandatory to solve a real issue
  • deprecated API endpoints can live more than 3 major versions, but after 3 major versions it might be deleted any time if there is a good reason for it
  • cleanup current situation in the breakdown per version table

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions