...
Note that this is not official policy but may help with checking releases.
Fill in the following:
- Are ☐ Are release files in correct location?
- Do ☐ Do release files have the word incubating in their name?
- Are ☐ Are the digital signature and hashes correct?
- Does ☐ Does DISCLAIMER file exist?
- Do ☐ Do LICENSE and NOTICE files exists?
- Is ☐ Is the LICENSE and NOTICE text correct?
- Is ☐ Is the NOTICE year correct?
- Un☐ Un-included software dependencies are not mentioned in LICENSE or NOTICE?
- License ☐ License information is not mentioned in NOTICE?
- Is there any 3rd party code contained inside the release? If so:
- Does ☐ Does the software have a compatible license?
- Are ☐ Are all software licenses mentioned in LICENSE?
- Is ☐ Is the full text of the licenses (or pointers to it) in LICENSE?
- Is any of this code Apache licensed? Do they have NOTICE files? If so:
- Have ☐ Have relevant parts of those NOTICE files been added to this NOTICE file?
- Do ☐ Do all source files have ASF headers?
- Do ☐ Do the contents of the release match with what's tagged in version control?
- Are ☐ Are there any unexpected binary files in the release?
- Can ☐ Can you compile from source? Are the instruction clear?
- Is the issue minor?
- Yes No ☐ Yes ☐ No ☐ Unsure
- Could it possibly be fixed in the next release?
- Yes No Unsure ☐ Yes ☐ No ☐ Unsure
- I vote with:
- ☐ +1 release the software
- ☐ +0 not sure if it should be released
- ☐ -1 don’t release the software because...