Proposal: Start of release cycle for 1.0.2

My feeling is that it's time to do another patch release for Subversion.

Solutions to several problems have been merged into the 1.0.x branch since
1.0.1 as mentioned in the CHANGES file on trunk:

 * fixed: segfault when remotely deleting svn:author property.
 * fixed: mod_dav_svn accepting too many authors. (issue #1786)
 * fixed: create runtime config files with native EOLs. (Issue #1802)
 * fixed: recursive propset can corrupt .svn/entries (issue #1794)
 * fixed: better support for shared working copies [not finished] (issue
#1509)

There are at least two additional problems which can be fixed by releasing
1.0.2:

* assertion failure in the libsvn_ra_svn which manifests itself (at least)
on obstructed updates (r9293; proposed and accepted)
* 1.0.1 identifying itself as a '-dev' build

There are a series of items in STATUS which could be merged if they had
enough +1's.

I think the list above (especially the assertion failure) warrents a new
patch release.

To allow some time for review of the remaining STATUS items I propose the
following timeline:

- Time to vote on items in STATUS until the end of Thursday April 15th;
- Releasing the 1.0.2 tarball on Friday or over the weekend depending on
Release Manager availability.

Erik.

-- 
NEU : GMX Internet.FreeDSL
Ab sofort DSL-Tarif ohne Grundgebühr: http://www.gmx.net/info
-- 
NEU : GMX Internet.FreeDSL
Ab sofort DSL-Tarif ohne Grundgebühr: http://www.gmx.net/info
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org