Marc Strapetz <marc.strapetz_at_syntevo.com> writes:
> I would really hope that
>
> * r31059, 31060, 31061, 31075, 31151
> Fix issue #3157, Merging a change from a path's natural history
> creates self-referential mergeinfo
>
> will still be included for 1.5.0. The simple reason is that the
> addressed problem introduces *irreversible* repository
> inconsistencies. I'm stumbling across this quite frequently for our
> production repository which we have already switched to RC5. It makes
> even short logs quite lengthy and confusing.
>
> As far as I understand there is consensus on that the self-referential
> mergeinfo is not correct? In that case I think the risk that this fix
> breaks something even *more* severe than this problem itself is quite
> low.
It's a judgement call, but I think we need to ship 1.5.0 at this point,
as it has many things besides merge-tracking.
Remember that we can't guarantee that merge-tracking doesn't have some
other bug anyway: it's not like including the above fixes and releasing
means we're home free. In the long run, it's better to inspect the
changes and truly understand that they are correct, than to ship them
thinking a bug is fixed when in fact it might be broken in some more
subtle way.
We should mention this problem in the Release Notes, of course, and say
that it will be fixed in 1.5.1.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-05-27 20:00:56 CEST