Skip to content

Should we declare 1.3 a Long Term Support release? #3815

Description

@swcurran

Release 1.3.1 is stable and that makes the v1.3.x a good candidate to be the next LTS.

Notes:

  • 0.12-lts will end of life this October.
  • 1.2-lts will continue to be maintained for 9 months after the next LTS is declared -- which is what this issue proposes.
  • We are likely to see some bigger changes soon -- particularly in the form of Kanon/updates to the database structures and the use of Askar. Those are good candidates for breaking changes, and for keeping 1.3 as an LTS.
  • We can still release 1.3.x from the main branch until we decide there are breaking changes to warrant going to either 1.4 or 2.0. Then we maintain the 1.3-lts branch and cherry pick from main.
    • Now that we have the "lts" artifact, we'll have to think about how to generate those artifacts when doing a 1.3.x from main.

Thoughts? Any objections to making this declaration.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions