accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r965617 - in /websites/staging/accumulo/trunk/content: ./ verifying_releases.html
Date Wed, 16 Sep 2015 03:26:03 GMT
Author: buildbot
Date: Wed Sep 16 03:26:02 2015
New Revision: 965617

Log:
Staging update by buildbot for accumulo

Modified:
    websites/staging/accumulo/trunk/content/   (props changed)
    websites/staging/accumulo/trunk/content/verifying_releases.html

Propchange: websites/staging/accumulo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Sep 16 03:26:02 2015
@@ -1 +1 @@
-1703321
+1703322

Modified: websites/staging/accumulo/trunk/content/verifying_releases.html
==============================================================================
--- websites/staging/accumulo/trunk/content/verifying_releases.html (original)
+++ websites/staging/accumulo/trunk/content/verifying_releases.html Wed Sep 16 03:26:02 2015
@@ -259,14 +259,30 @@ user convenience only, but still must ad
 some leeway in this rule. For example, test-only binary artifacts (such as test files or
jars) are acceptable as long
 as they are only used for testing the software and not running it.</p>
 <h2 id="apache-software-license-application">Apache Software License Application<a
class="headerlink" href="#apache-software-license-application" title="Permanent link">&para;</a></h2>
-<p>Application of the Apache Software License v2 consists of the following steps on
each artifact in a release.</p>
+<p>Application of the Apache Software License v2 consists of the following steps on
each artifact in a release. It's
+important to remember that for artifacts that contain other artifacts (e.g. a tarball that
contains JAR files or
+an RPM which contains JAR files), both the tarball, RPM and JAR files are subject to the
following roles.</p>
+<p>The difficulty in verifying each artifact is that, often times, each artifact requires
a different LICENSE and NOTICE
+file. For example, the Accumulo binary tarball must contain appropriate LICENSE and NOTICE
files considering the bundled
+jar files in <code>lib/</code>. The Accumulo source tarball would not contain
these same contents in the LICENSE and NOTICE files
+as it does not contain those same JARs.</p>
 <h3 id="license-file">LICENSE file<a class="headerlink" href="#license-file" title="Permanent
link">&para;</a></h3>
-<p>The LICENSE file should be present at the top-level of an artifact. This file should
be explicitly named <code>LICENSE</code>,
+<p>The LICENSE file should be present at the top-level of the artifact. This file should
be explicitly named <code>LICENSE</code>,
 however <code>LICENSE.txt</code> is acceptable but not preferred. This file contains
the text of the Apache Software License 
 at the top of the file. At the bottom of the file, all other open source licenses <em>contained
in the given
 artifact</em> must be listed at the bottom of the LICENSE file. Contained components
that are licensed with the ASL themselves
 do not need to be included in this file. It is common to see inclusions in file such as the
MIT License of 3-clause
 BSD License.</p>
+<h3 id="notice-file">NOTICE file<a class="headerlink" href="#notice-file" title="Permanent
link">&para;</a></h3>
+<p>The NOTICE file should be present at the top-level of the artifact beside the LICENSE
file. This file should be explicitly
+name <code>NOTICE</code>, while <code>NOTICE.txt</code> is also acceptable
but not preferred. This file contains the copyright notice for
+the artifact being released. As a reminder, the copyright is held by the Apache Software
Foundation, not the individual
+project.</p>
+<p>The second purpose this file serves is to distribute third-party notices from dependent
software. Specifically, other code
+which is licensed with the ASLv2 may also contain a NOTICE file. If such an artifact which
contains a NOTICE file is
+contained in artifact being verified for releases, the contents of the contained artifact's
NOTICE file should be appended
+to this artifact's NOTICE file. For example, Accumulo bundles the Apache Thrift libthrift
JAR file which also have its
+own NOTICE file. The contents of the Apache Thrift NOTICE file should be included within
Accumulo's NOTICE file.</p>
   </div>
 
   <div id="footer">



Mime
View raw message