DO NOT MERGE
[Debug] allow_upgrades_to_betaafterwards as it was changed to
Plugins can now very easily provide their own custom release channels but we're not making it a public API as it won't be needed for now. The API might change once there is an actual use case for it. Eg right now they require that the latest available version number is checked via HTTP and that this API returns only a version number etc (not eg a JSON etc). Such things could be changed if it ever becomes API.
Possible use cases for custom release channels in the future:
Such things were kinda possible before but much harder to do.
I added label needs review but we should not merge it yet as we need to wait for changes in
api.piwik.org to be done
Code looks good, and +1000 for the concept.
@mattab what's the current status of
api.piwik.org? Are they made? Can we merge this one?
For reference, API URLs for channels are:
@tsteur when merging this to 3.X branch, you can assume we'll have the 3.X LTS channel. so maybe we just replace 2.X by 3.X in the UI in 3.0.0 branch?
and when merging it, feel free to issue PR in api.piwik.org to add the new
3x_ config settings...
so maybe we just replace 2.X by 3.X in the UI in 3.0.0 branch?
I think we might just add a 3.X_beta and declare it as experimental or actually I think we'll think about it as soon as we actually release a beta :)
or actually I think we'll think about it as soon as we actually release a beta :)
Ok feel free to post any thought in #8836
After merge update docs that mention [Debug] allow_upgrades_to_beta afterwards as it was changed to [General]release_channel
All good it wasnt documented anywhere