skrawcz opened a new issue, #1336:
URL: https://github.com/apache/hamilton/issues/1336

   
   - [ ] Migrate license to 2.0 (https://github.com/apache/hamilton/pull/1335)
   - [ ] Are release files in correct location?
   
   - [ ] Do release files have the word incubating in their name? (Note: only 
the release artifacts require "incubating" in their names, jar files (included 
in the binary artifact or deployed onto maven repository) are suggested but not 
required to have "incubating" as name suffix)
   
   - [ ] Are the digital signature and hashes correct?
   
   - [x] Does DISCLAIMER file exist?  
(https://github.com/apache/hamilton/pull/1335)
   
   - [x] Do LICENSE and NOTICE files exists? 
(https://github.com/apache/hamilton/pull/1335)
   
   - [ ]  Is the LICENSE and NOTICE text correct?
   
   - [x] Is the NOTICE year correct? 
(https://github.com/apache/hamilton/pull/1335)
   
   - [ ] Un-included software dependencies are not mentioned in LICENSE or 
NOTICE?
   
   - [ ]  License information is not mentioned in NOTICE?
   
   - [ ] Do the contents of the release match with what's tagged in version 
control?
   
   - [ ]  Are there any unexpected binary files in the release?
   
   - [ ] Can you compile from source? Are the instruction clear?
   
   
   ## Is there any 3rd party code contained inside the release? If so:
   
   - [ ] Does the software have a compatible license?
   
   - [ ] Are all software licenses mentioned in LICENSE?
   
   - [ ]  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 relevant parts of those NOTICE files been added to this NOTICE 
file?
   
   - [ ] Do all source files have ASF headers?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to