-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, 12 May 2001 18:03:10 +0200, MaXxX thoughtfully wrote the
following:
M> And there's yet another thing - the betatesters of various programs
M> usually get special FREE licenses for the testing purposes, so that
M> they don't have to buy the program to help with its development. Here,
M> the testers HAVE to pay for the program (or else it'll stop
M> functioning), AND they won't benefit in any way from the hard testing
M> work they do, AND they're rarely listened to.
Ritlabs betas of TB! are public. They are free for anyone to try and
report bugs *if they wish*. You were not specifically asked the favour of
beta testing (am I wrong on this?). I therefore don't see why you're
necessarily entitled to something in return, of monetary value, such as a
free license.
The last time that I was actually *asked* to beta test, I did in fact get
a free license. :-) Just recently, PMView's beta testing was closed and
when it was finished ... no free license for me. I've also beta tested
many other public betas with no free license forthcoming. I see nothing
wrong with Ritlabs position in this regard. Once there's no official
agreement ... no freeby. :-)
As to the rest of your sentiments, I tend to agree, although they tend to
be more than a bit unreasonably sweeping. TB! does tend to harbour a lot
of bugs. As soon as you fix some, they are replaced by new ones and this
is largely because new features are being added so rapidly which introduce
a new set of bugs. Since my using TB! in April 1999, they've fixed a huge
quantity of bugs that we have indicated to them on this very beta list. I
do share your view that it's best that they slow down on the not so
necessary feature add-ons and concentrate more on fixing some more of
those older and also, more recent nasty bugs.
My two pet bugs which I am wary of constantly, and which have affected my
use of TB! for ages are:
a) the one where an incoming message filtered and dynamically added to the
folder which you're browsing can lead to you're replying to the wrong
recipient when you generate a reply to the message your reading when the
new message comes in
b) Using %cookies recursively with the %Qinclude macro leads to some
interesting effects when multiple cookies are being used within the same
template.
Both have been documented on this list so I won't go into detail on them.
�Allie
- --
A. Curtis Martin �� List Moderator (and fellow registered end-user)
Using SecureBat! (v1.53/iKey1000)293FF-929OB | Win2k (SP1) -
'Everybody is ignorant, only on different subjects.'
-----BEGIN PGP SIGNATURE-----
Version: PGP Cyber-Knights Templar 6.5.8ckt (build 05)
Comment: KeyID: 0x57C9EB602B0717E2 (Sealed for security).
iQA/AwUBOv3NClfJ62ArBxfiEQLv8ACfRmTOwmnSN5ppbYOLpWuYWmJy0XAAn1DR
RdmIcSY+AHd/gsQds/tdRYdZ
=UKYW
-----END PGP SIGNATURE-----
--
______________________________________________________
Archives : <http://tbbeta.thebat.dutaint.com>
Moderators : <mailto:[EMAIL PROTECTED]>
Unsubscribe: <mailto:[EMAIL PROTECTED]>
You are subscribed as : [email protected]
