August sees the ClassicPress project reach its first birthday. A lot has happened in those 12 months, much of which has been done behind the scenes. The milestone was celebrated with the release of a redesigned website and putting the finishing touches to v1.1.0 of the CMS.
The new website provides much better organized navigation. It is now a straightforward process to find and download the installation file for new sites or the migration plugin for existing sites. Until now, people were struggling to find those files and ending up at GitHub, which left them totally confused.
While the project team were busy on the website, they were also finalizing the next point release of the CMS, v1.1.0. The release date has been pushed back a few times, as new issues kept popping up, and had to be dealt with.
Some people have been critical of how long it is taking for the next release, even to the extent of accusing the team of resting on their heels and not having done anything useful in the last year.
It is important to remember that the team, especially the coders, also have day jobs. And there are not many of them in the first place. Unlike WordPress, which has many developers working on point releases at any one time, ClassicPress has only a handful.
The over-riding responsibility of the team is to ensure sites can be automatically updated to V1.1.0 without breaking anything. Pushing something out too soon, without thoroughly testing it, would do a lot more damage to the reputation of the CMS than delaying it.
For people who have grown used to WordPress pumping out updates on a regular basis, it does seem that not much is happening with ClassicPress. But that is not necessarily a bad thing. In fact, it is a testimony to how stable the current release is. CMS’s such as DotClear, only update when needed, often no more than a year at a time.
Operating systems, such as Linux, may only bring out updates every five years. Only security patches and package updates are sent out during the life of an LTS version. ClassicPress did that with v1.0.1.
There is no argument that more developers would see changes occurring faster, but unless those people volunteer to step forward, it’s not going to happen. End users are not the ones complaining about slow or no progress. It is developers . But none have offered their services. You can’t have your (birthday) cake and eat it too.
So, happy birthday ClassicPress, and we eagerly await the new release this year – when it is good and ready!