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

Package Manager Versioning #14

Closed
wldcordeiro opened this issue Sep 11, 2014 · 4 comments
Closed

Package Manager Versioning #14

wldcordeiro opened this issue Sep 11, 2014 · 4 comments

Comments

@wldcordeiro
Copy link
Contributor

Currently you have one branch, master and this doesn't work best if you want to have version numbers. According to the documentation, these are the two recommended methods.

If you are using GitHub or BitBucket for your hosting, you will need to choose one of the following versioning strategies:

RECOMMENDED: Use git/hg tags with each tag being a semantic version number. This allows features like install_prereleases and messaging to work properly.

Use a branch of the repository, e.g. master or default. For this versioning scheme, every commit is a new release and the version number is formulated from the latest commit date. To properly use this, the branch used by you for development should be different than the release branch.

Please note that once you use any semantic version numbers either via tags or manual releases, it will not be possible to go back to commit-based versioning. This is because all commit-based versions are prefixed with a 0. when doing comparisons to allow for an upgrade path to explicit versioning.

It may be best to update to using tags considering you have messages for version 1, 1.1 and 1.2.

@ctf0
Copy link
Owner

ctf0 commented Sep 12, 2014

am new into all of this ,can u make a PR about that ?

@wldcordeiro
Copy link
Contributor Author

Yeah I made a PR, it wouldn't let me send through the full tag but I added an explanation of the command you need to run it. #17

@wldcordeiro
Copy link
Contributor Author

It seems like my tags aren't getting merged with my PR. So here's what I had to do to get the tags made.

git checkout a5b6cb4b62bd58d4a4fe11c0e2fc550a104f1df8
git tag -a v1.0 -m "Release Version 1.0"
git push origin v1.0
git checkout 96ae3474b0d4c867d6498c348f744b609e134b39
git tag -a v1.1 -m "Release Version 1.1"
git push origin v1.1
git checkout a296b73e66a31a7c9ab39a464af15f6b46eeca8c
git tag -a v1.2 -m "Release Version 1.2"
git push origin v1.2
git checkout 3dafa26f0143e142836ce24b90c00944d7dd2c88
git tag -a v1.3 -m "Release Version 1.3"
git push origin v1.3

That should create the tags on your project with the tags pointing to the proper commits the releases were made on. @ctf0

Then you can just

git checkout master

to go back to your branch.

@ctf0
Copy link
Owner

ctf0 commented Sep 12, 2014

heeeeeeeeeey ,finally working ,btw i tried the
git fetch remote-url "refs/tags/*:refs/tags/*" which fetched all the tags then used
git merge tags then git push but nothing changed ,anyway its added now ,thanx for ur help 👍

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