what's a blocker bug? (was: [Release Planning 3.4] v3-4-test will be frozen tomorrow)

Kai Blin kai.blin at gmail.com
Fri Oct 16 01:07:46 MDT 2009

On Thursday 15 October 2009 16:34:01 Björn Jacke wrote:

> As long as we do not introduce new bugs inside a release branch, an
>  existing (old) bug should not be able to *block* an outstanding bugfix
>  relrease. If some bug, whether it's important or not is not yet fixed, it
>  will be fixed with the next release.

> For today's situation: I think it's not optimal if people don't get a 3.4.3
> release which already contains a bunch of important fixes just because we
>  are waiting for some more fixeѕ to come.

I like it. There's probably always some more bugs to fix, until we finally get 
a compiler that supports the -ffix-bugs flag. However as long as we don't 
introduce regressions, we're not actually making things worse for users who 
are bitten by a bug we don't fix, we just don't help them either. If we 
contrast this with the benefit of getting the bugfixes we do ship out to many 
users, there is a clear advantage for Björn's proposed policy.

However, we don't want to go to the other extreme of publishing a release per 
bug. (Not saying anybody proposed that, of course.) So we would want to wait 
until a reasonable number of bugfixes has accumulated. Which leaves the 
question of what that reasonable number is.

Kai Blin
WorldForge developer  http://www.worldforge.org/
Wine developer        http://wiki.winehq.org/KaiBlin
Samba team member     http://www.samba.org/samba/team/
Will code for cotton.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20091016/a7133cd5/attachment.pgp>

More information about the samba-technical mailing list