[wp-meta] [Making WordPress.org] #4009: Manage supported/recommended PHP versions in a central location
Making WordPress.org
noreply at wordpress.org
Wed Dec 19 03:29:17 UTC 2018
#4009: Manage supported/recommended PHP versions in a central location
-------------------------------------------------+-------------------------
Reporter: flixos90 | Owner: flixos90
Type: enhancement | Status: assigned
Priority: normal | Milestone:
Component: General | Resolution:
Keywords: 2nd-opinion servehappy has-patch |
dev-feedback |
-------------------------------------------------+-------------------------
Comment (by dd32):
Yeah, let's not do that.
We can instead make the raw data which `serve-happy` uses available
elsewhere on dotorg through either a global function or constants, similar
to `WP_CORE_LATEST_RELEASE` or `wporg_get_versions()` which you may have
run across in some templates.
It'll probably mean removing the constants from
https://meta.trac.wordpress.org/browser/sites/trunk/api.wordpress.org/public_html/core
/serve-happy/1.0/config.php and instead replacing it with something like
the following:
{{{
function wporg_get_recommended_php_version() {
return [
// The latest branch of PHP which WordPress.org
recommends.
'recommended' => '7.2',
// The lowest branch of PHP which is actively supported.
'supported' => '7.0',
// The lowest branch of PHP which is receiving security
updates.
'secure' => '5.6',
// The lowest branch of PHP which is still considered
acceptable in WordPress.
'acceptable' => '5.3'
];
}
}}}
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/4009#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list