On Fri, May 9, 2014 at 11:12 AM, Harald Sitter <[email protected]> wrote: > On Tue, Mar 11, 2014 at 2:55 PM, Jonathan Riddell <[email protected]> wrote: >> On Thu, Mar 06, 2014 at 01:53:57AM +0100, Harald Sitter wrote: >>> Off the top of my head I'd say: >>> - package is on the ISO/package-set or visibly promoted (e.g. the >>> featured apps in discover) >>> >>> - bug breaks core functionality of the application (e.g. crash on >>> startup or crash whenever one tries to use the core functionality, >>> like trying to hit play in amarok) >>> - OR bug hinders intended UX of the core functionality (e.g. amarok >>> constantly popping up a messagebox when the track changes) >>> - OR bug is causing substantial (relative) amounts of automated crash >>> reports on errors.ubuntu (random number: top 5 crashers subscribed by >>> kubuntu-bugs) >>> - OR upstream requests the bug to be noted and resolved >>> - AND upstream is aware and investigating >> >> Yes this seems like a good definition > > This was added as a new policy "High Impact Bugs" [1], additionally > the LTS policy was revised to explicitly mention HIBs are tracked and > addressed as part of long term support. > > [1] http://community.kde.org/Kubuntu/Policies#High_Impact_Bugs_.28.28NEW.29.29
Oh, I forgot to mention. There continues to be no formal defitinition of core functionality, since I guess it's documented here now. Should it ever become a problem that people are not sure about whether something is to be considered core or not we can always add it in. Not exactly rocket science ^^ HS -- kubuntu-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
