Plasma 5.8 is LTS we want it to be a new neon type as well.
# Mix
- LTS Ubuntu
- Latest Qt
- Latest frameworks
- LTS plasma
- Latest Apps and Extras
# Archives
- dev/stable/lts/plasma (from-branch build; variation of stable)
- user/lts/plasma (from-tar build; variation of release)
# Git Branches
- Neon/stable/LTS
- Neon/release/LTS
(merged standalone, release->stable) interaction via regular branches *only* through manual cherry picking.
# Build job names
- xenial_stable-lts_plasma_*
- xenial_release-lts_plasma_*
# Composition
We could compose LTS systems out of their base repo (dev/stable or user/) and simply stack the LTS stuff on top. Which would substantially cut down on tooling changes, build time impact and overall system complexity.
This would require LTS builds to be strictly greater versioned than their non-LTS counter-parts, or an apt priority config (i.e. a pin) at run **and** build time to make sure whenever a dep can be gotten from the LTS repos, it is obtained from there regardless of what is in the non-LTS repo!
# Concerns
- with everything being on latest other than plasma, things could very well break as things move about in the stack
- there is an excess amount of publishing hacks, qa hacks, multi-builds caused by the lack of T3407 which would be blown up by adding another permutation
-- failing to update one of the hacks in the tooling would also result in breakage, or inconsistent results