Skip to content

Release version 9.3.1#902

Merged
jrfnl merged 20 commits intomasterfrom
develop
Sep 5, 2019
Merged

Release version 9.3.1#902
jrfnl merged 20 commits intomasterfrom
develop

Conversation

@jrfnl
Copy link
Copy Markdown
Member

@jrfnl jrfnl commented Sep 5, 2019

PR for tracking changes for the 9.3.1 release. Target release date: Friday September 6.

  • Add changelog for 9.3.1 - PR Changelog for PHPCompatibility 9.3.1 #901
  • Merge this PR
  • Add release tag against master (careful, GH defaults to develop!) & copy & paste the changelog to it
  • Close the 9.3.1 milestone
  • Open a new milestone for the next release
  • If any open PRs which were milestoned for 9.3.1 do not make it into the release, update their milestone. (not applicable)
  • Tweet about the release.
  • Post about it in Slack.
  • 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 20 commits August 31, 2019 03:37
As `develop` is now the default branch, the conditions based on which the various build stages are being triggered need to be updated, otherwise, builds will only run the `sniff` stage for pull requests against `develop`.
... picked up along the way.
This changes all file docblocks to align with the proposal made in issue 734.

Any pertinent information which was in the file docblock and wasn't already mentioned elsewhere has been moved to the class docblock.
Note: only the docblocks for user-facing code contain `@since` tags.
…tation-fixes

Various minor documentation fixes
…g-exception-throws-tags

Documentation: add missing @throws tags
…ect-return-type

Documentation: fix incorrect @return type
…erty-var-types

Documentation: fix incorrect property @var tag types
…ocblocks

Documentation: fix up all file docblocks
…g-const-docblocks

Documentation: add docblocks to class constants
Bugs:
1. "Empty" tokens (whitespace, comments) were not disregarded when determining whether the first parameter was only a text string, which could lead to the second parameter being examined when it doesn't need to be.
2. If either parameter contained a ternary, potentially nested in some other construct, the ternary would confuse the sniff.

Both fixed now.

In addition to this if one of the parameters contains an `(array)` cast, let's presume that's the array parameter. This may lead to some false positives for complexly build parameters, but we'll deal with that later if needs be.

Includes unit tests.

Fixes 890
…er-bug

RemovedImplodeFlexibleParamOrder: fix two bugs + one enhancement
…r-develop-branch

Travis: update stage conditions
@jrfnl jrfnl added Type: meta Repo strategy/structure related PR: ready for review labels Sep 5, 2019
@jrfnl jrfnl added this to the 9.x Next milestone Sep 5, 2019
@jrfnl jrfnl requested a review from wimg September 5, 2019 18:03
@jrfnl jrfnl merged commit 9999344 into master Sep 5, 2019
@jrfnl
Copy link
Copy Markdown
Member Author

jrfnl commented Sep 5, 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.

2 participants