We will be having a core development meeting in the #core channel on Slack on Friday, April 23, 2021 at 7pm UTC (during the afternoon US time). To see the agenda and the exact time in your timezone, visit the forum thread: https://forums.classicpress.net/t/april-2021-core-meeting/3114 ClassicPress is looking for more developers to contribute to core. If you […]
We released stable versions 1.0.0 and 1.0.1 in March, and they are still actively providing a production-quality alternative to WordPress for over 1,600 active sites. Since then, we’ve been planning for the next versions of ClassicPress, and we’re here for the long term.
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.
Thanks to careful testing and reporting from our users, we’ve become aware of several minor issues with last week’s 1.0.0-rc1 release. None of these issues will affect the functionality of new or existing sites, but they are still worth fixing.
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.
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.
Today a few of us had a Zoom call about our strategy for project management in ClassicPress, including how we can better organize our open issues list to reflect progress and show others where they can contribute.
