Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compatibility testing with WordPress 6.4 #383

Closed
6 tasks
vikrampm1 opened this issue Nov 7, 2023 · 0 comments · Fixed by #386
Closed
6 tasks

Compatibility testing with WordPress 6.4 #383

vikrampm1 opened this issue Nov 7, 2023 · 0 comments · Fixed by #386
Assignees
Labels
priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. type: task The issue is an internally driven task (e.g. from another A8c team).
Milestone

Comments

@vikrampm1
Copy link
Contributor

vikrampm1 commented Nov 7, 2023

With the WordPress 6.4 release, perform the following:

  • E2e tests run only on the latest WP version, so ensure the release is out before running the tests.
  • Open PR to bump WordPress "tested up to" to 6.4.
  • Bump WordPress minimum supported to 6.2.
  • Search codebase for conditionals on minimum version numbers no longer supported that could be removed.
  • Check to see if e2e tests pass, if so move the issue to UAT. If e2e tests fail, see if that's an issue with the test or compatibility with WP.
  • Check other files where the version needs to be bumped - For this the main thing to look for is the function version_compare and then see if we're checking WordPress versions there or something else (sometimes we check PHP versions for instance or Woo versions). Some plugins also define what WordPress version we support (sometimes as a minimum) in a constant (see Square as an example). There's not always consistent naming on those constants so really the easiest way to find these is to search the codebase for the version string. Search the last few releases to catch them all (so search for 6.3, 6.2, 6.1). Also, suggest looking at the last PR that bumped versions because to copy what was done for those.

Sample Changelog entry should then be:

Dev - Bump WordPress "tested up to" version 6.4.
Dev - Bump WordPress minimum supported version to 6.2.

@vikrampm1 vikrampm1 added priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. type: task The issue is an internally driven task (e.g. from another A8c team). labels Nov 7, 2023
@ankitguptaindia ankitguptaindia self-assigned this Nov 8, 2023
@vikrampm1 vikrampm1 added this to the Future Release milestone Nov 9, 2023
@vikrampm1 vikrampm1 modified the milestones: Future Release, 1.2.2 Nov 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. type: task The issue is an internally driven task (e.g. from another A8c team).
Projects
None yet
2 participants