Version 3.5 testing game plan

I downloaded the binaries, looking for some guidance. Is there a different list? Thanks!

If you’re interested in testing 3.5 release the idea is to choose a platform. Use test-relase.sh script (if on unix) to bootstrap clang and compare the outputs of second and third phase (the script does this). After that you run nightly test suite and report any failures. Additionally you can run findRegressionNightly.py to find any performance regressions but you’ll test suite results from previous release to do this. I think we have testers for Debian, Ubuntu, Fedora, OpenSUSE, FreeBSD, Mac OS, Windows and a few more but Bill Wendling can give you the exact list.

Or, if you're interested in adding a different point of view, you can
download both 3.4.2 and 3.5-rc1 binaries and build something that is
important to you, either a benchmark or a program that you or your
company develops.

Compatibility testing is more important than performance regressions,
but we can't build the world with our release candidates on every
platform. If people would replace their own compilers with RC1 and
build their own projects, we'd love to hear from their failures!

cheers,
--renato