[
https://issues.apache.org/jira/browse/HADOOP-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15746176#comment-15746176
]
Xiao Chen commented on HADOOP-13780:
------------------------------------
In the faith of unblocking 3.0.0-alpha2 release, how do people feel about doing
#1 and #2 from [my above
comment|https://issues.apache.org/jira/browse/HADOOP-13780?focusedCommentId=15723765&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15723765]
in this jira, and defer the automation #3 to another jira? #1 is almost done,
and #2 shouldn't be too hard. So should be able to post a patch this week.
I have some local nasty scripts to sort of automate this, with some things that
need manual inspection. However even myself feel those scripts are not to the
standards... don't want them to block our mighty hadoop release.
> LICENSE/NOTICE are out of date for source artifacts
> ---------------------------------------------------
>
> Key: HADOOP-13780
> URL: https://issues.apache.org/jira/browse/HADOOP-13780
> Project: Hadoop Common
> Issue Type: Bug
> Components: common
> Affects Versions: 3.0.0-alpha2
> Reporter: Sean Busbey
> Assignee: Xiao Chen
> Priority: Blocker
>
> we need to perform a check that all of our bundled works are properly
> accounted for in our LICENSE/NOTICE files.
> At a minimum, it looks like HADOOP-10075 introduced some changes that have
> not been accounted for.
> e.g. the jsTree plugin found at
> {{hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/resources/webapps/static/jt/jquery.jstree.js}}
> does not show up in LICENSE.txt to (a) indicate that we're redistributing it
> under the MIT option and (b) give proper citation of the original copyright
> holder per ASF policy.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
