[wp-trac] [WordPress Trac] #43495: Use Semantic Versioning for releases

[WordPress Trac]

#43495: Use Semantic Versioning for releases
-----------------------------+--------------------------------------
 Reporter:  netweb           |      Owner:
     Type:  enhancement      |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  Upgrade/Install  |    Version:
 Severity:  normal           |   Keywords:  2nd-opinion dev-feedback
  Focuses:                   |
-----------------------------+--------------------------------------
 Via todays #core dev-chat:
 https://wordpress.slack.com/archives/C02RQBWTW/p1520470243000286


 > [https://profiles.wordpress.org/dd32 Dion] wrote:
 >
 > ''4.10 instead of a 5.0 isn’t likely to work very well, other than the
 fact that it moves us from using decimal versioning to semantic
 versioning, I feel we might have some locations where we expect a branch
 is 3 digits, but that might not be the case. If it’s simply to avoid the
 `5` number because we’ve suddenly decided the first digit is actually
 special, then maybe it’s time to set a plan in place to adopt semantic
 versioning over the next few releases.''

 Background context: The question was posed, can a release numbered
 `4.10.0` be released as a ''major'' version instead of a ''minor'' version

 What is Semantic Versioning?: ''Semantic Versioning is a formal convention
 for specifying compatibility using a three-part version number: ''major''
 version; ''minor'' version; and ''patch''.''  https://semver.org/

--
Ticket URL: <https://core.trac.wordpress.org/ticket/43495>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform