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

How to versionize a fork? (including the original version number) #278

Closed
rugk opened this Issue Nov 3, 2015 · 3 comments

Comments

Projects
None yet
3 participants
@rugk
Copy link

rugk commented Nov 3, 2015

Abstracting rugk/threema-msgapi-sdk-php#3...

We have:

  • a original version, which will be developed and versions of it will be released
  • a "community edition" of this version, which is based on the original version, but additional features or changes may be included
  • a situation where the community version will still be updated with new official version releases by integrating them into the CE version.

That's why it would be good to have both version numbers - the "official one" and the "forked one" together in one version number so you can see them both at a glance.
However I do not know whether that's possible.

If so what do you think would be the best way to do this? Some thoughts/ideas of me and a contributor you can find in the issue linked above.

@FichteFoll

This comment has been minimized.

Copy link

FichteFoll commented Nov 3, 2015

This is a long-standing discussion. See #264, #265 (probably more).

@rugk

This comment has been minimized.

Copy link
Author

rugk commented Nov 3, 2015

Okay, the only difference I see is that the other issues work with channels. We of course also have different channels, but the version number of both should be included in the new whole version number.
E.g. 1.1.2@CE.0.1 instead of just 1.1.2@CE.

@jwdonahue

This comment has been minimized.

Copy link
Contributor

jwdonahue commented Dec 9, 2017

@rugk, you can use a build meta tag to encode the other version. No need for a new kind of field in the SemVer spec. Unless you have further questions or intend to issue a PR linked to this issue, please close it at your earliest possible convenience.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.