[openbeos] Re: some points

  • From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
  • To: openbeos@xxxxxxxxxxxxx
  • Date: Mon, 28 Jun 2004 18:20:34 +0200 CEST

"Jonas Buckner" <mouriceno1@xxxxxxxxxxxxxxx> wrote:
> > 3. The status pages looks a little bit buggy:
> > http://haiku-os.org/learn.php?mode=status
> > 
> > For example: The "development" part of "Translation" isn't full 
> > marked,
> > but "alpha" and "beta" are already marked.

I am partially guilty for that :)
The way our status is presented was changed, and not all team leaders 
have taken the opportunity yet to update their team's status.

> I don't think it's buggy. I think it's just confusingly designed.
> 
> The development section is how far we are through the development of 
> the
> current phase. So, for example, BFS is almost through the beta stage,
> approaching mature, while the MIDI kit looks the same, but is almost
> through initial development, approaching alpha.
> 
> You have to look at the sections on the right, then on top of those 
> use
> the sections at the left to see how far it is through that stage.
> 
> I think that's right...feel free to correct me.

I think I have to :)
The "development" section is actually independent from the general 
status. "alpha" generally means something like "somewhat working", 
"beta" usually stands for "functionally complete".
So 90%-100% developed would generally mean anything between beta and 
mature. Beta could start earlier, the effort for alpha status is 
different from team to team. The development bar tries to reflect how 
much work has been done already to achieve maturity of the component; 
when it's 100% complete and the status is "mature" (note, also missing 
tests can keep a component in beta status), you can say it reached R1 
stage - ready for release.

Bye,
   Axel.


Other related posts: