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

Re: svn commit: r1869776 - /subversion/site/staging/docs/release-notes/1.14.html

From: Nathan Hartman <hartman.nathan_at_gmail.com>
Date: Fri, 15 Nov 2019 00:40:08 -0500

On Thu, Nov 14, 2019 at 1:51 PM Daniel Shahaf <d.s_at_daniel.shahaf.name>

> Nathan Hartman wrote on Thu, 14 Nov 2019 18:14 +00:00:
> > On Thu, Nov 14, 2019 at 10:33 AM Daniel Shahaf <d.s_at_daniel.shahaf.name>
> wrote:
> > > hartmannathan_at_apache.org wrote on Thu, 14 Nov 2019 05:26 +00:00:
> > Isn't it more accurate that building from tarball doesn't require
> > Python but building from a working copy (whether from branches/tags or
> > trunk) does?
> Well, yes, but the release notes aren't aimed at people building trunk.
> Also, "tag of 1.13.0" v. "tarball of 1.13.0" is a minimal pair;
> "trunk_at_HEAD" v. "tarball of 1.13.0" is not.

Good point.

> Thoughts?
> The content looks good.
> Suggest to move the mention of test suite to the second paragraph, since
> it only affects downstream maintainers, not downstream users.


Suggest to delete the "Note ...:" clause, to improve flow. Instead, perhaps
> "If you build Subversion yourself, Python is required if you build from a
> checked
> out working copy or run the test suite, but not otherwise"?

Too many "if's" in one sentence but I agree that the note text needs to be
restructured for better clarity and to separate between issues of concern
for end users / server operators and those which concern maintainers and

Not directly related, but the phrase "other Python-coded tools" makes
> for a circular definition. Does svnlook qualify? (You and I know it
> doesn't, but that's an implementation detail.) Maybe make those words a
> link to .../branches/1.13.x/tools/?

That could include 3rd party tools (though I did write "that ship with
Subversion"). Unfortunately I can't seem to think of another way to say it
besides "other Python-coded tools."

Here's the next attempt...


Python is optional.

Subversion does not require Python for its basic operation. In general, if
you are not using Subversion's SWIG Python bindings, hook scripts coded in
Python, or other tools that require Python, then this change does not
affect you.

You may need Python if you are building Subversion from source. Python is
not strictly required when building from a distribution tarball, but is
required to:
* build from a source checkout
* run Subversion's automated test suite
* run other maintainer-oriented scripts


Received on 2019-11-15 06:40:27 CET

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