Skip to content

Release PHPCompatibility 9.3.5#954

Merged
jrfnl merged 38 commits intomasterfrom
develop
Dec 27, 2019
Merged

Release PHPCompatibility 9.3.5#954
jrfnl merged 38 commits intomasterfrom
develop

Conversation

@jrfnl
Copy link
Copy Markdown
Member

@jrfnl jrfnl commented Dec 26, 2019

⚠️ DO NOT MERGE (YET) ⚠️

PR for tracking changes for the 9.3.5 release. Target release date: Friday December 27.

  • Add changelog for 9.3.5 - PR Changelog for PHPCompatibility 9.3.5 #953
  • Merge this PR
  • Add release tag against master (careful, GH defaults to develop!) & copy & paste the changelog to it
  • Close the 9.3.5 milestone
  • Open a new milestone for the next release
  • If any open PRs which were milestoned for 9.3.5 do not make it into the release, update their milestone. (not applicable)
  • Tweet about the release.
  • Post about it in Slack. (WordPress #tide channel and any others people deem relevant)
  • Open PR to merge master into develop to get rid of the This branch is out-of-date with the base branch messages on each release. (only after major releases)

jrfnl and others added 30 commits November 20, 2019 22:28
Most error messages in PHPCompatibility follow one of the below formats:
* "Feature x is not supported in PHP x.x and below" (new features)
* "Feature x was deprecated in PHP x.x and removed in PHP x.x" (removed features)

The error message for short array syntax did not follow that typical pattern and was confusing to some - I've recently had questions about it from a few different people -, so I'm proposing to adjust the error message to be more in line with other messages in the PHPCompatibility library.
…prove-error-msg

NewShortArray: improve error message
As [PHP 7.4 has been released](https://www.php.net/archive/2019.php#2019-11-28-1), the build against PHP 7.4 should no longer be allowed to fail.

Includes some tweaking of the matrix to have the coverage stage and the quick test stage include PHP 7.4.
…ot-allowed-to-fail

Travis: don't allow PHP 7.4 build to fail
…ainst-7.4

Travis: test against PHP 7.4, not snapshot
* Improve short descriptions.
* Where relevant, add long descriptions with more details about the PHP change and how the sniff handles it.
* Add _PHP version x.x_ annotations.
* Add `@link` tags to the relevant PHP documentation which led to the sniff.

And make sure these are in a consistent order as per above.
The base URL for the php.net manual site has changed.
... for non-class based files.
…blocks

Includes annotating significant changes to methods/properties.

Based on trace-back through the file history.

Note: this is only done for the sniff related files and for method in abstract classes, not for the sniff test files which are not user-facing.
The two new PHP 7.4 classes had inadvertently been added to the `$newExceptions` array, while they should have been added to the `$newClasses` aray.
Don't use double quotes when they're not needed.
…ass-descriptions

Documentation: improve sniff class descriptions
…st-class-descriptions

Documentation: simplify & sync the sniff test class descriptions
…ility-test-class-descriptions

Documentation: improve the utility test class descriptions
…pdate-ref-url

NewInterfaces: update reference URLs
…ocks-since-tags

Documentation: add @SInCE tags to file docblocks
…ocblocks-add-since-tags

Documentation: add `@since` tags to method, property and constant docblocks
…incorrectly-placed-classes

NewClasses: minor bug fix - move two classes
For the use of `@internal` tags with comments for dev internal information, it used to be recommended to use `{@internal ... }}` (not the double curlies at the end) format to help IDEs parse these correctly.

This format has since been superseded as the parsing of docblocks in IDEs has improved a lot since then.

The current recommendation is to just use a single curly at the end.

Ref: https://github.com/php-fig/fig-standards/blob/master/proposed/phpdoc-tags.md#55-internal
jrfnl and others added 7 commits December 22, 2019 04:11
... for the purposes of line end detection.
…on-detection

PHP 7.4: Add detection of features from the new FFI extension detection
…e-internal-tag

Documentation: improve use of `@internal` tags
…butes

.gitattributes: treat the test case files same as PHP files
Includes all merged & currently open PRs. Release date tentatively set at Friday December 27.
@jrfnl jrfnl added Type: meta Repo strategy/structure related PR: ready for review labels Dec 26, 2019
@jrfnl jrfnl added this to the 9.3.5 milestone Dec 26, 2019
@jrfnl jrfnl merged commit 9fb3244 into master Dec 27, 2019
@jrfnl
Copy link
Copy Markdown
Member Author

jrfnl commented Dec 27, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Type: meta Repo strategy/structure related

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants