[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subversion-commits
Subject:    svn commit: r1914969 - in /subversion/site/publish: ./ docs/community-guide/releasing.part.html
From:       hartmannathan () apache ! org
Date:       2023-12-29 4:14:02
Message-ID: 20231229041402.B0E4017BE25 () svn01-us-east ! apache ! org
[Download RAW message or body]

Author: hartmannathan
Date: Fri Dec 29 04:14:02 2023
New Revision: 1914969

URL: http://svn.apache.org/viewvc?rev=1914969&view=rev
Log:
In site/publish: Merge 1914249, 1914961-1914962, 1914968 from site/staging

* docs/community-guide/releasing.part.html:
  (#adding-changes): Add a clarifying paragraph and a hint for future
   patch-release managers about an easy way to list backports that
   deserve mention in CHANGES.
  (#releasing-upload): Fix typo.
  (#releasing-release): Fix confusing wording.
  (#releasing-release): ASF no longer uses mirrors for download delivery; this
   was replaced by a CDN in October 2021. Update the docs to reflect this,
   especially with respect to the time lag between release and appearance on
   the CDN (previously 24 hours, now 15 minutes according to [1]).

Modified:
    subversion/site/publish/   (props changed)
    subversion/site/publish/docs/community-guide/releasing.part.html

Propchange: subversion/site/publish/
------------------------------------------------------------------------------
  Merged /subversion/site/staging:r1914249,1914961-1914962,1914968

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=1914969&r1=1914968&r2=1914969&view=diff
 ==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Fri Dec 29 \
04:14:02 2023 @@ -1222,13 +1222,14 @@ This moves the tarballs, signatures and
 >^/dev/subversion</a>
 to <a href="https://dist.apache.org/repos/dist/release/subversion"
 >^/release/subversion</a>.
-It takes the mirrors up to 24 hours to get pick up the new release.
-The archive will also automatically pick up the release.  While
-running move-to-dist will move the signature files, committers are
-still able to commit new signatures to <tt>^/release/subversion</tt>;
-however it will take up to 24 hours for those signatures to mirror.
-Any such signatures cannot be included in the release announcement
-unless 24 hours have passed since they were committed.</p>
+It takes the content delivery network (CDN) approximately 15 minutes to
+pick up the new release. The archive will also automatically pick up the
+release. Although running <tt>move-to-dist</tt> will move the signature files,
+committers are still able to commit new signatures
+to <tt>^/release/subversion</tt>; however it will take up to 15 minutes for
+those signatures to appear on the CDN. Any such signatures cannot be included
+in the release announcement unless 15 minutes have passed since they were
+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.
@@ -1766,6 +1767,20 @@ should also add an item to <tt>CHANGES</
 guidelines outlined above.  This list will then be merged to the release
 branch when a patch release is made.</p>
 
+<p>In practice, CHANGES does not get updated each time a fix is
+backported to the release branch. Normally, the release manager updates
+CHANGES as one of the first steps to make a patch release.</p>
+
+<p>A convenient way to get the list of backports that should be mentioned
+in CHANGES is to use the same tool that populates
+<a href="https://subversion.apache.org/docs/release-notes/#upcoming-patch-release"
+>Coming up in the next patch release</a> on the Subversion website. This is
+the <tt>upcoming.py</tt> script in
+<a href="https://svn.apache.org/repos/asf/subversion/site/tools"
+>https://svn.apache.org/repos/asf/subversion/site/tools</a>. Run it while
+the current working directory is the root of a working copy of the minor
+branch.</p>
+
 </div> <!-- adding-changes -->
 
 </div> <!-- the-changes-file -->


[prev in list] [next in list] [prev in thread] [next in thread]