When should a bug be considered as a regression or a release_blocker?

[Marco Martin]

On Wednesday 20 June 2012, Mark wrote:
> https://bugs.kde.org/show_bug.cgi?id=301854, that bug described the
> KGet Piechart applet as being broken. I tested that and verified that
> it indeed is completely broken and even renders outside it's applet
> space. So i marked that one as release blocker as well because it's
> useless in it's current state.

they are annoying problems indeed, but don't prevent you from using the 
workspace, that's what a blocker is

> Both issues are not something that obstruct normal KDE usage, but they
> do render some parts of KDE completely useless. I'm a bit unsure if i
> should mark such bugs as release blockers. Perhaps there should be a
> keyword called "component_blocker" indicating that a specific
> component (specified in the component field on bugzilla) is not fit to
> be shipped with the release.

i don't think we should make releases with random pieces cutted out, or they 
will never be complete


-- 
Marco Martin