That is a rediculously conservative approach for any software, let-alone
a beta product. It would virtually guarantee that we don't get a
release for perhaps two months, while actively *discouraging* people
from fixing minor bugs since that would further delay the release.
Even Mozilla, with their 1.0 release did not have such a rediculously
conservative approach. Be realistic. 0.5 doesn't have to be perfect,
it merely has to be more stable that 0.3 (since technically 0.3 is the
code that we are recommending people use until 0.5 is released). It met
that criteria a LONG time ago.
Ian.
On Sat, Oct 19, 2002 at 09:20:10PM +0200, Oskar Sandberg wrote:
> There is a simple algorithm for this:
>
> do {
> freeze(code);
> time = currentTime();
> while (NOW < time + ONE_WEEK)
> if (bugfound()) {
> unfreeze(code);
> fix(code);
> continue;
> }
> }
> release = code;
> unfreeze(code);
> return release;
> } while (true);
>
>
> --
>
> Oskar Sandberg
> oskar at freenetproject.org
>
> _______________________________________________
> devl mailing list
> devl at freenetproject.org
> http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl
--
Ian Clarke ian@[freenetproject.org|locut.us|cematics.com]
Latest Project http://cematics.com/kanzi
Personal Homepage http://locut.us/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20021019/79a6478d/attachment.pgp>
