[haiku-development] Re: Creating a list of tasks for alpha 1
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Fri, 22 Feb 2008 10:01:36 +0100 CET
"Niels Reedijk" <niels.reedijk@xxxxxxxxx> wrote:
> The goal of alpha 1 is _not_ to create a perfect operating system
> that
> works on all the hardware out there, but rather to create a stable
> enough system for developers to play with, early adopters to test on,
> and BeOS/Haiku freaks to enjoy as a preview of what is to come. My
> translation of this is that unsupported hardware does not qualify as
> an issue, but issues of data loss do.
Pretty much. But it's also important that it runs on as many hardware
out there as possible - ie. a driver should not pretend to support a
given device when it in fact does not, and only causes problems (not
sure if there are any cases left of this).
> Note that the actual implementation is up to you.
Bummer ;-)
> To prioritize the different issues, I think there should be a
> separation between must-haves, and really-want-to-haves. I suggest
> using the 'priority' field for that.
Hmm, I don't think we need to repurpose the priority field for that.
There is already the milestone R1/alpha which should be pretty self
explaining - plus, the standard priority levels we are giving fit
pretty well, too (not that they differ that much, anyway).
In the end, only blocker tickets are really non-discussable.
> I would like to ask everyone to please evaluate everything before
> next
> Monday (the 25th). We can then continue the discussion on the alpha 1
> release.
Not sure if I'll find the time, but I'll try.
Bye,
Axel.
Other related posts:
