You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by rh...@apache.org on 2015/03/10 21:36:45 UTC
svn commit: r1665681 - /subversion/branches/1.9.x/STATUS
Author: rhuijben
Date: Tue Mar 10 20:36:45 2015
New Revision: 1665681
URL: http://svn.apache.org/r1665681
Log:
* STATUS: Extend nomination.
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=1665681&r1=1665680&r2=1665681&view=diff
==============================================================================
--- subversion/branches/1.9.x/STATUS (original)
+++ subversion/branches/1.9.x/STATUS Tue Mar 10 20:36:45 2015
@@ -44,6 +44,21 @@ Status of 1.9.0:
Notes:
Bert says it changes a public API and so needs to go into 1.9.0: see
http://colabti.org/irclogger/irclogger_log/svn-dev?date=2015-03-10#l93
+ .
+ rhuijben: While the new feature of allowing the resolving of individual
+ properties is not a release blocker to me, the known buggy behavior of
+ the current code that may cause unuexpected loss of properties and
+ conflict data is.
+ .
+ The part of the patch that enables the new feature is very small
+ compared to the part that fixes the issue, and the regression
+ test would be at least tree times harder to write and review without
+ enabling the resolving of individual property conflicts.
+ .
+ Note that not being able to resolve individual property conflicts
+ on update/switch/merge is a regression against 1.7.x, where we didn't
+ switch to resolving after the update completed yet.
+ .
Votes:
+1: rhuijben