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

Versioning scheme #187

Open
ptomato opened this issue Jul 28, 2024 · 1 comment
Open

Versioning scheme #187

ptomato opened this issue Jul 28, 2024 · 1 comment

Comments

@ptomato
Copy link

ptomato commented Jul 28, 2024

What versioning scheme should this module follow? An alternating stable-unstable one like GNOME does, so that you can derive the corresponding GJS version directly from the module's version? or semver, where you bump the major version every time a new version of the module can't be used with previous GJS, and there's like a table in the docs that says "4.x ↔ GJS 1.76–82" or whatever.

@JumpLink
Copy link
Collaborator

Good point. It should definitely be documented and maintained somewhere. Maybe we can tag types in the comments with @Version @deprecated tags and then support a wide range of GJS versions and only remove old types for major breaking changes in GJS? I'm still completely open here

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

2 participants