Maybe this could be a new topic, but I was wondering about the possibility of a “negative diff” kind of approach to keep ClassicPress up to date with WordPress updates…
That is, instead of a hard fork and having to review and add in every new change from WordPress, why not keep track of the differences that ClassicPress makes (which GitHub can do automatically anyway.)
So that when a new WordPress version comes out, any ClassicPress differences could be re-applied, and there could be some flag for those that don’t auto-apply (because the base WP code to be diffed has changed in the WP update.) I think given the size of the codebase, there would probably be fewer collisions that way, and it would be easier to keep track of the specifically chosen ClassicPress updates than all the WP ones.
I know there are pros and cons to each approach, but since ClassicPress is a fork of WordPress, to my mind it would make more sense to re-apply the changes on top of that base, rather than using ClassicPress as the base and trying to reinsert selectively from each new WordPress core version.
I hope that is clear enough, I’m not quite familiar with what the current process actually is, but this comes from thoughts of how I’d do such a fork. Mostly it just seems like a massive time burden to have to keep reviewing so many new tickets to keep up with changes, and something that will get harder over time and cause incompatibilities as things diverge… but it could be nipped in the bud with this alternative approach.