svn commit: r1846300 - /subversion/site/staging/docs/release-notes/1.11.html

[st...@apache.org]

Author: stsp
Date: Sat Nov 10 12:02:17 2018
New Revision: 1846300

URL: http://svn.apache.org/viewvc?rev=1846300&view=rev
Log:
* sites/staging/docs/release-notes/1.11.html
  (github-issue): Document compatibility problems between Github and SVN 1.11.

Modified:
    subversion/site/staging/docs/release-notes/1.11.html

Modified: subversion/site/staging/docs/release-notes/1.11.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/docs/release-notes/1.11.html?rev=1846300&r1=1846299&r2=1846300&view=diff
==============================================================================
--- subversion/site/staging/docs/release-notes/1.11.html (original)
+++ subversion/site/staging/docs/release-notes/1.11.html Sat Nov 10 12:02:17 2018
@@ -577,6 +577,24 @@ patch into their swig-3.0.8 packages.)</
 
 </div>  <!-- ruby-swig-issue-602 -->
 
+<div class="h3" id="github-issue">
+<h3>Github's SVN Bridge server implementation incompatible with SVN 1.11
+  <a class="sectionlink" href="#github-issue"
+    title="Link to this section">&para;</a>
+</h3>
+
+<p>As of November 2018, Subversion 1.11 clients are unable to
+check out repositories from Github. Stricter DAV RFC conformance checks
+were added to SVN 1.11 clients, and Github's custom SVN server implementation
+happens to not conform to the newly expected behaviour. We are waiting for
+Github to resolve the issue at their end. In the meantime, Subversion 1.10, and
+perhaps even the <a href="https://git-scm.com">Git version control system</a>,
+can be used as a workaround.
+</p>
+
+
+</div>  <!-- github-issue -->
+
 </div>  <!-- issues -->
 
 <!-- (This section only makes sense when there are some issues listed in it.)