On Fri, Aug 22, 2014 at 1:56 PM, Stefan Sperling <stsp_at_elego.de> wrote:
> On Fri, Aug 22, 2014 at 01:31:08PM +0200, Stefan Fuhrmann wrote:
> > People will get an error if one of the currently released 1.8 server
> > with revprop caching enabled or svnadmin change a revprop. In
> > that case, a 1.9 process using revprop caching will error out upon
> > revprop access.
> >
> > Local modifications via non-caching pre-1.9 applications may
> > remain invisible to revprop caching 1.9 applications until either
> > a 1.9 application performs a (any) revprop change or the respective
> > process respawns.
>
> I think we need a repository format bump from 1.8 to 1.9, and disable
> revprop caching in 1.8 and 1.9 for the current format. This should prevent
> unexpected errors when upgrading from 1.8.x (any version) to 1.9.
>
> Going forward, we should only allow revprop caching in a new repository
> format with a fixed implementation (given a fixed implementation is
> possible).
>
Agreed.
-- Stefan^2.
Received on 2014-08-22 14:01:06 CEST