- Edited
This post is to get some opinions about changing how KaOS ships Plasma 5.
Currently KDE releases a new major version every 3 months. For the first few weeks after a new release, there is a weekly minor version, then slows down to every 2-3 weeks, until a beta for the new major version comes out.
Issue is, new stable weekly/bi-weekly tars are tagged and released the same day, no testing upstream, many times, no one even build them before releasing.
Almost all KDE devs run and work on master Plasma git only, and only know issues in that branch. Bug fixes are much quicker available in master then anywhere else. New features (which most of the time are really needed options) can take months to move to release tars. This will be especially true with plasma 5.8. This is an LTS release, intended for distros staying on old Qt, so it can implement features that only Qt 5.7 and above support.
What is suggested now is to do a Plasma 5 build from git master for KaOS. Leave that build one week in the [build] repo for thorough checking (and if needed, create an internal test ISO with it), then move to all users.
This way there won't be a need to constantly backport much needed patches from git master and do many in between releases rebuilds.
Applications that don't see any commits in git will be left off these automated builds. Examples are (huge) oxygen-icons & plasma-workspace-wallpapers.
What is your opinion in this?