[wp-trac] [WordPress Trac] #23357: PSR compatibility

WordPress Trac noreply at wordpress.org
Fri Feb 1 15:10:41 UTC 2019


#23357: PSR compatibility
-------------------------+-------------------------
 Reporter:  fale         |       Owner:  (none)
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  General      |     Version:
 Severity:  normal       |  Resolution:  maybelater
 Keywords:               |     Focuses:
-------------------------+-------------------------
Changes (by desrosj):

 * keywords:  close =>
 * status:  reopened => closed
 * resolution:   => maybelater


Comment:

 >Some changes would significantly alter the shape of WordPress's codebase,
 and that's not something we care to do. Not just that, but many of these
 changes — including something as simple as StudlyCaps and camelCase —
 would be a backwards compatibility nightmare. **We do not break
 userspace.**

 I think that this sentiment still applies here. WordPress still supports
 PHP 5.2 (At least until April 2019), and will not raise the minimum
 version to 7.0 until ''at least'' December 2019
 ([https://make.wordpress.org/core/2018/12/08/updating-the-minimum-php-
 version/ more information on that plan])

 The main concern, though, is the massive backwards compatibility breaks
 that would be caused. WordPress is still committed to backwards
 compatibility as much as possible.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/23357#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list