RE: No-op changes no longer dumped by 'svnadmin dump' in 1.9
From: Bert Huijben <bert_at_qqmail.nl>
Date: Tue, 27 Oct 2015 15:29:33 +0100
> -----Original Message-----
> In 1.9 we changed how svn_fs_contents_changed() works, added an errata,
You are still focusing on the dump scenario.
I'm +1 on backporting that when documentation and regression tests are added.
I'm just -0.9 on reverting the rest 'as it *may* have problems too'.
That is not a good enough reason for me to backport a 'revert to 1.8 style' thing. That part needs a better reason. The other behavior changes need their own tests, their own documentation and their own argumentation.
Backporting now and only then trying to determine where this affects behavior is the wrong order.
If somebody wants to backport more than the dump/load fix it should be for a good reason. And every part of a backport with such impact needs a reason.
We should find out where backporting the change affects behavior *now* and only backport after that. Not the other way around (Revert, release and only then review)
We can't undo the release of 1.9.0, 1.9.1 and 1.9.2... and going back to the old behavior is a huge change.
Yes, there are still more users that use 1.0-1.8.x, but that doesn't make the 1.9.0-1.9.2 behavior directly 'broken'... 1.8.x has different behavior, relying on unexpected/unintended features but for many users they are useful.
But I haven't seen a document update explaining why those errata you mentioned where *all false*.
I still see a reasoning for fixing 'dump'... and a patch (not even a nomination yet) for changing much more than dump.
If the errata were bad, I also miss the errata patch.
This is an archived mail posted to the Subversion Dev mailing list.