[wp-meta] [Making WordPress.org] #4758: Adjust function signature of WPorg_Handbook_Walker::walk()

Making WordPress.org noreply at wordpress.org
Tue Oct 8 08:32:43 UTC 2019


#4758: Adjust function signature of WPorg_Handbook_Walker::walk()
-----------------------+---------------------
 Reporter:  jrf        |       Owner:  (none)
     Type:  defect     |      Status:  new
 Priority:  high       |   Milestone:
Component:  Handbooks  |  Resolution:
 Keywords:  has-patch  |
-----------------------+---------------------

Comment (by Otto42):

 You're kind of missing the point here, I feel.

 Yes, a change to core will break org, and thus we correct org afterwards
 to correct the problem. This happens whenever you break backward
 compatibility.

 But that works either way. If we change the code on .org before changing
 core, then we get the same problems and warnings. You don't solve a
 compatibility break by changing it in one place over another. Both changes
 need to happen simultaneously.


 > May I suggest educating yourself by reading the original ticket ?

 May I suggest that you simply explain the issue in detail here in this
 ticket, instead of pointing to a 3 month old ticket with 70+ comments and
 50+ patch attachments?

 Because I'm not going to make this change without some explanations. If
 this means core is blocked, then core will stay blocked.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4758#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list