On Mon, Nov 27, 2006 at 01:17:26PM -0500, Bruce Momjian wrote:
> Jim C. Nasby wrote:
> > Since testing in the past had a semi-defined goal (make sure it builds
> > and passes make check on your platform), perhaps that should be done in
> > the future; point out to users what features they should pay special
> > attention to during the beta. Of course, that will tend to mirror what's
> > in the change log, but people will pay better attention to a
> > plain-language description of what to test than trying to decipher it
> > from the change log.
>
> The release notes are available on day-1 of beta.
Of course, but hoping that users will read the release notes and start
testing everything in there isn't the same as putting out a call for
testing on X, Y, and Z. The release notes also don't pay any attention
to what's already handled by regression tests, and more important,
what's not. Presumably doing things like testing syntax doesn't do
nearly as much good as performance or scalability testing.
--
Jim Nasby jim@nasby.net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
