Every beta is a release candidate.
If all the work after beta3 with testing and verification results in no
more problems found, and no patches needed then beta4 will not be made.
Instead we make the stable release. If there are some problems found and
a decision is made to make a patch, then a beta4 is done and we restart
with it as the next release candidate.
/Linus
> -----Original Message-----
> From: Tom Morris [mailto:[EMAIL PROTECTED]
> Sent: den 21 juli 2006 19:15
> To: [email protected]
> Subject: RE: [argouml-dev] The immediate plan towards 0.22
>
> > Let me suggest one beta next week, one beta on the 7th and
> > then the stable release just after that (sometimes between
> > the 10th and the 15th).
>
> The problem that I see with scheduling two more betas is a
pyschological
> one. Knowing that there are additional releases schedule, people will
> feel
> free to cram in additional stuff, increasing the probability that we
end
> up
> having to do three more betas instead of two more.
>
> What work do we expect to have done between beta3 and beta4 that
requires
> that beta4 exist?
>
> It's only a few days, but the days have a way of adding up.
>
> Tom
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
