[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: URGENT: Last call for 1.6.0

From: Hyrum K. Wright <hyrum_wright_at_mail.utexas.edu>
Date: Tue, 17 Mar 2009 23:25:27 -0500

On Mar 17, 2009, at 9:49 AM, Philip Martin wrote:

> Mark Phippard <markphip_at_gmail.com> writes:
>
>>> On Mar 17, 2009, at 3:40 AM, Philip Martin wrote:
>>>
>>>> The resolution of issue 2461 (r33417) changed the behaviour of
>>>> svn:externals containing a backslash, see the discussion here:
>>>>
>>>> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=86142
>>>
>>> So, does this constitute a showstopper? Beyond just mentioning
>>> issues, it would be useful to point out the impact, and to justify
>>> why
>>> a particular bug or feature would hold up the release.
>>>
>>> (For the record, I *don't* think this is a showstopper, but this
>>> ain't
>>> my project. I'm just saying there'd better be some compelling
>>> evidence before stopping the release train.)
>>
>> Based on the thread he pointed to, I'd say Philip is reminding us to
>> include this in CHANGES and the release notes.
>
> That's right. As I understand it Windows and Unix did not have the
> same behaviour as each other in the past, the behaviour of both has
> changed and they are still not the same as each other. This is user
> visible and we know about it; so we should tell people what has
> changed, what they can do to get the old behaviour with new clients,
> and whether or not both old and new clients can be supported.

Ah, thanks for the clarification. Based upon that, I prefer to leave
the single-line entry in CHANGES as is, but we need to be sure to
mention this in the Release Notes.

-Hyrum

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1345157
Received on 2009-03-18 05:25:43 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.