accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From els...@apache.org
Subject svn commit: r1703739 - /accumulo/site/trunk/content/verifying_releases.mdtext
Date Fri, 18 Sep 2015 04:10:07 GMT
Author: elserj
Date: Fri Sep 18 04:10:06 2015
New Revision: 1703739

URL: http://svn.apache.org/viewvc?rev=1703739&view=rev
Log:
Fix typo, add foundation-level doc links

Modified:
    accumulo/site/trunk/content/verifying_releases.mdtext

Modified: accumulo/site/trunk/content/verifying_releases.mdtext
URL: http://svn.apache.org/viewvc/accumulo/site/trunk/content/verifying_releases.mdtext?rev=1703739&r1=1703738&r2=1703739&view=diff
==============================================================================
--- accumulo/site/trunk/content/verifying_releases.mdtext (original)
+++ accumulo/site/trunk/content/verifying_releases.mdtext Fri Sep 18 04:10:06 2015
@@ -40,6 +40,9 @@ Information on these tests can be found
 for days on end while injecting faults into the system. These are the tests that truly verify
the correctness of
 Accumulo on real systems.
 
+More information on these tests, and the requirements in running them for a given release,
can be found on the
+[governance page on releasing][1]
+
 ## Foundation Level Requirements ##
 
 The ASF requires that all artifacts in a release are cryptographically signed and distributed
with hashes.
@@ -49,13 +52,20 @@ Verification of a release artifact can b
 can be verified using the appropriate command (e.g. `sha1sum`, `md5sum`).
 
 An Apache release must contain a source-only artifact. This is the official release artifact.
While a release of
-and Apache project can contain other artifacts that do contain binary files. These non-source
artifacts are for
+an Apache project can contain other artifacts that do contain binary files. These non-source
artifacts are for
 user convenience only, but still must adhere to the same licensing rules.
 
 PMC members should take steps to verify that the source-only artifact does not contain any
binary files. There is
 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.
 
+The following are the aforementioned Foundation-level documents provided for reference:
+
+* [Applying the Apache Software License][2]
+* [Legal's license application guidelines][3]
+* [Common legal-discuss mailing list questions/resolutions][4]
+* [ASF Legal Affairs Page][5]
+
 ## Apache Software License Application ##
 
 Application of the Apache Software License v2 consists of the following steps on each artifact
in a release. It's
@@ -87,4 +97,10 @@ The second purpose this file serves is t
 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.
\ No newline at end of file
+own NOTICE file. The contents of the Apache Thrift NOTICE file should be included within
Accumulo's NOTICE file.
+
+[1]: /governance/releasing.html#testing
+[2]: http://www.apache.org/dev/apply-license.html
+[3]: http://www.apache.org/legal/src-headers.html
+[4]: http://apache.org/legal/resolved.html
+[5]: http://www.apache.org/legal/
\ No newline at end of file



Mime
View raw message