I'd been working on 3.1 for some time before abandoning the project. This was never completed released. As such, the current content of master is in limbo. I've moved the content of master into a separate branch (3.1-incomplete-work-2023) and cherry picked the pertinent commits/bug fixes back into the new master. This branched off the latest 3.0.20 code.
New version: 3.1.0
The new version for PHP 8 support will be 3.1. Currently we're at 3.0.20 and doing a patch update for this change feels far too minor. Since the previous 3.1.0 version was planned as the big upgrade/install rewrite, I'll just have to document this + bump the versions in the main README.
Website
Yikes!
Need to figure out what to do with the website to register the new core + extension versions... This is the scariest part of all of this - it's a huge web app and for financial reasons I had to drop the Virtual Private Server many years ago ($300+ a month was unfeasible for a project that never brought in much income). However, the site app needs far more permitted disk space and resources to offer the upgrade functionality. That housed all package versions + offered an option to let users dynamically construct their own upgrade packages.
Probably the only realistic way to do this is to:
(a) update the main download package for these new versions.
(b) create a prefab zip file containing everything (all modules, API, core, themes) with all the latest versions and ask people to prune whatever packages they don't want.
(c) update the upgrade script to explain all this.
Extensions
All these should be updated separately prior to releasing a new version of the core. The PHP 8 changes appear to be all backward compatible.
Modules
Rows that needed new versions have them listed next to it.
Branching
I'd been working on 3.1 for some time before abandoning the project. This was never completed released. As such, the current content of master is in limbo. I've moved the content of master into a separate branch (
3.1-incomplete-work-2023) and cherry picked the pertinent commits/bug fixes back into the new master. This branched off the latest 3.0.20 code.New version: 3.1.0
The new version for PHP 8 support will be 3.1. Currently we're at 3.0.20 and doing a patch update for this change feels far too minor. Since the previous 3.1.0 version was planned as the big upgrade/install rewrite, I'll just have to document this + bump the versions in the main README.
Website
Probably the only realistic way to do this is to:
Extensions
All these should be updated separately prior to releasing a new version of the core. The PHP 8 changes appear to be all backward compatible.
Modules
Rows that needed new versions have them listed next to it.
Themes - no changes needed for these
[x] classic grey
[x] oh canada
[x] deep blue
[x] API