This page tracks progress on 3.1. I've been taking a hiatus (Jan 2019) for a little bit to work on minor upgrades to 3.0.x and modules. Back on it soon!

1. Installation script update

First step is to complete the installation script so that users now only ever download the CORE, and can choose whatever components they want as a separate step in the installation process.

[Done, but needs tweakin']

Being worked on - Dec 9

• Hook up new in-application Update page.
• Add a link on the Modules, Themes and next to the API field on the Settings -> Main page to link users to the install/upgrade page.

3. FT CMS updates

-bug: updating a module puts it online when github repo tag not checked & zipfile not exported.

• To think about: either update component JSON feeds to only display the last version of an unreleased beta/alpha, or no betas/alpha rows at all for those that now have final versions. OR do all that client-side to hide the rows. It'll all depend on whether we actually need that info when upgrading users. I suspect not, so omitting it in the feed might be best.
• Nice to have: update the theme JSON details to include screenshot links. Those screenshots will also need to be generated on the CDN.
• improve the file includes to bundle whatever we can, both core + default theme
• Backups for when site down. A fallback server might be simplest for any failed request. Maybe set something up on digital ocean.
• Set up the subdomain for static file delivery only (nginx?).
• CMS idiosyncracy. Incomplete (i.e. BETA) core versions fail to get their component JSON file updated upon saving, but the "generate all" version on the Components page works. Rethink this; plus beta versions need to (weirdly) update the target version when they themselves are updated, so new compatible versions don't need to be manually added to the final version - plus the component JSON file is recreated every time a beta version is updated/created.
• Improve error handling for installation script.

TBD.

Remainder tasks

• Update all themes.

Misc tasks

• Drop the Custom Build script
• Update the Upgrade script (see notes below)
• update Translations subdomain: just remove content and mention FT now bundles all translations with it, plus links to help translate etc.
• update Add Core Version to allow you to copy a prev version of the core, including dependencies. Needed more now that default components is work to set up.
• Need to add in target_release_version in all alpha/beta json feeds.

Notes:

For anyone updating from a version older than 3.1, I say we drop the old upgrade process altogether. When redirecting to the upgrade page it will always show a single 3.1 core package that users can use to upgrade. The core should then auto-detect installed components and upgrade anything that's necessary (shouldn't be any, at this stage).

Check exceptions to this: this assumes that everyone can upgrading to 3.1 which isn't the case, I think there's some 2.x versions that require to upgrade to other 2.x versions first...? That may complicate things.

Depending on the last point, this should allow me to drop the custom build, upgrade script, _repos folder and contents - which is an absolutely MASSIVE win for me in terms of maintenance.

Reminder: don't update the website CMS until 3.1 is ready. It removes various stuff still needed for 3.0.x releases!