Hello All,
It happens every so often when a new beta is released that some
people would jump the gun and then crying for "what's new" if--as it
usually happens--the announcement is made after a beta release.
In the rare cases where the announcement is made _before_ the
software is put on the server, some people would rush to the beta
page (or ftp server), see nothing to download, and then rush to the
list to protest ("you announce a new beta, why isn't it there?"). I
remember it even happened once that someone downloaded a "broken"
beta because the software was in the process of uploading to the
server when he/she was downloading.
See the dilemma?
Here are my humble suggestions, one to RIT, one to my fellow
Bats(wo)men:
1. Maybe it's better for RIT folks to prepare a "what's new"
document first, and bundle it with the beta program (in the .arj
file). Then upload the software, followed by the official
announcement on the TBBETA list. Doing so guarantees the software is
on the server and ready for download when the announcement is made.
And those who scout the server often and download it before the
announcement is made could learn what's new from the accompanied
document. If RIT could do this consistently, we can also be sure a
beta version on the FTP is not an public release should there be no
accompanied document (and no subsequent announcement). Those who
choose to download such software would have no right to complain.
2. Before RIT does adopt the suggested practice, could we all please
be a little patient in waiting for announcement? Usually it's in
preparation or even on its way. (Mailing list is no instant
messaging.) Couldn't we wait just a little longer? It's not as if
who break the news (that there's a new beta) would get a candy or
something. :-)
--
Best regards,
Ming-Li
The Bat! 1.51 Beta/1 | Win2k SP1
--
______________________________________________________
Archives : <http://tbbeta.thebat.dutaint.com>
Moderators : <mailto:[EMAIL PROTECTED]>
Unsubscribe: <mailto:[EMAIL PROTECTED]>
You are subscribed as : [email protected]
