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

ZMK Versioning #2513

Open
Nick-Munnich opened this issue Sep 27, 2024 · 0 comments
Open

ZMK Versioning #2513

Nick-Munnich opened this issue Sep 27, 2024 · 0 comments

Comments

@Nick-Munnich
Copy link
Contributor

We want to add a proper versioning system to ZMK for multiple reasons:

  • Nicer handling of external module ecosystem
  • Stable branches prior to upgrading to Zephyr 3.7 (due to significant changes to how boards are defined)
  • Putting users on stable versions rather than main which may suddenly break reduces help requests

Current decisions made are:

  • Development work should happen in main
  • When a new feature (or group of features) seems stable, create a new branch release
  • Also create a new branch release prior to any breaking changes
  • Released branches get some amount of bug fixes, goal is to keep them as stable as possible
  • On bug fix, released branches get an additional tag added to them
  • Releases are accompanied by some form of release notes, optionally an upgrading guide when needed
  • New users are pointed to the latest stable branch when creating their config & setup

Unresolved questions that must be answered before beginning versioning are:

  • What naming system should we use for released branches?

Unresolved questions that would be nice to answer before beginning versioning are:

  • How do we handle versioning for the docs?

Unresolved questions that may best be answered afterwards are:

  • What bugs should be fixed in released branches?
  • Under what conditions should support for a released branch be dropped?
  • Anything to do with LTS releases.
  • Should we do any sort of "test/beta/stabilisation" release prior to a proper release?

Relevant discussion and content is here:

Other resources:

Please add any comments, thoughts, or questions, so that we can get this over with and get back to doing awesome stuff.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant