On Wed, Feb 08, 2012 at 01:28:48PM +0100, Matthijs Kooijman wrote:
> Looking at the branches available, I think these changes would become
> available in the 1.8.0 release? Any chance of backporting them to 1.7
> (This is not hugely important, but it would help getting my patches to
> git-svn accepted sooner).
There are some changes we cannot backport to 1.7.
For example, the addition of new functions prevents people from rolling
back to an earlier 1.7 patch release without breaking scripts which were
modified to use the new functions after updating to 1.7.3. That would
be a violation of our release compatibility guidelines.
Changes which don't add new API symbols can be backported.
Currently, the following changes are nominated for backport to 1.7:
* r1241530, r1241713, r1241726
Fix the python bindings for svn_auth_get_platform_specific_client_providers.
Justification:
The bindings should see passwords cached in the platform-specific providers.
Already fixed for the Perl bindings. Ruby fix is nominated separately.
Notes:
r1241713 and r1241726 tweak the unit test.
Votes:
+1: danielsh
* r1241553
Fix the ruby bindings for svn_auth_get_platform_specific_client_providers.
Justification:
The bindings should see passwords cached in the platform-specific providers.
Already fixed for the Perl bindings. Python fix is nominated separately.
Votes:
+1: stsp
Received on 2012-02-08 13:46:34 CET