Making the release

Uploading the archive

  1. The maintainer will send you a detached GPG signature for the archive.
  2. Create some release notes (this is basically just this version's section of the changelog, but sorted by function rather than by date).
  3. Go to Source Forge's file release system and:
    • Create a new release. New release name is just the version number part, not the whole program name.
    • Upload the archive and signature.
    • Set changelog, release notes, etc.
    • Set the file formats. The format for the signature is Other.
  4. Download archive and signature from file release system. Check signature matches:
    $ gpg program-x.y.z.tgz.sig
  5. Edit the program's web page (you can get to it from the software index page). Set the Current testing version to the new release's version number. The program will now automatically show up in the Testers wanted box on the news page.

Announcing the release

  1. Add the release to the Zero Install (AddApp) feed (if any), marked as testing.
  2. Click on the announce this release link at the bottom of the program's web page (it's next to the add new comment link) and enter a short paragraph about what changed. If you keep to plain text and write in the 3rd person, you can reuse this text for the freshmeat announcement later!
  3. Do the Send Email Notification on the file releases page.
  4. Send a release annoucement to the mailing lists (your new web announcement includes an automatically-generated message suitable for emailing to the list).
  5. Make a release announcement.
  6. Update any other places that seem interesting (ROX-Filer announcements also go to the news:comp.sys.acorn.announce newsgroup and

Marking as stable

  1. After a week or so with no major problems, update the page by moving the version from the testing field to the stable field.
  2. Update the Zero Install interface file in the same way.