git-svn-id: https://crawl-ref.svn.sourceforge.net/svnroot/crawl-ref/trunk@10462 c06c8d41-db1a-0410-9941-cceddc491573
GSLOAIUMFFVOEY3IER3TDFGQNPTCFPS7FF7VYHIZ6VP7VXRYCP3QC
8. Create a new release on Sourceforge
Requires SF permissions for file releases.
The release is generally named by the version number, i.e. 0.X.
Once it is created, edit the new release:
* Paste change log and notes into the corresponding fields.
* Set status to Hidden.
Use an older release as a guideline (but don't actually modify it!)
See https://sourceforge.net/apps/trac/sourceforge/wiki/Release%20files%20for%20download
for some rough explanation of this and some of the following steps.
11. Edit the release (again)
On Sourceforge edit the release, select the files you just uploaded, then
change their properties. Again, use an older release for reference.
Change release status to Active.
10. Create a new release in Sourceforge's file release system
Requires SF permissions for file releases.
* Click on Project Admin -> File Manager
* Create a new folder under "Stone Soup" named by version number -> 0.X.y
* Right-click on the uploaded files to Cut and later Paste them into the
newly created folder.
* Click on a file to change its settings.
* Mark a file as default for a given platform, so the "Download Now" link
can refer the user to the most fitting file for their system.
You can use an older release as a guideline (but don't actually modify it!)
See https://sourceforge.net/apps/trac/sourceforge/wiki/Release%20files%20for%20download
for some more detailed explanations.