Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Agree upon versioning strategy #477

Open
taylortom opened this issue Jan 11, 2022 · 0 comments
Open

Agree upon versioning strategy #477

taylortom opened this issue Jan 11, 2022 · 0 comments
Labels
high priority Should be prioritised over all other issues question Discussion is required standards Related to coding standards
Milestone

Comments

@taylortom
Copy link
Collaborator

taylortom commented Jan 11, 2022

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.
@taylortom taylortom added this to the v1.0.0 milestone Jan 11, 2022
@taylortom taylortom added documentation Requires docs to be written standards Related to coding standards question Discussion is required labels Jan 11, 2022
@taylortom taylortom modified the milestones: v1.0.0-rc.1, v1.0.0 Sep 27, 2022
@taylortom taylortom moved this from New to Documentation in adapt-authoring: The TODO Board Feb 23, 2023
@taylortom taylortom moved this from Documentation to Awaiting Response in adapt-authoring: The TODO Board Feb 23, 2023
@taylortom taylortom removed the documentation Requires docs to be written label Mar 2, 2023
@taylortom taylortom added the high priority Should be prioritised over all other issues label Jun 19, 2024
@taylortom taylortom moved this from Awaiting Response to Backlog in adapt-authoring: The TODO Board Jun 27, 2024
@taylortom taylortom moved this from Backlog to Awaiting Response in adapt-authoring: The TODO Board Aug 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
high priority Should be prioritised over all other issues question Discussion is required standards Related to coding standards
Projects
Status: Awaiting Response
Development

No branches or pull requests

1 participant