[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

New (1.5) feature questions -- things we need to address before a release can happen

From: Mark Phippard <markphip_at_gmail.com>
Date: 2007-05-20 17:53:14 CEST

I am doing a webinar at the end of the month and was going to do a few
slides on some of the new features in 1.5. We are going to need this
information to update the release note as well though.

It seems like there are a few new features that are really lacking in
documentation and information even though they have been in trunk for
a long time. Perhaps more significantly, they seem like fairly useful
features and thus deserve more documentation and attention.

SASL
Where is the notes file that explains the feature? What can you do
with it? Does it, or does it not support TLS or SSL? Does it work on
Windows? What is involved in bulding support for it into the client
and server? What happens if client and server do not both have the
support compiled in? How does one set it up etc. Given that we are
reasonably close to a 1.5 release this information should all be
readily available.

DAV write-through proxy
This has the potential to be a killer feature, but it is another one
that is not heavily documented. There is a notes file, but it looks
like it pre-dates the implementation in some of the details. This one
looks fairly easy to turn on but could benefit from some more
explanation about what it wants to accomplish with some real-world
implementation scenarios. For example, it seems fairly important that
the read-only "slaves" are updated after a commit. Presumably svnsync
would be a good candidate for doing this. An example hook-based
implementation would be useful. Also, some discussion on the
ramifications would be useful. What if I do a commit, followed by an
update and my mirror has not been updated yet? Likewise, what if
another user does a commit, and then I do a commit by mirror has not
been updated yet. Will that effect me?

I do not know any of these answers, or I would not be asking. I am
willing to help collect and format the information and get it into the
right places. I have tried searching mailing list threads but that
has often just led to more questions as I see references to things
like "I need to add TLS support and will post something ..." then I
cannot find that it was ever done.

It would be unlike this project to include features like this with so
little documentation available. By the way, although merge tracking
has a lot of documentation, one area that has not been well addressed
is the new SQLite dependency and its impact on the build process. In
particular, building on Windows is more of a black art than ever.

If it would be helpful, I can lead/organize the effort on fixing some
of these deficiencies, but it will really take "subject matter
experts" on these items to step forward and provide the information
and make sure the final output is accurate and complete.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun May 20 17:53:27 2007

This is an archived mail posted to the Subversion Dev mailing list.