Stefan Fuhrmann <stefan.fuhrm...@wandisco.com> writes: > Let's not repeat the revprop caching debacle. In Berlin this year, you > told us that you had identified issues with it and decided to disable it > in VisualSVN. Had you told us before 1.8, we might have found that the > underlying infrastructure is too restrictive. If not, you definitely would > have found the init race under Windows; it's manifest in the Apache error > logs. Everything that happened this summer wrt. to revprop caching > could have been dealt with before 1.8.0.
Not quite so. Ivan was on vacation and completely offline at the moment when we (Sergey Raevskiy <sergey.raevs...@visualsvn.com> and I) found and reported the problems with revprop caching [1]. This occured while we were developing a repository replication solution for Subversion 1.8, which happens to cover revprop modifications. We stumbled upon these problems on 19-20 August 2014, and the report followed immediately. Undoubtedly this could not have somehow happened prior to 1.8.0. [1] http://svn.haxx.se/dev/archive-2014-08/0235.shtml Regards, Evgeny Kotkov
