Skip to content

Agree upon versioning strategy #477

Open
@taylortom

Description

@taylortom

This one's been discussed a few times, but this needs to be decided & documented once and for all!

What we need:

  • SIMPLE for devs to implement/adhere to
  • Allow version clamping for peace of mind of testing/end-users
    • Should also apply to documentation so end-users/devs are able to look-up info with confidence

Possible route:

  • Versioning based on top-level first-party (i.e. adapt) deps (a minor version triggers a minor release etc.). Updates to 3rd party deps should only need patch releases but can be considered on a case-by-case basis
  • Changelog can either link to the changelogs of each changed module, or include specifics for all changes. Don't mind which we go for here. Depending on whether we decide to log issues with individual modules in their relevant repos or log everything in this repo, automating this task could be tricky.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    high priorityShould be prioritised over all other issuesquestionDiscussion is requiredstandardsRelated to coding standards

    Type

    No type

    Projects

    Status

    Awaiting Response

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Agree upon versioning strategy · Issue #477 · adapt-security/adapt-authoring