THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
When committers test a new release candidate and vote for approving (or not approving it), they usually post a checklist showing what they verified to explain their vote. A very thorough person might post check off an exhaustive checklist like the below one, although many post use shorter checklists:
Code Block | ||||
---|---|---|---|---|
| ||||
+1 [OK] verified signature of git tag [OK] verified hashes and signatures of source and helper binaries [OK] verified all signatures use key in KEYS with apache email address [OK] verified source has no unexpected binary files [OK] verified source and git tag are same minus KEYS file [OK] verified source and helper binaries include LICENSE/NOTICE/README [OK] verified LICENSE/NOTICE/README look correct [OK] verified online JavaDoc and ScalaDoc docs look correct [OK] compiled source and ran all tests & ratCheck (LANG set to both en_US and de_DE) [OK] verified jars built from source have same content as helper binary jars [OK] verified JavaDoc and ScalaDoc docs look correct [OK] verified dependencies in helper binaries are same as in maven poms [OK] tested bin & msi & rpm installers and checked "daffodil --version" output from each [OK] verified some public and private DFDL schema projects pass tests calling new release |
...