[jira] Updated: (FOR-855) verify the license situation prior to each release

"David Crossley (JIRA)" <[email protected]>
Newsgroups gmane.text.xml.forrest.devel
Message-ID <[email protected]>
     [ https://issues.apache.org/jira/browse/FOR-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Crossley updated FOR-855:
-------------------------------

        Fix Version/s:     (was: 0.9-dev)
                       0.10
    Affects Version/s: 0.10

Done for 0.9

> verify the license situation prior to each release
> --------------------------------------------------
>
>                 Key: FOR-855
>                 URL: https://issues.apache.org/jira/browse/FOR-855
>             Project: Forrest
>          Issue Type: Bug
>          Components: Project administration
>    Affects Versions: 0.9-dev, 0.10
>            Reporter: David Crossley
>            Assignee: David Crossley
>            Priority: Blocker
>             Fix For: 0.10
>
>
> This should be continually happening anyway, but immediately prior to each release we need to verify that our license situation is in order. This issue should not ever be closed, rather just move the "Fix for Version" on to the next release.
> Here are some of the tasks:
> A) Ensure that all supporting libraries have a corresponding license. Basically every jar file or other external package needs to have a *.license.txt file. Ensure that any license conditions are met, e.g. for some we must add an entry to NOTICE.txt, while for some others we must not. Remember to abide by the ASF guidelines (e.g. nothing more restrictive than the Apache License).
> B) Scan the whole trunk repository to add missing ASF license headers to source files and to ensure that the ASF license headers have not been accidently added to external files. See etc/relicense.txt
> C) Remove any author tags.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.