hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-18680) Document things to consider / document when changing dependencies
Date Fri, 25 Aug 2017 00:26:00 GMT
Sean Busbey created HBASE-18680:

             Summary: Document things to consider / document when changing dependencies
                 Key: HBASE-18680
                 URL: https://issues.apache.org/jira/browse/HBASE-18680
             Project: HBase
          Issue Type: Task
          Components: community, documentation
            Reporter: Sean Busbey

While reviewing HBASE-18674 ("upgrade hbase to commons-lang 3"), I realized that my questions
are the same as I'd give for any dependency change. We should try to update our docs to proactively
push folks on checking whenever a dependency changes (paraphrased):

# What's the license of the direct dependency overall?
# Does it contain parts that are under a different license (esp if the overall is ALv2)?
# If it is ALv2 does it contain a NOTICE file? If so, do we need to update our NOTICE file
based on it?
# Does it change the set of transitive dependencies? If so, apply the same questions above
to that set of changes.

This message was sent by Atlassian JIRA

View raw message