Author: hartmannathan
Date: Fri Jan 5 19:30:37 2024
New Revision: 1915096
URL: http://svn.apache.org/viewvc?rev=1915096&view=rev
Log:
In site/publish: Merge r1915030 from site/staging
* docs/community-guide/releasing.part.html
(#releasing-signing-why, #releasing-release, #releasing-upload): ASF
switched from a mirror network to a global CDN in late 2021. Update these
sections accordingly.
Modified:
subversion/site/publish/ (props changed)
subversion/site/publish/docs/community-guide/releasing.part.html
Propchange: subversion/site/publish/
------------------------------------------------------------------------------
Merged /subversion/site/staging:r1915030
Modified: subversion/site/publish/docs/community-guide/releasing.part.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/releasing.part.html?rev=1915096&r1=1915095&r2=1915096&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Fri Jan 5
19:30:37 2024
@@ -1071,13 +1071,18 @@ the dev@ list.</p>
title="Link to this section">¶</a>
</h4>
-<p>Because Subversion releases are distributed through the
-<a href="https://www.apache.org/dev/mirrors.html";>ASF mirror network</a>, it
-is important that end-users be able to verify the authenticity of the source
-code packages they download. Checksums are sufficient to detect corruption
-in the download process, but to prevent a malicious individual or mirror
-operator from distributing replacement packages, each source code package
-must be
+<p>Subversion releases are distributed through a global
+<a href="https://infra.apache.org/release-distribution.html";>Content
+Distribution Network</a> (CDN). (This replaced the former
+<a href="https://www.apache.org/dev/mirrors.html";>ASF mirror network</a> as
+of late 2021. Nevertheless, there may exist other organizations that choose
+to continue mirroring ASF releases.)</p>
+
+<p>It is important that end-users be able to verify the authenticity of the
+source code packages they download. Checksums are sufficient to detect
+corruption in the download process, but to prevent a malicious individual or
+mirror operator from distributing replacement packages, each source code
+package must be
<a href="https://www.apache.org/dev/release-signing.html";>cryptographically
signed</a> by members of the Subversion PMC. These
signatures are done using each committer's private PGP key, and are then
@@ -1205,15 +1210,16 @@ steps needed to publish a Subversion rel
title="Link to this section">¶</a>
</h4>
-<p>Subversion artifacts are distributed through the
-<a href="https://www.apache.org/dev/mirrors.html";>ASF mirror network</a>. The
-source code <a href="/download.cgi">download page</a> automatically assists
users
-in selecting mirrors closer to them. We usually host only the latest stable
-release for the supported release lines on the mirror network, while all
-previous Subversion releases are available in the
+<p>Subversion artifacts are distributed through a global
+<a href="https://infra.apache.org/release-distribution.html";>Content
+Distribution Network</a> (CDN). The source
+code <a href="/download.cgi">download page</a> automatically assists users
+in selecting a suitable download link. We usually host only the latest
+stable release for the supported release lines on the project's distribution
+directory, while all previous Subversion releases are available in the
<a href="https://archive.apache.org/dist/subversion/";>archives</a>.</p>
-<p>To upload a release to the mirrors:
+<p>To upload a release to the CDN:
<pre>
release.py move-to-dist 1.7.0
</pre>
@@ -1232,17 +1238,17 @@ in the release announcement unless 15 mi
committed.</p>
<p>At this point, the release may be publicly available, but its still a good
-idea to hold off on announcing it until after the mirrors have picked it up.
-After the 24 hour period has passed, giving the mirrors enough time to sync,
-the release manager will send the announcement and publish the changes to the
+idea to hold off on announcing it until after the CDN has picked it up. After
+the 15 minute period has passed, giving the CDN enough time to sync, the
+release manager will send the announcement and publish the changes to the
Subversion website, as described below.</p>
<p>It's also a good time to clean out any old releases from
<tt>^/release/subversion</tt>; only
the most recent release for each supported release line should be in that
-directory. The mirrors will eventually remove the older releases, but they
-will continue to remain available in the archives. You can clean old
-releases using:
+directory. Releases that have been available at <tt>^/release/subversion</tt>
+for at least 24 hours will continue to remain available in the archives. You
+can clean old releases using:
<pre>
release.py clean-dist
</pre>
