Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
in Update settings, let user choose "Use the latest release" or "Use the Long Term Support release" #8549
The goal of this issue is to give Piwik administrators the ability to choose which Piwik major version they want to use.
Current Update Settings
Proposed changes to Piwik core
Changes to api.piwik.org service
(fyi: I can make those changes to api.piwik.org whoever works on this please let me know)
Would you please default to LTS for existing 2.x users when they do nothing at all (no selection)? Basically that would mean that users should actively opt-in for 3.0 if they want to. Same for 4.0, 5.0, ...
The reason for that would be that they can easily upgrade to the newer version but downgrading to a LTS release could potentially be painful (schema changes in database etc.). Plus, dependencies for the new version might not be fulfilled.
There should also be a dependency check for the newer version (PHP version etc.).
referenced this issue
Aug 11, 2015
For us making Piwik it is very helpful when more users are on the latest version.
Maybe we should not let user update to the latest version and stay instead on LTS, when one or more plugin currently in use are not yet compatible with the latest version. Maybe we could detect this and let users know which plugins are not yet compatible with latest Piwik (looking on Marketplace for available updates, and listing there also any private/other third party plugin)
in your opinion, why should we default to LTS?
Because a downgrade back to LTS could be painful: Or can you make sure that database schema downgrades will be working (for years!) without the loss of data?
If you want to default to the new version, users should make at least an explicit choice before they leave LTS.
Personally, using Debian 8, I will go for 3.0.0 as for me there's no reason to stay on Piwik LTS.
I started working on it and after using a
I won't implement the proposed "When a user selects "Use the latest beta release = No" then...." thing as the UI will be generated depending on the release classes I reckon.
I moved the config entry to
I will send a additional URL parameter
What I need to know as well is under which URL the builds will be available. For example:
So what I need to know for now:
What @mattab needs to implement in
Ok, we can move the logic from http://builds.piwik.org/LATEST_BETA to api.piwik.org - I can make the change.
let's keep current URL structure http://builds.piwik.org/piwik-X.Y.0-bZ.zip
The screenshot above looks promising
referenced this issue
Sep 1, 2015
I just noticed we need to maybe hide or disable certain release channels if requirements are not met, eg because of PHP version. So far it's maybe not a problem yet as Piwik 2.X should run on all servers and if someone selects
I tend to not handle these kinda things right now and just always show all options but up to you.
added a commit
Sep 2, 2015
I worked a little on it but noticed it's not that easy and we'd kinda need an API on