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

Re: svn commit: r1494829 - /subversion/site/publish/docs/release-notes/1.8.html

From: Johan Corveleyn <jcorvel_at_gmail.com>
Date: Thu, 20 Jun 2013 15:18:36 +0200

On Thu, Jun 20, 2013 at 2:44 PM, Ivan Zhakov <ivan_at_visualsvn.com> wrote:
> On Thu, Jun 20, 2013 at 4:40 PM, C. Michael Pilato <cmpilato_at_collab.net> wrote:
>> On 06/20/2013 06:55 AM, Johan Corveleyn wrote:
>>> Fine for me. I actually don't care about this personally (at our
>>> workplace we're still lightyears away from upgrading, both client and
>>> server side). I just found it to be an important omission from our
>>> release notes (that actually should have been included way before
>>> release), and thought the information good enough, and at least better
>>> than nothing. But if people object, no problem.
>>
>> Note that there is often some benefit to *not* pointing out every single
>> feature or toggle we add. In this case (as in the case of the
>> http-max-connections configuration option), I intentionally left these out
>> of the release notes. Why? Because I don't want folks reading those notes
>> to feel as if they *have* to fiddle with every knob simply because it
>> exists, and the default behaviors here should be sufficient.
>>
>> Remember, the release notes aren't *the documentation*, and as such, they
>> needn't be exhaustive. They exist to advertise the benefits and (where
>> applicable) "gotchas" of the release, primarily for the benefit of people
>> who are existing Subversion users looking to upgrade to the new version.
>>
> Big +1. HTTP protocol options added mostly for debugging purpose, not
> for regular users.

Of course. I agree.

Note that I didn't ask for adding http-max-connections to the release
notes. But the skelta-mode and bulk updates behavior are not debugging
options IMO, they have important user-visible (or admin-visible)
effects. So I don't think these are just "every single feature or
toggle".

Remember all the discussions we had during 1.7 and 1.8 development
about serf increasing the amount of requests and subsequent increase
of access logs (which was by some considered quite important that we
at least point admins' attention to it). If this skelta/bulk behavior
isn't important enough to mention it in the release notes, why did we
have all those discussions then?

Until now, I hadn't seen any good overview of the possible config
knobs and their interactions (also with older servers) regarding the
skelta/bulk update stuff. Okay, perhaps it's now documented in the svn
book, but a lot of admins looking to upgrade from 1.7 to 1.8 will
mainly look at the release notes to find out the important changes. I
consider this an important change (mainly for the network traffic and
logging effects that we discussed at length before).

But, as I said: if others consider this too much clutter, or too
confusing, feel free to revert. I won't lose sleep over it (I already
have :-).

(though: I think that table that lays out the possible combinations of
client-side and server-side is great :-). So if this is yanked from
the release notes, please put it somewhere else where it's
discoverable by users.)

--
Johan
Received on 2013-06-20 15:19:28 CEST

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