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

[Christoph Feck]

On Wednesday 20 June 2012 22:15:35 Mark wrote:
> I would like to have some clarification on when something should be
> marked as a release blocker.

Take the word literally. A release blocker is a bug which makes the 
release unusable. Think "it is better to not release KDE at all, 
instead of releasing it with this bug".

Examples:
- Code does not even compile to create binary packages
- KDM fails to log you in
- KWin does not start, or starts without window decorations
- Plasma Workspace fails to start, or essential widgets do not work 
(e.g. task bar, system tray, application launcher)
- Essential KDE applications (e.g. Dolphin, Konqueror, KWrite, 
Konsole) fail to start or do not work at least basically.
- Essential system services do not work (this is often not in the 
scope of KDE, but if for whatever reason keyboard or network do not 
work because of a KDE issue, it is a release blocker)

(CCing kde-testing)

Christoph Feck (kdepepo)
KDE Quality Team