🚀 go-pugleaf

I have established an email address, bugs@borland.com, to which people
can send reports of bugs in any Borland language product. Mail sent to
bugs@borland.com will end up in the hands of a QA person who will
verify the bug and if it is a previously unknown one make sure that it
is tracked and given to R&D to be fixed in a patch, maintenance
release or future version.

Please note that we do not yet have Tech Support or Customer Service
hooked in to our Internet connection, so this is not an address for
asking questions or asking for help with your program. It is for
reporting what you are reasonably sure are bugs in a Borland language
product so that they can get fixed. Reports should contain enough
detail so that anyone could follow the steps to reproduce the problem,
and you should fix all warning messages, remove all device drivers and
TSRs and eliminate as much code as you can while still demonstrating
the problem before you report it.

In most cases, bugs@borland.com will not send confirmation, fixes or
workarounds in response to problem reports. This is a first step in
providing services on the Internet, and other tech support and
customer services will still have to be obtained via other channels.

You should include a working email address in case QA needs to reach
you for clarification. Do not rely on the mail header providing a
return path back to you: With all the contortions it will take to get
the message to QA (who are also not on the Internet yet), the header
may not survive in a useable form.

I have crossposted this message to a number of newsgroups where bug
reports often appear even though they may not be exactly on the topic
of the newsgroup. I hope that at least some of those reports could be
sent to bugs@borland.com where they will do more good. Please be
considerate of net traffic and don't unthinkingly followup this
message to all those groups.

 -- sidney markowitz <sidney@borland.com>
    Borland International (Languages - R&D)