[wp-meta] [Making WordPress.org] #3474: Introduce `serve-happy` API endpoint

Making WordPress.org noreply at wordpress.org
Tue Feb 27 04:50:26 UTC 2018

#3474: Introduce `serve-happy` API endpoint
 Reporter:  flixos90                  |       Owner:  dd32
     Type:  task                      |      Status:  accepted
 Priority:  normal                    |   Milestone:
Component:  API                       |  Resolution:
 Keywords:  has-patch has-unit-tests  |

Comment (by flixos90):

 Per today's PHP meeting, we decided to go with the following approach for
 the API endpoint:

 * Only return the WordPress recommended PHP version as an actual number,
 in a `recommended_version` field.
 * Return the following boolean flags (based on the passed PHP version):
     * `is_supported`: Whether the PHP version is actively supported.
 Currently that means anything >= 7.0.
     * `is_secure`: Whether the PHP version receives security updates.
 Currently that means anything >= 5.6.
     * `is_acceptable`: Whether the PHP version is still acceptable by
 WordPress (meaning no notice needs to show in core). Currently that means
 anything >= 5.3.
 * The whole IP address-related functionality should be removed. It's
 unknown whether it will ever be needed and may also have privacy
 implications not worth thinking about at this point. Handling host-
 specific update URLs should rather be possible via core functionality.

 To summarize, every API response should only consist of the four fields
 explained above.

Ticket URL: <https://meta.trac.wordpress.org/ticket/3474#comment:10>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list