thanks karl!
i would very much appreciate, if you consider applying criteria when
reconsidering, like:
- does the (current/potential) user notice a difference
by fixing the issue:
- in better stability,
(yes, then consider fix)
- in more functionality / usability,
(if necessary, then consider fix)
- in better speed (i.e. more than 2 times as fast),
(yes, then consider fix)
- in later release date,
i.e. is it big/dangerous/complicated, or byte sized
(yes, then consider postpone).
e.g. by fixing issue 510, you bring more flexibility into the code
(as i understand it), but you probably won't use this flexibility for
1.0, so the user would notice the fix by a later release date.
--------------------------------------------------
solo turn <soloturn99@yahoo.com> writes:
> 913: make import faster.
> reason: not used very often. works as it is.
> 510,511: xdelta reverse, svn patch
> reason: no bug, extension. potential danger of
> stability problems.
Yeah, 510 is questionable, though it's a pretty harsh interface
change
and it would be nice to have it in 1.0 (913 is essentially a no-op
once 510 is done). As we get closer to Beta and 1.0, we should
reconsider those; possibly they will get moved.
I think you're right about 511; have moved that one Post-1.0, hope no
one minds.
Thanks solo,
-Karl
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jan 8 11:59:31 2003