Skip to content

Decision on policy for versions to be supported #1

@meijer

Description

@meijer

At the moment there's no clear policy on how many versions back can be considered supported by the project. This impacts e.g. documentation, but once 2.0 is released also major version support.

How many versions will we consider to be supported by the project?

  • how far backwards compatible does the software need to be
  • how many old versions of the documentation are kept around
  • which versions can be expected to be maintained at any time?

Niels will put a question out on the -dev list, to measure the community's opinion.

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