You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by sv...@apache.org on 2022/03/28 04:15:02 UTC
svn commit: r1899276 - /subversion/site/publish/upcoming.part.html
Author: svn-role
Date: Mon Mar 28 04:15:01 2022
New Revision: 1899276
URL: http://svn.apache.org/viewvc?rev=1899276&view=rev
Log:
* upcoming.part.html: Automatically regenerated
Modified:
subversion/site/publish/upcoming.part.html
Modified: subversion/site/publish/upcoming.part.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/upcoming.part.html?rev=1899276&r1=1899275&r2=1899276&view=diff
==============================================================================
--- subversion/site/publish/upcoming.part.html (original)
+++ subversion/site/publish/upcoming.part.html Mon Mar 28 04:15:01 2022
@@ -2,6 +2,470 @@
<pre style="border-style: none">
Changes in ^/subversion/branches/1.14.x:
------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1877978">r1877978</a> | svn-role | 2020-05-21 04:00:13 +0000 (Thu, 21 May 2020) | 7 lines
+
+Merge <a href="https://svn.apache.org/r1877788">r1877788</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1877788">r1877788</a>
+ Fix a broken link in a docstring.
+ Votes:
+ +1: danielsh, stsp
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1878211">r1878211</a> | svn-role | 2020-05-28 04:00:12 +0000 (Thu, 28 May 2020) | 10 lines
+
+Merge <a href="https://svn.apache.org/r1877072">r1877072</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1877072">r1877072</a>
+ svnmucc: Change an error message to state another possible cause of the
+ error.
+ Justification:
+ Error messages should be accurate. User reported (<a href="/issue-4854">issue #4854</a>).
+ Votes:
+ +1: danielsh, stsp, jcorvel
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1878213">r1878213</a> | svn-role | 2020-05-28 04:00:16 +0000 (Thu, 28 May 2020) | 11 lines
+
+Merge <a href="https://svn.apache.org/r1877259">r1877259</a> from trunk:
+
+* <a href="https://svn.apache.org/r1877259">r1877259</a>
+ Move variable declarations to the start of block the to fix
+ syntax errors with VC9 (Visual Studio 2008).
+ Justification:
+ Our code should be C90.
+ Votes:
+ +1: brane, stsp, jcorvel
+ +0: danielsh (from dev@)
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1878415">r1878415</a> | svn-role | 2020-06-03 04:00:20 +0000 (Wed, 03 Jun 2020) | 12 lines
+
+Merge the <a href="https://svn.apache.org/r1876707">r1876707</a> group from trunk:
+
+ * <a href="https://svn.apache.org/r1876707">r1876707</a>, <a href="https://svn.apache.org/r1876734">r1876734</a>, <a href="https://svn.apache.org/r1877318">r1877318</a>, <a href="https://svn.apache.org/r1877712">r1877712</a>, <a href="https://svn.apache.org/r1878141">r1878141</a>, <a href="https://svn.apache.org/r1878142">r1878142</a>, <a href="https://svn.apache.org/r1878143">r1878143</a>,
+ <a href="https://svn.apache.org/r1878144">r1878144</a>
+ Various fixes for making the test suite run correctly with Python 3 on
+ Windows.
+ Justification:
+ Our test suite should test Subversion correctly also on Windows with
+ Python 3
+ Votes:
+ +1: futatuki, jcorvel, stsp
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1879245">r1879245</a> | svn-role | 2020-06-27 04:00:12 +0000 (Sat, 27 Jun 2020) | 11 lines
+
+Merge <a href="https://svn.apache.org/r1876662">r1876662</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1876662">r1876662</a>
+ Avoid check for SWIG version for Python bindings when --without-swig is
+ passed.
+ Justification:
+ SWIG python bindings should be able to be built without SWIG when we use
+ the release tarball
+ Votes:
+ +1: futatuki, stsp, rhuijben
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1879246">r1879246</a> | svn-role | 2020-06-27 04:00:17 +0000 (Sat, 27 Jun 2020) | 10 lines
+
+Merge <a href="https://svn.apache.org/r1876906">r1876906</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1876906">r1876906</a>
+ Make gen-make.py --debug work with Python 3
+ Justification:
+ We should also be able to build in Debug configuration with Python 3
+ on Windows.
+ Votes:
+ +1: jcorvel, stsp, rhuijben
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1879797">r1879797</a> | svn-role | 2020-07-12 04:00:12 +0000 (Sun, 12 Jul 2020) | 10 lines
+
+Merge <a href="https://svn.apache.org/r1876410">r1876410</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1876410">r1876410</a>
+ Fix the .editorconfig stanza for Makefile's.
+ Justification:
+ Make $EDITOR do the right thing on any backport branches we may create
+ off this stabilization branch.
+ Votes:
+ +1: danielsh, stsp, jamessan
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1879798">r1879798</a> | svn-role | 2020-07-12 04:00:17 +0000 (Sun, 12 Jul 2020) | 9 lines
+
+Merge <a href="https://svn.apache.org/r1878413">r1878413</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1878413">r1878413</a>
+ autogen.sh: Remove per SWIG bindings checked files on release mode.
+ Justification:
+ The release tarballs should not contain .swig_*_checked files
+ Votes:
+ +1: futatuki, rhuijben, jamessan
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1879799">r1879799</a> | svn-role | 2020-07-12 04:00:23 +0000 (Sun, 12 Jul 2020) | 9 lines
+
+Merge the <a href="https://svn.apache.org/r1878909">r1878909</a> group from trunk:
+
+ * <a href="https://svn.apache.org/r1878909">r1878909</a>, <a href="https://svn.apache.org/r1878918">r1878918</a>, <a href="https://svn.apache.org/r1878950">r1878950</a>
+ Fix a number of thinkos in human-readable file size formatting.
+ Justification:
+ Fixes wrong output and an assertion failure in debug mode.
+ Votes:
+ +1: brane, rhuijben, jamessan
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1879800">r1879800</a> | svn-role | 2020-07-12 04:00:28 +0000 (Sun, 12 Jul 2020) | 14 lines
+
+Merge <a href="https://svn.apache.org/r1879198">r1879198</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1879198">r1879198</a>
+ Fix an invalid quoting in working copy upgrade system that only works
+ because SQLite automatically fixed this. More recent SQLite functions
+ will signal an error when deprecated features are disabled.
+ Justification:
+ Causes user-visible errors.
+ Note:
+ This filechange by itself doesn't trigger a change that make will
+ handle. So make sure you recompile the sql queries for testing.
+ Votes:
+ +1: rhuijben, danielsh, jamessan
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1880465">r1880465</a> | svn-role | 2020-07-31 04:00:11 +0000 (Fri, 31 Jul 2020) | 10 lines
+
+Merge <a href="https://svn.apache.org/r1877960">r1877960</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1877960">r1877960</a>
+ INSTALL (I.C.12): Add Note that non-release mode is required for building
+ SWIG Python 2 bindings.
+ Justification:
+ We've not entirely dropped Python 2 bindings support on 1.14.x yet
+ Votes:
+ +1: futatuki, stsp, rhuijben
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1880916">r1880916</a> | svn-role | 2020-08-17 04:00:17 +0000 (Mon, 17 Aug 2020) | 11 lines
+
+Merge the 1.14.x-<a href="https://svn.apache.org/r1880374">r1880374</a>-fsfs branch:
+
+ * <a href="https://svn.apache.org/r1880374">r1880374</a>:subversion/libsvn_fs_fs
+ Fix an uninitialized read in svn_fs_fs__index_append().
+ Justification:
+ Uninitialized reads are potentially undefined behaviour.
+ Branch:
+ 1.14.x-<a href="https://svn.apache.org/r1880374">r1880374</a>-fsfs
+ Votes:
+ +1: danielsh, hartmannathan, jamessan
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1881075">r1881075</a> | svn-role | 2020-08-22 04:00:21 +0000 (Sat, 22 Aug 2020) | 9 lines
+
+Merge <a href="https://svn.apache.org/r1880886">r1880886</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1880886">r1880886</a>
+ Fix crash in JavaHL JNI wrapper caused by object lifetimes
+ Justification:
+ Fixes a crash encountered with GCC 10.
+ Votes:
+ +1: hartmannathan, jamessan
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1883406">r1883406</a> | svn-role | 2020-11-14 04:00:12 +0000 (Sat, 14 Nov 2020) | 9 lines
+
+Merge the <a href="https://svn.apache.org/r1878855">r1878855</a> group from trunk:
+
+ * <a href="https://svn.apache.org/r1878855">r1878855</a>, <a href="https://svn.apache.org/r1878859">r1878859</a>
+ Make the hot-backup.py script work with Python 3.
+ Justification:
+ Script should work with Python3
+ Votes:
+ +1: jamessan, brane
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1883407">r1883407</a> | svn-role | 2020-11-14 04:00:17 +0000 (Sat, 14 Nov 2020) | 9 lines
+
+Merge <a href="https://svn.apache.org/r1882115">r1882115</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1882115">r1882115</a>
+ JavaHL: Fix incorrect cache in SVNBase::createCppBoundObject
+ Justification:
+ Fixes a potential crash.
+ Votes:
+ +1: hartmannathan, brane
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1884481">r1884481</a> | svn-role | 2020-12-16 04:00:11 +0000 (Wed, 16 Dec 2020) | 9 lines
+
+Merge <a href="https://svn.apache.org/r1882157">r1882157</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1882157">r1882157</a>
+ Do not suggest --help -v for commands which do not support -v.
+ Justification:
+ The --help message for several commands is misleading. User complained.
+ Votes:
+ +1: stsp, brane, jcorvel
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1884482">r1884482</a> | svn-role | 2020-12-16 04:00:16 +0000 (Wed, 16 Dec 2020) | 9 lines
+
+Merge <a href="https://svn.apache.org/r1877338">r1877338</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1877338">r1877338</a>
+ Add SWIG4 support for SWIG Python binding on Windows.
+ Justification:
+ SWIG Python bindings should be able to build with SWIG4 on Windows, too
+ Votes:
+ +1: futatuki, jun66j5, jcorvel
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1884483">r1884483</a> | svn-role | 2020-12-16 04:00:22 +0000 (Wed, 16 Dec 2020) | 9 lines
+
+Merge <a href="https://svn.apache.org/r1883335">r1883335</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1883335">r1883335</a>
+ Fix unable to load *.pyd files with Python 3.8.x on Windows.
+ Justification:
+ Make Python bindings available with Python 3.8+ on Windows.
+ Votes:
+ +1: jun66j5, jcorvel
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1884484">r1884484</a> | svn-role | 2020-12-16 04:00:27 +0000 (Wed, 16 Dec 2020) | 10 lines
+
+Merge <a href="https://svn.apache.org/r1883337">r1883337</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1883337">r1883337</a>
+ Remove uses of os.dup2() from run_tests.py in order to adapt the new
+ console reader and writer on Windows since Python 3.6.
+ Justification:
+ PYTHONLEGACYWINDOWSSTDIO is no longer needed to run unit tests on Windows.
+ Votes:
+ +1: jun66j5, jcorvel
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1884535">r1884535</a> | svn-role | 2020-12-17 04:00:12 +0000 (Thu, 17 Dec 2020) | 9 lines
+
+Merge <a href="https://svn.apache.org/r1883570">r1883570</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1883570">r1883570</a>
+ Fix C4204 errors while building swig-py with Python 3.9 on Windows.
+ Justification:
+ Allow building Python bindings with Python 3.9 on Windows.
+ Votes:
+ +1: jun66j5, jcorvel
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1884589">r1884589</a> | svn-role | 2020-12-18 04:00:24 +0000 (Fri, 18 Dec 2020) | 9 lines
+
+Merge the <a href="https://svn.apache.org/r1881958">r1881958</a> group from trunk:
+
+ * <a href="https://svn.apache.org/r1881958">r1881958</a>, 1882128
+ Restoring support for building with APR 1.4.
+ Justification:
+ Allow building on older distros such as CentOS 7.
+ Votes:
+ +1: brane, hartmannathan, julianfoad
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1884590">r1884590</a> | svn-role | 2020-12-18 04:00:28 +0000 (Fri, 18 Dec 2020) | 12 lines
+
+Merge <a href="https://svn.apache.org/r1882326">r1882326</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1882326">r1882326</a>
+ Fix <a href="/issue-4762">issue #4762</a> "authz doesn't combine global and repository rules"
+ Justification:
+ Restore behaviour of SVN 1.9: It is now again possible to override
+ per-path access rules for specific users (and groups) at the global
+ level. Such global rules are overridden by repository-specific rules
+ only if both the user and the path match the repository-specific rule.
+ Votes:
+ +1: stsp, brane, jcorvel
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1884591">r1884591</a> | svn-role | 2020-12-18 04:00:36 +0000 (Fri, 18 Dec 2020) | 10 lines
+
+Merge the <a href="https://svn.apache.org/r1878997">r1878997</a> group from trunk:
+
+ * <a href="https://svn.apache.org/r1878997">r1878997</a>, <a href="https://svn.apache.org/r1879192">r1879192</a>, <a href="https://svn.apache.org/r1879474">r1879474</a>, <a href="https://svn.apache.org/r1879959">r1879959</a>
+ Fix <a href="/issue-4859">issue #4859</a>, Merge removing a folder with non-inheritable mergeinfo
+ -> E155023: can't set properties: invalid status for updating properties
+ Justification:
+ Annoying failure, encountered in real use.
+ Votes:
+ +1: julianfoad, hartmannathan, jcorvel
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1884592">r1884592</a> | svn-role | 2020-12-18 04:00:41 +0000 (Fri, 18 Dec 2020) | 9 lines
+
+Merge <a href="https://svn.apache.org/r1875675">r1875675</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1875675">r1875675</a>
+ Rewrite load_normalize_node_props to avoid literal trailing spaces.
+ Justification:
+ Prevents the bug fixed in <a href="https://svn.apache.org/r1875620">r1875620</a> from recurring.
+ Votes:
+ +1: danielsh, brane, jcorvel
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1884617">r1884617</a> | svn-role | 2020-12-19 04:00:12 +0000 (Sat, 19 Dec 2020) | 11 lines
+
+Merge <a href="https://svn.apache.org/r1880192">r1880192</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1880192">r1880192</a>
+ Fix <a href="/issue-4862">issue #4862</a> "Merge: the resulting mergeinfo is non-deterministic".
+ Justification:
+ Non-deterministic merge result is bad.
+ Depends:
+ <a href="https://svn.apache.org/r1878997">r1878997</a>, <a href="https://svn.apache.org/r1879192">r1879192</a>, <a href="https://svn.apache.org/r1879474">r1879474</a>, <a href="https://svn.apache.org/r1879959">r1879959</a> (Fix <a href="/issue-4859">issue #4859</a>)
+ Votes:
+ +1: julianfoad, hartmannathan, jcorvel
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1884618">r1884618</a> | svn-role | 2020-12-19 04:00:18 +0000 (Sat, 19 Dec 2020) | 11 lines
+
+Merge the <a href="https://svn.apache.org/r1881985">r1881985</a> group from trunk:
+
+ * <a href="https://svn.apache.org/r1881985">r1881985</a>, <a href="https://svn.apache.org/r1882105">r1882105</a>
+ Follow up to <a href="https://svn.apache.org/r1880192">r1880192</a>: Fix an EOL issue in test on Windows.
+ Justification:
+ We should test correctly on Windows environment, too.
+ Depends:
+ <a href="https://svn.apache.org/r1880192">r1880192</a>
+ Votes:
+ +1: futatuki, jcorvel, hartmannathan
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1884665">r1884665</a> | svn-role | 2020-12-21 04:00:12 +0000 (Mon, 21 Dec 2020) | 10 lines
+
+Merge <a href="https://svn.apache.org/r1884642">r1884642</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1884642">r1884642</a>
+ Fix win-tests.py is unable to load Python bindings with debug configuration
+ since Python 3.5.
+ Justification:
+ Allow unit tests with debug configuration on Windows.
+ Votes:
+ +1: jun66j5, jcorvel
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1885507">r1885507</a> | svn-role | 2021-01-15 04:00:13 +0000 (Fri, 15 Jan 2021) | 11 lines
+
+Merge <a href="https://svn.apache.org/r1885112">r1885112</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1885112">r1885112</a>
+ swig-py: Fix a typo in tests.
+ Justification:
+ This typo causes DeprecationWarning since Python 3.6 and it will be
+ Syntax error.
+ Votes:
+ +1: futatuki
+ +0: jcorvel
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1885828">r1885828</a> | svn-role | 2021-01-23 04:00:42 +0000 (Sat, 23 Jan 2021) | 9 lines
+
+Merge <a href="https://svn.apache.org/r1885795">r1885795</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1885795">r1885795</a>
+ Update copyright year to 2021.
+ Justification:
+ The future is here!
+ Votes:
+ +1: stsp, futatuki, jcorvel
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1885829">r1885829</a> | svn-role | 2021-01-23 04:00:51 +0000 (Sat, 23 Jan 2021) | 9 lines
+
+Merge the <a href="https://svn.apache.org/r1884427">r1884427</a> group from trunk:
+
+ * <a href="https://svn.apache.org/r1884427">r1884427</a>, <a href="https://svn.apache.org/r1885557">r1885557</a>, <a href="https://svn.apache.org/r1885600">r1885600</a>, <a href="https://svn.apache.org/r1885656">r1885656</a>, <a href="https://svn.apache.org/r1885784">r1885784</a>, <a href="https://svn.apache.org/r1885785">r1885785</a>
+ Make mailer.py work properly with Python 3.
+ Justification:
+ Hook scripts should support Python 3 on 1.14.x.
+ Votes:
+ +1: stsp, futatuki
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1885931">r1885931</a> | svn-role | 2021-01-27 04:00:18 +0000 (Wed, 27 Jan 2021) | 10 lines
+
+Merge <a href="https://svn.apache.org/r1877794">r1877794</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1877794">r1877794</a>
+ Use Doxygen comment leader for comments with doxygen syntax.
+ Justification:
+ Improve $EDITOR's syntax highlighting.
+ Votes:
+ +0: danielsh
+ +1: brane, jamessan
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1886041">r1886041</a> | svn-role | 2021-01-30 04:00:44 +0000 (Sat, 30 Jan 2021) | 9 lines
+
+Merge <a href="https://svn.apache.org/r1882234">r1882234</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1882234">r1882234</a>
+ Fix file name to edit from utf8 to local style.
+ Justification:
+ Editor invocation should work correctly in any valid locale.
+ Votes:
+ +1: futatuki, jcorvel, stsp
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1886042">r1886042</a> | svn-role | 2021-01-30 04:00:48 +0000 (Sat, 30 Jan 2021) | 12 lines
+
+Merge <a href="https://svn.apache.org/r1885953">r1885953</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1885953">r1885953</a>
+ Fix file name encoding and quoting when invoking editor on Windows.
+ Justification:
+ Invoking editor with special character or spaces in path is broken
+ on Windows.
+ Depends:
+ <a href="https://svn.apache.org/r1882234">r1882234</a>
+ Votes:
+ +1: jcorvel, futatuki, stsp
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1886043">r1886043</a> | svn-role | 2021-01-30 04:00:53 +0000 (Sat, 30 Jan 2021) | 9 lines
+
+Merge <a href="https://svn.apache.org/r1886019">r1886019</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1886019">r1886019</a>
+ Fix a potential NULL dereference in the config file parser.
+ Justification:
+ Missing return value check. C is hard.
+ Votes:
+ +1: stsp, hartmannathan, jcorvel
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1886044">r1886044</a> | svn-role | 2021-01-30 04:00:58 +0000 (Sat, 30 Jan 2021) | 9 lines
+
+Merge <a href="https://svn.apache.org/r1885983">r1885983</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1885983">r1885983</a>
+ Fix <a href="/issue-4869">issue #4869</a>: 'svn info --xml' gives wrong 'source-right' of conflict
+ Justification:
+ Bugfix; 'svn info --xml' should give correct results; user complained.
+ Votes:
+ +1: hartmannathan, stsp, jcorvel
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1886045">r1886045</a> | svn-role | 2021-01-30 04:01:04 +0000 (Sat, 30 Jan 2021) | 9 lines
+
+Merge <a href="https://svn.apache.org/r1886029">r1886029</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1886029">r1886029</a>
+ Fix several crashes and JNI warnings in javahl TunnelAgent.
+ Justification:
+ JavaHL shouldn't crash.
+ Votes:
+ +1: jcorvel, amiloslavskiy
+
+------------------------------------------------------------------------
<a href="https://svn.apache.org/r1889654">r1889654</a> | svn-role | 2021-05-08 04:00:13 +0000 (Sat, 08 May 2021) | 7 lines
Merge <a href="https://svn.apache.org/r1889487">r1889487</a> from trunk:
@@ -62,6 +526,65 @@ Merge <a href="https://svn.apache.org/r1
+1: jun66j5, futatuki
------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1899255">r1899255</a> | svn-role | 2022-03-27 18:03:44 +0000 (Sun, 27 Mar 2022) | 9 lines
+
+Merge <a href="https://svn.apache.org/r1886708">r1886708</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1886708">r1886708</a>
+ swig-py: Fix dependency of make copy-swig-py target.
+ Justification:
+ Fix a regression introduced between 1.13.0 and 1.14.0.
+ Votes:
+ +1: futatuki, jun66j5
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1899256">r1899256</a> | svn-role | 2022-03-27 18:03:45 +0000 (Sun, 27 Mar 2022) | 7 lines
+
+Merge the <a href="https://svn.apache.org/r1883838">r1883838</a> group from trunk:
+
+ * <a href="https://svn.apache.org/r1883838">r1883838</a>, <a href="https://svn.apache.org/r1883989">r1883989</a>, <a href="https://svn.apache.org/r1886460">r1886460</a>, <a href="https://svn.apache.org/r1886582">r1886582</a>
+ Add test coverage for CVE-2020-17525 (mod_authz_svn NULL deref)
+ Votes:
+ +1: stsp, markphip, hartmannathan
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1899257">r1899257</a> | svn-role | 2022-03-27 18:03:46 +0000 (Sun, 27 Mar 2022) | 9 lines
+
+Merge the <a href="https://svn.apache.org/r1887641">r1887641</a> group from trunk:
+
+ * <a href="https://svn.apache.org/r1887641">r1887641</a>, <a href="https://svn.apache.org/r1890013">r1890013</a>
+ Fix encoding of error message on failure of system() call.
+ Justification:
+ Error messages should be displayed correctly even if non UTF-8 locale.
+ Votes:
+ +1: futatuki, markphip, hartmannathan
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1899258">r1899258</a> | svn-role | 2022-03-27 18:03:47 +0000 (Sun, 27 Mar 2022) | 9 lines
+
+Merge <a href="https://svn.apache.org/r1889629">r1889629</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1889629">r1889629</a>
+ Document how the port number is passed to custom tunnels.
+ Justification:
+ Documentation should be complete.
+ Votes:
+ +1: danielsh, markphip, hartmannathan
+
+------------------------------------------------------------------------
+<a href="https://svn.apache.org/r1899259">r1899259</a> | svn-role | 2022-03-27 18:03:48 +0000 (Sun, 27 Mar 2022) | 10 lines
+
+Merge <a href="https://svn.apache.org/r1897449">r1897449</a> from trunk:
+
+ * <a href="https://svn.apache.org/r1897449">r1897449</a>
+ tests: Include additional information in an error message.
+ Justification:
+ Trivial test harness change that may help investigate unreproducible
+ errors.
+ Votes:
+ +1: danielsh, markphip, hartmannathan
+
+------------------------------------------------------------------------
</pre>
<p>Further changes currently under consideration are listed in each release line's
Re: svn commit: r1899276 - /subversion/site/publish/upcoming.part.html
Posted by Nathan Hartman <ha...@gmail.com>.
On Mon, Apr 11, 2022 at 7:27 AM Mark Phippard <ma...@gmail.com> wrote:
> On Sun, Apr 10, 2022 at 9:45 PM Daniel Shahaf <d....@daniel.shahaf.name>
> wrote:
> >
> > Daniel Sahlberg wrote on Mon, Mar 28, 2022 at 21:55:36 +0200:
> > > Den mån 28 mars 2022 kl 09:55 skrev Daniel Sahlberg <
> > > daniel.l.sahlberg@gmail.com>:
> > >
> > > > This commit doesn't look correct.
> > > >
> > > > I executed the generate-upcoming-changes-log.sh manually yesterday
> and it
> > > > created r1899244, removing a lot of log entries belonging to 1.14.1.
> This
> > > > commit (which was executed by cron) restores them.
> > > >
> > > > The crontab entry is:
> > > > [[[
> > > > # Puppet Name: Update our upcoming changes list
> > > > SVN=svn
> > > > 15 4 * * * chronic
> ~/src/svn/site/tools/generate-upcoming-changes-log.sh
> > > > ]]]
> > > >
> > > > The script begins with a comment
> > > > [[[
> > > > # This should be run from the root of a branches/1.{9,10,11}.x
> working
> > > > copy.
> > > > ]]]
> > > >
> > > > I suppose the crontab command should be changed to:
> > > > cd ~/src/svn/1.14.x && chronic
> > > > ~/src/svn/site/tools/generate-upcoming-changes-log.sh
> > > >
> > >
> > > So I've investigated this further and my initial analysis seems
> correct.
> > >
> > > This is what happens:
> > > * generate-upcoming-changes-log.sh determines last patch release
> number and
> > > generates upcoming.part.html based on all commits since that patch
> release
> > > was tagged.
> > > * It has two different ways to determine "the last patch release":
> > > * If `cwd` is a WC it look in the subversion/include/svn_version.h
> > > * Else look in
> https://dist.apache.org/repos/dist/release/subversion/
> > > * The logic looking at dists.a.o selected the oldest patch release
> > > available on dists.a.o, in case there are more than one.
> > > * The crontab entry executed generate-upcoming-changes-log.sh from ~,
> thus
> > > forcing a lookup from dists.a.o
> > >
> > > Currently, both 1.14.0 and 1.14.1 are available on dists.a.o. Thus it
> > > emitted all merged changes since 1.14.0, while expected behaviour (of
> > > upcoming.part.html) would be to only display merged changes since
> 1.14.1.
> > >
> >
> > dist/ should only contain the latest release from each supported minor
> > line, except when a release is being staged. I.e., today it should
> > contain 1.14.2 and 1.14.1 since we're in the process of staging 1.14.2;
> > but by Friday it should contain 1.14.2 and 1.10.8 and only those two.
> >
> > The script relies on this. Thus, if we'd deleted 1.14.0's artifacts
> > when we released 1.14.1 and kept the cron job as it was, the output
> > would then have been correct (and we wouldn't have had an extra manual
> > step in our create-a-A.B.x-branch workflow).
>
> I am guessing he just did not realize this was the root cause. It
> makes sense now what was happening.
>
> You probably all saw I cleaned up those old releases and then put them
> back. I was following the instructions in HACKING. I am not sure if
> previous RM's decided to leave those behind or just did not follow
> HACKING to the letter.
>
> Anyway, I thought the documentation was ambiguous about WHEN you
> should do this cleanup. I decided it should be done after the release
> is announced which is why I put them back.
>
> I am happy to do the cleanup later this week though.
>
> Mark
>
I've been trying to follow along and have learned a lot about releases
these last few weeks and your notes on the subject are very valuable. After
the release I would like to go through this part of HACKING and improve any
areas that led to questions etc. I think this will be very instructional,
as well, so hopefully I will be able to RM in the future.
Thanks for everything you have been doing.
Cheers,
Nathan
Re: svn commit: r1899276 - /subversion/site/publish/upcoming.part.html
Posted by Daniel Sahlberg <da...@gmail.com>.
Den mån 11 apr. 2022 kl 13:27 skrev Mark Phippard <ma...@gmail.com>:
> On Sun, Apr 10, 2022 at 9:45 PM Daniel Shahaf <d....@daniel.shahaf.name>
> wrote:
> >
> > Daniel Sahlberg wrote on Mon, Mar 28, 2022 at 21:55:36 +0200:
> > > Den mån 28 mars 2022 kl 09:55 skrev Daniel Sahlberg <
> > > daniel.l.sahlberg@gmail.com>:
> > >
> > > > This commit doesn't look correct.
> > > >
> > > > I executed the generate-upcoming-changes-log.sh manually yesterday
> and it
> > > > created r1899244, removing a lot of log entries belonging to 1.14.1.
> This
> > > > commit (which was executed by cron) restores them.
> > > >
> > > > The crontab entry is:
> > > > [[[
> > > > # Puppet Name: Update our upcoming changes list
> > > > SVN=svn
> > > > 15 4 * * * chronic
> ~/src/svn/site/tools/generate-upcoming-changes-log.sh
> > > > ]]]
> > > >
> > > > The script begins with a comment
> > > > [[[
> > > > # This should be run from the root of a branches/1.{9,10,11}.x
> working
> > > > copy.
> > > > ]]]
> > > >
> > > > I suppose the crontab command should be changed to:
> > > > cd ~/src/svn/1.14.x && chronic
> > > > ~/src/svn/site/tools/generate-upcoming-changes-log.sh
> > > >
> > >
> > > So I've investigated this further and my initial analysis seems
> correct.
> > >
> > > This is what happens:
> > > * generate-upcoming-changes-log.sh determines last patch release
> number and
> > > generates upcoming.part.html based on all commits since that patch
> release
> > > was tagged.
> > > * It has two different ways to determine "the last patch release":
> > > * If `cwd` is a WC it look in the subversion/include/svn_version.h
> > > * Else look in
> https://dist.apache.org/repos/dist/release/subversion/
> > > * The logic looking at dists.a.o selected the oldest patch release
> > > available on dists.a.o, in case there are more than one.
> > > * The crontab entry executed generate-upcoming-changes-log.sh from ~,
> thus
> > > forcing a lookup from dists.a.o
> > >
> > > Currently, both 1.14.0 and 1.14.1 are available on dists.a.o. Thus it
> > > emitted all merged changes since 1.14.0, while expected behaviour (of
> > > upcoming.part.html) would be to only display merged changes since
> 1.14.1.
> > >
> >
> > dist/ should only contain the latest release from each supported minor
> > line, except when a release is being staged. I.e., today it should
> > contain 1.14.2 and 1.14.1 since we're in the process of staging 1.14.2;
> > but by Friday it should contain 1.14.2 and 1.10.8 and only those two.
> >
> > The script relies on this. Thus, if we'd deleted 1.14.0's artifacts
> > when we released 1.14.1 and kept the cron job as it was, the output
> > would then have been correct (and we wouldn't have had an extra manual
> > step in our create-a-A.B.x-branch workflow).
>
> I am guessing he just did not realize this was the root cause. It
> makes sense now what was happening.
>
I realized this and I figured the chance/risk of RM forgetting to cleanup
justified to use the first way of detecting "latest patch release" (through
svn_version.h). Part of my investigation was to look at the log of dist/
and finding that this wasn't the first time that old releases were laying
around for a long time.
I agree that it makes sense to display the upcoming changes until the
release has been announced, in which case the change in puppet should be
reverted (or we should adjust the script for a better way detect "lastest
patch release". More below.
You probably all saw I cleaned up those old releases and then put them
> back. I was following the instructions in HACKING. I am not sure if
> previous RM's decided to leave those behind or just did not follow
> HACKING to the letter.
>
> Anyway, I thought the documentation was ambiguous about WHEN you
> should do this cleanup. I decided it should be done after the release
> is announced which is why I put them back.
>
As I read the documentation, you should cleanup as soon as the release is
uploaded, but hold back the announcement for 24 hours until the mirrors
have picked up the release. As far as I understand the mirror system at ASF
has been deprecated in favour of a CDN [1], where the CDN is supposed to
pick up the files "within 15 minutes" [2].
It is not immediately clear to me if cleaning up also disables downloading
the old release. If so, we have a 24 hour window when there are no
(announced) releases available for downloading. I have not investigated
this.
If we upload and immediately cleanup, then wait for 24 hours the upcoming
page will still display the "wrong" for one day. So the cleanup should
ideally not be done until after the release announcement. But it is an
additional thing to remember for the RM, so I can see why it is done the
same time as the upload. Mark, your input on this question is most valued!
That being said, I believe we could remove the 24 hours wait between upload
and announcement considering the "within 15 minutes" guarantee of the CDN.
/Daniel
[1] https://lists.apache.org/thread/6932rjo7jps7sdqr0h3bcfdm2zbw3sc3
[2] https://lists.apache.org/thread/0b3j0lmbjbrw0gw1vnnjrbc3owzpos7l
Re: svn commit: r1899276 - /subversion/site/publish/upcoming.part.html
Posted by Daniel Sahlberg <da...@gmail.com>.
Den mån 11 apr. 2022 kl 13:27 skrev Mark Phippard <ma...@gmail.com>:
> On Sun, Apr 10, 2022 at 9:45 PM Daniel Shahaf <d....@daniel.shahaf.name>
> wrote:
> >
> > Daniel Sahlberg wrote on Mon, Mar 28, 2022 at 21:55:36 +0200:
> > > Den mån 28 mars 2022 kl 09:55 skrev Daniel Sahlberg <
> > > daniel.l.sahlberg@gmail.com>:
> > >
> > > > This commit doesn't look correct.
> > > >
> > > > I executed the generate-upcoming-changes-log.sh manually yesterday
> and it
> > > > created r1899244, removing a lot of log entries belonging to 1.14.1.
> This
> > > > commit (which was executed by cron) restores them.
> > > >
> > > > The crontab entry is:
> > > > [[[
> > > > # Puppet Name: Update our upcoming changes list
> > > > SVN=svn
> > > > 15 4 * * * chronic
> ~/src/svn/site/tools/generate-upcoming-changes-log.sh
> > > > ]]]
> > > >
> > > > The script begins with a comment
> > > > [[[
> > > > # This should be run from the root of a branches/1.{9,10,11}.x
> working
> > > > copy.
> > > > ]]]
> > > >
> > > > I suppose the crontab command should be changed to:
> > > > cd ~/src/svn/1.14.x && chronic
> > > > ~/src/svn/site/tools/generate-upcoming-changes-log.sh
> > > >
> > >
> > > So I've investigated this further and my initial analysis seems
> correct.
> > >
> > > This is what happens:
> > > * generate-upcoming-changes-log.sh determines last patch release
> number and
> > > generates upcoming.part.html based on all commits since that patch
> release
> > > was tagged.
> > > * It has two different ways to determine "the last patch release":
> > > * If `cwd` is a WC it look in the subversion/include/svn_version.h
> > > * Else look in
> https://dist.apache.org/repos/dist/release/subversion/
> > > * The logic looking at dists.a.o selected the oldest patch release
> > > available on dists.a.o, in case there are more than one.
> > > * The crontab entry executed generate-upcoming-changes-log.sh from ~,
> thus
> > > forcing a lookup from dists.a.o
> > >
> > > Currently, both 1.14.0 and 1.14.1 are available on dists.a.o. Thus it
> > > emitted all merged changes since 1.14.0, while expected behaviour (of
> > > upcoming.part.html) would be to only display merged changes since
> 1.14.1.
> > >
> >
> > dist/ should only contain the latest release from each supported minor
> > line, except when a release is being staged. I.e., today it should
> > contain 1.14.2 and 1.14.1 since we're in the process of staging 1.14.2;
> > but by Friday it should contain 1.14.2 and 1.10.8 and only those two.
> >
> > The script relies on this. Thus, if we'd deleted 1.14.0's artifacts
> > when we released 1.14.1 and kept the cron job as it was, the output
> > would then have been correct (and we wouldn't have had an extra manual
> > step in our create-a-A.B.x-branch workflow).
>
> I am guessing he just did not realize this was the root cause. It
> makes sense now what was happening.
>
I realized this and I figured the chance/risk of RM forgetting to cleanup
justified to use the first way of detecting "latest patch release" (through
svn_version.h). Part of my investigation was to look at the log of dist/
and finding that this wasn't the first time that old releases were laying
around for a long time.
I agree that it makes sense to display the upcoming changes until the
release has been announced, in which case the change in puppet should be
reverted (or we should adjust the script for a better way detect "lastest
patch release". More below.
You probably all saw I cleaned up those old releases and then put them
> back. I was following the instructions in HACKING. I am not sure if
> previous RM's decided to leave those behind or just did not follow
> HACKING to the letter.
>
> Anyway, I thought the documentation was ambiguous about WHEN you
> should do this cleanup. I decided it should be done after the release
> is announced which is why I put them back.
>
As I read the documentation, you should cleanup as soon as the release is
uploaded, but hold back the announcement for 24 hours until the mirrors
have picked up the release. As far as I understand the mirror system at ASF
has been deprecated in favour of a CDN [1], where the CDN is supposed to
pick up the files "within 15 minutes" [2].
It is not immediately clear to me if cleaning up also disables downloading
the old release. If so, we have a 24 hour window when there are no
(announced) releases available for downloading. I have not investigated
this.
If we upload and immediately cleanup, then wait for 24 hours the upcoming
page will still display the "wrong" for one day. So the cleanup should
ideally not be done until after the release announcement. But it is an
additional thing to remember for the RM, so I can see why it is done the
same time as the upload. Mark, your input on this question is most valued!
That being said, I believe we could remove the 24 hours wait between upload
and announcement considering the "within 15 minutes" guarantee of the CDN.
/Daniel
[1] https://lists.apache.org/thread/6932rjo7jps7sdqr0h3bcfdm2zbw3sc3
[2] https://lists.apache.org/thread/0b3j0lmbjbrw0gw1vnnjrbc3owzpos7l
Re: svn commit: r1899276 - /subversion/site/publish/upcoming.part.html
Posted by Mark Phippard <ma...@gmail.com>.
On Sun, Apr 10, 2022 at 9:45 PM Daniel Shahaf <d....@daniel.shahaf.name> wrote:
>
> Daniel Sahlberg wrote on Mon, Mar 28, 2022 at 21:55:36 +0200:
> > Den mån 28 mars 2022 kl 09:55 skrev Daniel Sahlberg <
> > daniel.l.sahlberg@gmail.com>:
> >
> > > This commit doesn't look correct.
> > >
> > > I executed the generate-upcoming-changes-log.sh manually yesterday and it
> > > created r1899244, removing a lot of log entries belonging to 1.14.1. This
> > > commit (which was executed by cron) restores them.
> > >
> > > The crontab entry is:
> > > [[[
> > > # Puppet Name: Update our upcoming changes list
> > > SVN=svn
> > > 15 4 * * * chronic ~/src/svn/site/tools/generate-upcoming-changes-log.sh
> > > ]]]
> > >
> > > The script begins with a comment
> > > [[[
> > > # This should be run from the root of a branches/1.{9,10,11}.x working
> > > copy.
> > > ]]]
> > >
> > > I suppose the crontab command should be changed to:
> > > cd ~/src/svn/1.14.x && chronic
> > > ~/src/svn/site/tools/generate-upcoming-changes-log.sh
> > >
> >
> > So I've investigated this further and my initial analysis seems correct.
> >
> > This is what happens:
> > * generate-upcoming-changes-log.sh determines last patch release number and
> > generates upcoming.part.html based on all commits since that patch release
> > was tagged.
> > * It has two different ways to determine "the last patch release":
> > * If `cwd` is a WC it look in the subversion/include/svn_version.h
> > * Else look in https://dist.apache.org/repos/dist/release/subversion/
> > * The logic looking at dists.a.o selected the oldest patch release
> > available on dists.a.o, in case there are more than one.
> > * The crontab entry executed generate-upcoming-changes-log.sh from ~, thus
> > forcing a lookup from dists.a.o
> >
> > Currently, both 1.14.0 and 1.14.1 are available on dists.a.o. Thus it
> > emitted all merged changes since 1.14.0, while expected behaviour (of
> > upcoming.part.html) would be to only display merged changes since 1.14.1.
> >
>
> dist/ should only contain the latest release from each supported minor
> line, except when a release is being staged. I.e., today it should
> contain 1.14.2 and 1.14.1 since we're in the process of staging 1.14.2;
> but by Friday it should contain 1.14.2 and 1.10.8 and only those two.
>
> The script relies on this. Thus, if we'd deleted 1.14.0's artifacts
> when we released 1.14.1 and kept the cron job as it was, the output
> would then have been correct (and we wouldn't have had an extra manual
> step in our create-a-A.B.x-branch workflow).
I am guessing he just did not realize this was the root cause. It
makes sense now what was happening.
You probably all saw I cleaned up those old releases and then put them
back. I was following the instructions in HACKING. I am not sure if
previous RM's decided to leave those behind or just did not follow
HACKING to the letter.
Anyway, I thought the documentation was ambiguous about WHEN you
should do this cleanup. I decided it should be done after the release
is announced which is why I put them back.
I am happy to do the cleanup later this week though.
Mark
Re: svn commit: r1899276 - /subversion/site/publish/upcoming.part.html
Posted by Mark Phippard <ma...@gmail.com>.
On Sun, Apr 10, 2022 at 9:45 PM Daniel Shahaf <d....@daniel.shahaf.name> wrote:
>
> Daniel Sahlberg wrote on Mon, Mar 28, 2022 at 21:55:36 +0200:
> > Den mån 28 mars 2022 kl 09:55 skrev Daniel Sahlberg <
> > daniel.l.sahlberg@gmail.com>:
> >
> > > This commit doesn't look correct.
> > >
> > > I executed the generate-upcoming-changes-log.sh manually yesterday and it
> > > created r1899244, removing a lot of log entries belonging to 1.14.1. This
> > > commit (which was executed by cron) restores them.
> > >
> > > The crontab entry is:
> > > [[[
> > > # Puppet Name: Update our upcoming changes list
> > > SVN=svn
> > > 15 4 * * * chronic ~/src/svn/site/tools/generate-upcoming-changes-log.sh
> > > ]]]
> > >
> > > The script begins with a comment
> > > [[[
> > > # This should be run from the root of a branches/1.{9,10,11}.x working
> > > copy.
> > > ]]]
> > >
> > > I suppose the crontab command should be changed to:
> > > cd ~/src/svn/1.14.x && chronic
> > > ~/src/svn/site/tools/generate-upcoming-changes-log.sh
> > >
> >
> > So I've investigated this further and my initial analysis seems correct.
> >
> > This is what happens:
> > * generate-upcoming-changes-log.sh determines last patch release number and
> > generates upcoming.part.html based on all commits since that patch release
> > was tagged.
> > * It has two different ways to determine "the last patch release":
> > * If `cwd` is a WC it look in the subversion/include/svn_version.h
> > * Else look in https://dist.apache.org/repos/dist/release/subversion/
> > * The logic looking at dists.a.o selected the oldest patch release
> > available on dists.a.o, in case there are more than one.
> > * The crontab entry executed generate-upcoming-changes-log.sh from ~, thus
> > forcing a lookup from dists.a.o
> >
> > Currently, both 1.14.0 and 1.14.1 are available on dists.a.o. Thus it
> > emitted all merged changes since 1.14.0, while expected behaviour (of
> > upcoming.part.html) would be to only display merged changes since 1.14.1.
> >
>
> dist/ should only contain the latest release from each supported minor
> line, except when a release is being staged. I.e., today it should
> contain 1.14.2 and 1.14.1 since we're in the process of staging 1.14.2;
> but by Friday it should contain 1.14.2 and 1.10.8 and only those two.
>
> The script relies on this. Thus, if we'd deleted 1.14.0's artifacts
> when we released 1.14.1 and kept the cron job as it was, the output
> would then have been correct (and we wouldn't have had an extra manual
> step in our create-a-A.B.x-branch workflow).
I am guessing he just did not realize this was the root cause. It
makes sense now what was happening.
You probably all saw I cleaned up those old releases and then put them
back. I was following the instructions in HACKING. I am not sure if
previous RM's decided to leave those behind or just did not follow
HACKING to the letter.
Anyway, I thought the documentation was ambiguous about WHEN you
should do this cleanup. I decided it should be done after the release
is announced which is why I put them back.
I am happy to do the cleanup later this week though.
Mark
Re: svn commit: r1899276 - /subversion/site/publish/upcoming.part.html
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Daniel Sahlberg wrote on Mon, Mar 28, 2022 at 21:55:36 +0200:
> Den mån 28 mars 2022 kl 09:55 skrev Daniel Sahlberg <
> daniel.l.sahlberg@gmail.com>:
>
> > This commit doesn't look correct.
> >
> > I executed the generate-upcoming-changes-log.sh manually yesterday and it
> > created r1899244, removing a lot of log entries belonging to 1.14.1. This
> > commit (which was executed by cron) restores them.
> >
> > The crontab entry is:
> > [[[
> > # Puppet Name: Update our upcoming changes list
> > SVN=svn
> > 15 4 * * * chronic ~/src/svn/site/tools/generate-upcoming-changes-log.sh
> > ]]]
> >
> > The script begins with a comment
> > [[[
> > # This should be run from the root of a branches/1.{9,10,11}.x working
> > copy.
> > ]]]
> >
> > I suppose the crontab command should be changed to:
> > cd ~/src/svn/1.14.x && chronic
> > ~/src/svn/site/tools/generate-upcoming-changes-log.sh
> >
>
> So I've investigated this further and my initial analysis seems correct.
>
> This is what happens:
> * generate-upcoming-changes-log.sh determines last patch release number and
> generates upcoming.part.html based on all commits since that patch release
> was tagged.
> * It has two different ways to determine "the last patch release":
> * If `cwd` is a WC it look in the subversion/include/svn_version.h
> * Else look in https://dist.apache.org/repos/dist/release/subversion/
> * The logic looking at dists.a.o selected the oldest patch release
> available on dists.a.o, in case there are more than one.
> * The crontab entry executed generate-upcoming-changes-log.sh from ~, thus
> forcing a lookup from dists.a.o
>
> Currently, both 1.14.0 and 1.14.1 are available on dists.a.o. Thus it
> emitted all merged changes since 1.14.0, while expected behaviour (of
> upcoming.part.html) would be to only display merged changes since 1.14.1.
>
dist/ should only contain the latest release from each supported minor
line, except when a release is being staged. I.e., today it should
contain 1.14.2 and 1.14.1 since we're in the process of staging 1.14.2;
but by Friday it should contain 1.14.2 and 1.10.8 and only those two.
The script relies on this. Thus, if we'd deleted 1.14.0's artifacts
when we released 1.14.1 and kept the cron job as it was, the output
would then have been correct (and we wouldn't have had an extra manual
step in our create-a-A.B.x-branch workflow).
> I've pushed a change in puppet to the crontab entry as suggested above.
> This should solve the problem for now. When branching 1.15.x, we need to
> update this crontab entry.
Then please update
<https://subversion.apache.org/docs/community-guide/releasing.html#creating-branch>
accordingly :)
Cheers,
Daniel
Re: svn commit: r1899276 - /subversion/site/publish/upcoming.part.html
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Daniel Sahlberg wrote on Mon, Mar 28, 2022 at 21:55:36 +0200:
> Den mån 28 mars 2022 kl 09:55 skrev Daniel Sahlberg <
> daniel.l.sahlberg@gmail.com>:
>
> > This commit doesn't look correct.
> >
> > I executed the generate-upcoming-changes-log.sh manually yesterday and it
> > created r1899244, removing a lot of log entries belonging to 1.14.1. This
> > commit (which was executed by cron) restores them.
> >
> > The crontab entry is:
> > [[[
> > # Puppet Name: Update our upcoming changes list
> > SVN=svn
> > 15 4 * * * chronic ~/src/svn/site/tools/generate-upcoming-changes-log.sh
> > ]]]
> >
> > The script begins with a comment
> > [[[
> > # This should be run from the root of a branches/1.{9,10,11}.x working
> > copy.
> > ]]]
> >
> > I suppose the crontab command should be changed to:
> > cd ~/src/svn/1.14.x && chronic
> > ~/src/svn/site/tools/generate-upcoming-changes-log.sh
> >
>
> So I've investigated this further and my initial analysis seems correct.
>
> This is what happens:
> * generate-upcoming-changes-log.sh determines last patch release number and
> generates upcoming.part.html based on all commits since that patch release
> was tagged.
> * It has two different ways to determine "the last patch release":
> * If `cwd` is a WC it look in the subversion/include/svn_version.h
> * Else look in https://dist.apache.org/repos/dist/release/subversion/
> * The logic looking at dists.a.o selected the oldest patch release
> available on dists.a.o, in case there are more than one.
> * The crontab entry executed generate-upcoming-changes-log.sh from ~, thus
> forcing a lookup from dists.a.o
>
> Currently, both 1.14.0 and 1.14.1 are available on dists.a.o. Thus it
> emitted all merged changes since 1.14.0, while expected behaviour (of
> upcoming.part.html) would be to only display merged changes since 1.14.1.
>
dist/ should only contain the latest release from each supported minor
line, except when a release is being staged. I.e., today it should
contain 1.14.2 and 1.14.1 since we're in the process of staging 1.14.2;
but by Friday it should contain 1.14.2 and 1.10.8 and only those two.
The script relies on this. Thus, if we'd deleted 1.14.0's artifacts
when we released 1.14.1 and kept the cron job as it was, the output
would then have been correct (and we wouldn't have had an extra manual
step in our create-a-A.B.x-branch workflow).
> I've pushed a change in puppet to the crontab entry as suggested above.
> This should solve the problem for now. When branching 1.15.x, we need to
> update this crontab entry.
Then please update
<https://subversion.apache.org/docs/community-guide/releasing.html#creating-branch>
accordingly :)
Cheers,
Daniel
Re: svn commit: r1899276 - /subversion/site/publish/upcoming.part.html
Posted by Daniel Sahlberg <da...@gmail.com>.
Den mån 28 mars 2022 kl 09:55 skrev Daniel Sahlberg <
daniel.l.sahlberg@gmail.com>:
> This commit doesn't look correct.
>
> I executed the generate-upcoming-changes-log.sh manually yesterday and it
> created r1899244, removing a lot of log entries belonging to 1.14.1. This
> commit (which was executed by cron) restores them.
>
> The crontab entry is:
> [[[
> # Puppet Name: Update our upcoming changes list
> SVN=svn
> 15 4 * * * chronic ~/src/svn/site/tools/generate-upcoming-changes-log.sh
> ]]]
>
> The script begins with a comment
> [[[
> # This should be run from the root of a branches/1.{9,10,11}.x working
> copy.
> ]]]
>
> I suppose the crontab command should be changed to:
> cd ~/src/svn/1.14.x && chronic
> ~/src/svn/site/tools/generate-upcoming-changes-log.sh
>
So I've investigated this further and my initial analysis seems correct.
This is what happens:
* generate-upcoming-changes-log.sh determines last patch release number and
generates upcoming.part.html based on all commits since that patch release
was tagged.
* It has two different ways to determine "the last patch release":
* If `cwd` is a WC it look in the subversion/include/svn_version.h
* Else look in https://dist.apache.org/repos/dist/release/subversion/
* The logic looking at dists.a.o selected the oldest patch release
available on dists.a.o, in case there are more than one.
* The crontab entry executed generate-upcoming-changes-log.sh from ~, thus
forcing a lookup from dists.a.o
Currently, both 1.14.0 and 1.14.1 are available on dists.a.o. Thus it
emitted all merged changes since 1.14.0, while expected behaviour (of
upcoming.part.html) would be to only display merged changes since 1.14.1.
I've pushed a change in puppet to the crontab entry as suggested above.
This should solve the problem for now. When branching 1.15.x, we need to
update this crontab entry.
I don't have time right now to look at generating separate
upcoming.$VERSION.part.html files for the supported versions, but I will
leave it on the todo list.
/Daniel
Re: svn commit: r1899276 - /subversion/site/publish/upcoming.part.html
Posted by Daniel Sahlberg <da...@gmail.com>.
Den mån 28 mars 2022 kl 13:29 skrev Nathan Hartman <hartman.nathan@gmail.com
>:
> On Mon, Mar 28, 2022 at 3:55 AM Daniel Sahlberg <
> daniel.l.sahlberg@gmail.com> wrote:
>
>> This commit doesn't look correct.
>>
>> I executed the generate-upcoming-changes-log.sh manually yesterday and it
>> created r1899244, removing a lot of log entries belonging to 1.14.1. This
>> commit (which was executed by cron) restores them.
>>
>> The crontab entry is:
>> [[[
>> # Puppet Name: Update our upcoming changes list
>> SVN=svn
>> 15 4 * * * chronic ~/src/svn/site/tools/generate-upcoming-changes-log.sh
>> ]]]
>>
>> The script begins with a comment
>> [[[
>> # This should be run from the root of a branches/1.{9,10,11}.x working
>> copy.
>> ]]]
>>
>> I suppose the crontab command should be changed to:
>> cd ~/src/svn/1.14.x && chronic
>> ~/src/svn/site/tools/generate-upcoming-changes-log.sh
>>
>> However that will create an "upcoming" only for 1.14 and not for 1.10.
>> Any thoughts
>>
>
>
> We don't really have a place on the release notes page for "upcoming" for
> two different major lines. For now it probably makes sense to show it for
> 1.14.x only, but when 1.15 is released we'll have to decide whether to show
> "upcoming" for just 1.15 or separately for 1.14 and 1.15.
>
(y)
It should be fairly simple to run the script twice (with a version
argument) and generate two separate upcoming.$VERSION.part.html and
referencing from the website. I feel this being an itch for me and I'll see
if I can find some time to scratch for 1.10 and 1.14. It might be good to
have a framework for the future even if 1.10 is approaching EOL.
> Regarding things disappearing and reappearing, some time ago I noticed
> that if an error occurs in the script, such as it can't reach the repo,
> then it fails to generate any text but proceeds to commit unconditionally.
> I don't remember if that was ever fixed.
>
I saw that as well but in this case there are merges from 2020 showing up
in "upcoming". These changes were part of 1.14.1.
I'll try again to run the script manually, noting the `cwd` each time and
see what happens. There may be some spurious commit messages while I'm
doing this.
I'll also try to figure out what to do in case of problems reaching the
repo.
Kind regards,
Daniel
Re: svn commit: r1899276 - /subversion/site/publish/upcoming.part.html
Posted by Daniel Sahlberg <da...@gmail.com>.
Den mån 28 mars 2022 kl 13:29 skrev Nathan Hartman <hartman.nathan@gmail.com
>:
> On Mon, Mar 28, 2022 at 3:55 AM Daniel Sahlberg <
> daniel.l.sahlberg@gmail.com> wrote:
>
>> This commit doesn't look correct.
>>
>> I executed the generate-upcoming-changes-log.sh manually yesterday and it
>> created r1899244, removing a lot of log entries belonging to 1.14.1. This
>> commit (which was executed by cron) restores them.
>>
>> The crontab entry is:
>> [[[
>> # Puppet Name: Update our upcoming changes list
>> SVN=svn
>> 15 4 * * * chronic ~/src/svn/site/tools/generate-upcoming-changes-log.sh
>> ]]]
>>
>> The script begins with a comment
>> [[[
>> # This should be run from the root of a branches/1.{9,10,11}.x working
>> copy.
>> ]]]
>>
>> I suppose the crontab command should be changed to:
>> cd ~/src/svn/1.14.x && chronic
>> ~/src/svn/site/tools/generate-upcoming-changes-log.sh
>>
>> However that will create an "upcoming" only for 1.14 and not for 1.10.
>> Any thoughts
>>
>
>
> We don't really have a place on the release notes page for "upcoming" for
> two different major lines. For now it probably makes sense to show it for
> 1.14.x only, but when 1.15 is released we'll have to decide whether to show
> "upcoming" for just 1.15 or separately for 1.14 and 1.15.
>
(y)
It should be fairly simple to run the script twice (with a version
argument) and generate two separate upcoming.$VERSION.part.html and
referencing from the website. I feel this being an itch for me and I'll see
if I can find some time to scratch for 1.10 and 1.14. It might be good to
have a framework for the future even if 1.10 is approaching EOL.
> Regarding things disappearing and reappearing, some time ago I noticed
> that if an error occurs in the script, such as it can't reach the repo,
> then it fails to generate any text but proceeds to commit unconditionally.
> I don't remember if that was ever fixed.
>
I saw that as well but in this case there are merges from 2020 showing up
in "upcoming". These changes were part of 1.14.1.
I'll try again to run the script manually, noting the `cwd` each time and
see what happens. There may be some spurious commit messages while I'm
doing this.
I'll also try to figure out what to do in case of problems reaching the
repo.
Kind regards,
Daniel
Re: svn commit: r1899276 - /subversion/site/publish/upcoming.part.html
Posted by Nathan Hartman <ha...@gmail.com>.
On Mon, Mar 28, 2022 at 3:55 AM Daniel Sahlberg <da...@gmail.com>
wrote:
> This commit doesn't look correct.
>
> I executed the generate-upcoming-changes-log.sh manually yesterday and it
> created r1899244, removing a lot of log entries belonging to 1.14.1. This
> commit (which was executed by cron) restores them.
>
> The crontab entry is:
> [[[
> # Puppet Name: Update our upcoming changes list
> SVN=svn
> 15 4 * * * chronic ~/src/svn/site/tools/generate-upcoming-changes-log.sh
> ]]]
>
> The script begins with a comment
> [[[
> # This should be run from the root of a branches/1.{9,10,11}.x working
> copy.
> ]]]
>
> I suppose the crontab command should be changed to:
> cd ~/src/svn/1.14.x && chronic
> ~/src/svn/site/tools/generate-upcoming-changes-log.sh
>
> However that will create an "upcoming" only for 1.14 and not for 1.10. Any
> thoughts
>
We don't really have a place on the release notes page for "upcoming" for
two different major lines. For now it probably makes sense to show it for
1.14.x only, but when 1.15 is released we'll have to decide whether to show
"upcoming" for just 1.15 or separately for 1.14 and 1.15.
Regarding things disappearing and reappearing, some time ago I noticed that
if an error occurs in the script, such as it can't reach the repo, then it
fails to generate any text but proceeds to commit unconditionally. I don't
remember if that was ever fixed.
Nathan
Re: svn commit: r1899276 - /subversion/site/publish/upcoming.part.html
Posted by Nathan Hartman <ha...@gmail.com>.
On Mon, Mar 28, 2022 at 3:55 AM Daniel Sahlberg <da...@gmail.com>
wrote:
> This commit doesn't look correct.
>
> I executed the generate-upcoming-changes-log.sh manually yesterday and it
> created r1899244, removing a lot of log entries belonging to 1.14.1. This
> commit (which was executed by cron) restores them.
>
> The crontab entry is:
> [[[
> # Puppet Name: Update our upcoming changes list
> SVN=svn
> 15 4 * * * chronic ~/src/svn/site/tools/generate-upcoming-changes-log.sh
> ]]]
>
> The script begins with a comment
> [[[
> # This should be run from the root of a branches/1.{9,10,11}.x working
> copy.
> ]]]
>
> I suppose the crontab command should be changed to:
> cd ~/src/svn/1.14.x && chronic
> ~/src/svn/site/tools/generate-upcoming-changes-log.sh
>
> However that will create an "upcoming" only for 1.14 and not for 1.10. Any
> thoughts
>
We don't really have a place on the release notes page for "upcoming" for
two different major lines. For now it probably makes sense to show it for
1.14.x only, but when 1.15 is released we'll have to decide whether to show
"upcoming" for just 1.15 or separately for 1.14 and 1.15.
Regarding things disappearing and reappearing, some time ago I noticed that
if an error occurs in the script, such as it can't reach the repo, then it
fails to generate any text but proceeds to commit unconditionally. I don't
remember if that was ever fixed.
Nathan
Re: svn commit: r1899276 - /subversion/site/publish/upcoming.part.html
Posted by Daniel Sahlberg <da...@gmail.com>.
Den mån 28 mars 2022 kl 09:55 skrev Daniel Sahlberg <
daniel.l.sahlberg@gmail.com>:
> This commit doesn't look correct.
>
> I executed the generate-upcoming-changes-log.sh manually yesterday and it
> created r1899244, removing a lot of log entries belonging to 1.14.1. This
> commit (which was executed by cron) restores them.
>
> The crontab entry is:
> [[[
> # Puppet Name: Update our upcoming changes list
> SVN=svn
> 15 4 * * * chronic ~/src/svn/site/tools/generate-upcoming-changes-log.sh
> ]]]
>
> The script begins with a comment
> [[[
> # This should be run from the root of a branches/1.{9,10,11}.x working
> copy.
> ]]]
>
> I suppose the crontab command should be changed to:
> cd ~/src/svn/1.14.x && chronic
> ~/src/svn/site/tools/generate-upcoming-changes-log.sh
>
So I've investigated this further and my initial analysis seems correct.
This is what happens:
* generate-upcoming-changes-log.sh determines last patch release number and
generates upcoming.part.html based on all commits since that patch release
was tagged.
* It has two different ways to determine "the last patch release":
* If `cwd` is a WC it look in the subversion/include/svn_version.h
* Else look in https://dist.apache.org/repos/dist/release/subversion/
* The logic looking at dists.a.o selected the oldest patch release
available on dists.a.o, in case there are more than one.
* The crontab entry executed generate-upcoming-changes-log.sh from ~, thus
forcing a lookup from dists.a.o
Currently, both 1.14.0 and 1.14.1 are available on dists.a.o. Thus it
emitted all merged changes since 1.14.0, while expected behaviour (of
upcoming.part.html) would be to only display merged changes since 1.14.1.
I've pushed a change in puppet to the crontab entry as suggested above.
This should solve the problem for now. When branching 1.15.x, we need to
update this crontab entry.
I don't have time right now to look at generating separate
upcoming.$VERSION.part.html files for the supported versions, but I will
leave it on the todo list.
/Daniel
Re: svn commit: r1899276 - /subversion/site/publish/upcoming.part.html
Posted by Daniel Sahlberg <da...@gmail.com>.
This commit doesn't look correct.
I executed the generate-upcoming-changes-log.sh manually yesterday and it
created r1899244, removing a lot of log entries belonging to 1.14.1. This
commit (which was executed by cron) restores them.
The crontab entry is:
[[[
# Puppet Name: Update our upcoming changes list
SVN=svn
15 4 * * * chronic ~/src/svn/site/tools/generate-upcoming-changes-log.sh
]]]
The script begins with a comment
[[[
# This should be run from the root of a branches/1.{9,10,11}.x working copy.
]]]
I suppose the crontab command should be changed to:
cd ~/src/svn/1.14.x && chronic
~/src/svn/site/tools/generate-upcoming-changes-log.sh
However that will create an "upcoming" only for 1.14 and not for 1.10. Any
thoughts?
Kind regards,
Daniel
Den mån 28 mars 2022 kl 06:15 skrev <sv...@apache.org>:
> Author: svn-role
> Date: Mon Mar 28 04:15:01 2022
> New Revision: 1899276
>
> URL: http://svn.apache.org/viewvc?rev=1899276&view=rev
> Log:
> * upcoming.part.html: Automatically regenerated
>
> Modified:
> subversion/site/publish/upcoming.part.html
>
> Modified: subversion/site/publish/upcoming.part.html
> URL:
> http://svn.apache.org/viewvc/subversion/site/publish/upcoming.part.html?rev=1899276&r1=1899275&r2=1899276&view=diff
>
> ==============================================================================
> --- subversion/site/publish/upcoming.part.html (original)
> +++ subversion/site/publish/upcoming.part.html Mon Mar 28 04:15:01 2022
> @@ -2,6 +2,470 @@
> <pre style="border-style: none">
> Changes in ^/subversion/branches/1.14.x:
> ------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1877978">r1877978</a> | svn-role |
> 2020-05-21 04:00:13 +0000 (Thu, 21 May 2020) | 7 lines
> +
> +Merge <a href="https://svn.apache.org/r1877788">r1877788</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1877788">r1877788</a>
> + Fix a broken link in a docstring.
> + Votes:
> + +1: danielsh, stsp
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1878211">r1878211</a> | svn-role |
> 2020-05-28 04:00:12 +0000 (Thu, 28 May 2020) | 10 lines
> +
> +Merge <a href="https://svn.apache.org/r1877072">r1877072</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1877072">r1877072</a>
> + svnmucc: Change an error message to state another possible cause of the
> + error.
> + Justification:
> + Error messages should be accurate. User reported (<a
> href="/issue-4854">issue #4854</a>).
> + Votes:
> + +1: danielsh, stsp, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1878213">r1878213</a> | svn-role |
> 2020-05-28 04:00:16 +0000 (Thu, 28 May 2020) | 11 lines
> +
> +Merge <a href="https://svn.apache.org/r1877259">r1877259</a> from trunk:
> +
> +* <a href="https://svn.apache.org/r1877259">r1877259</a>
> + Move variable declarations to the start of block the to fix
> + syntax errors with VC9 (Visual Studio 2008).
> + Justification:
> + Our code should be C90.
> + Votes:
> + +1: brane, stsp, jcorvel
> + +0: danielsh (from dev@)
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1878415">r1878415</a> | svn-role |
> 2020-06-03 04:00:20 +0000 (Wed, 03 Jun 2020) | 12 lines
> +
> +Merge the <a href="https://svn.apache.org/r1876707">r1876707</a> group
> from trunk:
> +
> + * <a href="https://svn.apache.org/r1876707">r1876707</a>, <a href="
> https://svn.apache.org/r1876734">r1876734</a>, <a href="
> https://svn.apache.org/r1877318">r1877318</a>, <a href="
> https://svn.apache.org/r1877712">r1877712</a>, <a href="
> https://svn.apache.org/r1878141">r1878141</a>, <a href="
> https://svn.apache.org/r1878142">r1878142</a>, <a href="
> https://svn.apache.org/r1878143">r1878143</a>,
> + <a href="https://svn.apache.org/r1878144">r1878144</a>
> + Various fixes for making the test suite run correctly with Python 3 on
> + Windows.
> + Justification:
> + Our test suite should test Subversion correctly also on Windows with
> + Python 3
> + Votes:
> + +1: futatuki, jcorvel, stsp
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1879245">r1879245</a> | svn-role |
> 2020-06-27 04:00:12 +0000 (Sat, 27 Jun 2020) | 11 lines
> +
> +Merge <a href="https://svn.apache.org/r1876662">r1876662</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1876662">r1876662</a>
> + Avoid check for SWIG version for Python bindings when --without-swig is
> + passed.
> + Justification:
> + SWIG python bindings should be able to be built without SWIG when we
> use
> + the release tarball
> + Votes:
> + +1: futatuki, stsp, rhuijben
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1879246">r1879246</a> | svn-role |
> 2020-06-27 04:00:17 +0000 (Sat, 27 Jun 2020) | 10 lines
> +
> +Merge <a href="https://svn.apache.org/r1876906">r1876906</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1876906">r1876906</a>
> + Make gen-make.py --debug work with Python 3
> + Justification:
> + We should also be able to build in Debug configuration with Python 3
> + on Windows.
> + Votes:
> + +1: jcorvel, stsp, rhuijben
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1879797">r1879797</a> | svn-role |
> 2020-07-12 04:00:12 +0000 (Sun, 12 Jul 2020) | 10 lines
> +
> +Merge <a href="https://svn.apache.org/r1876410">r1876410</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1876410">r1876410</a>
> + Fix the .editorconfig stanza for Makefile's.
> + Justification:
> + Make $EDITOR do the right thing on any backport branches we may
> create
> + off this stabilization branch.
> + Votes:
> + +1: danielsh, stsp, jamessan
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1879798">r1879798</a> | svn-role |
> 2020-07-12 04:00:17 +0000 (Sun, 12 Jul 2020) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1878413">r1878413</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1878413">r1878413</a>
> + autogen.sh: Remove per SWIG bindings checked files on release mode.
> + Justification:
> + The release tarballs should not contain .swig_*_checked files
> + Votes:
> + +1: futatuki, rhuijben, jamessan
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1879799">r1879799</a> | svn-role |
> 2020-07-12 04:00:23 +0000 (Sun, 12 Jul 2020) | 9 lines
> +
> +Merge the <a href="https://svn.apache.org/r1878909">r1878909</a> group
> from trunk:
> +
> + * <a href="https://svn.apache.org/r1878909">r1878909</a>, <a href="
> https://svn.apache.org/r1878918">r1878918</a>, <a href="
> https://svn.apache.org/r1878950">r1878950</a>
> + Fix a number of thinkos in human-readable file size formatting.
> + Justification:
> + Fixes wrong output and an assertion failure in debug mode.
> + Votes:
> + +1: brane, rhuijben, jamessan
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1879800">r1879800</a> | svn-role |
> 2020-07-12 04:00:28 +0000 (Sun, 12 Jul 2020) | 14 lines
> +
> +Merge <a href="https://svn.apache.org/r1879198">r1879198</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1879198">r1879198</a>
> + Fix an invalid quoting in working copy upgrade system that only works
> + because SQLite automatically fixed this. More recent SQLite functions
> + will signal an error when deprecated features are disabled.
> + Justification:
> + Causes user-visible errors.
> + Note:
> + This filechange by itself doesn't trigger a change that make
> will
> + handle. So make sure you recompile the sql queries for testing.
> + Votes:
> + +1: rhuijben, danielsh, jamessan
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1880465">r1880465</a> | svn-role |
> 2020-07-31 04:00:11 +0000 (Fri, 31 Jul 2020) | 10 lines
> +
> +Merge <a href="https://svn.apache.org/r1877960">r1877960</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1877960">r1877960</a>
> + INSTALL (I.C.12): Add Note that non-release mode is required for
> building
> + SWIG Python 2 bindings.
> + Justification:
> + We've not entirely dropped Python 2 bindings support on 1.14.x
> yet
> + Votes:
> + +1: futatuki, stsp, rhuijben
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1880916">r1880916</a> | svn-role |
> 2020-08-17 04:00:17 +0000 (Mon, 17 Aug 2020) | 11 lines
> +
> +Merge the 1.14.x-<a href="https://svn.apache.org/r1880374">r1880374</a>-fsfs
> branch:
> +
> + * <a href="https://svn.apache.org/r1880374
> ">r1880374</a>:subversion/libsvn_fs_fs
> + Fix an uninitialized read in svn_fs_fs__index_append().
> + Justification:
> + Uninitialized reads are potentially undefined behaviour.
> + Branch:
> + 1.14.x-<a href="https://svn.apache.org/r1880374">r1880374</a>-fsfs
> + Votes:
> + +1: danielsh, hartmannathan, jamessan
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1881075">r1881075</a> | svn-role |
> 2020-08-22 04:00:21 +0000 (Sat, 22 Aug 2020) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1880886">r1880886</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1880886">r1880886</a>
> + Fix crash in JavaHL JNI wrapper caused by object lifetimes
> + Justification:
> + Fixes a crash encountered with GCC 10.
> + Votes:
> + +1: hartmannathan, jamessan
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1883406">r1883406</a> | svn-role |
> 2020-11-14 04:00:12 +0000 (Sat, 14 Nov 2020) | 9 lines
> +
> +Merge the <a href="https://svn.apache.org/r1878855">r1878855</a> group
> from trunk:
> +
> + * <a href="https://svn.apache.org/r1878855">r1878855</a>, <a href="
> https://svn.apache.org/r1878859">r1878859</a>
> + Make the hot-backup.py script work with Python 3.
> + Justification:
> + Script should work with Python3
> + Votes:
> + +1: jamessan, brane
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1883407">r1883407</a> | svn-role |
> 2020-11-14 04:00:17 +0000 (Sat, 14 Nov 2020) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1882115">r1882115</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1882115">r1882115</a>
> + JavaHL: Fix incorrect cache in SVNBase::createCppBoundObject
> + Justification:
> + Fixes a potential crash.
> + Votes:
> + +1: hartmannathan, brane
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1884481">r1884481</a> | svn-role |
> 2020-12-16 04:00:11 +0000 (Wed, 16 Dec 2020) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1882157">r1882157</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1882157">r1882157</a>
> + Do not suggest --help -v for commands which do not support -v.
> + Justification:
> + The --help message for several commands is misleading. User
> complained.
> + Votes:
> + +1: stsp, brane, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1884482">r1884482</a> | svn-role |
> 2020-12-16 04:00:16 +0000 (Wed, 16 Dec 2020) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1877338">r1877338</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1877338">r1877338</a>
> + Add SWIG4 support for SWIG Python binding on Windows.
> + Justification:
> + SWIG Python bindings should be able to build with SWIG4 on Windows,
> too
> + Votes:
> + +1: futatuki, jun66j5, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1884483">r1884483</a> | svn-role |
> 2020-12-16 04:00:22 +0000 (Wed, 16 Dec 2020) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1883335">r1883335</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1883335">r1883335</a>
> + Fix unable to load *.pyd files with Python 3.8.x on Windows.
> + Justification:
> + Make Python bindings available with Python 3.8+ on Windows.
> + Votes:
> + +1: jun66j5, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1884484">r1884484</a> | svn-role |
> 2020-12-16 04:00:27 +0000 (Wed, 16 Dec 2020) | 10 lines
> +
> +Merge <a href="https://svn.apache.org/r1883337">r1883337</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1883337">r1883337</a>
> + Remove uses of os.dup2() from run_tests.py in order to adapt the new
> + console reader and writer on Windows since Python 3.6.
> + Justification:
> + PYTHONLEGACYWINDOWSSTDIO is no longer needed to run unit tests on
> Windows.
> + Votes:
> + +1: jun66j5, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1884535">r1884535</a> | svn-role |
> 2020-12-17 04:00:12 +0000 (Thu, 17 Dec 2020) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1883570">r1883570</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1883570">r1883570</a>
> + Fix C4204 errors while building swig-py with Python 3.9 on Windows.
> + Justification:
> + Allow building Python bindings with Python 3.9 on Windows.
> + Votes:
> + +1: jun66j5, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1884589">r1884589</a> | svn-role |
> 2020-12-18 04:00:24 +0000 (Fri, 18 Dec 2020) | 9 lines
> +
> +Merge the <a href="https://svn.apache.org/r1881958">r1881958</a> group
> from trunk:
> +
> + * <a href="https://svn.apache.org/r1881958">r1881958</a>, 1882128
> + Restoring support for building with APR 1.4.
> + Justification:
> + Allow building on older distros such as CentOS 7.
> + Votes:
> + +1: brane, hartmannathan, julianfoad
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1884590">r1884590</a> | svn-role |
> 2020-12-18 04:00:28 +0000 (Fri, 18 Dec 2020) | 12 lines
> +
> +Merge <a href="https://svn.apache.org/r1882326">r1882326</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1882326">r1882326</a>
> + Fix <a href="/issue-4762">issue #4762</a> "authz doesn't
> combine global and repository rules"
> + Justification:
> + Restore behaviour of SVN 1.9: It is now again possible to override
> + per-path access rules for specific users (and groups) at the global
> + level. Such global rules are overridden by repository-specific rules
> + only if both the user and the path match the repository-specific
> rule.
> + Votes:
> + +1: stsp, brane, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1884591">r1884591</a> | svn-role |
> 2020-12-18 04:00:36 +0000 (Fri, 18 Dec 2020) | 10 lines
> +
> +Merge the <a href="https://svn.apache.org/r1878997">r1878997</a> group
> from trunk:
> +
> + * <a href="https://svn.apache.org/r1878997">r1878997</a>, <a href="
> https://svn.apache.org/r1879192">r1879192</a>, <a href="
> https://svn.apache.org/r1879474">r1879474</a>, <a href="
> https://svn.apache.org/r1879959">r1879959</a>
> + Fix <a href="/issue-4859">issue #4859</a>, Merge removing a folder
> with non-inheritable mergeinfo
> + -> E155023: can't set properties: invalid status for updating
> properties
> + Justification:
> + Annoying failure, encountered in real use.
> + Votes:
> + +1: julianfoad, hartmannathan, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1884592">r1884592</a> | svn-role |
> 2020-12-18 04:00:41 +0000 (Fri, 18 Dec 2020) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1875675">r1875675</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1875675">r1875675</a>
> + Rewrite load_normalize_node_props to avoid literal trailing spaces.
> + Justification:
> + Prevents the bug fixed in <a href="https://svn.apache.org/r1875620">r1875620</a>
> from recurring.
> + Votes:
> + +1: danielsh, brane, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1884617">r1884617</a> | svn-role |
> 2020-12-19 04:00:12 +0000 (Sat, 19 Dec 2020) | 11 lines
> +
> +Merge <a href="https://svn.apache.org/r1880192">r1880192</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1880192">r1880192</a>
> + Fix <a href="/issue-4862">issue #4862</a> "Merge: the resulting
> mergeinfo is non-deterministic".
> + Justification:
> + Non-deterministic merge result is bad.
> + Depends:
> + <a href="https://svn.apache.org/r1878997">r1878997</a>, <a href="
> https://svn.apache.org/r1879192">r1879192</a>, <a href="
> https://svn.apache.org/r1879474">r1879474</a>, <a href="
> https://svn.apache.org/r1879959">r1879959</a> (Fix <a
> href="/issue-4859">issue #4859</a>)
> + Votes:
> + +1: julianfoad, hartmannathan, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1884618">r1884618</a> | svn-role |
> 2020-12-19 04:00:18 +0000 (Sat, 19 Dec 2020) | 11 lines
> +
> +Merge the <a href="https://svn.apache.org/r1881985">r1881985</a> group
> from trunk:
> +
> + * <a href="https://svn.apache.org/r1881985">r1881985</a>, <a href="
> https://svn.apache.org/r1882105">r1882105</a>
> + Follow up to <a href="https://svn.apache.org/r1880192">r1880192</a>:
> Fix an EOL issue in test on Windows.
> + Justification:
> + We should test correctly on Windows environment, too.
> + Depends:
> + <a href="https://svn.apache.org/r1880192">r1880192</a>
> + Votes:
> + +1: futatuki, jcorvel, hartmannathan
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1884665">r1884665</a> | svn-role |
> 2020-12-21 04:00:12 +0000 (Mon, 21 Dec 2020) | 10 lines
> +
> +Merge <a href="https://svn.apache.org/r1884642">r1884642</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1884642">r1884642</a>
> + Fix win-tests.py is unable to load Python bindings with debug
> configuration
> + since Python 3.5.
> + Justification:
> + Allow unit tests with debug configuration on Windows.
> + Votes:
> + +1: jun66j5, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1885507">r1885507</a> | svn-role |
> 2021-01-15 04:00:13 +0000 (Fri, 15 Jan 2021) | 11 lines
> +
> +Merge <a href="https://svn.apache.org/r1885112">r1885112</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1885112">r1885112</a>
> + swig-py: Fix a typo in tests.
> + Justification:
> + This typo causes DeprecationWarning since Python 3.6 and it will be
> + Syntax error.
> + Votes:
> + +1: futatuki
> + +0: jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1885828">r1885828</a> | svn-role |
> 2021-01-23 04:00:42 +0000 (Sat, 23 Jan 2021) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1885795">r1885795</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1885795">r1885795</a>
> + Update copyright year to 2021.
> + Justification:
> + The future is here!
> + Votes:
> + +1: stsp, futatuki, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1885829">r1885829</a> | svn-role |
> 2021-01-23 04:00:51 +0000 (Sat, 23 Jan 2021) | 9 lines
> +
> +Merge the <a href="https://svn.apache.org/r1884427">r1884427</a> group
> from trunk:
> +
> + * <a href="https://svn.apache.org/r1884427">r1884427</a>, <a href="
> https://svn.apache.org/r1885557">r1885557</a>, <a href="
> https://svn.apache.org/r1885600">r1885600</a>, <a href="
> https://svn.apache.org/r1885656">r1885656</a>, <a href="
> https://svn.apache.org/r1885784">r1885784</a>, <a href="
> https://svn.apache.org/r1885785">r1885785</a>
> + Make mailer.py work properly with Python 3.
> + Justification:
> + Hook scripts should support Python 3 on 1.14.x.
> + Votes:
> + +1: stsp, futatuki
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1885931">r1885931</a> | svn-role |
> 2021-01-27 04:00:18 +0000 (Wed, 27 Jan 2021) | 10 lines
> +
> +Merge <a href="https://svn.apache.org/r1877794">r1877794</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1877794">r1877794</a>
> + Use Doxygen comment leader for comments with doxygen syntax.
> + Justification:
> + Improve $EDITOR's syntax highlighting.
> + Votes:
> + +0: danielsh
> + +1: brane, jamessan
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1886041">r1886041</a> | svn-role |
> 2021-01-30 04:00:44 +0000 (Sat, 30 Jan 2021) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1882234">r1882234</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1882234">r1882234</a>
> + Fix file name to edit from utf8 to local style.
> + Justification:
> + Editor invocation should work correctly in any valid locale.
> + Votes:
> + +1: futatuki, jcorvel, stsp
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1886042">r1886042</a> | svn-role |
> 2021-01-30 04:00:48 +0000 (Sat, 30 Jan 2021) | 12 lines
> +
> +Merge <a href="https://svn.apache.org/r1885953">r1885953</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1885953">r1885953</a>
> + Fix file name encoding and quoting when invoking editor on Windows.
> + Justification:
> + Invoking editor with special character or spaces in path is broken
> + on Windows.
> + Depends:
> + <a href="https://svn.apache.org/r1882234">r1882234</a>
> + Votes:
> + +1: jcorvel, futatuki, stsp
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1886043">r1886043</a> | svn-role |
> 2021-01-30 04:00:53 +0000 (Sat, 30 Jan 2021) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1886019">r1886019</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1886019">r1886019</a>
> + Fix a potential NULL dereference in the config file parser.
> + Justification:
> + Missing return value check. C is hard.
> + Votes:
> + +1: stsp, hartmannathan, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1886044">r1886044</a> | svn-role |
> 2021-01-30 04:00:58 +0000 (Sat, 30 Jan 2021) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1885983">r1885983</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1885983">r1885983</a>
> + Fix <a href="/issue-4869">issue #4869</a>: 'svn info --xml'
> gives wrong 'source-right' of conflict
> + Justification:
> + Bugfix; 'svn info --xml' should give correct results; user
> complained.
> + Votes:
> + +1: hartmannathan, stsp, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1886045">r1886045</a> | svn-role |
> 2021-01-30 04:01:04 +0000 (Sat, 30 Jan 2021) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1886029">r1886029</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1886029">r1886029</a>
> + Fix several crashes and JNI warnings in javahl TunnelAgent.
> + Justification:
> + JavaHL shouldn't crash.
> + Votes:
> + +1: jcorvel, amiloslavskiy
> +
> +------------------------------------------------------------------------
> <a href="https://svn.apache.org/r1889654">r1889654</a> | svn-role |
> 2021-05-08 04:00:13 +0000 (Sat, 08 May 2021) | 7 lines
>
> Merge <a href="https://svn.apache.org/r1889487">r1889487</a> from trunk:
> @@ -62,6 +526,65 @@ Merge <a href="https://svn.apache.org/r1
> +1: jun66j5, futatuki
>
> ------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1899255">r1899255</a> | svn-role |
> 2022-03-27 18:03:44 +0000 (Sun, 27 Mar 2022) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1886708">r1886708</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1886708">r1886708</a>
> + swig-py: Fix dependency of make copy-swig-py target.
> + Justification:
> + Fix a regression introduced between 1.13.0 and 1.14.0.
> + Votes:
> + +1: futatuki, jun66j5
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1899256">r1899256</a> | svn-role |
> 2022-03-27 18:03:45 +0000 (Sun, 27 Mar 2022) | 7 lines
> +
> +Merge the <a href="https://svn.apache.org/r1883838">r1883838</a> group
> from trunk:
> +
> + * <a href="https://svn.apache.org/r1883838">r1883838</a>, <a href="
> https://svn.apache.org/r1883989">r1883989</a>, <a href="
> https://svn.apache.org/r1886460">r1886460</a>, <a href="
> https://svn.apache.org/r1886582">r1886582</a>
> + Add test coverage for CVE-2020-17525 (mod_authz_svn NULL deref)
> + Votes:
> + +1: stsp, markphip, hartmannathan
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1899257">r1899257</a> | svn-role |
> 2022-03-27 18:03:46 +0000 (Sun, 27 Mar 2022) | 9 lines
> +
> +Merge the <a href="https://svn.apache.org/r1887641">r1887641</a> group
> from trunk:
> +
> + * <a href="https://svn.apache.org/r1887641">r1887641</a>, <a href="
> https://svn.apache.org/r1890013">r1890013</a>
> + Fix encoding of error message on failure of system() call.
> + Justification:
> + Error messages should be displayed correctly even if non UTF-8
> locale.
> + Votes:
> + +1: futatuki, markphip, hartmannathan
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1899258">r1899258</a> | svn-role |
> 2022-03-27 18:03:47 +0000 (Sun, 27 Mar 2022) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1889629">r1889629</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1889629">r1889629</a>
> + Document how the port number is passed to custom tunnels.
> + Justification:
> + Documentation should be complete.
> + Votes:
> + +1: danielsh, markphip, hartmannathan
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1899259">r1899259</a> | svn-role |
> 2022-03-27 18:03:48 +0000 (Sun, 27 Mar 2022) | 10 lines
> +
> +Merge <a href="https://svn.apache.org/r1897449">r1897449</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1897449">r1897449</a>
> + tests: Include additional information in an error message.
> + Justification:
> + Trivial test harness change that may help investigate unreproducible
> + errors.
> + Votes:
> + +1: danielsh, markphip, hartmannathan
> +
> +------------------------------------------------------------------------
> </pre>
>
> <p>Further changes currently under consideration are listed in each
> release line's
>
>
>
Re: svn commit: r1899276 - /subversion/site/publish/upcoming.part.html
Posted by Daniel Sahlberg <da...@gmail.com>.
This commit doesn't look correct.
I executed the generate-upcoming-changes-log.sh manually yesterday and it
created r1899244, removing a lot of log entries belonging to 1.14.1. This
commit (which was executed by cron) restores them.
The crontab entry is:
[[[
# Puppet Name: Update our upcoming changes list
SVN=svn
15 4 * * * chronic ~/src/svn/site/tools/generate-upcoming-changes-log.sh
]]]
The script begins with a comment
[[[
# This should be run from the root of a branches/1.{9,10,11}.x working copy.
]]]
I suppose the crontab command should be changed to:
cd ~/src/svn/1.14.x && chronic
~/src/svn/site/tools/generate-upcoming-changes-log.sh
However that will create an "upcoming" only for 1.14 and not for 1.10. Any
thoughts?
Kind regards,
Daniel
Den mån 28 mars 2022 kl 06:15 skrev <sv...@apache.org>:
> Author: svn-role
> Date: Mon Mar 28 04:15:01 2022
> New Revision: 1899276
>
> URL: http://svn.apache.org/viewvc?rev=1899276&view=rev
> Log:
> * upcoming.part.html: Automatically regenerated
>
> Modified:
> subversion/site/publish/upcoming.part.html
>
> Modified: subversion/site/publish/upcoming.part.html
> URL:
> http://svn.apache.org/viewvc/subversion/site/publish/upcoming.part.html?rev=1899276&r1=1899275&r2=1899276&view=diff
>
> ==============================================================================
> --- subversion/site/publish/upcoming.part.html (original)
> +++ subversion/site/publish/upcoming.part.html Mon Mar 28 04:15:01 2022
> @@ -2,6 +2,470 @@
> <pre style="border-style: none">
> Changes in ^/subversion/branches/1.14.x:
> ------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1877978">r1877978</a> | svn-role |
> 2020-05-21 04:00:13 +0000 (Thu, 21 May 2020) | 7 lines
> +
> +Merge <a href="https://svn.apache.org/r1877788">r1877788</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1877788">r1877788</a>
> + Fix a broken link in a docstring.
> + Votes:
> + +1: danielsh, stsp
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1878211">r1878211</a> | svn-role |
> 2020-05-28 04:00:12 +0000 (Thu, 28 May 2020) | 10 lines
> +
> +Merge <a href="https://svn.apache.org/r1877072">r1877072</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1877072">r1877072</a>
> + svnmucc: Change an error message to state another possible cause of the
> + error.
> + Justification:
> + Error messages should be accurate. User reported (<a
> href="/issue-4854">issue #4854</a>).
> + Votes:
> + +1: danielsh, stsp, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1878213">r1878213</a> | svn-role |
> 2020-05-28 04:00:16 +0000 (Thu, 28 May 2020) | 11 lines
> +
> +Merge <a href="https://svn.apache.org/r1877259">r1877259</a> from trunk:
> +
> +* <a href="https://svn.apache.org/r1877259">r1877259</a>
> + Move variable declarations to the start of block the to fix
> + syntax errors with VC9 (Visual Studio 2008).
> + Justification:
> + Our code should be C90.
> + Votes:
> + +1: brane, stsp, jcorvel
> + +0: danielsh (from dev@)
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1878415">r1878415</a> | svn-role |
> 2020-06-03 04:00:20 +0000 (Wed, 03 Jun 2020) | 12 lines
> +
> +Merge the <a href="https://svn.apache.org/r1876707">r1876707</a> group
> from trunk:
> +
> + * <a href="https://svn.apache.org/r1876707">r1876707</a>, <a href="
> https://svn.apache.org/r1876734">r1876734</a>, <a href="
> https://svn.apache.org/r1877318">r1877318</a>, <a href="
> https://svn.apache.org/r1877712">r1877712</a>, <a href="
> https://svn.apache.org/r1878141">r1878141</a>, <a href="
> https://svn.apache.org/r1878142">r1878142</a>, <a href="
> https://svn.apache.org/r1878143">r1878143</a>,
> + <a href="https://svn.apache.org/r1878144">r1878144</a>
> + Various fixes for making the test suite run correctly with Python 3 on
> + Windows.
> + Justification:
> + Our test suite should test Subversion correctly also on Windows with
> + Python 3
> + Votes:
> + +1: futatuki, jcorvel, stsp
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1879245">r1879245</a> | svn-role |
> 2020-06-27 04:00:12 +0000 (Sat, 27 Jun 2020) | 11 lines
> +
> +Merge <a href="https://svn.apache.org/r1876662">r1876662</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1876662">r1876662</a>
> + Avoid check for SWIG version for Python bindings when --without-swig is
> + passed.
> + Justification:
> + SWIG python bindings should be able to be built without SWIG when we
> use
> + the release tarball
> + Votes:
> + +1: futatuki, stsp, rhuijben
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1879246">r1879246</a> | svn-role |
> 2020-06-27 04:00:17 +0000 (Sat, 27 Jun 2020) | 10 lines
> +
> +Merge <a href="https://svn.apache.org/r1876906">r1876906</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1876906">r1876906</a>
> + Make gen-make.py --debug work with Python 3
> + Justification:
> + We should also be able to build in Debug configuration with Python 3
> + on Windows.
> + Votes:
> + +1: jcorvel, stsp, rhuijben
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1879797">r1879797</a> | svn-role |
> 2020-07-12 04:00:12 +0000 (Sun, 12 Jul 2020) | 10 lines
> +
> +Merge <a href="https://svn.apache.org/r1876410">r1876410</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1876410">r1876410</a>
> + Fix the .editorconfig stanza for Makefile's.
> + Justification:
> + Make $EDITOR do the right thing on any backport branches we may
> create
> + off this stabilization branch.
> + Votes:
> + +1: danielsh, stsp, jamessan
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1879798">r1879798</a> | svn-role |
> 2020-07-12 04:00:17 +0000 (Sun, 12 Jul 2020) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1878413">r1878413</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1878413">r1878413</a>
> + autogen.sh: Remove per SWIG bindings checked files on release mode.
> + Justification:
> + The release tarballs should not contain .swig_*_checked files
> + Votes:
> + +1: futatuki, rhuijben, jamessan
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1879799">r1879799</a> | svn-role |
> 2020-07-12 04:00:23 +0000 (Sun, 12 Jul 2020) | 9 lines
> +
> +Merge the <a href="https://svn.apache.org/r1878909">r1878909</a> group
> from trunk:
> +
> + * <a href="https://svn.apache.org/r1878909">r1878909</a>, <a href="
> https://svn.apache.org/r1878918">r1878918</a>, <a href="
> https://svn.apache.org/r1878950">r1878950</a>
> + Fix a number of thinkos in human-readable file size formatting.
> + Justification:
> + Fixes wrong output and an assertion failure in debug mode.
> + Votes:
> + +1: brane, rhuijben, jamessan
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1879800">r1879800</a> | svn-role |
> 2020-07-12 04:00:28 +0000 (Sun, 12 Jul 2020) | 14 lines
> +
> +Merge <a href="https://svn.apache.org/r1879198">r1879198</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1879198">r1879198</a>
> + Fix an invalid quoting in working copy upgrade system that only works
> + because SQLite automatically fixed this. More recent SQLite functions
> + will signal an error when deprecated features are disabled.
> + Justification:
> + Causes user-visible errors.
> + Note:
> + This filechange by itself doesn't trigger a change that make
> will
> + handle. So make sure you recompile the sql queries for testing.
> + Votes:
> + +1: rhuijben, danielsh, jamessan
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1880465">r1880465</a> | svn-role |
> 2020-07-31 04:00:11 +0000 (Fri, 31 Jul 2020) | 10 lines
> +
> +Merge <a href="https://svn.apache.org/r1877960">r1877960</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1877960">r1877960</a>
> + INSTALL (I.C.12): Add Note that non-release mode is required for
> building
> + SWIG Python 2 bindings.
> + Justification:
> + We've not entirely dropped Python 2 bindings support on 1.14.x
> yet
> + Votes:
> + +1: futatuki, stsp, rhuijben
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1880916">r1880916</a> | svn-role |
> 2020-08-17 04:00:17 +0000 (Mon, 17 Aug 2020) | 11 lines
> +
> +Merge the 1.14.x-<a href="https://svn.apache.org/r1880374">r1880374</a>-fsfs
> branch:
> +
> + * <a href="https://svn.apache.org/r1880374
> ">r1880374</a>:subversion/libsvn_fs_fs
> + Fix an uninitialized read in svn_fs_fs__index_append().
> + Justification:
> + Uninitialized reads are potentially undefined behaviour.
> + Branch:
> + 1.14.x-<a href="https://svn.apache.org/r1880374">r1880374</a>-fsfs
> + Votes:
> + +1: danielsh, hartmannathan, jamessan
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1881075">r1881075</a> | svn-role |
> 2020-08-22 04:00:21 +0000 (Sat, 22 Aug 2020) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1880886">r1880886</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1880886">r1880886</a>
> + Fix crash in JavaHL JNI wrapper caused by object lifetimes
> + Justification:
> + Fixes a crash encountered with GCC 10.
> + Votes:
> + +1: hartmannathan, jamessan
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1883406">r1883406</a> | svn-role |
> 2020-11-14 04:00:12 +0000 (Sat, 14 Nov 2020) | 9 lines
> +
> +Merge the <a href="https://svn.apache.org/r1878855">r1878855</a> group
> from trunk:
> +
> + * <a href="https://svn.apache.org/r1878855">r1878855</a>, <a href="
> https://svn.apache.org/r1878859">r1878859</a>
> + Make the hot-backup.py script work with Python 3.
> + Justification:
> + Script should work with Python3
> + Votes:
> + +1: jamessan, brane
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1883407">r1883407</a> | svn-role |
> 2020-11-14 04:00:17 +0000 (Sat, 14 Nov 2020) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1882115">r1882115</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1882115">r1882115</a>
> + JavaHL: Fix incorrect cache in SVNBase::createCppBoundObject
> + Justification:
> + Fixes a potential crash.
> + Votes:
> + +1: hartmannathan, brane
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1884481">r1884481</a> | svn-role |
> 2020-12-16 04:00:11 +0000 (Wed, 16 Dec 2020) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1882157">r1882157</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1882157">r1882157</a>
> + Do not suggest --help -v for commands which do not support -v.
> + Justification:
> + The --help message for several commands is misleading. User
> complained.
> + Votes:
> + +1: stsp, brane, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1884482">r1884482</a> | svn-role |
> 2020-12-16 04:00:16 +0000 (Wed, 16 Dec 2020) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1877338">r1877338</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1877338">r1877338</a>
> + Add SWIG4 support for SWIG Python binding on Windows.
> + Justification:
> + SWIG Python bindings should be able to build with SWIG4 on Windows,
> too
> + Votes:
> + +1: futatuki, jun66j5, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1884483">r1884483</a> | svn-role |
> 2020-12-16 04:00:22 +0000 (Wed, 16 Dec 2020) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1883335">r1883335</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1883335">r1883335</a>
> + Fix unable to load *.pyd files with Python 3.8.x on Windows.
> + Justification:
> + Make Python bindings available with Python 3.8+ on Windows.
> + Votes:
> + +1: jun66j5, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1884484">r1884484</a> | svn-role |
> 2020-12-16 04:00:27 +0000 (Wed, 16 Dec 2020) | 10 lines
> +
> +Merge <a href="https://svn.apache.org/r1883337">r1883337</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1883337">r1883337</a>
> + Remove uses of os.dup2() from run_tests.py in order to adapt the new
> + console reader and writer on Windows since Python 3.6.
> + Justification:
> + PYTHONLEGACYWINDOWSSTDIO is no longer needed to run unit tests on
> Windows.
> + Votes:
> + +1: jun66j5, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1884535">r1884535</a> | svn-role |
> 2020-12-17 04:00:12 +0000 (Thu, 17 Dec 2020) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1883570">r1883570</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1883570">r1883570</a>
> + Fix C4204 errors while building swig-py with Python 3.9 on Windows.
> + Justification:
> + Allow building Python bindings with Python 3.9 on Windows.
> + Votes:
> + +1: jun66j5, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1884589">r1884589</a> | svn-role |
> 2020-12-18 04:00:24 +0000 (Fri, 18 Dec 2020) | 9 lines
> +
> +Merge the <a href="https://svn.apache.org/r1881958">r1881958</a> group
> from trunk:
> +
> + * <a href="https://svn.apache.org/r1881958">r1881958</a>, 1882128
> + Restoring support for building with APR 1.4.
> + Justification:
> + Allow building on older distros such as CentOS 7.
> + Votes:
> + +1: brane, hartmannathan, julianfoad
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1884590">r1884590</a> | svn-role |
> 2020-12-18 04:00:28 +0000 (Fri, 18 Dec 2020) | 12 lines
> +
> +Merge <a href="https://svn.apache.org/r1882326">r1882326</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1882326">r1882326</a>
> + Fix <a href="/issue-4762">issue #4762</a> "authz doesn't
> combine global and repository rules"
> + Justification:
> + Restore behaviour of SVN 1.9: It is now again possible to override
> + per-path access rules for specific users (and groups) at the global
> + level. Such global rules are overridden by repository-specific rules
> + only if both the user and the path match the repository-specific
> rule.
> + Votes:
> + +1: stsp, brane, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1884591">r1884591</a> | svn-role |
> 2020-12-18 04:00:36 +0000 (Fri, 18 Dec 2020) | 10 lines
> +
> +Merge the <a href="https://svn.apache.org/r1878997">r1878997</a> group
> from trunk:
> +
> + * <a href="https://svn.apache.org/r1878997">r1878997</a>, <a href="
> https://svn.apache.org/r1879192">r1879192</a>, <a href="
> https://svn.apache.org/r1879474">r1879474</a>, <a href="
> https://svn.apache.org/r1879959">r1879959</a>
> + Fix <a href="/issue-4859">issue #4859</a>, Merge removing a folder
> with non-inheritable mergeinfo
> + -> E155023: can't set properties: invalid status for updating
> properties
> + Justification:
> + Annoying failure, encountered in real use.
> + Votes:
> + +1: julianfoad, hartmannathan, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1884592">r1884592</a> | svn-role |
> 2020-12-18 04:00:41 +0000 (Fri, 18 Dec 2020) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1875675">r1875675</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1875675">r1875675</a>
> + Rewrite load_normalize_node_props to avoid literal trailing spaces.
> + Justification:
> + Prevents the bug fixed in <a href="https://svn.apache.org/r1875620">r1875620</a>
> from recurring.
> + Votes:
> + +1: danielsh, brane, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1884617">r1884617</a> | svn-role |
> 2020-12-19 04:00:12 +0000 (Sat, 19 Dec 2020) | 11 lines
> +
> +Merge <a href="https://svn.apache.org/r1880192">r1880192</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1880192">r1880192</a>
> + Fix <a href="/issue-4862">issue #4862</a> "Merge: the resulting
> mergeinfo is non-deterministic".
> + Justification:
> + Non-deterministic merge result is bad.
> + Depends:
> + <a href="https://svn.apache.org/r1878997">r1878997</a>, <a href="
> https://svn.apache.org/r1879192">r1879192</a>, <a href="
> https://svn.apache.org/r1879474">r1879474</a>, <a href="
> https://svn.apache.org/r1879959">r1879959</a> (Fix <a
> href="/issue-4859">issue #4859</a>)
> + Votes:
> + +1: julianfoad, hartmannathan, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1884618">r1884618</a> | svn-role |
> 2020-12-19 04:00:18 +0000 (Sat, 19 Dec 2020) | 11 lines
> +
> +Merge the <a href="https://svn.apache.org/r1881985">r1881985</a> group
> from trunk:
> +
> + * <a href="https://svn.apache.org/r1881985">r1881985</a>, <a href="
> https://svn.apache.org/r1882105">r1882105</a>
> + Follow up to <a href="https://svn.apache.org/r1880192">r1880192</a>:
> Fix an EOL issue in test on Windows.
> + Justification:
> + We should test correctly on Windows environment, too.
> + Depends:
> + <a href="https://svn.apache.org/r1880192">r1880192</a>
> + Votes:
> + +1: futatuki, jcorvel, hartmannathan
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1884665">r1884665</a> | svn-role |
> 2020-12-21 04:00:12 +0000 (Mon, 21 Dec 2020) | 10 lines
> +
> +Merge <a href="https://svn.apache.org/r1884642">r1884642</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1884642">r1884642</a>
> + Fix win-tests.py is unable to load Python bindings with debug
> configuration
> + since Python 3.5.
> + Justification:
> + Allow unit tests with debug configuration on Windows.
> + Votes:
> + +1: jun66j5, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1885507">r1885507</a> | svn-role |
> 2021-01-15 04:00:13 +0000 (Fri, 15 Jan 2021) | 11 lines
> +
> +Merge <a href="https://svn.apache.org/r1885112">r1885112</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1885112">r1885112</a>
> + swig-py: Fix a typo in tests.
> + Justification:
> + This typo causes DeprecationWarning since Python 3.6 and it will be
> + Syntax error.
> + Votes:
> + +1: futatuki
> + +0: jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1885828">r1885828</a> | svn-role |
> 2021-01-23 04:00:42 +0000 (Sat, 23 Jan 2021) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1885795">r1885795</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1885795">r1885795</a>
> + Update copyright year to 2021.
> + Justification:
> + The future is here!
> + Votes:
> + +1: stsp, futatuki, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1885829">r1885829</a> | svn-role |
> 2021-01-23 04:00:51 +0000 (Sat, 23 Jan 2021) | 9 lines
> +
> +Merge the <a href="https://svn.apache.org/r1884427">r1884427</a> group
> from trunk:
> +
> + * <a href="https://svn.apache.org/r1884427">r1884427</a>, <a href="
> https://svn.apache.org/r1885557">r1885557</a>, <a href="
> https://svn.apache.org/r1885600">r1885600</a>, <a href="
> https://svn.apache.org/r1885656">r1885656</a>, <a href="
> https://svn.apache.org/r1885784">r1885784</a>, <a href="
> https://svn.apache.org/r1885785">r1885785</a>
> + Make mailer.py work properly with Python 3.
> + Justification:
> + Hook scripts should support Python 3 on 1.14.x.
> + Votes:
> + +1: stsp, futatuki
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1885931">r1885931</a> | svn-role |
> 2021-01-27 04:00:18 +0000 (Wed, 27 Jan 2021) | 10 lines
> +
> +Merge <a href="https://svn.apache.org/r1877794">r1877794</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1877794">r1877794</a>
> + Use Doxygen comment leader for comments with doxygen syntax.
> + Justification:
> + Improve $EDITOR's syntax highlighting.
> + Votes:
> + +0: danielsh
> + +1: brane, jamessan
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1886041">r1886041</a> | svn-role |
> 2021-01-30 04:00:44 +0000 (Sat, 30 Jan 2021) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1882234">r1882234</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1882234">r1882234</a>
> + Fix file name to edit from utf8 to local style.
> + Justification:
> + Editor invocation should work correctly in any valid locale.
> + Votes:
> + +1: futatuki, jcorvel, stsp
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1886042">r1886042</a> | svn-role |
> 2021-01-30 04:00:48 +0000 (Sat, 30 Jan 2021) | 12 lines
> +
> +Merge <a href="https://svn.apache.org/r1885953">r1885953</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1885953">r1885953</a>
> + Fix file name encoding and quoting when invoking editor on Windows.
> + Justification:
> + Invoking editor with special character or spaces in path is broken
> + on Windows.
> + Depends:
> + <a href="https://svn.apache.org/r1882234">r1882234</a>
> + Votes:
> + +1: jcorvel, futatuki, stsp
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1886043">r1886043</a> | svn-role |
> 2021-01-30 04:00:53 +0000 (Sat, 30 Jan 2021) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1886019">r1886019</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1886019">r1886019</a>
> + Fix a potential NULL dereference in the config file parser.
> + Justification:
> + Missing return value check. C is hard.
> + Votes:
> + +1: stsp, hartmannathan, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1886044">r1886044</a> | svn-role |
> 2021-01-30 04:00:58 +0000 (Sat, 30 Jan 2021) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1885983">r1885983</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1885983">r1885983</a>
> + Fix <a href="/issue-4869">issue #4869</a>: 'svn info --xml'
> gives wrong 'source-right' of conflict
> + Justification:
> + Bugfix; 'svn info --xml' should give correct results; user
> complained.
> + Votes:
> + +1: hartmannathan, stsp, jcorvel
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1886045">r1886045</a> | svn-role |
> 2021-01-30 04:01:04 +0000 (Sat, 30 Jan 2021) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1886029">r1886029</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1886029">r1886029</a>
> + Fix several crashes and JNI warnings in javahl TunnelAgent.
> + Justification:
> + JavaHL shouldn't crash.
> + Votes:
> + +1: jcorvel, amiloslavskiy
> +
> +------------------------------------------------------------------------
> <a href="https://svn.apache.org/r1889654">r1889654</a> | svn-role |
> 2021-05-08 04:00:13 +0000 (Sat, 08 May 2021) | 7 lines
>
> Merge <a href="https://svn.apache.org/r1889487">r1889487</a> from trunk:
> @@ -62,6 +526,65 @@ Merge <a href="https://svn.apache.org/r1
> +1: jun66j5, futatuki
>
> ------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1899255">r1899255</a> | svn-role |
> 2022-03-27 18:03:44 +0000 (Sun, 27 Mar 2022) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1886708">r1886708</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1886708">r1886708</a>
> + swig-py: Fix dependency of make copy-swig-py target.
> + Justification:
> + Fix a regression introduced between 1.13.0 and 1.14.0.
> + Votes:
> + +1: futatuki, jun66j5
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1899256">r1899256</a> | svn-role |
> 2022-03-27 18:03:45 +0000 (Sun, 27 Mar 2022) | 7 lines
> +
> +Merge the <a href="https://svn.apache.org/r1883838">r1883838</a> group
> from trunk:
> +
> + * <a href="https://svn.apache.org/r1883838">r1883838</a>, <a href="
> https://svn.apache.org/r1883989">r1883989</a>, <a href="
> https://svn.apache.org/r1886460">r1886460</a>, <a href="
> https://svn.apache.org/r1886582">r1886582</a>
> + Add test coverage for CVE-2020-17525 (mod_authz_svn NULL deref)
> + Votes:
> + +1: stsp, markphip, hartmannathan
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1899257">r1899257</a> | svn-role |
> 2022-03-27 18:03:46 +0000 (Sun, 27 Mar 2022) | 9 lines
> +
> +Merge the <a href="https://svn.apache.org/r1887641">r1887641</a> group
> from trunk:
> +
> + * <a href="https://svn.apache.org/r1887641">r1887641</a>, <a href="
> https://svn.apache.org/r1890013">r1890013</a>
> + Fix encoding of error message on failure of system() call.
> + Justification:
> + Error messages should be displayed correctly even if non UTF-8
> locale.
> + Votes:
> + +1: futatuki, markphip, hartmannathan
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1899258">r1899258</a> | svn-role |
> 2022-03-27 18:03:47 +0000 (Sun, 27 Mar 2022) | 9 lines
> +
> +Merge <a href="https://svn.apache.org/r1889629">r1889629</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1889629">r1889629</a>
> + Document how the port number is passed to custom tunnels.
> + Justification:
> + Documentation should be complete.
> + Votes:
> + +1: danielsh, markphip, hartmannathan
> +
> +------------------------------------------------------------------------
> +<a href="https://svn.apache.org/r1899259">r1899259</a> | svn-role |
> 2022-03-27 18:03:48 +0000 (Sun, 27 Mar 2022) | 10 lines
> +
> +Merge <a href="https://svn.apache.org/r1897449">r1897449</a> from trunk:
> +
> + * <a href="https://svn.apache.org/r1897449">r1897449</a>
> + tests: Include additional information in an error message.
> + Justification:
> + Trivial test harness change that may help investigate unreproducible
> + errors.
> + Votes:
> + +1: danielsh, markphip, hartmannathan
> +
> +------------------------------------------------------------------------
> </pre>
>
> <p>Further changes currently under consideration are listed in each
> release line's
>
>
>