[openbeos] Re: some points
- From: "Jonas Buckner" <mouriceno1@xxxxxxxxxxxxxxx>
- To: "Haiku Mailing List" <openbeos@xxxxxxxxxxxxx>
- Date: Mon, 28 Jun 2004 13:16:03 -0400
On Mon, 28 Jun 2004 18:20:34 +0200 CEST, "Axel Dörfler"
<axeld@xxxxxxxxxxxxxxxx> said:
> "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.
>
>
Well, gee wiz. That is even more confusing.
So the midi kit is almost done with development but hasn't reached a
point yet where they can can claim it's alpha? Is that because it really
can't be tested or used until it's just about code complete? Or is it
just that the team lead hasn't updated status? From the MIDI status
page, it looks like the former.
If it is, it really seems like alpha/beta/mature section deperately
needs to be in a different table.
Of course, maybe I'm just still lost about the whole thing and shouldn't
really be worrying about it at this point.
-Jonas B.
- Follow-Ups:
- [openbeos] Re: some points
- From: Michael Phipps
- References:
- [openbeos] Re: some points
- From: Axel Dörfler
Other related posts:
- » [openbeos] some points
- » [openbeos] Re: some points
- » [openbeos] Re: some points
- » [openbeos] Re: some points
- » [openbeos] Re: some points
- » [openbeos] Re: some points
- » [openbeos] Re: some points
- » [openbeos] Re: some points
- » [openbeos] Re: some points
- » [openbeos] Re: some points
- » [openbeos] Re: some points
- » [openbeos] Re: some points
- » [openbeos] Re: some points
- » [openbeos] Re: some points
- » [openbeos] Re: some points
- » [openbeos] Re: some points
- » [openbeos] Re: some points
- » [openbeos] Re: some points
- » [openbeos] Re: some points
- » [openbeos] Re: some points
- » [openbeos] Re: some points
- » [openbeos] Re: some points
- » [openbeos] Re: some points
- » [openbeos] Re: some points
- » [openbeos] Re: some points
- [openbeos] Re: some points
- From: Michael Phipps
- [openbeos] Re: some points
- From: Axel Dörfler