As we near our first birthday as an organization, ClassicPress is finalizing work on version 1.1.0 to make sure it represents the stability and quality that our users love. Read on for more details.
We’ve just released ClassicPress 1.0.1, a security release. We recommend that you update your site(s) as soon as possible. ClassicPress 1.0.1 is a security release to match the security changes in WordPress 5.1.1 and 4.9.10 (both released today). It is available now.
Testing is critical during the RC phase – if we have any new bugs in ClassicPress 1.0.0-rc2, we need to know now so that we can get them fixed before the final release! Otherwise, the final release will be out on Tuesday, March 5.
Today we’re excited to announce the release of ClassicPress 1.0.0-rc1, available immediately. We have now left the “beta” release stage, and we are one step closer to a full, stable release that will serve as our foundation for many more future releases.
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.
This month, we will celebrate six months together as an organization. It’s been a very busy six months! In addition to preparing for the launch of ClassicPress v1, we have been laying a firm foundation within the organization that will serve us well as we grow.
We’ve just released ClassicPress 1.0.0-beta2, a security release. If you’re still on an older version of ClassicPress, we recommend that you update your site(s) as soon as possible.
the short answer to the question is YES! You might be wondering why ClassicPress is still in BETA if this is the case. The answer is simple — there are a few things we need to do before launching v1
We’re extremely excited to announce the first alpha release of ClassicPress, codenamed Sunrise. This launch has been a work of sheer dedication, a sprinkling of love, a dash of frustration and a large helping of teamwork, collaboration and enjoyment.
We think that for the time being (two years at least), big players in the plugin and theme space will want to keep backward compatibility. As long as the Classic Editor plugin is being “promoted” as an alternative, these plugins should remain working.