This file tracks the status of releases in the 1.3.x line. See "Stabilizing and maintaining releases" in trunk/www/hacking.html for details on how release lines and voting work, what kinds of bugs can delay a release, etc. Status of 1.3.0: ================ Soak period: 2005-11-30 - Begun with public announcement of rc4. 2005-12-21 - Final week commences - critical backports only. 2005-12-28 - Soak period elapsed! Candidate changes: Status of 1.3.1: ================ Candidate changes: * r17333, [and friends...] Fix issue #2306: modification of "svn:needs-lock" should adjust the native file system's read-only attribute within a WC. Branch: [merge branch to-be-created] Justification: Backport of a change to trunk which resolves buggy behavior on (at least) Windows and Mac OS X, behavior which is inconsistent with Linux. Votes: +1: dlr * r17829, r17831 Fix issue # 1456: Subversion RedHat RPMs have bad interaction with NFS server/client. Justification: Prevents spurious NFS and AUTOMOUNT messages in log files. Votes: +1: david * r17910 Fix the ability to link libsvn_swig_py on Solaris 10 when compiling with GCC 3.4.2. Justification: Allows successful builds of the Python bindings in a relatively common situation on Solaris via a minor tweak to our build machinery which restores its behavior from Subversion 1.2.3 and earlier. The new behavior is required only for Cygwin, and this change makes that (conditionally) so. Votes: +1: dlr Approved changes: * r17795, r17811 (testcase) Improve Ruby bindings memory management by supporting subpool. This change solves a program which uses Ruby bindings grows fat because making subpool each svn function call causes Ruby's GC at high frequency. Branch: swig-rb-subpool Justification: Without this change, a program which uses Ruby bindings grows over a hundred MB easily. Here is a problem case: http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=109776 Votes: +1: kou +0: blair