You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by se...@apache.org on 2023/12/28 17:57:37 UTC
(www-site) branch sebbASF-patch-2 created (now a16c0fca8)
This is an automated email from the ASF dual-hosted git repository.
sebb pushed a change to branch sebbASF-patch-2
in repository https://gitbox.apache.org/repos/asf/www-site.git
at a16c0fca8 Clarifications
This branch includes the following new commits:
new a16c0fca8 Clarifications
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
(www-site) 01/01: Clarifications
Posted by se...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
sebb pushed a commit to branch sebbASF-patch-2
in repository https://gitbox.apache.org/repos/asf/www-site.git
commit a16c0fca88bffe55d64f99ddcda638a25beaeccb
Author: Sebb <se...@users.noreply.github.com>
AuthorDate: Thu Dec 28 17:57:33 2023 +0000
Clarifications
---
content/legal/release-policy.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/legal/release-policy.md b/content/legal/release-policy.md
index e03723086..bdd6dd30f 100644
--- a/content/legal/release-policy.md
+++ b/content/legal/release-policy.md
@@ -71,11 +71,11 @@ contain compiled code.
#### Release signing {#release-signing}
-All supplied packages MUST be cryptographically signed with a detached signature.
+All supplied packages MUST be cryptographically signed with a detached ascii signature.
It MUST be signed by either the Release Manager or the automated release
infrastructure, where the underlying implementation MUST follow the principles
[outlined](/dev/release-signing.html#automated-release-signing) by the Apache
-Security Team. All supplied packages MUST use a detached signature. Those who
+Security Team. Those who
vote +1 for release MAY offer their own cryptographic signature to be concatenated
with the detached signature file (at the Release Manager's discretion)
prior to release.
@@ -83,7 +83,7 @@ prior to release.
#### Compiled packages {#compiled-packages}
The Apache Software Foundation produces open source software. All releases
-are in the form of the source materials needed to make changes to the
+are in the form of the source materials needed to build the
software being released.
As a convenience to users that might not have the appropriate tools to build a
@@ -105,7 +105,7 @@ Policy](/legal/resolved).
Each package MUST provide a `LICENSE` file and a `NOTICE` file which account
for the package's exact content. `LICENSE` and `NOTICE` MUST NOT provide
-unnecessary information about materials which are not bundled in the package,
+information about materials which are not bundled in the package,
such as separately downloaded dependencies.
For source packages, `LICENSE` and `NOTICE` MUST be located at the root of the
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org