Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions release-process.rst
Original file line number Diff line number Diff line change
Expand Up @@ -86,6 +86,12 @@ The following are **not considered** BC breaks:
choosing new names, but SHOULD NOT pick significantly worse names purely to
reduce conflict risk.

- Adding TypeError and ValueError exceptions to validate inputs to functions
and methods. These are not classified as BC breaks because not adding them
allows incorrect code to run and thus leads to hard to debug code.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add hyphens to turn the adjective phrase into a compound word, increasing readability.

Suggested change
allows incorrect code to run and thus leads to hard to debug code.
allows incorrect code to run and thus leads to hard-to-debug code.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are not classified as BC breaks because not adding them allows incorrect code to run and thus leads to hard to debug code.

IMO this wording is not great. Maybe:

Missing validation for undocumented or clearly unintended argument values are considered PHP core bugs with unpredictable or incorrect behavior. As such, adding the desired validation is not considered BC breaking.


- Changing the wording of diagnostic, error, or exception messages.

- Behavior changes in undefined or undocumented edge cases MAY be allowed if
well justified. However, care SHOULD be taken to minimize disruption.

Expand Down