[wp-meta] [Making WordPress.org] #3867: Refreshing Core Patches

[Making WordPress.org]

#3867: Refreshing Core Patches
-------------------------+---------------------
 Reporter:  pento        |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  Trac         |  Resolution:
 Keywords:               |
-------------------------+---------------------

Comment (by pento):

 [attachment:"patch-upgrader.php"] is an experiment in the viability of
 this approach. It should be run from a git checkout of WordPress, and
 expects a directory called "working" to exist in the same parent directory
 as the checkout, for it to store output.

 It’s currently fairly restrictive, it only processes tickets where the
 newest patch was last updated before the first big reformat (2017-12-01),
 and only tries applying them to `trunk` as it was just before the first
 big reformat.

 Running through them oldest to newest, in the first 500 tickets processed:

 - 425 of them had their newest patch uploaded before 2017-12-01.
 - The script was able to refresh patches for 52 of them.
 - With a quick visual inspection, 49 of them are correct, 2 have minor
 errors, 1 is clearly incorrect.

 Removing the restrictions will hopefully increase the number of patches
 that can be refreshed, though I don’t know what effect that will have on
 the accuracy: the more times we have to fast forward through version
 history, the more opportunity there is for mistakes to happen.

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