Current status of ClassicPress v1
It has taken us longer than we originally planned to get the final, official ClassicPress
1.0.0 version released, but we’re making steady progress. I’m providing a quick update from the core development team so that everyone remains aware of the current status of the project.
Right now, ClassicPress is in stable beta status and it is safe to use it on your sites. We started our fork from the WordPress 4.9 branch, and we have not and will not be making any changes to the platform’s core functionality in the version 1 release series. (You can find more information about our medium- to long-term plans for the platform on our roadmap page.)
What’s still left to do for v1
We’ll release the final version
1.0.0 when we’ve replaced or removed all WordPress-specific functionality from the ClassicPress dashboard and addressed all known bugs. Roughly, there are a few categories of changes we’re still looking to complete in the next few weeks:
- Finish porting changes from WordPress for PHP 7.3 compatibility.
- Remove most links to WordPress.org and features that use WordPress.org accounts.
- Fix any known bugs that are new to ClassicPress.
- Miscellaneous other “polish” such as better organization for new files and improving the experience around ClassicPress default themes.
For an up-to-date list of specific tasks remaining for the release, see the v1.0.0-rc1 milestone on GitHub. If you see a task there that you can help us with, please jump in!
After these tasks are completed, the v1.0.0 release will come in two stages. First, version
1.0.0-rc1 (release candidate 1) will be made available for testing for about a week. Then, if there are no new issues, we’ll release ClassicPress
1.0.0 with essentially the same code.
Updated launch dates
We are currently targeting Wednesday, February 20, 2019 for the
1.0.0-rc1 release, and Tuesday, February 26, 2019 for the
These dates are a current best estimate, and they are subject to change if absolutely necessary.
If you’d like to help push ClassicPress over the finish line, please take a look at the task list on GitHub. Feel free to ask questions there on the individual issues, in the core development forum, or in Slack.
What else is going on
We all knew when we got involved with ClassicPress that successfully forking WordPress would be a huge amount of work. That is still very clear (perhaps even more clear) after many valuable contributions from ClassicPress leadership and community members, not just in core development but also in many other areas.
To point out just a few: marketing, design, internationalization, technical infrastructure, organizational structure, ClassicPress-first plugins, keeping our community running smoothly including an active support forum, and many other activities that are helping to make ClassicPress the best CMS platform for business and professional-quality websites everywhere.