Important: This website is now read only (except to admins) to comply with the UK Online Safety Act. Composr CMS is in the process of migrating to a new Constitutional governance model and Bazaar development model, with functionality of the old website (constructed by ocProducts Ltd, the prior copyright holder, a UK company) spread between GitLab and the new website (which has no connections to the UK).
Composr 10 RC6 released
This news article has not yet been validated by our staff, so we cannot accept responsibility for it. You followed a direct link to get to it.
Version 10 RC6 has now been released. This version is a release candidate for the next major version of Composr. Upgrading to this release is not recommended for live sites.
To upgrade follow the steps in your website's http://mybaseurl/upgrader.php script. You will need to copy the URL of the attached file (created via the form below) during step 3.
Your upgrade to version 10 RC6
You can generate an upgrader from any version of Composr to any other version. If you access this upgrade post via the version information box on your Admin Zone front page then we'll automatically know what version you're running.
If you'd prefer though you can enter in your version number right here:
All reported bugs since the last release have been fixed.
We are getting into higher release candidate numbers now than we have in the past, and more than I had expected to be honest.
However, I don't want to rush the final release. We'll keep making regular new release candidates as long as there are any failure-type bugs within particular corners of the system. We're unlike other software because there are hundreds of corners to Composr, and most users never try out most of those corners – so it can take a while for every problem to bubble up, and there's some back and forth involved. I plan for us to make the final release when we've just had a 2-week period with only cosmetic bugs reported - even if that sends us to RC20.
With the ocPortal releases we probably were guilty of going to the final release too quickly, and I don't want to make that mistake with Composr releases - so we'll be more conservative now. Besides, we can plan our activities better if we're not juggling bug fixing with customer upgrade programs and marketing.
An RC release is stable enough to use on live, and supported with quick fixes – either via a hotfix, or via a new release made soon. The difference to a final release sits in us not doing our final marketing yet, and continuing to support ocPortal 9 with bug fixes as the official stable version. I certainly recommend people be building new sites on Composr though, not ocPortal – Composr is an overwhelming upgrade in most areas .
Also, don't feel compelled to upgrade to every new RC we're putting out. These are coming out fast and furious, and if you're happy that the features you're using work well, there's no reason to upgrade unless we say so. The speed of releases is more to ensure that the back-and-forth process works through as quickly as possible.
Thanks for the explanation and good to see you and the team are taking very careful measures to ensure that Composr CMS is as stable as possible.
I personally will be upgrading these RCs as much as possible since TLC+ is one site being used as a live site testing ground for the new Composr software.
Edited
Comments
However, I don't want to rush the final release. We'll keep making regular new release candidates as long as there are any failure-type bugs within particular corners of the system. We're unlike other software because there are hundreds of corners to Composr, and most users never try out most of those corners – so it can take a while for every problem to bubble up, and there's some back and forth involved. I plan for us to make the final release when we've just had a 2-week period with only cosmetic bugs reported - even if that sends us to RC20.
With the ocPortal releases we probably were guilty of going to the final release too quickly, and I don't want to make that mistake with Composr releases - so we'll be more conservative now. Besides, we can plan our activities better if we're not juggling bug fixing with customer upgrade programs and marketing.
An RC release is stable enough to use on live, and supported with quick fixes – either via a hotfix, or via a new release made soon. The difference to a final release sits in us not doing our final marketing yet, and continuing to support ocPortal 9 with bug fixes as the official stable version.
I certainly recommend people be building new sites on Composr though, not ocPortal – Composr is an overwhelming upgrade in most areas
Also, don't feel compelled to upgrade to every new RC we're putting out. These are coming out fast and furious, and if you're happy that the features you're using work well, there's no reason to upgrade unless we say so. The speed of releases is more to ensure that the back-and-forth process works through as quickly as possible.
I personally will be upgrading these RCs as much as possible since TLC+ is one site being used as a live site testing ground for the new Composr software.