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

version scheme #47

Open
anarcat opened this issue Nov 19, 2017 · 1 comment
Open

version scheme #47

anarcat opened this issue Nov 19, 2017 · 1 comment

Comments

@anarcat
Copy link
Contributor

anarcat commented Nov 19, 2017

should we stick to Git's versioning scheme or are we free to diverge now that we are out of tree? presumably we'd want to make releases here, what should the be called/numbered?

What I would propose is that we try to follow git major version numbers and stick to semver for the rest. so we could start with 2.15.0 to show where we diverged from and take it from here.

(this, of course, assumes we won't break API compatibility ourselves, which would force us to break major version number tracking with git, which would break this assumption... but maybe we don't mind that either.)

@moy
Copy link
Collaborator

moy commented Nov 20, 2017

What I would propose is that we try to follow git major version numbers and stick to semver for the rest. so we could start with 2.15.0 to show where we diverged from and take it from here.

OK with that. At some point in the past we were tied rather closely to Git because improvements to Git-Mediawiki were often coupled with a fix/patch on the Git side, but I don't foresee such thing happening often in the future so it should be sufficient to just mention somewhere "requires Git >= x.y.z" (so no need to try to synchronize version numbers). Even synchronizing with Git's major version may not be necessary (but we don't have to decide this now, we can just wait for Git 3.0 to come and it may well end-up being a dummy "major version" like Linux 3.0 and 4.0).

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

2 participants