[wp-trac] [WordPress Trac] #64634: Build/Tools: Update PHPCompatibilityWP to 3.0.0-alpha2

[WordPress Trac]

#64634: Build/Tools: Update PHPCompatibilityWP to 3.0.0-alpha2
-------------------------------------+--------------------------------
 Reporter:  rodrigosprimo            |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  7.1
Component:  Build/Test Tools         |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  needs-patch 2nd-opinion  |     Focuses:  php-compatibility
-------------------------------------+--------------------------------
Changes (by desrosj):

 * keywords:   => needs-patch 2nd-opinion
 * milestone:  Awaiting Review => 7.1


Comment:

 @rodrigosprimo Thanks for opening this detailed report! I think that
 tackling these next steps will help support this update. I think this will
 help chunk through everything that needs to happen here.

 - Note on the open issues for item 1 that this ticket is blocked by
 resolving those (unless temporary `ignore` statements are added, which I
 would like to avoid wherever possible).
 - For item 4, please create a ticket for updating Requests to the latest
 version. Feel free to refer to this ticket and add context as to why
 updating is related.

 I have yet to perform a deep dive into any of these points, but I wanted
 to give some quick, surface-level feedback to help push this along.

 Given the surrounding circumstances and adoption of the `3.0.0alpha2`
 version, I am supportive of using this version once other outstanding
 issues are addressed. @johnbillion or @jorbin, do you have any objections
 to that?

 The rest of your suggestions seem reasonable at first glance. I do think
 that I prefer your suggestion of adding the package's dependencies to the
 `composer.json` file over changing `minimum-stability` to `dev` is
 preferred.

 Starting a pull request addressing the smaller ones here will also help to
 surface the violations being reported without having to run the scan.
 Items 2, 3, and 5 in the report description as well as 1 and 3 in your
 follow up is a great start. Then the PR can just be updated with the fixes
 merged to `trunk` through the other tickets.

 Adding `2nd-opinion` because it would be good to get thoughts from a few
 more contributors.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64634#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform