>> To all interested users: we'd like your opinion!
>>
>> As many of you know, significant development effort is going into
>> implementing merge tracking as a part of Subversion. This work is
>> going
>> well, but there is a concern among some of the developers that it has
>> been too long since our last release and that we should not delay the
>> Subversion 1.5 release while we wrap up this feature.
>>
>> There are currently several new features in trunk which are ready
>> to go
>> into the next Subversion release. These include:
>> * Cyrus SASL support (SoC project '06)
>> * Copy/move improvements (Peg revision support, support 'svn mv
>> file1
>> file2; svn mv file2 file3', support 'svn cp *.c dir')
>> * Dav mirroring
>> * Cancellation improvements
>> * JavaHL improvements
>> * Partial sparse directories support (not in trunk yet, but
>> anticipated to be merged soon.)
>> * Changelist support
>> * Various bugfixes
Just another data point: Merge tracking would help my particular
situation a lot.
That said, if the process overhead of pushing other features out
first isn't too great, I don't see much reason to sit on unrelated
features. Copy/move improvements would be nice - it would save me a
fair amount of silly one-off script writing. Sparse directories are
intriguing, but I realize that won't be available until clients catch
up. An bugfixes are always good.
Most of the rest doesn't impact me directly, but I'm not the only
consumer, so I have no real comment there.
(Off topic, but are there any reasonable SASL management tools out
there? I use it for mail and wouldn't mind using it more widely, but
handling changes is a major PITA using saslauthdb2 and related, and
it just turns in to yet another parallel authentication mechanism
that confuses end users.)
-j
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Mar 11 19:10:19 2007