Hi,
It is now 3 months since we released 1.3.0 (and six months since we
branched). I think we have enough on trunk to warrant branching for
1.4. Below is a list of some things that come to my head, others
could probably fill in more.
diff/merge/blame can ignore whitespace and eol-style only changes.
svnsync/replay
svnserve is a real service on Windows.
wc replacements, bug fixes.
Lots of client bug fixes in diff (referring to malcolm's work)
wc propcaching and other speed and space improvements
svndiff1 format
The -c option to diff and merge (minor, but anyway)
The sws feature (http://www.red-bean.com/sws)
Use switch instead of recheckout when changing URLs of svn:externals.
bdb 4.4 support (if it doesn't go into 1.3.x)
Experimental serf support.
svn diff --summarize
So, I'm proposing to branch in two weeks, meaning April 21. The
reasons I want to wait for two weeks is for people to have some time
for stuff they want in before branching. (I, for example, have some
things that will affect the WC format that I want to get into
1.4. I'll post separately about that.) Note that branching doesn't
mean that we release an RC immediately, so the door won't be closed at
that date.
If we branch at the proposed date, then give it some weeks to
stabilize before RC, some more weeks for RC trouble (which we can hope
we don't have:-) and a month for soak. Then, we might release in late
June, making us roll 1.4.0 about 6 months after 1.3.0. Given the list
of improvements and the timing, I think starting the release process
soon is appropriate.
Any opinions about this?
Thanks,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 6 22:05:37 2006