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

Re: [PATCH] Troubleshooting section for release template

From: Stefan Hett <stefan_at_egosoft.com>
Date: Thu, 12 May 2016 11:35:10 +0200

On 5/12/2016 8:47 AM, Branko Čibej wrote:
> On 12.05.2016 02:27, Stefan wrote:
>> Hi,
>>
>> the idea of adding a troubleshooting section to release notes was
>> discussed shortly on IRC a few days ago between brane and myself (Bert
>> was following the discussion too) in light of a user who ran into
>> problems due to (presumably) some proxy issue with http-pipelining
>> support.
>>
>> To him, it seemed like it was a bug in SVN 1.9, since the same
>> operation (locking multiple files) worked fine using SVN 1.8.
>>
>> Ivan pointed out it's most likely a problem with the proxy (maybe it's
>> not correctly supporting http pipelining).
>>
>> Looking for a way to record such known issues, we concluded on IRC
>> that the best way would be to document these things in a new
>> troubleshooting section on the release notes pages.
>>
>> Following is a patch against 1.10.html with the suggested section
>> layout. If that passes, I'm planning to provide another patch for the
>> 1.9 release notes covering problems due to the increased
>> http-header-section size and issues with proxies (the two known cases
>> atm which could cause users to run into problems when using 1.9 which
>> wouldn't be encountered using 1.8).
>>
>> [[[
>> Add a new troubleshooting section covering known issues which can be
>> encountered with the new version but are not directly bugs in Subversion
>> itself.
>>
>> * docs/release-notes/1.10.html
>> (troubleshooting): Add new section including a placeholder entry.
>> (news): Add link to new troubleshooting section.
>> ]]]
>
> Looks good, +1 to commit.
Thanks for the review/approval - committed in r1743487.

-- 
Regards,
Stefan Hett
Received on 2016-05-12 14:21:58 CEST

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.