If you keep the quality of the releases, I don't worry about 1.5 with these
features now and wait more for merge-tracking.
I think if you release the 1.5 now, you'll have less impact for the users
when releasing the future 1.6.
On 3/9/07, Hyrum K. Wright <firstname.lastname@example.org> wrote:
> 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
Received on Fri Mar 9 21:29:24 2007