[haiku-development] Re: Alpha 1 Discussion: an overview
- From: "Stephan Assmus" <superstippi@xxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sun, 02 Mar 2008 10:04:05 +0100
-------- Original-Nachricht --------
> Datum: Sun, 02 Mar 2008 01:35:05 +0100
> Von: Alexandre Deckner <alex@xxxxxxxxxxxx>
> An: haiku-development@xxxxxxxxxxxxx
> Betreff: [haiku-development] Re: Alpha 1 Discussion: an overview
> Urias McCullough wrote :
> >
> > I completely second this notion. If partitioning is the most dangerous
> > part of a Haiku install, then it should be the most tested. There is
> > no better way to test it than to get it out in the wild complete with
> > BIG DISCLAIMERS.
> >
> > [.....]
> >
> > I've got all sorts of hardware lying around to throw at Haiku for
> > testing purposes - someone just needs to indicate that Haiku's
> > DriveSetup replacement is ready for pre-alpha/alpha testing.
> >
> >
> >
> Hi!
> Well, speaking about testing, before getting out in wild, i think there
> is an intermediary solution.
> It could be interesting to have a way to organize testing within the
> small (for now) community. For that, it would be nice to add a way to
> post testing jobs (on track if possible).
> For example, a developer has finished a driver and would like some
> people to test his work. For now, he can only wait for 'bug' (negative)
> tickets to appear, or at best, say hey in the mailing list, but there's
> no real tracking of the tests.
> I think it would be more productive for all to post a 'testing
> job/request' so that one can evaluate the number of negative _and_
> positive tests. We could then picture more precisely how ready and
> polished things are, and allow developers to have a quicker response
> from the users.
> To summarize, we could use some infrastructure for the testing work.
+1
Best regards,
-Stephan
Other related posts:
