
How To Make A Cream Release

o Verify all new vars pushed into cream-conf.
o Test on all platforms (all two and a half of them).
  * Run without any existing view files.
  * Confirm all files are unix fileformat.
  * Double-check upgrading is seamless.
o Docs
  * Make Press Release.
  * Verify all the web documents:
    - home.html: date, news headlines
    - download.html: verify file names and sizes
    - featurelist.html: update
    - screenshots.html: update
    - keyboardshortcuts.html: update
o cream.vim:
  * update header version number
  * update header date
  * update variable version number
 ---- FREEZE ----
o Package:
  * Use handy-dandy release function to create TAR.GZ package.
  * Use NSIS to create Cream with gVim EXE package (excludes vim.exe).
  * Use NSIS to create gVim EXE package (includes vim.exe).
o Release files to SourceForge.
o Tag CVS with release version:
    "cvs -q tag release-0-42_2009-08-01"
o Upload web pages.
o Send Press Release email to list.
o Post news at:
  * SourceForge project news
  * FreshMeat.net
  * comp.editors
  * GnomeFiles.org


A Nice List of Goals

o Regressions - Make sure that previous bugs don't pop up again.
o Integration - Make sure that all the pieces work when you put them
  together.
o Globalization - Make sure that none of the user messages /
  interfaces are hard coded.
o Localization - Make sure that it is translated into other languages
  correctly.
o Accessiblity - Make sure that handicapped users (blind / deaf /
  etc.) can use the product. (Can you use the program without a mouse?
  Does it work with large fonts, high contrast, etc?)
o Scalability - Large numbers of records, large amounts of data.
o Performance - Is it sufficiently fast?
o Reliability / Memory leaks - Can the system stay up for multiple
  months without hint of reliability problems?
o Security - Do we verify the data before we use it? Do we protect
  sensitive data?
o Update testing - Does data persist and functionality work correctly
  after upgrades?

