[Bf-committers] Beta Testing for pre-release versions?

14 May 2004 22:20:51 -0400

--=-BdtQGa1i/N9ee8tO4Byx
Content-Type: multipart/alternative; boundary="=-vADuapYVkCkJ9Aclf7jf"

--=-vADuapYVkCkJ9Aclf7jf
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Don't you find annoying that each new version of Blender ships with new
bugs, and most of the time those bugs are related to things that used to
work fine on previous releases (while one would expect to find more bugs
related to new features) :-/ Some better quality control measures should
be put in practice.

I know that there is a Test Release forum at BO, and it works really
fine when it comes to testing new/experimental features, but it falls
flat out when it comes to caching bugs non related to the spectacular
new feature of the moment. Most of the bugs showing on new releases are
quite obvious, but still managed to make it into the final release. See
2.33a: First day of release and already two QUITE obvious bugs related
to the interface !!!

I would suggest for the platform managers to post the final compiled
versions (built after the CVS is TOTALLY frozen) a fixed number of days
on the forum before the releases are made official. i.e. The just
released 2.33a would be posted today on the forum, have bugs reports
come in, and 7 days from today then 2.33a would be officially released
if there isn't any fix to be made.

Even further, I would like to see some sort of official beta testers
group, not just the casual forum passer-by.=20

I know that by taking this approach the release cycle would be extended
for a week each time (or even more, depending on the bugs), but it is
outrageous how blender has been shipping release after release with so
many bugs.  Certainly the bugs eventually get into the bug tracker and
are sorted out, but isn't it better if the bugs where detected BEFORE
the release goes public.

Shall the trend continue, and sooner than later Blender will be known as
=C2=A8The free 3D app with an odd interface and always many bugs=C2=A8, and=
 I
don't need to explain how hard is to erase those kind of negative images
from the public's mind.

Apollux.

P.D.  If the official beta-tester groups are formed, I volunteer for the
Linux platform.=20

--=-vADuapYVkCkJ9Aclf7jf
Content-Type: text/html; charset=utf-8

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
 <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
 <META NAME="GENERATOR" CONTENT="GtkHTML/1.1.9">
</HEAD>
<BODY>
Don't you find annoying that each new version of Blender ships with new bugs, and most of the time those bugs are related to things that used to work fine on previous releases (while one would expect to find more bugs related to new features) <IMG SRC="cid:1084586421.2908.5.camel@localhost.localdomain" ALIGN="bottom" ALT=":-/" BORDER="0"> Some better quality control measures should be put in practice. 
 
I know that there is a Test Release forum at BO, and it works really fine when it comes to testing new/experimental features, but it falls flat out when it comes to caching bugs non related to the spectacular new feature of the moment. Most of the bugs showing on new releases are quite obvious, but still managed to make it into the final release. See 2.33a: First day of release and already two QUITE obvious bugs related to the interface !!! 
 
I would suggest for the platform managers to post the final compiled versions (built after the CVS is TOTALLY frozen) a fixed number of days on the forum before the releases are made official. i.e. The just released 2.33a would be posted today on the forum, have bugs reports come in, and 7 days from today then 2.33a would be officially released if there isn't any fix to be made. 
 
Even further, I would like to see some sort of official beta testers group, not just the casual forum passer-by. 
 
I know that by taking this approach the release cycle would be extended for a week each time (or even more, depending on the bugs), but it is outrageous how blender has been shipping release after release with so many bugs.&nbsp; Certainly the bugs eventually get into the bug tracker and are sorted out, but isn't it better if the bugs where detected BEFORE the release goes public. 
 
Shall the trend continue, and sooner than later Blender will be known as &#168;The free 3D app with an odd interface and always many bugs&#168;, and I don't need to explain how hard is to erase those kind of negative images from the public's mind. 
 
Apollux. 
 
P.D.&nbsp; If the official beta-tester groups are formed, I volunteer for the Linux platform. 
 
</BODY>
</HTML>

--=-vADuapYVkCkJ9Aclf7jf--

--=-BdtQGa1i/N9ee8tO4Byx
Content-ID: <1084586421.2908.5.camel@localhost.localdomain>
Content-Disposition: attachment; filename=smiley-9.png
Content-Type: image/png; name=smiley-9.png
Content-Transfer-Encoding: base64

iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAABmJLR0QA/wD/AP+gvaeTAAAC8UlE
QVR42n2TW2hUZxSFv3OZmMuMeCuoEWeiWBUhqSFiWxSxCFUUFbGQovTBCzWibSl9sX0q7VMRrIVa
qwhiqQSp4AUtEw1otGmiTFqJmJgKM0YmMZk5M2fmzOXc/v/0oWmhVvrBetjsvTYs2Bv+SxQ4BFwG
3CldAt6f6v0L5YX6u2Wx+gNH9q1k49vL0RtiIGxca5je3rt89k2O4VH3JNDxsgXdn3e0vHX4g3YU
rQ6/nMItjaAoGlrtPLSa2XjlJMeO3+Srzmw3sAFAmzKf+uJQ287DH+5CVNN4lRTSK6CoIQCka+CX
k0DAG6tjaJXJRb88tOcC11Qg2rJ05v6DHVsR9gTCyaAoGnuP9KHqYSYMSfvHCRQ1hHRNFDXEwffm
8OoC7QAQ1YBd/T80bq6dtQrXGkbVG9j/aQ9dd55iWpI/xiNc+nmQkhth45Z2qpnbaNNmMU236Oqr
3tOB5vCCnTjmA0AFRefLT9ZjVQK+Pn4CpzBIIpHg6LHvsUbP/xU4kDQ1hgC2q42N8/cCSL8ISAh8
Fi5uJR6/gXCyOLl+rl7+iWLqLK45AIBvTzJvjgawQzcMAxQdpEsgPQJRxcnfxzF/g8AnEFXMkaME
vkW+4DAjUg+eSakiAVBt27kW+OV/zFLYSL+E9IpIv0QuX+RJKsvpC0k6b6rkQ9sRQpDOCIB+HYhX
nl/fVjPjNYQ9AYHPmCEZemJxf0gSqnuF1avWsntPjHBdQI2So/d3j6GHJYBOBYg2L4mk4uc2Iexx
UmmHxOgK1qx5kyWxCMIx8KvPsDM9CCfDpFGhZ8Dm9IUcj9PBUg0oTOTchdOV8sq2tsXUh4q0tiwi
LAepjF3Bzd/Dsx4hPZOn41VSYz59/QW6H4iTwLm/L/HKrQFzXSmbaXq92SVwx5F+Eelb5EyLbN4h
Y/ok0x69fQXOxL3bwDsve6YzTXPVPe+uD9PcUkdDrULVCTAtSTLtcbHLZCTNj8Bu/oco8BHwK+AB
BjAEfAu0vjj8JwJEdi3l5jnqAAAAAElFTkSuQmCC

--=-BdtQGa1i/N9ee8tO4Byx--