Is there anything you would REMOVE at all from ClassicPress?

[alvarofranz]

@anon66243189

In v2 do what you feel like.

This is contradictory to this:

@ElisabettaCarrara

compatibility CP [1] with CP [2]
That is meant to ensure that if I am on V1 and wanting to upgrade to V2 my site won’t get bonkers when I hit upgrade.

But yeah, that second statement doesn’t make much sense anyway because if CP 1 is compatible with CP 2, then CP 2 limits = CP 1 limits. Or am I wrong?

So, I’ll start working on the 3 mentioned topics. But I wonder if the ClassicPress-research/ClassicPress-next should stay as a fork from ClassicPress/ClassicPress or if it should indeed become a standalone repo, so that it doesn’t constantly say “this repo is x commits behind”. Some people may want to keep on with CP 1.x (an that’s fair), but eventually both versions will be independent. Any benefits for having the fork relationship?