search

dkydheeraj / gtm-oauth2

Automatically exported from code.google.com/p/gtm-oauth2
0 stars 0 forks source link

Please add semantic version tags #12

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
I’ve recently updated gtm-oauth2 to the CocoaPods package manager repo.

CocoaPods is a tool for managing dependencies for OS X and iOS Xcode projects 
and provides a central repository for iOS/OS X libraries. This makes adding 
libraries to a project and updating them extremely easy and it will help users 
to resolve dependencies of the libraries they use.

However, gtm-oauth2 doesn't have any version tags. I’ve added the current 
HEAD as version 0.0.1, but a version tag will make dependency resolution much 
easier.

Semantic version tags (instead of plain commit hashes/revisions) allow for 
resolution of cross-dependencies.

In case you didn’t know this yet; you can tag the current HEAD as, for 
instance, version 1.0.0, like so:

$ git tag -a 1.0.0 -m "Tag release 1.0.0"
$ git push --tags

Original issue reported on code.google.com by r...@archyapp.com on 22 Mar 2013 at 12:38

GoogleCodeExporter commented 9 years ago 
Current version is revision 110. What's wrong with using that number in 
CocoaPods?

Original comment by julien.c...@gmail.com on 20 Apr 2013 at 3:49

GoogleCodeExporter commented 9 years ago 
(also gtm-oauth2 doesn't use git, but svn)

Original comment by julien.c...@gmail.com on 20 Apr 2013 at 3:51

GoogleCodeExporter commented 9 years ago 
Currently, the revision used for podspec is 107. You can update it because I 
think that would be fine in 110.

https://github.com/CocoaPods/Specs/blob/master/gtm-oauth2/0.0.1/gtm-oauth2.podsp
ec

Original comment by r...@archyapp.com on 22 Apr 2013 at 8:37

GoogleCodeExporter commented 9 years ago 
The problem with revision numbers is that they don't provide any information 
about the changes being made. For example, are there any deprecations or 
backward incompatible changes being introduced with a particular revision? 
Semantic versioning aims to solve that problem.

See: http://semver.org/ for a full explanation.

Frankly, I'm surprised that Google isn't doing this already. It is such a 
brilliant concept.

btw, these can be implemented as tags in subversion like so:

svn copy http://gtm-oauth2.googlecode.com/svn/trunk/ 
http://gtm-oauth2.googlecode.com/svn/tags/1.0.0 -m "Tag release 1.0.0"

Original comment by j.a.grig...@gmail.com on 13 Mar 2014 at 6:08