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/11 13:11:52 UTC
svn commit: r1665857 - /subversion/branches/1.9.x/STATUS
Author: philip
Date: Wed Mar 11 12:11:51 2015
New Revision: 1665857
URL: http://svn.apache.org/r1665857
Log:
* STATUS: Add to analyze proposal, vote/approve RA session 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=1665857&r1=1665856&r2=1665857&view=diff
==============================================================================
--- subversion/branches/1.9.x/STATUS (original)
+++ subversion/branches/1.9.x/STATUS Wed Mar 11 12:11:51 2015
@@ -15,24 +15,6 @@ Status of 1.9.0:
1.9.0 release blockers:
=======================
- * r1664078,r1664080,r1664187,r1664191,r1664200,r1664344,r1664588,r1664927
- 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.9.0 candidate changes that cannot go into a later 1.9.x:
==========================================================
@@ -215,7 +197,7 @@ Other candidate changes:
Veto-blocked changes:
=====================
- * r1664476, r1664480, r1664481, r1664483, r1664507, r1664520, r1664521, r1664523, r1664526, r1664527
+ * r1664476, r1664480, r1664481, r1664483, r1664507, r1664520, r1664521, r1664523, r1664526, r1664527, r1665845, r1665850, r1665852
Automatic create sqlite_stat1 table in wc.db if it doesn't exist.
Justification:
Avoid performance regression on some old working copies.
@@ -226,8 +208,9 @@ Veto-blocked changes:
See "Manual Control Of Query Plans Using SQLITE_STAT Tables"
on https://www.sqlite.org/optoverview.html#manctrl
Votes:
- +1: philip, brane, rhuijben
- -1: ivan (test failures.
+ +1: philip
+ +1: brane, rhuijben (before r1665845, r1665850, r1665852)
+ -1: ivan (test failures before r1665845, r1665850, r1665852
See http://svn.haxx.se/dev/archive-2015-03/0119.shtml)
Approved changes:
@@ -256,3 +239,21 @@ Approved changes:
reducing the number of db operations.
Votes:
+1: rhuijben, philip, brane
+
+ * r1664078,r1664080,r1664187,r1664191,r1664200,r1664344,r1664588,r1664927
+ 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