Hello David, Few suggestions to some of the topics:
> On Sep 20, 2015, at 22:03, David Hill <hi...@ucalgary.ca> wrote: [...] > I presume I do not have to use "gnupload" or "ncftpput-ftp" scripts, [... ] > and that I can then use basic anonymous ftp to upload the triplet -- the > main, the .sig file and the directive.asc file. While I have not tried manual upload myself, it seems there should not be a problem. The relevant parts from 'gnupload' point to using host 'ftp-upload.gnu.org' and uploading the files to either '/incoming/ftp' or '/incoming/alpha'. See http://git.savannah.gnu.org/cgit/gnulib.git/tree/build-aux/gnupload#n312 Specifically lines 331,336. > You don't expect uploaders to use sftp -- right? Based on my reading of the script: uploading files to ftp.gnu.org is done with FTP . uploading files to 'downloads.savannah.gnu.org' is done with rsync/sftp/scp . However, for more accurate information you might want ask at ftp-upl...@gnu.org . --- It's worth mentioning 'alpha.gnu.org' : this is a similar server which can be used to hold release candidates for testing and experimentation - worth trying out before publishing a 'final' official release. Example, emacs and guix projects publish files there (including some binaries): http://alpha.gnu.org/gnu/guix/ http://alpha.gnu.org/gnu/emacs/ Another useful resource is the 'platform-test...@gnu.org'. If you want to get as much testing as possible for a pre-release upload, you can upload your files to 'alpha.gnu.org', and send an email to 'platform-testers' asking for help in testing. ( see https://lists.gnu.org/mailman/listinfo/platform-testers ). [...] > When the release has been accepted, I should send a note out to the mailing > list telling people where to find it, with perhaps some other comments. Any > suggestions as to what to include? And as a matter of interest, where will > people find the release? The most common place is the 'info-...@gnu.org' mailing list. Most GNU maintainers announce new releases there. Eg. announcements from Sept-2015: http://lists.gnu.org/archive/html/info-gnu/2015-08/index.html Some maintainers write detailed release messages, especially if this is a major release: http://lists.gnu.org/archive/html/info-gnu/2015-08/msg00002.html http://lists.gnu.org/archive/html/info-gnu/2015-08/msg00003.html http://lists.gnu.org/archive/html/info-gnu/2015-07/msg00001.html Others are terse: http://lists.gnu.org/archive/html/info-gnu/2015-05/msg00010.html A good outline would be: 1. A short description of what the project is 2. New feutres, bug fixes, etc. 3. Where to download the files from (e.g. ftp.gnu.org's exact URL, after you've successfully uploaded the files and received confirmation) 4. GPG signature to verify the download. There's a script to automatically generate such a template announcement in gnulib: http://git.savannah.gnu.org/cgit/gnulib.git/tree/build-aux/announce-gen Hope this helps, - assaf
