Tests		GrabBuild	GRUMMP	MOAB	FMDB	NWGrid	CGM/Lasso	SCORECModel

Grab&Build              	+1m	+1m	+1m	+1m	+1m		+1m

ComplianceTests
  iMesh		+1m		+1test	Xmas	Xmas	Xmas
  iMeshP	TBD(see below)
  iRel		+1m   						+1test
  iGeom 	04Jul10						04Jul10		LaborDay10

iZoltan(iMesh)	+1m		+2test	Xmas	Xmas
iZoltan(iMeshP)	+1m				Xmas

Mesquite	+1m		Xmas	Xmas 	Xmas		Thank10		Thank10
Swapping	+1m		MLK10	MLK10	MLK10

VisIt		+1m 		Xmas 	Xmas 	Xmas
FronTier	+1m		Xmas	Xmas
iMeshIO		+1m		Xmas	Xmas	Xmas

meshAdapt	+1m		Thank10	Thank10	LaborDay10
eyeMesh (build)	+1m		Xmas	Xmas	Xmas

Tim's comp.	Xmas		Xmas	Xmas	Xmas
      kernel
Tutorial ex.	VDay10		VDay10	VDay10	VDay10

----------------------------------------------------------------------------------------------
Times are relative from set-up of infrastructure.
+1m    = 1 month from establishment of infrastructure
+1test = Should work immediately or after one round of testing.

Schedule...
By Christmas...
-  Grab and Build
-  Mesh Compliance tests for GRUMMP, MOAB, FMDB, NWGrid
-  iZoltan/Zoltan with GRUMMP, MOAB, FMDB
-  Mesquite with GRUMMP, MOAB, FMDB
-  VisIt with GRUMMP, MOAB, FMDB
-  iMeshIO with GRUMMP, MOAB, FMDB
-  FronTier with GRUMMP and MOAB

----------------------------------------------------------------------------------------------
Other decisions:
-  Tests will be run every two weeks.
-  Tests will be run on the mesh machine.
-  Software must provide mechanism for test framework to obtain repository versions of code.  
   For example,
   +  anonymous svn
   +  cron job that creates a tarball of the repository
-  Testing code and baseline answers will, for now, be acquired in the "grab" operation for 
   each tool.
-  Eventually, we should include coverage in the test.
-  Also, we should be doing performance testing (at least internally); need collection of
   representative computational kernels on larger problems.
-  Release schedule:
   +  First release under new schedule:  Valentine's Day 2010
   +  Subsequent releases every six months.
   +  Need release notes for ITAPS + each tool
      -  Have a template for release notes, with bug fixes, new features, compatibility 
         with other ITAPS tools.
      -  Also have a release checklist.
-  Documentation:
   +  Need a new User's Guide.  
      -  Start with ACM TOMS paper.  Add examples, more how-to information.
   +  Update Doxygen in header files to include error codes that can be returned; more 
      clearly define the spec.
-  Compatibility checks between versions:
   +  Mark Miller has a scheme for enforcing that the header file included by the app
      matches the library to which an app links.
      Mark can add magic macros to iMesh.h that will make this happen.
   
----------------------------------------------------------------------------------------------
Todo:
-  Send technical requirements to Mark S. for a system that could be used for testing.
-  Get Ellen and Greg accounts on mesh machine to get tools in place.
-  Need regression-test email list to archive results.
-  Need more centralized way to track propositions for changes, requests, etc.
   +  To easy to forget about / lose emails in mailbox.
   +  Tim can host at Argonne.

Start-up:  Ellen and Greg should work with teams in this order:
1.  Grab and build for all
2.  Carl:   GRUMMP compliance tests
3.  Vitus:  iZoltan with GRUMMP

----------------------------------------------------------------------------------------------
Notes:

Swapping tests:  For now, merely check whether output mesh is better than input mesh.
eyeMesh tests:  Not sure how to test, since it is a GUI around iMesh.

----------------------------------------------------------------------------------------------
iMeshP compliance testing:  
+  One idea:  have a partitioned mesh (iMeshP), plus have entire mesh (iMesh) on each 
   processor (separate instances).   Then can compare results (adjacencies, etc., 
   before/after migration).
+  Have some starting points in MOAB's unit tests, iZoltan, Mesquite.
+  But who will do it?  If we design it, can we find a student to implement it?