THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Any new files added in this release must have a valid license header.
- Make sure any new submodules or dependencies that have been added in this release have been mentioned in the top level LICENSE file - There is no test to cover this (and is a frequent cause of a -1)
- Make sure the Apache RAT test is passing (this is ensured automatically by the PR validation check)
- DISCLAIMER is correct, file names include “incubating”
- Check if the license issues listed in Github are all addressed addressed or they're not the release blocker.
- Major modifications/additions to third-party and dual license should be dealt with on a case-by-case basis by the PMC.
More Details
The top level LICENSE and NOTICE files are correct and dependency licenses are acceptable
- LICENSE and NOTICE files at the root of the artifact directory must only reflect the contents of the artifact in which they are contained.
- Any new dependency with a non-ASF license must be added to the top level LICENSE file as directed in the links below.
- All source files have license headers where appropriate.
- The provenance of all source files is clear (ASF or software grants)
...
- license_header.py can be used to check the potential license issue and add license header if necessary.
Refer to the following Links
...