My opinion should carry next to no weight since I'm so new to the tool.
However, that said, as a newbie, I'd rather see bug fixes in particular at
this point rather than Merge tracking since bugs are more likely to give me
grief right now since I'll be making plenty of mistakes of my own and it's
all that much harder to figure out what I did wrong if it actually turns out
to be a bug.
Another 2 cents.... I huge issue for me will be reliability of the integrity
of the data in the repository so if any of those bug fixes are related to
avoiding corruption/lose of data in the repository database then PLEASE fix
the bugs first.
From: Hyrum K. Wright [mailto:email@example.com]
Sent: Friday, March 09, 2007 1:44 PM
Subject: Subversion 1.5
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
Our question to you is whether or not you, as users of Subversion, would
like Subversion 1.5 now with the above features, or 1.5 in 6 months with
features plus merge tracking? Releasing 1.5 now will push 1.6 back
slightly due to the overhead associated with 1.5. If we do release 1.5
now, we hope to release 1.6, with merge tracking, by 4Q 2007.
The Subversion Development Team
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Mar 9 19:59:26 2007