If possible on the list of items ready to go, the issue id should be listed. This way if someone thinks it is something they've been waiting for, they can verify that feature or fix is related to the item in the issue tracker.
From: "Hyrum K. Wright" <firstname.lastname@example.org>
Date: 03/09/07 10:09 AM
Subject: Re: Subversion 1.5
Hyrum K. Wright wrote:
> Hyrum K. Wright wrote:
>> What are other's thoughts about shipping 1.5 soon?
> One other thought: what about pinging users@ and getting a feel for what
> some of the users want? I know that may be asking for trouble, but it
> may give us a better idea about whether or not there is enough stuff in
> trunk right now for people to justify an upgrade.
After getting a few positive responses on irc, I've drafted the
following mail for users@. I'm sending it here, just to make sure that
I'm not over/under promising anything.
To all interested users: we need your help!
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 may
delay the Subversion 1.5 release for quite some time.
There are currently several new features in trunk which are ready to go
into the next minor 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
* ...and much more!
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
these features plus merge tracking?
The Subversion Development Team
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Mar 9 17:46:22 2007