Scripsit Arnaud Vandyck <[EMAIL PROTECTED]>
> Scott Minns <[EMAIL PROTECTED]> writes:

> > Stable - released when the software is rock sold and very mature
> > 
> > Current - This is software that has been in testing for six months and
> >           experienced no critical bugs, floors or dependency
> >           problems. A new version is released every six

> This is nearly impossible. I don't know if other developers will agree
> but IMHO, it's like having two `stable' releases!

I concur. In particular, the process is already such that if we get
even near something that fits this description of "current", a big
party will be thrown and that something will be frozen to become the
next "stable" within a short timeframe.

Everybody seems to agree that new stable versions *should* be out
about every 6 months. The problem of getting testing into a freezeable
state is not going to go away simply by calling the goal "current"
instead of "stable".

-- 
Henning Makholm                          "What has it got in its pocketses?"


Reply via email to