so i am responisble for a very large wordpress installation (600.000 posts and growing).
we are using our own block-based-editor (for quiet some time) - and won’t be switching to gutenberg.
having the following questions:
we are not able to use the migration plugin (docker based workflow)
we would clone the ClassiPress-release instead of the the traditional wordpress
Hey @hjanuschka, I think @james will be able to better answer some of these questions but I can answer a few
We are using the Semantic Versioning so everything on from 1.0 to 1.9 will be backwards compatible. Version 2 will likely have breaking changes, we will be using the petitions site to guide us on what features we add and what features get moved out of the core and into a core plugin.
No, as we maintain completely compatibility with all plugins that support 4.9.x.
Technically, yes you could by overwriting the ClassicPress files with the WordPress files. We have had discussions regarding adding the ability to migrate back to WP within the migration plugin.
Yes - in your case you would update the Docker image again to undo the changes and contain WordPress instead of ClassicPress.
is there a official list, of removed/added/changed filters?
As Wade says, we are preserving full compatibility with WordPress 4.9.x, so no internal APIs have been removed or changed. We’ve added a few functions like classicpress_version() - you can use function_exists( 'classicpress_version' ) to determine if you are running under ClassicPress.
2.0 will bring breaking changes, i read, is there any roadmap?
Our tentative plan for v2 is to begin splitting out older / deprecated features like XML-RPC into separate core plugins. We will preserve backwards compatibility as much as we can, and we will indicate any breaking changes clearly at the time of the upgrade. You’ll also be able to continue using the 1.x release series if you need to.
