The ASF is moving to using SVN for uploading releases [1] The process involves uploading the release artifacts (archives, sigs, hashes) to https://dist.apache.org/repos/dist/release/<project>
There is a parallel development area at https://dist.apache.org/repos/dist/dev/<project> which can be used for release candidates (RC). The release manager (RM) can create RC files in the dev/ tree, and publish them by moving them to the release/ tree once the vote succeeds. Now release archives can be quite large, so one wants to minimise network transfers, and not have to checkout large workspaces either. One way which seems to work OK is to use a separate directory for each RC; this can then be renamed directly on the SVN server. Thus the RM only has to import the RC files once into the dev/ tree; all further copying is done on the server. However, many projects currently use a different layout for the release directory. A common layout is to use binaries/ source/ These directories may contain multiple concurrent release versions, and the existing release will anyway need to be retained for a few days during the release process to allow mirrors time to sync. In this case, there is no parent directory which can easily be renamed, so what are the options for minising network usage? One could rename each file individually on the server, but that would result in lots of separate commits, and would be tedious and error prone. Is there a way to rename multiple files as part of a single commit? Or some other method? [1] http://www.apache.org/dev/release.html#upload-ci
