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

[WordPress Trac]

#43495: Use Semantic Versioning for releases
-----------------------------+----------------------
 Reporter:  netweb           |       Owner:  (none)
     Type:  enhancement      |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Upgrade/Install  |     Version:
 Severity:  normal           |  Resolution:  wontfix
 Keywords:                   |     Focuses:
-----------------------------+----------------------

Comment (by eclev91):

 Replying to [comment:12 jorbin]:
 > There are breaking changes every release, only they are generally minor
 and planned out in such a way that the impact is low.

 That feels like the whole problem, and one reason I'm frequently
 interacting with people who are afraid to hit the update button on their
 site, let alone enable automatic updates of any sort. I'll refer back to
 my last comment:

 > SemVer, and an auto-update system that was cognizant of it, would
 encourage core to collect these changes under the banner of a major (as
 defined by SemVer) release

 And finally, again:

 > What's standing in the way of adopting SemVer? Sounds like some changes
 to core update logic and a consensus?

 Is this just something I should be bringing to #core from time to time to
 get eyes on? Would happily help in contributing to changes in core's
 update logic where needed.

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