Re: [ANNOUNCE] Apache Subversion 1.10.3 released
From: Julian Foad <julianfoad_at_apache.org>
Date: Wed, 10 Oct 2018 18:01:08 +0100
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:
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.
This is an archived mail posted to the Subversion Dev mailing list.