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

[Martin Gräßlin]

On Thursday 21 June 2012 16:56:51 Marco Martin wrote:
> On Thursday 21 June 2012, Mark wrote:
> > >> 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.
> > > 
> > > not when they are this minor, no.
> > 
> > True and i completely agree with it.
> > But this doesn't make it any easier. Marco said (above): "i don't
> > think we should make releases with random pieces cutted out, or they
> > will never be complete" so we don't cut out pieces that don't work yet
> > we also don't want to release pieces that don't work.
> > 
> > If you follow that reasoning it is... a blocker :p
> 
> sometimes we just have to release with known issues or release never.
+1

we cannot reach 0 bugs, it's impossible. So we have to compromise. For minor 
issues it is valid to say that can go into the release.

What we do at KWin is using the target milestone (set by developers!) to 
indicate what we want and need to fix till the next release or the second 
next. That might work also for Plasma.

Cheers
Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20120621/c2514a07/attachment.sig>