New jail_interface broken in 6.1-RELEASE

[Dirk Engling]

On Thu, 11 May 2006, Brooks Davis wrote:

> The Q/A process is that users download the BETA and RC releases and test
> the feature they care about.  Unless someone out of the blue gives us
> tens of millions of dollars to hire a massive testing staff there is
> no other option.  If you depend on a critical feature that isn't used
> by the average user you need to either test it or risk this happening.
> This is not idea, but that's the world we live in.

I _did_ in fact test 6.1. I tested it since 6.1-BETA, every test release 
there was. So I _know_, new features, apparently untested and buggy, were 
introduced to RELENG after RC2 went out.

So this "millions of dollar"-story is a rather lame excuse. When I declare 
release candidate I declare feature freeze. So I can simply forbid any 
commits or merges to my release branches as long they are not bug fixes.

You do neither need a huge staff to do that, nor millions of dollars. Just 
a policy you even can enforce automatically. That would improve Q/A, in my 
eyes.

I can see your point. If every arbitrary user starts complaining over any 
tiny bug breaking some esoteric features, you'd never achieve anything. 
However, if no one ever complains for fear of offending volunteers, Open 
Source Software dies of mediocracy.

Regards

   erdgeist