Closed emteknetnz closed 1 month ago
CMS 5 PR merged. Reassigning to Steve for CMS 6 PR prep
I do note "Ensure any deprecation warnings in PHPUnit 9 have been resolved" has been ticked though it seems not enough CMS 5 PRs to actually achieve that?
Changes required or questions asked in
Some PRs also need a rebase.
PRs merged. I still don't think "Ensure any deprecation warnings in PHPUnit 9 have been resolved" is done? Reassigning to Steve to check that.
New PRs merged.
Reassigning to Steve because "Ensure any deprecation warnings in PHPUnit 9 have been resolved" still doesn't seem to have been done. The branches that are still running PHPUnit 9 still seem to have deprecation warnings.
The AC of fixing phpunit 9 warnings meant fix it for CMS 6, not for CMS 5. I should have spelt that out clearer in the initial ACs.
Projects aren't going to be running our unit-tests so it does matters at all if we have a bunch of warnings about phpunit 10 in our CMS 5 builds, we've had them for probably well over a year at this point. If they still both you feel free to open a new card and link to the framework PR (I think) which has the custom error handler stuff which we'd need to backport to CMS 5 to resolve. Another option is just turn off phpunit deprecation warnings for CMS 5 builds because at this point they're irrelevant since we've just done the upgrade work in the CMS 6 branches.
Acceptance criteria
Expecting E_DEPRECATED and E_USER_DEPRECATED is deprecated and will no longer be possible in PHPUnit 10.
Notes
CMS 5 PRs
Recipe sink CI CMS 6
CMS 6 PRs (ensure CMS 5 PRs are merged, merged-up and rebased on before merging these)
Follow up PRs