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:19:42 UTC
svn commit: r1889186 - in /subversion/site/publish:
docs/community-guide/issues.part.html docs/release-notes/1.1.html
roadmap.html security/index.html
Author: hartmannathan
Date: Mon Apr 26 04:19:42 2021
New Revision: 1889186
URL: http://svn.apache.org/viewvc?rev=1889186&view=rev
Log:
site/publish: Fix numerous missing "link to this section" pilcrows
* docs/community-guide/issues.part.html:
(#security-approach, #security-handling, #security-handling-mailing-lists,
#security-handling-tracking-issues, #security-handling-procedures): Add div
tags with these new IDs and add missing pilcrows.
* docs/release-notes/1.1.html:
(#overview, #compatibility-concerns, #new-major-features,
#non-database-repositories, #symlink-versioning, #client-follows-renames,
#auto-escaping-uri, #localized-messages, #other-improvements,
#speed-optimizations, #shareable-working-copies, #store-passwords-variable,
#bugfixes, #new-subcommand-switches, #developer-changes,
#testimonials-and-roadmap): Same as above.
* roadmap.html:
(#transition-lts-regular-releases): Same as above.
* security/index.html:
(#advisories): Fix missing div around the section.
Found by: danielsh
Modified:
subversion/site/publish/docs/community-guide/issues.part.html
subversion/site/publish/docs/release-notes/1.1.html
subversion/site/publish/roadmap.html
subversion/site/publish/security/index.html
Modified: subversion/site/publish/docs/community-guide/issues.part.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/issues.part.html?rev=1889186&r1=1889185&r2=1889186&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/issues.part.html (original)
+++ subversion/site/publish/docs/community-guide/issues.part.html Mon Apr 26 04:19:42 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/publish/docs/release-notes/1.1.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.1.html?rev=1889186&r1=1889185&r2=1889186&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.1.html (original)
+++ subversion/site/publish/docs/release-notes/1.1.html Mon Apr 26 04:19:42 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/publish/roadmap.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/roadmap.html?rev=1889186&r1=1889185&r2=1889186&view=diff
==============================================================================
--- subversion/site/publish/roadmap.html (original)
+++ subversion/site/publish/roadmap.html Mon Apr 26 04:19:42 2021
@@ -134,7 +134,10 @@ compatibility policies, see the section
numbering, compatibility, and deprecation"</a> in the
<a href="/docs/community-guide/">Subversion Community Guide</a>.</p>
+<div class="h3" id="transition-lts-regular-releases">
<h3>Transition to LTS and Regular Releases</h3>
+ <a class="sectionlink" href="#transition-lts-regular-releases"
+ title="Link to this section">¶</a>
<p>Summary:
<ul><li>1.9 and 1.10 are treated as LTS releases</li>
@@ -152,7 +155,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
Modified: subversion/site/publish/security/index.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/security/index.html?rev=1889186&r1=1889185&r2=1889186&view=diff
==============================================================================
--- subversion/site/publish/security/index.html (original)
+++ subversion/site/publish/security/index.html Mon Apr 26 04:19:42 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>