You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by ph...@apache.org on 2015/03/12 19:07:40 UTC
svn commit: r1666267 - /subversion/branches/1.9.x/STATUS
Author: philip
Date: Thu Mar 12 18:07:39 2015
New Revision: 1666267
URL: http://svn.apache.org/r1666267
Log:
* STATUS: Vote/approve session parameter fix.
Modified:
subversion/branches/1.9.x/STATUS
Modified: subversion/branches/1.9.x/STATUS
URL: http://svn.apache.org/viewvc/subversion/branches/1.9.x/STATUS?rev=1666267&r1=1666266&r2=1666267&view=diff
==============================================================================
--- subversion/branches/1.9.x/STATUS (original)
+++ subversion/branches/1.9.x/STATUS Thu Mar 12 18:07:39 2015
@@ -15,25 +15,6 @@ Status of 1.9.0:
1.9.0 release blockers:
=======================
- * r1664078,r1664080,r1664187,r1664191,r1664200,r1664344,r1664588,r1664927,r1665886
- Instead of making more changes to the auth batons from ra sessions, reduce
- the number of changes by introducing an internal slave auth baton feature.
- Justification:
- Without this patch (or a complete redesign of the auth layer), the
- ra sessions cache (currently on a feature branch), will open the ra
- sessions from outside configuration changes caused by opening other
- ra sessions. This patch not only reverts the additional changes to the
- auth baton on init that are new in 1.9, but also removes cases where we
- already applied similar changes inside specific ra providers.
- Notes:
- The reason I group this under release blockers, is to avoid the behavior
- change introduced in r1609499 from reaching released versions. The changes
- itself are safe for a later backport as it only affects ra-session
- internal state.
- Votes:
- +1: rhuijben, brane
- +1: philip (Without r1665886)
-
1.9.0 candidate changes that cannot go into a later 1.9.x:
==========================================================
@@ -264,3 +245,21 @@ Approved changes:
I (philip) think we cannot release 1.9.0 without this fix.
Votes:
+1: philip, rhuijben, ivan, brane
+
+ * r1664078,r1664080,r1664187,r1664191,r1664200,r1664344,r1664588,r1664927,r1665886
+ Instead of making more changes to the auth batons from ra sessions, reduce
+ the number of changes by introducing an internal slave auth baton feature.
+ Justification:
+ Without this patch (or a complete redesign of the auth layer), the
+ ra sessions cache (currently on a feature branch), will open the ra
+ sessions from outside configuration changes caused by opening other
+ ra sessions. This patch not only reverts the additional changes to the
+ auth baton on init that are new in 1.9, but also removes cases where we
+ already applied similar changes inside specific ra providers.
+ Notes:
+ The reason I group this under release blockers, is to avoid the behavior
+ change introduced in r1609499 from reaching released versions. The changes
+ itself are safe for a later backport as it only affects ra-session
+ internal state.
+ Votes:
+ +1: rhuijben, brane, philip