-
Notifications
You must be signed in to change notification settings - Fork 26
Versioning #10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I think altered/removed SHOULDs needs to be moved to Minor becuase it is still optional requirement and, thus, original code will be compatible. |
I've updated the list to make added
Removing or altering SHOULDs can have the effect of breaking compatibility. Imagine removing this:
Removing this or altering it in a substantial way would rise to a major change in my mind. That said, I mentioned that there are times when SHOULDs can be altered or removed in a way that doesn't effect compatibility and in those cases (and in all cases really) we will use this post as a starting point and determine which release level is appropriate at the time of release. |
Removing |
Uh oh!
There was an error while loading. Please reload this page.
I wanted to clearly define what "major" "minor" and "patch" mean in the context of this PER and how we will handle versioning for v1.0.0 and after. This is an important thing to nail down because we only need core committee approval for major versions.
To make this easier to follow, let's split the available requirement keywords into two groups:
MUST
,REQUIRED
orSHALL
SHOULD
,RECOMMEND
,MAY
, orOPTIONAL
MUST
s for already covered syntax and altered/removedSHOULD
sSHOULD
s and addedMUST
s for new syntaxThere are times when
SHOULD
s can be modified or even removed in backwards compatible ways and in those cases we may opt for a minor release rather than a major release, erring on the side of a major release (and therefore a core committee vote) whenever appropriate. This is all up for discussion so if folks have any disagreements please add comments here.With all of that said version 1.0.0 will be effectively a "patch" change from PSR-12, all changes are done to align names and descriptions with this PER and no requirements have been altered/added/removed.
The text was updated successfully, but these errors were encountered: