svn commit: r1915030 - /subversion/site/staging/docs/community-guide/releasing.part.html
Author: hartmannathan Date: Sun Dec 31 20:52:20 2023 New Revision: 1915030 URL: http://svn.apache.org/viewvc?rev=1915030&view=rev Log: In 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/staging/docs/community-guide/releasing.part.html Modified: subversion/site/staging/docs/community-guide/releasing.part.html URL: http://svn.apache.org/viewvc/subversion/site/staging/docs/community-guide/releasing.part.html?rev=1915030&r1=1915029&r2=1915030&view=diff == --- subversion/site/staging/docs/community-guide/releasing.part.html (original) +++ subversion/site/staging/docs/community-guide/releasing.part.html Sun Dec 31 20:52:20 2023 @@ -1071,13 +1071,18 @@ the dev@ list. title="Link to this section">¶ -Because Subversion releases are distributed through the -https://www.apache.org/dev/mirrors.html";>ASF mirror network, 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 +Subversion releases are distributed through a global +https://infra.apache.org/release-distribution.html";>Content +Distribution Network (CDN). (This replaced the former +https://www.apache.org/dev/mirrors.html";>ASF mirror network as +of late 2021. Nevertheless, there may exist other organizations that choose +to continue mirroring ASF releases.) + +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 https://www.apache.org/dev/release-signing.html";>cryptographically signed 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">¶ -Subversion artifacts are distributed through the -https://www.apache.org/dev/mirrors.html";>ASF mirror network. The -source code download page 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 +Subversion artifacts are distributed through a global +https://infra.apache.org/release-distribution.html";>Content +Distribution Network (CDN). The source +code download page 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 https://archive.apache.org/dist/subversion/";>archives. -To upload a release to the mirrors: +To upload a release to the CDN: release.py move-to-dist 1.7.0 @@ -1232,17 +1238,17 @@ in the release announcement unless 15 mi committed. 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. It's also a good time to clean out any old releases from ^/release/subversion; 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 ^/release/subversion +for at least 24 hours will continue to remain available in the archives. You +can clean old releases using: release.py clean-dist
svn commit: r1915029 - in /subversion/site/staging: index.html news.html
Author: hartmannathan Date: Sun Dec 31 20:21:15 2023 New Revision: 1915029 URL: http://svn.apache.org/viewvc?rev=1915029&view=rev Log: In site/staging: Add link to 1.14.3 [ANNOUNCE] mail in archives * staging/index.html: (#news-20231228-1.14.3): As above. * staging/news.html (#news-20231228-1.14.3): As above. Modified: subversion/site/staging/index.html subversion/site/staging/news.html Modified: subversion/site/staging/index.html URL: http://svn.apache.org/viewvc/subversion/site/staging/index.html?rev=1915029&r1=1915028&r2=1915029&view=diff == --- subversion/site/staging/index.html (original) +++ subversion/site/staging/index.html Sun Dec 31 20:21:15 2023 @@ -80,12 +80,8 @@ This is the most complete Subversion release to date, and we encourage users of Subversion to upgrade as soon as reasonable. Please see the - release notes for more information about this release. Modified: subversion/site/staging/news.html URL: http://svn.apache.org/viewvc/subversion/site/staging/news.html?rev=1915029&r1=1915028&r2=1915029&view=diff == --- subversion/site/staging/news.html (original) +++ subversion/site/staging/news.html Sun Dec 31 20:21:15 2023 @@ -36,12 +36,8 @@ This is the most complete Subversion release to date, and we encourage users of Subversion to upgrade as soon as reasonable. Please see the - release notes for more information about this release.
svn commit: r1915028 - in /subversion/site/publish: ./ site-nav.html
Author: dsahlberg Date: Sun Dec 31 16:34:08 2023 New Revision: 1915028 URL: http://svn.apache.org/viewvc?rev=1915028&view=rev Log: In site/publish: merge 1915027 from staging * site-nav.html (#copyright): Update year Modified: subversion/site/publish/ (props changed) subversion/site/publish/site-nav.html Propchange: subversion/site/publish/ -- Merged /subversion/site/staging:r1915027 Modified: subversion/site/publish/site-nav.html URL: http://svn.apache.org/viewvc/subversion/site/publish/site-nav.html?rev=1915028&r1=1915027&r2=1915028&view=diff == --- subversion/site/publish/site-nav.html (original) +++ subversion/site/publish/site-nav.html Sun Dec 31 16:34:08 2023 @@ -70,7 +70,7 @@ -Copyright © 2022 https://www.apache.org/"; class="nopadding">The Apache +Copyright © 2023 https://www.apache.org/"; class="nopadding">The Apache Software Foundation, Licensed under the https://www.apache.org/licenses/LICENSE-2.0"; class="nopadding">Apache License, Version 2.0. Apache, Apache Subversion, and
svn commit: r1915027 - /subversion/site/staging/site-nav.html
Author: dsahlberg Date: Sun Dec 31 16:28:31 2023 New Revision: 1915027 URL: http://svn.apache.org/viewvc?rev=1915027&view=rev Log: In site/staging: * site-nav.html (#copyright): Update copyright year now that we've made a release in 2023.. Modified: subversion/site/staging/site-nav.html Modified: subversion/site/staging/site-nav.html URL: http://svn.apache.org/viewvc/subversion/site/staging/site-nav.html?rev=1915027&r1=1915026&r2=1915027&view=diff == --- subversion/site/staging/site-nav.html (original) +++ subversion/site/staging/site-nav.html Sun Dec 31 16:28:31 2023 @@ -70,7 +70,7 @@ -Copyright © 2022 https://www.apache.org/"; class="nopadding">The Apache +Copyright © 2023 https://www.apache.org/"; class="nopadding">The Apache Software Foundation, Licensed under the https://www.apache.org/licenses/LICENSE-2.0"; class="nopadding">Apache License, Version 2.0. Apache, Apache Subversion, and
svn commit: r1915016 - /subversion/site/staging/docs/community-guide/releasing.part.html
Author: dsahlberg Date: Sun Dec 31 10:10:40 2023 New Revision: 1915016 URL: http://svn.apache.org/viewvc?rev=1915016&view=rev Log: In site/staging: * docs/community-guide/releasing.part.html (#releasing-release): Add note how to add the release to reporter.a.o on the command line. Modified: subversion/site/staging/docs/community-guide/releasing.part.html Modified: subversion/site/staging/docs/community-guide/releasing.part.html URL: http://svn.apache.org/viewvc/subversion/site/staging/docs/community-guide/releasing.part.html?rev=1915016&r1=1915015&r2=1915016&view=diff == --- subversion/site/staging/docs/community-guide/releasing.part.html (original) +++ subversion/site/staging/docs/community-guide/releasing.part.html Sun Dec 31 10:10:40 2023 @@ -1249,7 +1249,11 @@ release.py clean-dist Submit the version number of the new release on https://reporter.apache.org/addrelease.html?subversion"; ->reporter.apache.org. (Can we automate that?) +>reporter.apache.org. The following command + +curl -u USERNAME "https://reporter.apache.org/addrelease.py?date=`date +%s`&committee=subversion&version=VERSION&xdate=`date +%F`" + +will add the release, it should probably be added to release.py.
svn commit: r1915015 - /subversion/trunk/subversion/libsvn_subr/sysinfo.c
Author: jun66j5 Date: Sun Dec 31 09:33:34 2023 New Revision: 1915015 URL: http://svn.apache.org/viewvc?rev=1915015&view=rev Log: Correctly report newer macOS version names. * subversion/libsvn_subr/sysinfo.c (release_name_from_version): Detect Ventura (13.x) and Sonoma (14.x). Modified: subversion/trunk/subversion/libsvn_subr/sysinfo.c Modified: subversion/trunk/subversion/libsvn_subr/sysinfo.c URL: http://svn.apache.org/viewvc/subversion/trunk/subversion/libsvn_subr/sysinfo.c?rev=1915015&r1=1915014&r2=1915015&view=diff == --- subversion/trunk/subversion/libsvn_subr/sysinfo.c (original) +++ subversion/trunk/subversion/libsvn_subr/sysinfo.c Sun Dec 31 09:33:34 2023 @@ -1404,13 +1404,10 @@ release_name_from_version(int major, int } break; -case 11: - return "Big Sur"; - break; - -case 12: - return "Monterey"; - break; +case 11: return "Big Sur"; +case 12: return "Monterey"; +case 13: return "Ventura"; +case 14: return "Sonoma"; } } return NULL;
svn commit: r1915014 - /subversion/trunk/subversion/tests/cmdline/getopt_tests.py
Author: jun66j5 Date: Sun Dec 31 09:12:18 2023 New Revision: 1915014 URL: http://svn.apache.org/viewvc?rev=1915014&view=rev Log: Follow-up to r1899721, fix failing getopt_tests.py 2 and 4 on macOS. * subversion/tests/cmdline/getopt_tests.py (del_lines_res): Replace "Mac OS X" with "macOS" in the pattern. Modified: subversion/trunk/subversion/tests/cmdline/getopt_tests.py Modified: subversion/trunk/subversion/tests/cmdline/getopt_tests.py URL: http://svn.apache.org/viewvc/subversion/trunk/subversion/tests/cmdline/getopt_tests.py?rev=1915014&r1=1915013&r2=1915014&view=diff == --- subversion/trunk/subversion/tests/cmdline/getopt_tests.py (original) +++ subversion/trunk/subversion/tests/cmdline/getopt_tests.py Sun Dec 31 09:12:18 2023 @@ -81,7 +81,7 @@ del_lines_res = [ re.compile(r"\* Plaintext cache.*"), re.compile(r"\* Gnome Keyring"), re.compile(r"\* GPG-Agent"), - re.compile(r"\* Mac OS X Keychain"), + re.compile(r"\* macOS Keychain"), re.compile(r"\* KWallet \(KDE\)"), ]
