[openbeos] Re: Quality Assurance

"Simon Taylor" <simontaylor1@xxxxxxxxxxxx> wrote:
> > And while alpha/beta releases might not always be a good 
> > replacement 
> > for inhouse testing, it's pretty important to us, as we probably 
> > can't buy all the hardware that is out there (and even test them in 
> > all 
> > possible configurations). That's a special attribute of OS and 
> > driver 
> > development, though.
> I was thinking along the same lines as niels about having a semi-
> private release to people (experienced users) who are aware that it 
> may 
> contain bugs, and who are keen to try and identify them and write 
> good 
> bug reports so they can be fixed. People on this list, for instance, 
> have much more interest in making Haiku successful and would be much 
> more useful as testers than joe public. We are also more forgiving of 
> bugs as we're aware of the many years of effort that have gone into 
> creating Haiku. A poor quality first official public release should 
> be 
> avoided at all costs.

Definitely. But OTOH we already have something like this: the 
"makehdimage" script. You still need to download the sources and 
compile everything on your own, so not everyone will want to do this 
(restricted target release).
We can just start to ask people to try it out at some point, way before 
thinking about the first beta release.
As you said, it doesn't make sense to do this too early, as people are 
lazy and will report the same bug over and over (sure, not all of them 
:)).

Bye,
   Axel.

Other related posts: