Build ISO upon [stable] and [kde-staging] rather than [testing] and [kde-staging] (which is current situation)
[testing]freeze statement breaks packaging flow, especially in this particular cycle that the beta to release takes more time than expected
- testers and packages aren't aware of
[testing]-in-fact thus causing conflicts across repos
- group updates being postponed since it may break system in more aspects than expected
- it is hard to determine whether the bug in ISO is related to iso scripts or the packages
- a newly installed user may get confused about why their packages are newer than those in
- move all packages in current stable enough
[testing](which is like the standard procedure) to
[stable]before alpha or beta build
- build ISO with only
[kde-staging]for newly introduced artwork and codename)
- The system in the ISO is always the solid stable one
- It is more easily to determined situations occurs in live system
- The packaging flow isn't interrupted, the tester flow won't, either.
- The release is out-of-date by nature: well, it is true for all distros, freeze the repo don't freeze the time, all the projects are still under development, and emerging new releases.
- Bugs may have been fixed in
[testing]: and introduce new bugs, too. IMO, we should release more "snapshot" ISO to overcome this, rather than bet on possibilities.