This is a list of the steps involved when we're doing a release of 'Tavi. It's here mainly for the purpose of documenting the process and to be used as a guideline for new (or forgetful) developers. Do note that I've used version 0.24 as an example throughout this list. You must of course change this to whatever release you're making.

  1. Add code to the TaviCVS-repository until you're ready to release a new version.
  2. Do a final update, followed by a commit on the whole project. Remember to change the ChangeLog?.txt and News.txt to include information on the new version
  3. Branch and tag using TaviCVSTags of the form release-v0_24 (Using WinCvs?: Modify -> Create branch on selection when standing on the 'tavi'-directory)
  4. Export a fresh version of the code somewhere beside your normal repository
    • Ideally this should be using anonymous access, i.e. cvs -d:pserver:anonymous@cvs1.sourceforge.net:/cvsroot/tavi co tavi
    • But lately I've been forced to use personal access, i.e.:
      1. export CVS_RSH=ssh
      2. cvs -d:ext:holroy@cvs.sf.net:/cvsroot/tavi export -rrelease-v0_24 tavi
  5. Tar and gzip it together: tar zcvf tavi-0.24.tar.gz tavi/
  6. Use ftp to upload to upload.sourceforget.net:/incoming
  7. Login and go to http://sourceforge.net/projects/tavi/, and go to admin -> File Release. Near the bottom you'll find [Add release]
  8. Complete the steps, add the uploaded file as any and .gz using the tavi-0.24-name
  9. Upgrade and document on web site
    1. Login to shells.sourceforge.net
    2. Get a hold of the tavi-0.24.tar.gz, or do a cvs-checkout to get the latest software
    3. Backup the old stuff
      1. cd ~/tavi
      2. tar zcvf backups/htdocs-DATETIME.tar.gz htdocs/ --exclude htdocs/prerel
      3. tar zxvf ~/tavi-0.24.tar.gz
      4. diff -qr tavi/ htdocs/ # This one is to see differences between old and new versions. Nice to use as a safety guard
      5. \cp -nr tavi/* htdocs/ Doesn't work anymore, see next step
      6. cd tavi; tar cf - * | (cd htdocs; tar xf -)
      7. Edit htdocs/template/common.php and add the line include ("template/sourceforge.inc"); right after the lines <div id="toolbar-bottom">\n<?php. This is to include the images which we are required to have on our SourceForge provided website.
    4. Document any new features properly, and change FormalFormattingRules if necessary. Also do update TaviToDo and write a little notice on main page, WikkiTikkiTavi, to let users now that there is a new version available
  10. Post a news message using Admin -> Publicity -> Submit project news to let the SourceForge community know we have a new version. This message will also display on the summary page, so that people surfing by will notice we have new version
  11. Start looking for bugs and features and stuff to implement for the next version... Go through TaviSuggestions or TaviBugs to locate new tasks to add to TaviToDo?!