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.
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.
One of the most common support questions we get lately is regarding choosing languages in fresh installs of ClassicPress, and we hear you! Let’s break down how we got here, how you can help and what you can do if you want to use an untranslated language.
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
It is with great pleasure that we announce the BETA release of ClassicPress. Please help us spread the word about the BETA and, most importantly, please try it out in a test environment for your current websites.
It is with great pleasure that we announce the addition of Michelle Coe (Creative Director and Owner of BlueSkyPhoenix LLC) to the founding committee of ClassicPress.
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.
