Yes, Chris,
Good idea to keep your Bug Report available on the HJ site.
I do wish, though, that we could have more feedback of bugs HJ think are
fixed and a number of us are interested in a list of files which have been
altered since a previous version.
--
Carol Pearson
[EMAIL PROTECTED]
At 09:34 16/10/99 -0500, Development Manager wrote:
>Hi Tom, et al,
>
>This is a good idea. In the next go around, we will try to be more clear
>about the difference between a release candidate (which is under a code
>freeze) and a general beta.
>
>I think, however, that we should keep our bug report on the web site
>permanently. All software will show defects out in the field. This will
>provide our users with a system for getting the reports to us in a standard
>manner so we can fix them in patches or in upcoming versions of the product.
>
>Thanks,
>cdh
>
>Chris Hofstader
>Development Manager
>Henter-Joyce, Inc.
>(727) 803-8000
>[EMAIL PROTECTED]
>
>-----Original Message-----
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]]On Behalf Of Tom Lange
>Sent: Friday, October 15, 1999 11:04 PM
>To: [EMAIL PROTECTED]
>Subject: Re: Do people want public betas?
>
>
>Hi,
>I'm very much in favor of public betas. I thought the first beta release of
>3.31 worked well for me as has RC2, what is now the official 3.31 version.
>
>However, here is what I would have liked to have seen.
>1. If HJ knew that RC2 was indeed going to end up being the official
>release 3.31 and didn't say so, the announcement of RC2 should have
>mentioned the date on which bug reports would no longer be accepted and on
>which code would be frozen.
>2. It wouldn't have been necessary to tell people how long the code freeze
>would last so as not to reveal the intended release date, but a description
>of the code freeze and its purpose would have quelled misperceptions by
>some that their gripes weren't being listened to. Anyone who's been around
>a software development shop knows that the code freeze is to prevent
>changes being made to the code at the eleventh hour and last minute. Often
>those types of changes can have unforseen consequences and can break more
>than what was intended to be fixed. At some point, people have to
>understand that what isn't addressed during the final beta cycle can't be
>fixed until after the release date, and there should be a further
>understanding thatthose types of things will be addressed in post-release
>patches.
>
>Having said that, I'll take a moment to commend HJ on a job well done and I
>look forward to future developments. Good work, guys!
>
> Cheers!
>Tom
>-
>Visit the jfw ml web page: http://jfw.cjb.net
>
>-
>Visit the jfw ml web page: http://jfw.cjb.net
>
-
Visit the jfw ml web page: http://jfw.cjb.net
