You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by ha...@apache.org on 2021/04/26 04:38:31 UTC
svn commit: r1889189 - in /subversion/site/staging: ./ docs/community-guide/
docs/release-notes/ security/
Author: hartmannathan
Date: Mon Apr 26 04:38:31 2021
New Revision: 1889189
URL: http://svn.apache.org/viewvc?rev=1889189&view=rev
Log:
* site/staging: Catch-up merge from site/publish
Modified:
subversion/site/staging/ (props changed)
subversion/site/staging/docs/community-guide/issues.part.html
subversion/site/staging/docs/community-guide/releasing.part.html
subversion/site/staging/docs/release-notes/1.1.html
subversion/site/staging/docs/release-notes/1.9.html
subversion/site/staging/index.html (props changed)
subversion/site/staging/mailing-lists.html
subversion/site/staging/news.html (props changed)
subversion/site/staging/roadmap.html (contents, props changed)
subversion/site/staging/security/index.html
subversion/site/staging/upcoming.part.html
Propchange: subversion/site/staging/
------------------------------------------------------------------------------
Merged /subversion/site/publish:r1885718-1889188
Modified: subversion/site/staging/docs/community-guide/issues.part.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/docs/community-guide/issues.part.html?rev=1889189&r1=1889188&r2=1889189&view=diff
==============================================================================
--- subversion/site/staging/docs/community-guide/issues.part.html (original)
+++ subversion/site/staging/docs/community-guide/issues.part.html Mon Apr 26 04:38:31 2021
@@ -410,7 +410,11 @@ Security reporting instructions</a>.</p>
</div>
-<h3>Security approach in Subversion's Design and Implementation</h3>
+<div class="h3" id="security-approach">
+<h3>Security approach in Subversion's Design and Implementation
+ <a class="sectionlink" href="<!--#echo var="GUIDE_ISSUES_PAGE" -->#security-approach"
+ title="Link to this section">¶</a>
+</h3>
<p>Subversion's first job is keeping your data safe. To do that, the
Subversion development community takes security very seriously. One way we
@@ -424,7 +428,13 @@ SASL or by the Apache HTTP Server and it
degree that we can leverage the knowledge of security experts by using the
third-party libraries and APIs they provide, we will continue to do so.</p>
-<h3>Handling reported security vulnerabilities</h3>
+</div> <!-- security-approach -->
+
+<div class="h3" id="security-handling">
+<h3>Handling reported security vulnerabilities
+ <a class="sectionlink" href="<!--#echo var="GUIDE_ISSUES_PAGE" -->#security-handling"
+ title="Link to this section">¶</a>
+</h3>
<p>This document describes the steps we take when receiving or finding an
issue which may be classified as having security implications, and is meant to
@@ -440,7 +450,11 @@ to committers for the same.</p>
Other stuff?
-->
-<h4>Mailing Lists</h4>
+<div class="h4" id="security-handling-mailing-lists">
+<h4>Mailing Lists
+ <a class="sectionlink" href="<!--#echo var="GUIDE_ISSUES_PAGE" -->#security-handling-mailing-lists"
+ title="Link to this section">¶</a>
+</h4>
<p>Security problems should be discussed on private@subversion.apache.org +
security@apache.org. security@subversion.apache.org is a convenience alias
@@ -448,7 +462,13 @@ that targets these two lists. (Note tha
it is not a mailing list, so you can't subscribe/unsubscribe to it
separately.)</p>
-<h4>Tracking Issues</h4>
+</div> <!-- security-handling-mailing-lists -->
+
+<div class="h4" id="security-handling-tracking-issues">
+<h4>Tracking Issues
+ <a class="sectionlink" href="<!--#echo var="GUIDE_ISSUES_PAGE" -->#security-handling-tracking-issues"
+ title="Link to this section">¶</a>
+</h4>
<p>We publish the list of previous security advisories at:
<a href="http://subversion.apache.org/security/#advisories">http://subversion.apache.org/security/</a></p>
@@ -456,7 +476,13 @@ separately.)</p>
<p>We track in-progress issues in the PMC's private repository:
<tt>https://svn.apache.org/repos/private/pmc/subversion/security</tt></p>
-<h4>Procedures We Follow</h4>
+</div> <!-- security-handling-tracking-issues -->
+
+<div class="h4" id="security-handling-procedures">
+<h4>Procedures We Follow
+ <a class="sectionlink" href="<!--#echo var="GUIDE_ISSUES_PAGE" -->#security-handling-procedures"
+ title="Link to this section">¶</a>
+</h4>
<p>We aim to follow a published procedure.</p>
@@ -469,6 +495,9 @@ are managed in the PMC's private reposit
<a href="how-to-roll-releases-in-private.txt">How to Roll Releases in Private</a>.
At present we do <b>not</b> usually use this procedure.</p>
+</div> <!-- security-handling-procedures -->
+
+</div> <!-- security-handling -->
</div> <!-- security -->
Modified: subversion/site/staging/docs/community-guide/releasing.part.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/docs/community-guide/releasing.part.html?rev=1889189&r1=1889188&r2=1889189&view=diff
==============================================================================
--- subversion/site/staging/docs/community-guide/releasing.part.html (original)
+++ subversion/site/staging/docs/community-guide/releasing.part.html Mon Apr 26 04:38:31 2021
@@ -1517,7 +1517,11 @@ developed.</p>
Release Manager creates it with one of the following procedures (substitute
A.B with the version you're preparing, eg. 1.3, or 2.0).</p>
-<h4>Automated Procedure with release.py</h4>
+<div class="h4" id="creating-branch-automated">
+<h4>Automated Procedure with release.py
+ <a class="sectionlink" href="#creating-branch-automated"
+ title="Link to this section">¶</a>
+</h4>
<p>Most of the work to create a release branch can be automated by
tools/dist/release.py:</p>
<p>Run this in an empty-ish directory where it will make some temporary checkouts:</p>
@@ -1534,8 +1538,13 @@ svn ci -m "Add release notes template."
<div class="notice">Some steps are not automated by release.py and must be
done manually—skip to the end of the following section, where they are
highlighted:</div>
+</div> <!-- creating-branch-automated -->
-<h4>Manual Procedure</h4>
+<div class="h4" id="creating-branch-manual">
+<h4>Manual Procedure
+ <a class="sectionlink" href="#creating-branch-manual"
+ title="Link to this section">¶</a>
+</h4>
<p>Most of the steps in this section can be automated by
tools/dist/release.py—see above—but are documented here in case
the Release Manager wants to do them manually:</p>
@@ -1599,6 +1608,7 @@ the Release Manager wants to do them man
<li><p>Create a template release-notes document,
<tt>site/publish/docs/release-notes/A.B.html</tt></p></li>
</ul>
+</div> <!-- creating-branch-manual -->
<div class="notice">The following steps must be done manually, even when
using release.py to automate most of the other steps:</div>
Modified: subversion/site/staging/docs/release-notes/1.1.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/docs/release-notes/1.1.html?rev=1889189&r1=1889188&r2=1889189&view=diff
==============================================================================
--- subversion/site/staging/docs/release-notes/1.1.html (original)
+++ subversion/site/staging/docs/release-notes/1.1.html Mon Apr 26 04:38:31 2021
@@ -26,7 +26,11 @@ href="http://svnbook.red-bean.com/svnboo
href="http://svnbook.red-bean.com/svnbook-1.1/pr02s07.html">the new
1.1 features</a>. Still, here are some brief release notes.</p>
-<h3>Overview</h3>
+<div class="h3" id="overview">
+<h3>Overview
+ <a class="sectionlink" href="#overview"
+ title="Link to this section">¶</a>
+</h3>
<p>Subversion 1.1 can best be summarized as: (1) an optional new
non-database repository back-end, and (2) a whole slew of client-side
@@ -37,7 +41,13 @@ releases. The 1.0.x releases contain no
backported from the 1.1 development line. Subversion 1.1 introduces
new features and fixes many smaller bugs.</p>
-<h3>Compatibility Concerns</h3>
+</div> <!-- #overview -->
+
+<div class="h3" id="compatibility-concerns">
+<h3>Compatibility Concerns
+ <a class="sectionlink" href="#compatibility-concerns"
+ title="Link to this section">¶</a>
+</h3>
<p>Subversion's compatibility and version-numbering policy is
documented <a href="hacking.html#release-numbering">here</a>. Here's
@@ -62,10 +72,19 @@ a quick summary:</p>
</ul>
+</div> <!-- compatibility-concerns -->
-<h3>New Major Features</h3>
-
-<h4>Non-database repositories (<em>new server feature</em>)</h4>
+<div class="h3" id="new-major-features">
+<h3>New Major Features
+ <a class="sectionlink" href="#new-major-features"
+ title="Link to this section">¶</a>
+</h3>
+
+<div class="h4" id="non-database-repositories">
+<h4>Non-database repositories (<em>new server feature</em>)
+ <a class="sectionlink" href="#non-database-repositories"
+ title="Link to this section">¶</a>
+</h4>
<p>It's now possible to create repositories that don't use a
BerkeleyDB database. Instead, these new repositories store data in
@@ -91,8 +110,13 @@ a quick summary:</p>
compile time, <tt>'svnadmin create'</tt> will default to type
fsfs.</p>
+</div> <!-- #non-database-repositories -->
-<h4>Symlink versioning (<em>new client feature</em>)</h4>
+<div class="h4" id="symlink-versioning">
+<h4>Symlink versioning (<em>new client feature</em>)
+ <a class="sectionlink" href="#symlink-versioning"
+ title="Link to this section">¶</a>
+</h4>
<p>This feature allows unix users to place symlinks under version
control. (Note: this is <em>not</em> about creating links
@@ -108,8 +132,13 @@ a quick summary:</p>
will still have an affect of changing the symlink on a unix
system.)</p>
+</div> <!-- #symlink-versioning -->
-<h4>Client follows renames (<em>new client feature</em>)</h4>
+<div class="h4" id="client-follows-renames">
+<h4>Client follows renames (<em>new client feature</em>)
+ <a class="sectionlink" href="#client-follows-renames"
+ title="Link to this section">¶</a>
+</h4>
<p>Subversion makes a lot of noise about the way branches (copies) of
files and directories maintain historical connections to their
@@ -122,9 +151,14 @@ a quick summary:</p>
backwards through renames when examining older versions of files
and directories.</p>
+</div> <!-- #client-follows-renames -->
+<div class="h4" id="auto-escaping-uri">
<h4>Command line auto-escaping of URI and IRIs (<em>new client
-feature</em>)</h4>
+feature</em>)
+ <a class="sectionlink" href="#auto-escaping-uri"
+ title="Link to this section">¶</a>
+</h4>
<p>In the 1.0 command line client, users had to escape URLs manually.
The client only accepted "legally correct" URLs, such as</p>
@@ -141,9 +175,13 @@ feature</em>)</h4>
progress; see <a
href="https://www.w3.org/International/iri-edit/">the draft spec</a>.</p>
+</div> <!-- #auto-escaping-uri -->
-
-<h4>Localized messages (<em>new client feature</em>)</h4>
+<div class="h4" id="localized-messages">
+<h4>Localized messages (<em>new client feature</em>)
+ <a class="sectionlink" href="#localized-messages"
+ title="Link to this section">¶</a>
+</h4>
<p>Subversion 1.1 is now using gettext() to display translated error,
informational, and help messages to the user. We currently have
@@ -161,14 +199,31 @@ feature</em>)</h4>
[...]
</pre>
+</div> <!-- #localized-messages -->
-<h3>Other Improvements</h3>
+</div> <!-- #new-major-features -->
-<h4>Speed optimizations: (<em>requires both new client and server</em>)</h4>
+<div class="h3" id="other-improvements">
+<h3>Other Improvements
+ <a class="sectionlink" href="#other-improvements"
+ title="Link to this section">¶</a>
+</h3>
+
+<div class="h4" id="speed-optimizations">
+<h4>Speed optimizations: (<em>requires both new client and server</em>)
+ <a class="sectionlink" href="#speed-optimizations"
+ title="Link to this section">¶</a>
+</h4>
<p>Faster <tt>checkout</tt>, <tt>update</tt>, <tt>status</tt>, and
<tt>blame</tt> commands.</p>
-<h4>Shareable working copies: (<em>client fix</em>)</h4>
+</div> <!-- #speed-optimizations -->
+
+<div class="h4" id="shareable-working-copies">
+<h4>Shareable working copies: (<em>client fix</em>)
+ <a class="sectionlink" href="#shareable-working-copies"
+ title="Link to this section">¶</a>
+</h4>
<p>There have been historical problems with permissions when multiple
users share a working copy. We believe these problems to be fixed
@@ -176,7 +231,13 @@ now, see <a
href="https://issues.apache.org/jira/browse/SVN-1509">issue
#1509</a>.</p>
-<h4>New 'store-passwords' runtime variable: (<em>new client feature</em>)</h4>
+</div> <!-- #shareable-working-copies -->
+
+<div class="h4" id="store-passwords-variable">
+<h4>New 'store-passwords' runtime variable: (<em>new client feature</em>)
+ <a class="sectionlink" href="#store-passwords-variable"
+ title="Link to this section">¶</a>
+</h4>
<p>The previous <tt>store-auth-creds</tt> runtime variable still
works, but many users were unhappy with it. It disables <b>all</b>
@@ -184,12 +245,24 @@ credentials caching on local disk: passw
This new runtime variable only disables password caching, so that
server certificates can still be remembered.</p>
-<h4>Bugfixes:</h4>
+</div> <!-- #store-passwords-variable -->
+
+<div class="h4" id="bugfixes">
+<h4>Bugfixes:
+ <a class="sectionlink" href="#bugfixes"
+ title="Link to this section">¶</a>
+</h4>
<p>More than 40 "small" bugs fixed. See the <a
href="https://svn.apache.org/repos/asf/subversion/trunk/CHANGES">CHANGES</a> file
for details.</p>
-<h4>New subcommand switches:</h4>
+</div> <!-- #bugfixes -->
+
+<div class="h4" id="new-subcommand-switches">
+<h4>New subcommand switches:
+ <a class="sectionlink" href="#new-subcommand-switches"
+ title="Link to this section">¶</a>
+</h4>
<dl>
<dt><tt>svn blame --verbose</tt></dt>
<dd>show extra annotation information</dd>
@@ -235,8 +308,15 @@ href="https://svn.apache.org/repos/asf/s
</dl>
+</div> <!-- #new-subcommand-switches -->
-<h3>Developer Changes</h3>
+</div> <!-- #other-improvements -->
+
+<div class="h3" id="developer-changes">
+<h3>Developer Changes
+ <a class="sectionlink" href="#developer-changes"
+ title="Link to this section">¶</a>
+</h3>
<p>A number of new 1.1 functions have been introduced, with the "2"
suffix, and the older versions are now marked deprecated (and will be
@@ -250,8 +330,13 @@ bindings. More coverage, more functiona
integrated into the main Subversion build system (just run 'make
swig-py' or 'make swig-pl' or 'make javahl').</p>
+</div> <!-- #developer-changes -->
-<h3>Testimonials and Roadmap</h3>
+<div class="h3" id="testimonials-and-roadmap">
+<h3>Testimonials and Roadmap
+ <a class="sectionlink" href="#testimonials-and-roadmap"
+ title="Link to this section">¶</a>
+</h3>
<p>See our <a href="/roadmap.html">roadmap</a> for what the future
looks like.</p>
@@ -265,6 +350,8 @@ Subversion-related sites, projects, and
href="http://subversion.tigris.org/links.html">links
page</a>.</p>
+</div> <!-- #testimonials-and-roadmap -->
+
<!-- ***************** END CONTENT ****************** -->
</div> <!-- #site-content -->
</body>
Modified: subversion/site/staging/docs/release-notes/1.9.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/docs/release-notes/1.9.html?rev=1889189&r1=1889188&r2=1889189&view=diff
==============================================================================
--- subversion/site/staging/docs/release-notes/1.9.html (original)
+++ subversion/site/staging/docs/release-notes/1.9.html Mon Apr 26 04:38:31 2021
@@ -1237,6 +1237,11 @@ For example, the following conflict:</p>
Unconflicted lines
</pre>
+<p>Tip: Manually applying to the
+<tt>>>>>>>></tt> hunk the changes that would transform
+the <tt>|||||||</tt> hunk into the <tt><<<<<<<</tt> hunk
+is equivalent, and in real-life conflicts is sometimes easier.</p>
+
<p>The three-way conflict display was already used by property conflicts and
by the interactive conflicts resolver in previous releases of Subversion.</p>
Propchange: subversion/site/staging/index.html
------------------------------------------------------------------------------
Merged /subversion/site/publish/index.html:r1879655-1889188
Modified: subversion/site/staging/mailing-lists.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/mailing-lists.html?rev=1889189&r1=1889188&r2=1889189&view=diff
==============================================================================
--- subversion/site/staging/mailing-lists.html (original)
+++ subversion/site/staging/mailing-lists.html Mon Apr 26 04:38:31 2021
@@ -160,6 +160,8 @@ delay for your post to appear (see below
>svn.haxx.se</a> (archives up to December 2020, no longer updated)</li>
<li><a href="nntps://news.gmane.org/gmane.comp.version-control.subversion.user"
>news.gmane.org</a> (NNTP/SSL)</li>
+ <li><a href="https://www.mail-archive.com/users@subversion.apache.org/"
+ >mail-archive.com</a> (searchable)</li>
</ul></td>
</tr>
<tr>
@@ -222,6 +224,8 @@ delay for your post to appear (see below
>svn.haxx.se</a> (archives up to December 2020, no longer updated)</li>
<li><a href="nntps://news.gmane.org/gmane.comp.version-control.subversion.devel"
>news.gmane.org</a> (NNTP/SSL)</li>
+ <li><a href="https://www.mail-archive.com/dev@subversion.apache.org/"
+ >mail-archive.com</a> (searchable)</li>
</ul></td>
</tr>
</tbody>
@@ -260,6 +264,8 @@ delay for your post to appear (see below
>mail-archives.apache.org</a></li>
<li><a href="https://lists.apache.org/list.html?commits@subversion.apache.org"
>lists.apache.org</a> (searchable)</li>
+ <li><a href="https://www.mail-archive.com/commits@subversion.apache.org/"
+ >mail-archive.com</a> (searchable)</li>
</ul></td>
</tr>
</tbody>
@@ -300,6 +306,8 @@ delay for your post to appear (see below
>mail-archives.apache.org</a></li>
<li><a href="https://lists.apache.org/list.html?announce@subversion.apache.org"
>lists.apache.org</a> (searchable)</li>
+ <li><a href="https://www.mail-archive.com/announce@subversion.apache.org/"
+ >mail-archive.com</a> (searchable)</li>
</ul></td>
</tr>
</tbody>
@@ -349,6 +357,8 @@ delay for your post to appear (see below
>mail-archives.apache.org</a></li>
<li><a href="https://lists.apache.org/list.html?notifications@subversion.apache.org"
>lists.apache.org</a> (searchable)</li>
+ <li><a href="https://www.mail-archive.com/notifications@subversion.apache.org/"
+ >mail-archive.com</a> (searchable)</li>
</ul></td>
</tr>
</tbody>
Propchange: subversion/site/staging/news.html
------------------------------------------------------------------------------
Merged /subversion/site/publish/news.html:r1881643-1889188
Modified: subversion/site/staging/roadmap.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/roadmap.html?rev=1889189&r1=1889188&r2=1889189&view=diff
==============================================================================
--- subversion/site/staging/roadmap.html (original)
+++ subversion/site/staging/roadmap.html Mon Apr 26 04:38:31 2021
@@ -134,7 +134,11 @@ compatibility policies, see the section
numbering, compatibility, and deprecation"</a> in the
<a href="/docs/community-guide/">Subversion Community Guide</a>.</p>
-<h3>Transition to LTS and Regular Releases</h3>
+<div class="h3" id="transition-lts-regular-releases">
+<h3>Transition to LTS and Regular Releases
+ <a class="sectionlink" href="#transition-lts-regular-releases"
+ title="Link to this section">¶</a>
+</h3>
<p>Summary:
<ul><li>1.9 and 1.10 are treated as LTS releases</li>
@@ -152,7 +156,9 @@ better plan their upgrade cycles, partic
<p>The LTS support schedule will apply also to 1.10 and 1.9 (the existing supported releases), so each will receive support for 4 years from its initial release. General enhancements will go into the regular releases and will not be backported to 1.10.</p>
-</div>
+</div> <!-- #transition-lts-regular-releases -->
+
+</div> <!-- #release-planning -->
<div class="h2" id="features-most-wanted">
<h2>Our "Most Wanted" Features
Propchange: subversion/site/staging/roadmap.html
------------------------------------------------------------------------------
Merged /subversion/site/publish/roadmap.html:r1879655-1889188
Modified: subversion/site/staging/security/index.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/security/index.html?rev=1889189&r1=1889188&r2=1889189&view=diff
==============================================================================
--- subversion/site/staging/security/index.html (original)
+++ subversion/site/staging/security/index.html Mon Apr 26 04:38:31 2021
@@ -33,6 +33,7 @@
<p>To learn more about how the Subversion development team treats discovered
and reported security vulnerabilities, please visit the <a href="/docs/community-guide/issues.html#security">Security section</a> of the Community Guide.</p>
+<div class="h2" id="advisories">
<h2 id="advisories">Previous Security Advisories
<a class="sectionlink" href="#advisories"
title="Link to this section">¶</a>
@@ -316,6 +317,8 @@ clients using http(s)://</td>
</tbody>
</table>
+</div> <!-- #advisories -->
+
</div> <!-- #site-content -->
</body>
</html>
Modified: subversion/site/staging/upcoming.part.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/upcoming.part.html?rev=1889189&r1=1889188&r2=1889189&view=diff
==============================================================================
--- subversion/site/staging/upcoming.part.html (original)
+++ subversion/site/staging/upcoming.part.html Mon Apr 26 04:38:31 2021
@@ -366,6 +366,106 @@ Merge <a href="https://svn.apache.org/r1
+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
+
+------------------------------------------------------------------------
</pre>
<p>Further changes currently under consideration are listed in each release line's