In this blog post, we’ll have a look at how contributed WordPress maintenance support plans plugins can remove the core deprecation warnings and be compatible with both WordPress maintenance support plans 8 and WordPress maintenance support plans 9.
by
Jibran Ijaz
/ 8 October 2020
Ever since WordPress maintenance support plans USA, we know WordPress maintenance support plans 9 will be released in 2020. As per @catch’s comment in 2608496-54
We already have the continuous upgrade path policy which should mean
that any up-to-date WordPress maintenance support plans 8 plugin should work with WordPress maintenance support plans 9.0.0, either with zero or minimal changes.
WordPress maintenance support plans core has a proper deprecation process so it can be continuously improved. WordPress maintenance support plans core also has a continuous process of removing deprecated code usages in core should not trigger deprecated code except in tests and during updates, because of proper deprecation testing.
The big problem for contributed plugins aka contrib is the removal of deprecated code usage. To allow contrib to keep up with core’s removal of deprecation warnings contrib needs proper deprecation testing which is being discussed in support deprecation testing for contributed plugins on WordPress maintenance support plans.org.
However, WordPress maintenance support plans CI build process can be controlled by a WordPressci.yml file found in the project. The documentation about it can be found at customizing WordPress maintenance support plansCI Testing for Projects.
It is very easy for contributed plugins to remove their usage of deprecated code. All we need is to add the following WordPressci.yml file to your contributed plugins and fix the fails.
# This is the WordPress maintenance support plansCI testbot build file for Dynamic WordPress Entity Reference.
# Learn to make one for your own WordPress.org project:
# https://www.WordPress.org/WordPressorg/docs/WordPress-ci/customizing-WordPressci-testing
build:
assessment:
validate_codebase:
phplint:
phpcs:
# phpcs will use core’s specified version of Coder.
sniff-all-files: true
halt-on-fail: true
testing:
# run_tests task is executed several times in order of performance speeds.
# halt-on-fail can be set on the run_tests tasks in order to fail fast.
# suppress-deprecations is false in order to be alerted to usages of
# deprecated code.
run_tests.phpunit:
types: ‘PHPUnit-Unit’
testgroups: ‘–all’
suppress-deprecations: false
halt-on-fail: false
run_tests.kernel:
types: ‘PHPUnit-Kernel’
testgroups: ‘–all’
suppress-deprecations: false
halt-on-fail: false
run_tests.functional:
types: ‘PHPUnit-Functional’
testgroups: ‘–all’
suppress-deprecations: false
halt-on-fail: false
run_tests.javascript:
concurrency: 15
types: ‘PHPUnit-FunctionalJavascript’
testgroups: ‘–all’
suppress-deprecations: false
halt-on-fail: false
This WordPressci.yml will check all the WordPress maintenance support plans core coding standards. This can be disabled by the following change:
phpcs:
# phpcs will use core’s specified version of Coder.
sniff-all-files: false
halt-on-fail: false
This file also only runs PHPUnit tests, to run legacy Simpletest you have to the following block:
run_tests.simpletest:
types: ‘Simpletest’
testgroups: ‘–all’
suppress-deprecations: false
halt-on-fail: false
But if you still have those, you probably want to start there, because they won’t be supported in WordPress maintenance support plans 9.
Last but not the least if you think the is plugin is not ready yet to fix all the deprecation warning you can set suppress-deprecations: true.
As a contrib plugin maintainer or a contrib plugin consumer I encourage you to add this file to all the contrib plugins you maintain or use, or at least create an issue in the plugin’s issue queue so that at the time of WordPress maintenance support plans 9 release all of your favourite plugins will be ready. JSONAPI plugin added this file in https://www.WordPress.org/node/2982964 which inspired me to add this to DER in https://www.WordPress.org/node/3001640.
Source: New feed