reparing Cloudy for a release
start process several weeks before end of month so that versions do not change

==========================================================
Source directory

run entire project through pclint

if still c code, copy to cpp and compile entire source as c++ to check conformance

update copyright year across all of source

license.txt
	has version number and year - based on BSD license

readme_source.htm
	review and confirm still correct

list_headers.pl
	checks on any header files that are not used
	produces following output files
	headers.txt: summary of all header fils 
	listfiles.list: all source files using each header
	
todo_search.pl
	make prioritized list of todo's, creates todo_table.txt and todo_table.htm
	check no TODO criticality 0

list_routines.pl
	creates list of all routines with description and file,
	output into sorttable.html and sortsrc.list
	
extract_atomic_data.pl - extract all atomic data references
	The files created are:
	atomicdata.list:Contains new refernces
	and oldatomicdata.list:Contains old references.

fabden should stop with statement of condition

record size of code

==========================================================
data

readme_data.htm
	review and update
	
*.pl - nothing to be done

==========================================================
Test suite - auto

runall.pl - check that it does not skip any models 

readme_tests.htm
	review
	
doc_tsuite.pl
	this creates a list of all test cases, including the input commands and
	a description of its purpose
	OUTPUT:
	doc_tsuite.txt: contains a tab delimited list of the files, 
	doc_tsuite.htm: formatted list

valgrind - run on cloud9

check for sims close to an assert

check asserted zones in all sims - some may be only 1 or two zones from throwing an assert
	and close will not catch it
	also check on those with silly asserted zone much larger than needed
	
itrzn check rational, or too close

==========================================================
Test suite - slow
slow tests ok?

==========================================================
programs 
run tests check output,
run copy_programs.pl to create programs.tar.gz, programs.zip
copy these to site

==========================================================
bugs 
go over models in bugs dir and see if any can be removed or are show-stoppers

==========================================================
Hazy
create using "web gary" with jaws, view document to confirm that greeks are embedded properly

update tables in Hazy part III

in headinfo check that copyright and citation information is correct, 
	any other numbers that might have changed

review all comments in hazy 

update table "atomic data sources" in hazy 3

cloudy size growth in hazy 3

update table model test suite in hazy 3

create PDF
	check that page numbers are correct (were not in Jul 05 release)
	check that links are hot - click on page number to go there
		(were not hot in Jul 05 release)

==========================================================

copy to web site
source, data, test suite, from last or last good dir
slow from tsuite/slow
hazy 4 files
programs from tsuite/programs
output files from full set of machines
post on front page of web site
make discussion group announcement
create branch in repository
