Significant changes:
* don't run TestUpgrade if TAP tests are present in |src/bin/pg_upgrade|
* Add proposed new location of |pg_upgrade| logs in TestUpgrade module
* Use an HMAC over the whole content as the signature.
* Quote |PROVE_FLAGS |in case there are multiple settings
* tighten failure detection for cross version upgrade
* be more verbose about git mirror failures
* Support symlinks on Windows where possible in SCM module
* Document |rm_worktrees| setting and make |on| the default.
* Add new branches_to_build keywords |STABLE| and |OLD|
Because of the changes to how pg_upgrade logging works, owners are
strongly urged to upgrade to the new release as soon as possible if they
are running the TestUpgrade module.
The meaning of the branches_to_build keywords are as follows: STABLE
means all the live branches other than master/HEAD, while OLD means
those branches older than STABLE that we are now supporting limited
builds for (currently REL9_2_STABLE through REL9_6_STABLE).
Downloads are available at
<https://github.com/PGBuildFarm/client-code/releases> and
<https://buildfarm.postgresql.org/downloads>
cheers
andrew