Re: tsvn:logwidth in svn repository (Re: svn commit: r12696 - trunk/subversion/po)

[Barry Scott <ba...@barrys-emacs.org>]

I'm guessing that outside of the core subversion members few people 
have any idea what your
development goals and plans are.

For example the client API rewrite is talked about when problems are 
discussed but I have no
idea when such work might begin. I see little point in talking further 
about problems that will not
see fixes for years.

Barry


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: tsvn:logwidth in svn repository (Re: svn commit: r12696 - trunk/subversion/po)

[kf...@collab.net]

Barry Scott <ba...@barrys-emacs.org> writes:
> I'm guessing that outside of the core subversion members few people
> have any idea what your
> development goals and plans are.
> 
> For example the client API rewrite is talked about when problems are
> discussed but I have no
> idea when such work might begin. I see little point in talking further
> about problems that will not
> see fixes for years.

Was this in response to something specific?  (You didn't quote any
text, and I'm not sure exactly who it's addressed to.)

I'm not familiar with any conversations about a client API rewrite.
In general, any concrete plans are put on the public status/roadmap
pages, or are arranged by target release in the issue tracker.  When
something *isn't* represented in one of these publicly visible ways,
it just means there isn't a concrete plan to do it yet.  But the way
things go from "no concrete plan" to "scheduled for release" is by
talking about them, so I can't quite agree with the (implied?)
pessimism of your last sentence...

Best,
-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org