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

Support charm versioning #898

Open
anastasiamac opened this issue Feb 26, 2020 · 2 comments
Open

Support charm versioning #898

anastasiamac opened this issue Feb 26, 2020 · 2 comments

Comments

@anastasiamac
Copy link

As per https://bugs.launchpad.net/juju-charmstore/+bug/1864903

@vernhart
Copy link

To save folks a click, here's the text of that bug:

Currently the charmstore only supports a revision for charms. This can make it difficult to know if a newly available charm is just a patch level update, a minor change, or a major revision.

If charms supported specifying a version, similar to snaps, then the charm developers could supply a version. The revision could increment exactly as before but we'd also have a version that can assist in making upgrade decisions.

I would expect the version would be optional for backwards compatibility. We could recommend the use of semantic versioning in the charm developer docs but, again, it wouldn't be a hard requirement.

@mitechie
Copy link
Contributor

The charms are looking to migrate to a snap store setup which would allow for full track management in the future. When you say "versions" I assume you mean the tracks that can be setup for major versioning?

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

No branches or pull requests

4 participants