subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1848380 - /subversion/site/publish/docs/release-notes/1.10.html
Date Fri, 07 Dec 2018 08:32:33 GMT
Author: brane
Date: Fri Dec  7 08:32:33 2018
New Revision: 1848380

Update future references in the 1.10 release notes.

The compatibility section for authz mentions possible changes in "future
1.10 releases" but we're already at 1.11.x, and the issues are still

* publish/docs/release-notes/1.10.html: Remove text about future "1.10"
   releases and add links to relevant issues in the tracker.


Modified: subversion/site/publish/docs/release-notes/1.10.html
--- subversion/site/publish/docs/release-notes/1.10.html (original)
+++ subversion/site/publish/docs/release-notes/1.10.html Fri Dec  7 08:32:33 2018
@@ -265,8 +265,8 @@ matching the same name, alias or group a
 <p>In 1.9 the final, read-only, match
 for <tt>user</tt>, <tt>&alias</tt> and <tt>@group</tt>
would be
 selected while 1.10 combines all the lines to give read-write access.
-The 1.10 implementation may change in future 1.10.x releases, perhaps
-to make this case an error.</p>
+The 1.10 implementation may change in future releases, perhaps to
+<a href="/issue/SVN-4794">make this case an error</a>.</p>
 <p>The 1.9 implementation combined the global and per-repository rules
 for the same path:</p>
@@ -281,9 +281,10 @@ for the same path:</p>
 <p>In 1.9 this would define access for both <tt>userA</tt>
 and <tt>userB</tt>, in 1.10 the per-repository rule overrides the
 global rule and this only defines access for <tt>userB</tt>.  The 1.10
-implementation may change in future 1.10.x releases, but the exact
-change is still being discussed on the dev mailing list.</p>
+implementation may change in future releases, but the exact change
+is still being <a href="/issue/4762">discussed</a> on the dev mailing
 </div>  <!-- authz-compatibility -->
 <div class="h4" id="svnadmin-LOCK_PATH-canonical">

View raw message