site: Auto-update the link the the current release's STATUS file to alwayspoint 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 ofthe 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, showchanges 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.
site: upcoming.py: Refactor the computation of an interim quantity (the tagthat defines the older end of the 'svn log' output to generate).No functional change.In preparation for SVN-4823.* site/tools/upcoming.py (collections): Import. (Version, versions_on_dist_release): New. (copyfrom_revision_of_previous_tag_of_this_stable_branch): Refactor with the new helper.
* site/tools/upcoming.py (get_merges_for_range): Add an optional parameter that will be needed when this script learns to run without a working copy, as requested in SVN-4823. (copyfrom_revision_of_previous_tag_of_this_stable_branch): Add escaping, though it's unlikely to ever be needed here.
* tools/upcoming.py (DIST_RELEASE_URL): New constant. (copyfrom_revision_of_previous_tag_of_this_stable_branch): Determine the latest release by checking dist/release/, not by checking tags, in order to also show changes that have been merged into a patch release that has not been announced yet.This change will cause tonight's bot run to effectively revert r1850708 (andadd Monday's merge to the output as well), re-adding all the merges thatwent into 1.11.1 to the Web site — which is correct, since 1.11.1 has not yetbeen published.
* tools/escape.py,* tools/upcoming.py: New scripts, to be used in generating 'svn log' filtered to show merges only. See dev@ thread: . https://svn.haxx.se/dev/archive-2019-01/0010.shtml Subject: Display outstanding backported fixes for each release?