subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1231295 - /subversion/site/publish/docs/release-notes/1.8.html
Date Fri, 13 Jan 2012 21:00:09 GMT
Author: cmpilato
Date: Fri Jan 13 21:00:09 2012
New Revision: 1231295

* site/publish/docs/release-notes/1.8.html
  Remove a bunch of placeholder text now that real data exists in those areas.


Modified: subversion/site/publish/docs/release-notes/1.8.html
--- subversion/site/publish/docs/release-notes/1.8.html (original)
+++ subversion/site/publish/docs/release-notes/1.8.html Fri Jan 13 21:00:09 2012
@@ -37,12 +37,10 @@ describes what is planned for the releas
-  <li><a href="#patch"
-      >XXX(1.7) New feature: svn patch</a></li>
+  <li><a href="#gpg-agent"
+      >In-memory password caching via GnuPG (<em>Unix client</em>)</a></li>
   <li><a href="#enhancements"
       >Many enhancements and bug fixes</a></li>
-  <li><a href="#distribution-changes"
-      >Dependency, license and distribution changes</a></li>
 <p>Apache Subversion 1.8 is a superset of all previous Subversion
@@ -239,108 +237,6 @@ will error out on a file that the Subver
     title="Link to this section">&para;</a>
-<div class="h3" id="wc-ng">
-<h3>XXX(1.7) Working Copy Metadata Storage Improvements (<em>client</em>)
-  <a class="sectionlink" href="#wc-ng"
-    title="Link to this section">&para;</a>
-<p>Subversion 1.7 features a complete re-write of the working copy
-metadata management system of Subversion, code named WC-NG.  The old system
-was one of the first parts of Subversion written, and over time had grown
-difficult to maintain and extend.  WC-NG is intended to provide an
-immediate performance improvement, while also enabling many future feature 
-<p>Although Subversion 1.7 does not introduce these new features, the
-improvements in the working copy storage make them much more likely to
-appear in future releases.</p>
-<p>A number of known (and unknown) bugs have been fixed by the new working
-copy metadata system (see
-<a href="">issue
-<div class="h4" id="single-db"> 
-<h4>Centralized Metadata Storage
-  <a class="sectionlink" href="#single-db"
-    title="Link to this section">&para;</a> 
-<p>A key feature of the changes introduced in Subversion 1.7 is the
-centralization of working copy metadata storage into a single location.
-Instead of a <tt>.svn</tt> directory in every directory in the working
-copy, Subversion 1.7 working copies have just one <tt>.svn</tt>
-directory&mdash;in the root of the working copy.  This directory includes
-(among other things) an SQLite-backed database which contains all of the
-metadata Subversion needs for that working copy.</p>
-<p>Even though the data is stored in a structured format, the relationships
-between the data are complex.  We highly discourage external tools from
-modifying the data held in this database, as such modification is likely to
-result in working copy corruption.</p>
-<div class="notice"><span style="color: red"><b>WARNING:</b></span>
It is not
-  safe to copy an SQLite file while it's being accessed via the SQLite
-  libraries.  Consequently, duplicating a working copy (using <tt>tar</tt>,
-  <tt>cp</tt>, or <tt>rsync</tt>) that is being accessed by a Subversion
-  process is not supported for Subversion&nbsp;1.7 working copies, and may
-  cause the duplicate (new) working copy to be created corrupted. (See <a
-    href=""
-  >issue #3596</a> for details.)</div>
-</div>  <!-- single-db -->
-<div class="h4" id="wc-pristines"> 
-<h4>Pristine Contents
-  <a class="sectionlink" href="#wc-pristines"
-    title="Link to this section">&para;</a> 
-<p>Subversion keeps a record of the unmodified contents of all files in the
-working copy.  Historically, these have been called <em>text-bases</em>, but
-in Subversion 1.7, they have received a new name, and a new home.  With the
-centralization of metadata, the text-bases have been renamed
-<em>pristines</em>, and are now located in the same <tt>.svn</tt>
-directory as the working copy metadata.</p>
-<p>The pristines are stored by checksum in a sharded format.  Any files
-in the working copy which have the same pristine content will now share
-references to the pristine store, making such working copies slightly
-smaller.  Running <tt>svn cleanup</tt> will remove any pristines which
-are no longer needed by the current state of the working copy.</p>
-<p><strong>Note:</strong> In 1.7, we recommend to run <tt>svn cleanup</tt>
-periodically in order to claim
-back the disk space of unreferenced pristines.  We expect a future Subversion
-release to purge unreferenced (and thus unused) pristines automatically; see
-<a href="">issue #XXX</a>
-for details.</p>
-</div>  <!-- wc-pristines -->
-<div class="h4" id="wc-upgrade"> 
-<h4>Upgrading the Working Copy
-  <a class="sectionlink" href="#wc-upgrade"
-    title="Link to this section">&para;</a> 
-<p>Subversion 1.7 introduces substantial changes to the working copy format.
-In previous releases of Subversion, Subversion would automatically update
-the working copy to the new format when a write operation was performed.
-Subversion 1.7, however, will make this a manual step.  Before using
-Subversion 1.7 with their working copies, users will be required
-to run a new command, <tt>svn upgrade</tt> to update the metadata to the
-new format.  This command may take a while, and for some users, it may be more
-practical to simply checkout a new working copy.</p>
-</div>  <!-- wc-upgrade -->
-</div>  <!-- wc-ng -->
 <div class="h3" id="gpg-agent">
 <h3>In-memory password caching via GnuPG (<em>Unix client</em>)
   <a class="sectionlink" href="#gpg-agent"
@@ -367,23 +263,6 @@ href="
 </div>  <!-- gpg-agent -->
-<div class="h3" id="svnrdump">
-<h3>XXX(1.7) New remote dumpfile tool: <tt>svnrdump</tt> (<em>client</em>)
-  <a class="sectionlink" href="#svnrdump"
-    title="Link to this section">&para;</a>
-</div>  <!-- svnrdump -->
-<div class="h3" id="patch">
-<h3>XXX(1.7) New feature: <tt>svn patch</tt> (<em>client</em>)
-  <a class="sectionlink" href="#patch"
-    title="Link to this section">&para;</a>
-</div>  <!-- patch -->
 </div>  <!-- new-features -->
 <div class="h2" id="enhancements">
@@ -410,42 +289,6 @@ for a complete list.</p>
 <!-- Insert selected items here -->
-<div class="h4" id="log-diff">
-<h4>XXX(1.7) svn log can now print diffs
-  <a class="sectionlink" href="#log-diff"
-    title="Link to this section">&para;</a>
-<p><tt>svn log</tt> accepts the new <strong><tt>--diff</tt></strong>
-option which causes it to show changes committed in a revision as
-a unified diff. Below is example output:</p>
-  $ svn log --diff -r1033146
-  ------------------------------------------------------------------------
-  r1033146 | hwright | 2010-11-09 19:40:46 +0100 (Tue, 09 Nov 2010) | 3 lines
-  * subversion/libsvn_wc/wc_db.c
-    (svn_wc__db_op_copy): Remove unused variable.
-  Index: subversion/libsvn_wc/wc_db.c
-  ===================================================================
-  --- subversion/libsvn_wc/wc_db.c	(revision 1033145)
-  +++ subversion/libsvn_wc/wc_db.c	(revision 1033146)
-  @@ -3061,7 +3061,7 @@ svn_wc__db_op_copy(svn_wc__db_t *db,
-                      apr_pool_t *scratch_pool)
-   {
-     svn_wc__db_pdh_t *src_pdh, *dst_pdh;
-  -  const char *src_relpath, *dst_relpath, *dst_op_root_relpath;
-  +  const char *src_relpath, *dst_relpath;
-     apr_int64_t dst_op_depth;
-     SVN_ERR_ASSERT(svn_dirent_is_absolute(src_abspath));
-  ------------------------------------------------------------------------
-</div>  <!-- log-diff -->
 <div class="h4" id="empty-pseudo-changelist">
 <h4>Operating on files not in any changelist
   <a class="sectionlink" href="#empty-pseudo-changelist"
@@ -536,75 +379,6 @@ for details.</p>
 </div>  <!-- bug-fixes -->
-<div class="h3" id="serf">
-<h3>XXX(1.7) Serf HTTP library improved and stabilized (<em>client</em>)
-  <a class="sectionlink" href="#serf"
-    title="Link to this section">&para;</a>
-<p>The <code>libsvn_ra_serf</code> repository access library has received
-a lot of improvements and stabilization.
-The design of <a href="">serf</a> facilitates
-future performance improvements that are impossible to achieve with
-<a href="">neon</a>. There were plans to make
-serf the default HTTP access library for the 1.7 release.
-But because of some remaining issues (for instance
-<a href=""
-  >issue #3979</a>,
-<a href=""
-  >issue #3980</a>, and
-<a href=""
-  >issue #3981</a>),
-Subversion 1.7 still uses neon by default.
-Remaining problems are mostly due to insufficient infrastructure deployed
-in the wild wild web, such as HTTP proxies that do not support HTTP/1.1.
-Workarounds for these problems will be implemented for the next release.
-serf will become the default HTTP access library in Subversion 1.8.
-In the meantime, we encourage all users to try serf with Subversion 1.7 and
-<a href="/docs/community-guide/issues.html#reporting-bugs"
->report any problems</a>. Successful test reports are appreciated as well.
-Tests in networks that use HTTP proxies or enterprise authentication are
-particularly helpful.
-You can configure which library the client should use on a default or
-host-by-host basis by setting the <tt>http-library</tt> variable in the
-client-side <tt>servers</tt> configuration file
-<div class="notice">
-<p>Note that 
-<a href=""
->server-side configuration changes</a> might be required to avoid
-performance regressions for serf clients in some setups.</p>
-<p>The <strong>MaxKeepAliveRequests</strong> option in <tt>httpd.conf</tt>
-needs to be increased from 100 (the default) to <b>at least</b> 1000
-(there is no reason why it could not be 10000).
-This will improve performance by allowing serf clients to use fewer
-TCP connections to the server.
-Clients using neon will also work fine with this configuration.</p>
-<p>Because serf clients issue a larger number of HTTP GET requests
-than neon clients it is possible that serf clients cause quicker
-growth of httpd server logs than neon clients do.</p>
-</div>  <!-- serf -->
-<div class="h3" id="http-redirects">
-<h3>XXX(1.7) Improved handling of HTTP redirects (<em>client</em>)
-  <a class="sectionlink" href="#http-redirects"
-    title="Link to this section">&para;</a>
-<p>In the past, when the Subversion client encountered an HTTP redirect
-response from the server, it displayed an obtuse, and rarely-useful error
-message.  Subversion 1.7 improves the situation by following permanent
-redirects (<tt>301 Moved Permanently</tt>) for <tt>svn update</tt>
and <tt>svn
-info</tt>, and providing a more useful error message on temporary
-redirects (<tt>302 Found</tt> and <tt>307 Temporary Redirect</tt>).</p>
-</div>  <!-- http-redirects -->
 <div class="h3" id="merge-tracking-enhancements">
 <h3>Merge-Tracking Enhancements
@@ -636,86 +410,6 @@ mergeinfo.</p>
 </div>  <!-- enhancements -->
-<div class="h2" id="distribution-changes">
-<h2>XXX(1.7) Dependency, license and distribution changes
-  <a class="sectionlink" href="#distribution-changes"
-    title="Link to this section">&para;</a>
-<p>Subversion 1.7 marks the first official feature release as part of the
-Apache Software Foundation.  A few bits of minutiae have changed as a
-<div class="h3" id="deps">
-<h3>Subversion Dependency Distribution
-  <a class="sectionlink" href="#deps"
-    title="Link to this section">&para;</a>
-<p>Previous releases of Subversion shipped with companion artifacts which
-included a number of Subversion dependencies.  In the past, these dependencies
-were hard to find and build, and not often installed on the target platform.
-Today, this is no longer a problem, so we have discontinued shipping the
-companion dependency tarballs.  If you still want to get some of the required
-Subversion dependencies before building, you can run the
-<tt></tt> script in the root of the unpacked archive.</p>
-</div>  <!-- deps -->
-<div class="h3" id="license">
-<h3>License changed to Apache License, version 2
-  <a class="sectionlink" href="#license"
-    title="Link to this section">&para;</a>
-<p>Since its inception, Subversion has a used a "modified Apache license".
-The migration of the project to the Apache Software Foundation provided
-an opprotunity to also change the license to the standard
-<a href="">Apache License,
-version 2.</a>  Additionally, the copyright to the collective work is now
-owned by the ASF.  While this has very little practical effect, it does mean
-consumers have one less license to worry about when deploying Subversion.</p>
-</div>  <!-- license -->
-<div class="h3" id="asf-mirrors">
-<h3>Download location changes
-  <a class="sectionlink" href="#asf-mirrors"
-    title="Link to this section">&para;</a>
-<p>The download location for Subversion tarballs and other release artifacts
-are now hosted by the Apache Software Foundation.  This includes the official
-distribution location, as well as
-<a href="">archives</a> of all
-previous Subversion releases.  Of course, other locations are welcome to
-continue to host Subversion distribution artifacts, but the Apache download
-sites are now the canonical source for Subversion releases.</p>
-</div>  <!-- asf-mirrors -->
-<div class="h3" id="contrib">
-<h3>No longer shipping <tt>contrib/</tt>
-  <a class="sectionlink" href="#contrib"
-    title="Link to this section">&para;</a>
-<p>Since the early days of Subversion development, the Subversion repository
-has hosted a section for various other tools and scripts related to
-Subversion.  As Subversion has become more popular, the need to host these
-tools in the main repository has decreased to the point where we encourage
-tool authors to host their contributions at one of a number of external
-hosting platforms.  For this reason, and the potentially uncertain nature of
-some of the licenses on these scripts, we have stopped shipping the
-<tt>contrib/</tt> directory in the release tarballs.  For the time being,
-these scripts remain available via the
-<a href="">main
-</div>  <!-- contrib -->
-</div>  <!-- distribution-changes -->
 <div class="h2" id="svn-1.6-deprecation">
 <h2>Subversion 1.6.x series no longer supported
   <a class="sectionlink" href="#svn-1.6-deprecation"

View raw message