$Id: CHANGELOG.ambush,v 1.11 2004/04/03 04:17:37 jmuelmen Exp $

0.2.2:		history file added
0.2.1:		sequential statements implemented
0.2.0:		surf_brd_set_anl_v / dig_v set the sense voltage
0.2.x:		All bug fixes of the 0.1.x series

0.1.1:		Remaining bug in module tables (^M in directory names) fixed.
0.1.0:		Ambush can run turbodaq scans on one module.

0.0.9rc11:	A hardwired TurboDAQ_files pathname was still left over.
0.0.9rc10:	Ambush understands the "#include file.name" directive.
0.0.9rc9:	Ambush tries to read a configuration file (~/.ambush/config)
		on startup now to get settings like TURBODAQ_DIR.
0.0.9rc8:	Fixed two bugs Lukas found: one in module table parsing, one
		in data directory tree creation.
0.0.9rc7:	Remaining stupid bug in logging fixed.  TurboDAQ communication
		locked properly.
0.0.9rc6:	Locking issue in the surf board system fixed.  When you ask a
		surf board to generate a status report, you have to make sure
		nothing goes over the bus to that board before you've read the 
		status report.
0.0.9rc5:	Log file directory tree creation implemented; log files are 
		opened when the module table is loaded (creating the subdirs of
		TurboDAQ_Files if necessary) and closed when ambush exits.
0.0.9rc4:	Discovered that what I thought was POSIX non-compliance was
		really my forgetting to initialize condition variables.  Fixed
		now.
0.0.9rc3:	Implemented a workaround for multiple instances of cygwin
		pthread POSIX non-compliance.

Roadmap for future AMBuSh development
-----------------------------------------------

0.1.x:		Bug fixes for 0.1, additional hardware (env ch, HV)

0.2:		development branch for multi-module turbodaq operation, 
		firmware compensation, history file, automatic pontifex,
		tab completion