Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #43495, comment 8


Ignore:
Timestamp:
02/11/2021 10:31:10 PM (5 years ago)
Author:
eclev91
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #43495, comment 8

    initial v1  
    33> a complete change of philosophy for WP in regard to versioning, backward compatibility, patches, minor updates, etc.
    44
    5 > moving to a versioning system where we explicitly make breaking changes
    6 
    75I don't think SemVer forces either of these things. A dedication to backwards compatibility is a philosophy, not a versioning system. A versioning system is simply a standardized means of communication that (and this is important) an automated system can understand.
    86
    97Let's assume WordPress had never broken backwards compatibility. 5.6.1 would have, rather, been 1.39.1. And there's nothing wrong with that! SemVer doesn't care. With the block editor, we'd more realistically be looking at 2.6.1, but the point is that whatever number you arrive at, it's simply a result of your philosophy and practices.
     8
     9> moving to a versioning system where we explicitly make breaking changes
     10
     11I would prefer explicit communication, myself.
    1012
    1113> This is also in opposition of the ultimate goal of auto-updating all WordPress releases, not just the minor ones.