Daniel Shahaf

* docs/release-notes/1.14.html

(#python-is-optional): Make it possible to link to the "Python is Optional" box.

* STATUS: Nominate r1868151.
Whitespace changes only. No functional change.

* subversion/svn/info-cmd.c

(find_print_what, print_info_item): Reindent blocks from last commit.

'info': Support multiple items in --show-item, as tab-separated values (TSV).

Suggested by: brane

Thread:

.

https://mail-archives.apache.org/mod_mbox/subversion-dev/201911.mbox/%3Cf6dc88d3-8227-4f22-768c-2cf6ce70fcb7%40apache.org%3E

Date: Thu, 7 Nov 2019 17:28:35 +0100

From: Branko Čibej <brane@apache.org>

To: dev@subversion.apache.org

Subject: svn status tabbed output [was: Re: svn status should not show unmodified files in changelists]

Message-ID: <f6dc88d3-8227-4f22-768c-2cf6ce70fcb7@apache.org>

* subversion/svn/info-cmd.c

(print_info_baton_t::print_what): Rename to..

(print_info_baton_t::print_whats): .. this.

(find_print_what): Rename argument and parse it as a list.

(print_info_item): Track changes to the baton.

(svn_cl__info): Track changes to the baton.

* subversion/svn/svn.c

(svn_cl__options."show_item"): Update docstring.

* subversion/tests/cmdline/info_tests.py

(info_item_simple): Extend existing test case to unit test this feature.

Blocks that haven't been reindented in this commit will be reindented in the

next commit.

* CHANGES: Use the cleaner, forward-compatible URL for issues.
* docs/release-notes/release-history.html: Fix typo.
* tools/dist/release.py

(write_news): Remove scalpel left behind in r1869134.

release.py: Automatically add to dist/ a current KEYS file with each release.

In particular, this means versioned KEYS files will be archived to

archive.a.o/dist/, and will continue to contain keys after those have

been removed from a committer's id.a.o profile.

* tools/dist/release.py

(download_file): Make checksum verification opt-outable.

(roll_tarballs): Download the KEYS file to the target directory.

Rely on TLS for authenticity and integrity of the downloaded

file (as we already do for authenticity and integrity of the subsequent

commit operation).

* tools/dist/templates/download.ezt,

* tools/dist/templates/rc-release-ann.ezt,

* tools/dist/templates/stable-release-ann.ezt:

Link to the per-release KEYS file.

* tools/dist/release.py

(write_news): Validate the argument to the --news-release-date option.

Follow-up to r1869118.

* tools/dist/nominate.pl

(nominate_main, nominate_usage): Add syntactic sugar CLI for recent revisions.

* STATUS: Nominate r1868575.
* STATUS: Nominate r1868575.
* build/run_tests.py

(TestHarness.run): Tweak new output.

* STATUS: Nominate r1868151.
* STATUS: Nominate r1868151.
* subversion/tests/cmdline/svnserveautocheck.sh

(random_port): Fix syntax error when $PYTHON is Python 3.

* docs/community-guide/releasing.part.html

(#backport-merge-bot): Link to the relevant bug.

* docs/community-guide/releasing.part.html

(#backport-merge-bot): Fix invalid markup.

* index.html

(#site-content): Use the correct trademark symbol.

* docs/community-guide/releasing.part.html

(#release-stabilization-how-many-votes): Simplify.

* docs/community-guide/releasing.part.html

(#release-stabilization): Fix broken link.

* docs/community-guide/releasing.part.html: Use markup.
* docs/community-guide/releasing.part.html

(#release-stabilization): Mention nominate.pl and backport.pl interactive mode.

* docs/community-guide/releasing.part.html

(#release-stabilization): Remove a paragraph.

"Vote if consensus fails" is the default; it needn't be spelled out.

* docs/community-guide/releasing.part.html

(#release-stabilization): Reorganization.

Add subsection headers.

Move paragraphs for flow.

Add some content (no new policies, of course).

Remove the "(for 1.7.2)" example. We don't need to spell out the

possibility of doing that.

Sync-merge from publish
    • ?
    /site/staging/security/CVE-2018-11782-advisory.txt.asc
    • ?
    /site/staging/security/CVE-2019-0203-advisory.txt.asc
  1. … 4 more files in changeset.
site: Auto-update the link the the current release's STATUS file to always

point to the current stable branch.

* publish/docs/release-notes/index.html

(#upcoming-patch-release): Move a sentence from here..

* publish/upcoming.part.html: .. to here, which is automatically generated ..

* tools/generate-upcoming-changes-log.sh: .. here.

* tools/upcoming.py

(Version.__str__): New.

(get_reference_version): Add comment.

site: tools/upcoming.py: Remove the last remnant of working copy usage: use of

the short URL syntax.

For SVN-4823.

* site/tools/upcoming.py:

(REPOS_ROOT_URL): New.

(copyfrom_revision_of_previous_tag_of_this_stable_branch):

Don't use the short URL syntax.

(get_merges_for_range): Change argument type.

(main): Update caller.

site: upcoming.py: When cwd is not a stable branch working copy root, show

changes of the newest branch.

Fixes SVN-4823.

* site/tools/upcoming.py

(__doc__): Expand.

(get_reference_version__from_working_copy): Add TODO.

(get_reference_version__latest_stable_release): New.

(get_reference_version): New.

(main): Update caller.

site: upcoming.py: Continue removing uses of the cwd.

No functional change.

* site/tools/upcoming.py

(relative_url): Remove.

(get_merges_for_range): Change signature.

Stop calling relative_url(), which, incidentally, removes a fork() from

each iteration of the loop.

(main): Instead of calling relative_url(), just compute the URL directly.