ClassicPress releases V1/V2 Roadmap

Roadmap

ClassicPress has released their roadmap for both V1.x.x and V2.x.x explaining what features they intend to add or remove.

1.x.x will remain compatible with WP 4.9.x and 2.x.x will venture into new territory, beginning to move away from simply being a WordPress clone.

Version 1
“It’s extremely important to note that version 1.x.x of ClassicPress will be fully backwards compatible with WordPress 4.9.x. We won’t introduce any changes or features that would cause plugins or themes to break.

WordPress 4.9.x itself will be maintained for the next few years and plugin/theme authors will need to remain compatible with this version. As such we can confidently say that the vast majority of plugins and themes will continue to work with ClassicPress for many years to come.”

“The first [stable] version of ClassicPress will be a long-term support (LTS) version. If you choose to, you can stay on this version for years to come. We won’t introduce any changes that could break compatibility with themes or plugins that support WordPress 4.9.x.”

The release of 1.0.0 stable should happen very early in 2019.

Version 2
“Version 2 may start to introduce changes that break compatibility with plugins and themes that only support WordPress 4.9.x. However, we expect incompatibilities to be limited to uncommon edge cases, and we will do our best to maintain compatibility. We will only make breaking changes when it is absolutely necessary, and we will communicate them clearly during the upgrade process.

The upgrade from v1 to v2 will be opt-in, and we already have commitments from major plugin developers to support ClassicPress v2.”

“We’ll launch an independent plugin directory for ClassicPress that will rethink and modernise plugin discovery, updates and promotion. An equal footing will be available for all plugin authors to reach the ClassicPress audience that might be interested in their solutions.”

“In our quest for creating a CMS that is streamlined, fast and secure we will introduce the concept of core plugins. These plugins will move “core” features into plugins that are turned on by default. Developers [and you] can then selectively disable and delete these plugins based on the needs of their customers. Some example core plugins could include:

  • XML-RPC
  • Gravatars
  • REST API
  • Emojis

“WordPress has been burdened with the need to maintain compatibility with PHP versions below 7.x. This has led, through no fault of their own, to poor quality and bloated code. We will take a measured approach to introducing PHP 7.”

The release of 2.0.0 stable should happen in the latter half of 2019.

What does this all mean?
For people who want a stable version of CP that works like WP 4.9 does now, you can stay on V1 indefinitely and it will receive any necessary security updates.

For those who want to follow CP as it evolves into an entirely different beast to WordPress, you can upgrade to V2 and any future versions, such as V3, V4, etc.

There are a lot of unknowns that will need to be addressed in 2.x.x and the CP team will address them as needed before releasing any point upgrades.

Leave a Reply

Your email address will not be published. Required fields are marked *