# StrongED$Mode = Document

 Release Instructions
~~~~~~~~~~~~~~~~~~~~~~

Instructions for use when releasing any version of Director.
With minor changes this should also be suitable for AssLib as well.


 Before releasing anything
---------------------------

Bug check/test.

Update Docs.!ChangeLog to reflect changes.

Write Release (Notes) and Change (Log) files for SourceForge

Write the Announce email for csaa etc. incorporating Release (Notes) and
  Change (Log)

These files should be written with a wrap width of 72 so that they will integrate seamlessly with existing email clients.


 Files to check date, time and version information
---------------------------------------------------

!ReadMe
!ReadMe1st (in two places!)
!Director.!Run
!Director.Makefile
3rdParty.!ReadMe
Docs.!ChangeLog
Docs.!Commands
NewDocs.Dsl.Intro

Commit all changes.


 CVS
-----

Tag the files with:
  cvs -z6 -q tag release_x_xx[_beta]

If late changes are required, then the tag can be removed with:
  cvs -z6 -q tag -d release_x_xx[_beta]

If late changes are required, then the tag can be forcibly replaced with:
  cvs -z6 -q tag -F release_x_xx[_beta]


 Release scripts
-----------------

Run the Release.unix script from a Unix/Linux box with:
  ../director/NewDocs/Scripts/Release.unix


When completed, run the Release/riscos script from a RISC OS box.

Rename director-devel/zip to director-devel-x/xx[-beta]/zip ,
  director-docs/zip to director-docs-x/xx[-beta]/zip
  and director/zip to director-x/xx[-beta]/zip


 Create a new release on SourceForge
-------------------------------------

Upload director*/zip and to SourceForge with anonymous ftp to the site
upload.sourceforge.net into the directory /incoming :
ftp://upload.sourceforge.net/incoming/

On SourceForge:
Go to http://www.sourceforge.net/account/login.php and log in.
Go to the SourceForge Director homepage at
  https://www.sourceforge.net/projects/director
Click on Admin and then Edit/Release Files
For the Director package click on [Add Release]
The New release name is x.xx[ beta] and then click on Create This Release

Either paste in or upload the release notes and change log files.
If you do entered pre-formatted text then ensure that "Preserve my pre-formatted text." is ticked.
Click on Submit/Refresh to commit these changes.

Once this looks OK click on 'Files'.
When this new release is reflected in the Files page:
Download all three archives.
Once downloaded, ensure that they can all be opened by SparkFS.
Test each archive by Ctrl-dragging the archive to the SparkFS icon. In the
  SparkFS status window click on the button 'Test'.
Click on the release name (x.xx [beta]) and ensure that the release notes and
  change log details are OK.

Remove any previous beta releases from the Releases section.
  https://sourceforge.net/projects/director
Click on Admin and then Edit/Release Files
For the Director package click on [Edit Releases]
Each the beta release click on [Edit this Release]
Change the Status of the release from Active to Hidden.
Click on Submit/Refresh to commit this changes.


 Announce the new version of Director
--------------------------------------

On SourceForge:
Go to http://sourceforge.net/account/login.php and log in.
Go to the SourceForge Director summary page at
  https://sourceforge.net/projects/director
Click on '[Submit News]'
Paste in the subject line from the Announce file.
Paste in the contents of the Announce file.
Click on 'Submit'.
Go back to the SourceForge Director summary page at
  https://sourceforge.net/projects/director
Click on '[News archive]'.
Click on 'Admin'. (?)
Open the messages/posting which are no longer relevant (as they talk about
previous stable/beta releases)
For each one:
  Change the Status to: Delete
  Click on 'SUBMIT' to confirm.


Update the website:
In your favourite text editor load the file
  LanMan98#notypes::www.$.director.htdocs.download/php
Update the version number, the number of released files (if required), update
the version number and the links to the right place to download them and the
entries for the release files (if required), the release notes/change log id
and whether it's/there's a beta version at present. 


On the ANS filebase:
Go to http://filebase.acornusers.org/login.php and log in.
Click on 'My Software' or going to http://filebase.acornusers.org/mysoftware.php
Click on 'Update entry'
Update the:
  version number,
  date,
  filesize,
  and download URL.
Click on 'Update entry' to submit the new details.

On Iconbar:
Go to http://www.iconbar.com/news/addsoftupdate.php3
Enter the details:
  Program name: Director
  New version number: x.xx [beta]
  Author's name: Director Developers
  Description of update: <insert contents of Changes file>
  Website: http://director.sourceforge.net

Send an e-mail to:
  mailto:director-users@lists.sourceforge.net

Post a message to:
  news:comp.sys.acorn.announce

Post a message to Drobe:
  mailto:news__drobe_co_uk
