[wp-trac] [WordPress Trac] #26767: Use semantic versioning in tags when exporting to Github

[WordPress Trac]

#26767: Use semantic versioning in tags when exporting to Github
-----------------------------+-----------------------------
 Reporter:  nessthehero      |      Owner:
     Type:  feature request  |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  General          |    Version:  trunk
 Severity:  normal           |   Keywords:
-----------------------------+-----------------------------
 When the SVN repo is exported to Github, some of the tags do not fall
 under semantic versioning guidelines, e.g. A.B.C where A is the major
 revision, B is the minor revision, and C is the patch version.

 For example, the latest tag on Github as of the creation of this ticket is
 "3.8".

 This seems a petty request, but package management console applications,
 such as Bower, seem to ignore Github tags that don't follow this
 convention, and it is impossible to upgrade via a simple command, such as
 "bower update". Doing a fresh "bower install Wordpress/Wordpress" will
 install the latest version of 3.7.x, and will continue to do so until a
 new tag, such as 3.8.1, is added to the repo. It is a convenience to be
 able to upgrade my local copy of wordpress and quickly use it in my Grunt
 based workflow.

 It would be great if this could be changed.

 Thanks.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/26767>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress blogging software