>>>> https://subversion.apache.org/download.cgi#supported-releases >>> >>> I think that is the wrong link. It does not point to 1.10.3 >> >> Thanks ... you're right. I have now figured out what I did wrong.
The problem was I had changed the 'recommended release' defined in release.py to 1.11, prematurely. We might want to consider using different link anchors, perhaps that specify the version number directly, because the support status of any particular version can and does change at some time after it was released while readers may still find and follow the link in future. I think that's not a big deal as long as it lands on the 'downloads' page. Of course we should try to avoid the mistake I made, and so have it land on the correct section at the time of the announcement. Nathan Hartman wrote: > The list of people who provided PGP signatures in the announcement was empty > as well. Not sure if that's correct. Argh... that wasn't intentional. I ran 'release.py write-announcement --target=X' where X is indeed a WC directory for the release artifacts, but my directory was set to depth=empty at that time, leading 'release.py' to print an empty list. I think 'release.py' should error out when it cannot find the signature files. - Julian
