On Oct 4, 2006, at 10:53 AM, Ian M. Jones wrote:
On Wed, October 4, 2006 15:46, Joseph Nastasi wrote:
On Oct 4, 2006, at 9:59 AM, Daniel Stenning wrote:
It would be nice if there could at least be one "dot" release
following a
quarterly release. As suddenly a huge number of "beta testers" are
effectively
being unleashed on the poor R4 official release, new bugs are
bound to come
to light - some of which might be serious to some users. At least
one minor
release would be a good idea imo.
Oh boy, do I second that. The problem with the current rapid release
paradigm is that bug fixes from new release don't surface until the
next major release. Waiting a few months isn't the real problem. The
real problem is that the new version almost always introduces other
issues that work fine in the previous official release.
A bug fix release would be a real good idea, IMHO.
Thirded!
--
Ian M. Jones
Though I have no proof for this, my feeling is that many of these new
bugs come from other bug fixes as often as from the new features.
Anyone who's done a few rounds in the beta program can attest to the
many new bugs that pop up in the betas (after the alphas) - after
they've added all the new features and are just squashing bugs. So I
think you'll just double your headaches to 8 times a year. I've come
to accept a few weeks of frantic work near the end of the beta cycle
to check to see what's broken, try to find workarounds, and remove
old (and now unnecessary) workarounds.
I'd rather push for a longer beta cycle 4 times a year, perhaps have
more people test, or do the fc stage publicly with all rb users.
mike
--
Mike Woodworth
[EMAIL PROTECTED]
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
