10.16.1 Release Vetting Checklist
Here's a checklist to consult when vetting the release.
Table of Contents
10.16.1.1 (RC2)
Status | Test | Comment | Tester |
OK | Directory structure should look correct in all zips. | See RC1. | Rick |
OK | Links should work in index.html in the bin distribution. | All links, including PDFs, now work. | Rick |
> | bin scripts should work. | bin scripts run correctly on Mac OSX 11.2.3 | Rick |
OK | No junk files like derby.log | See RC1 | Rick |
OK | No unnecessary 3rd party jars like Junit | See RC1 | Rick |
OK | Source zip can be used to generate jars and docs | From the source distro, I successfully built the docs, both the html and the pdf versions. I also cleanly built the product jars and javadoc. The tests ran cleanly against those jars using both the classpath and the modulepath. | Rick |
OK | Signatures and checksums correct | I verified all the signatures and checksums using Ubuntu 18 and gpg and sha512sum | Bryan |
| OK | Java version compatibility on Linux | On Ubuntu 18, using both JDK 8 and JDK 11, I verified that I got the expected message when I tried to run Derby 10.16.1.1. Specifically, I get a java.lang.UnsupportedClassVersionError specifying that the class files are version 61.0 and cannot be run by java that expects class version 52.0 (jdk8) and 55.0 (jdk11). Using JDK 17, I verified that I am able to run Derby 10.16.1.1 on my Ubuntu 18 machine. | Bryan |
| OK | Java version compatibility on Windows | On Windows 10, using both JDK 8 and JDK 9, I verified that I got the expected message when I tried to run Derby 10.16.1.1: java.lang.UnsupportedClassVersion message, accurately. Using JDK 17, I verified that I am able to run Derby 10.16.1.1 on my Windows 10 machine | Bryan |
> | Long running tests | ||
> | Performance tests (e.g., org.apache.derbyTesting.perf.clients.Runner) | ||
> | upgrade and compatibility (ask Kathey) | ||
> | Large data volume tests | ||
> | Recovery after crashing engine | ||
> | Java EE CTS | ||
> | Code coverage results | ||
OK | For 10.11 and higher, remove the Lucene jars and the simple json jar from the class path and run the tests with -Dderby.tests.omitLucene=true and -Dderby.tests.omitJson=true | No problems found. | Rick |
OK | Verify that you can upgrade from the release candidate to the development trunk. | Successfully ran upgrade tests on the 10.17.0.0 trunk, using 10.16.1.1 as the starting point of the upgrade trajectory. | Rick |
10.16.1.0 (RC1)
Status | Test | Comment | Tester |
OK | Directory structure should look correct in all zips. | The directory structures look ok in the zip distros. I did not check the tar distros. Discrepancies between 10.16.1.0 and 10.15.2.0 distos are accounted for by differences in the output of the JDK 11 and 17 javadoc tools and by the deletion of Derby source files related to the SecurityManager. | Rick |
FAIL | Links should work in index.html in the bin distribution. | PDFs missing for Reference, Security, Admin, and Tuning Guides. | Rick |
> | bin scripts should work. | ||
OK | No junk files like derby.log | None found in the zip distros. | Rick |
OK | No unnecessary 3rd party jars like Junit | None found in the zip distros. | Rick |
> | Source zip can be used to generate jars and docs | ||
> | Signatures and checksums correct | ||
> | Long running tests | ||
> | Performance tests (e.g., org.apache.derbyTesting.perf.clients.Runner) | ||
> | upgrade and compatibility (ask Kathey) | ||
> | Large data volume tests | ||
> | Recovery after crashing engine | ||
> | Java EE CTS | ||
> | Code coverage results | ||
> | For 10.11 and higher, remove the Lucene jars and the simple json jar from the class path and run the tests with -Dderby.tests.omitLucene=true and -Dderby.tests.omitJson=true | ||
> | Verify that you can upgrade from the release candidate to the development trunk. |