RFC: release script and ftp.gnu.org

[Gabriel Dos Reis <gdr at integrable-solutions dot net>]

Hi,

  Currently our release script is set so that when it comes to make an
actual release, it will package everything and do an upload on our ftp
server.  It was hoped that mirrors will pick the release from there
(that is what most of them do).  The remarkable exception is
ftp.gnu.org, which at some point was requiring an explicit copying.

  With the recent redesign of the way packages are uploaded on
ftp.gnu.org, the release process is a little bit complicated.  For
every file in the release gcc-x.y.z/ one needs to provide a triplet
of files (the actual file, a GnuPG signed one, a directive file).
Those are fairly mechanic but tedious (best handled by custom script).
I was wondering whether it would not be a good idea to extend our
release script to take account of that additional process or if there
were conceptual/technical problems with it.

-- Gaby