SIGs/KDE/Update policy

Fedora KDE Plasma Desktop update policy

We are asking for exception to ship 1 4.x update in Fn release.

Our update process

Our update process is quite complex to assure quality of final -> stable push. 1. the new 4.x packages are built for Rawhide 2. packages are pushed to kde-unstable repository 3. input is requested from the first testers 4. bug tracker is created to collect 4.x bugs and known regressions 5. once most of bugs are fixed -> go/no-go meeting (kde sig meeting) 6. update is pushed to updates-testing repository (usually for a few weeks) 7. we closely tracking bugs and regressions - we have lot of testers 8. once most of bugs/criticals are fixed -> stable go/no-go meeting 9. final updates push