Composr development update - November
1 guest and 0 members have just viewed this.
Control functions:
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).
A symbol is missing: CSRF_TOKEN. This usually happens when Comcode is written without placing template/PHP code within a code tag.
Composr development update - November
2nd December 2016, 5:47 pmIt is exciting for me to share the first monthly development update on changes implemented in Composr. You can expect this to be a regular thing from now on :).
Let us start with the development from October and November.
Question, what will we be doing when v11 releases? Will ocPortal support be completely discontinued (eg. version 9 and below)? And will we be supporting both v10 and v11, or will v10 be a short support cycle?
Generally we'll have an in-development version, a bleeding edge version (e.g. like how v10 is still in RC – we'll be having longer pre-release periods with Composr until an external [i.e. neutral] criteria is met), a stable version, and a supported version. It all depends on the situation though, really it's a bit more complex:
Right now… v11=dev, v10=bleeding, v9=stable, v8=supported
Soon… v11=dev, v10=stable, v9=supported, v8=supported
Then… v11=dev, v10=stable
Then… v12=dev, v11=bleeding, v10=stable
I don't have dates really, but it'll be based on what is reasonable.