cmpilato@collab.net writes:
> I really wanted to get this into 0.19, but my DAV testing setup is
> hosed (and it apparently isn't because of this patch, as reversion
> doesn't fix anything). Could someone please apply and test? If all
> is well, let me know, and I'll commit up the change.
Just a thought:
I have absolutely no objection to this particular change going into
0.19. But in general, we should avoid rushing to get an unplanned
change into an imminent release. I mean, what difference does it make
if this gets committed before 0.19 or immediately afterwards?
(The Neon XML validation changes being discussed are a different story
-- there is actually a reason to want that in clients earlier rather
than later, to avoid compatibility problems with future development.
But most changes aren't like that; this one certainly isn't.)
That "I've got to scramble to get my change into this upcoming
release" urge is treacherous :-). It's much better to have lots of
code flux right *after* the release, so the next release after that
has code that has been tested for as long as possible.
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Mar 7 07:26:13 2003