libisoburn/releng
2011-07-19 17:16:21 +00:00
..
codesamples renamed to better reflect intentions 2011-07-19 17:16:21 +00:00
inc handle specific help anywhere 2011-07-18 17:22:59 +00:00
auto_cxx postpone creation of self data dir, until compiler is checked first 2011-07-19 16:51:51 +00:00
auto_isocontent handle specific help anywhere 2011-07-18 17:22:59 +00:00
auto_isojigdo handle specific help anywhere 2011-07-18 17:22:59 +00:00
auto_printsize handle specific help anywhere 2011-07-18 17:22:59 +00:00
CHECKLIST renamed to reflect user expectations 2011-07-19 17:11:40 +00:00
manual_devices handle specific help anywhere 2011-07-18 17:22:59 +00:00
README renamed to reflect user expectations 2011-07-19 17:11:40 +00:00
run_all_auto rename releng_ scripts to auto_ 2011-07-18 12:21:39 +00:00
template_new drop ramaining leftover 2011-07-19 17:09:03 +00:00
TODO merge remaining todo entries into TODO file, drop completed 2011-07-19 17:02:09 +00:00

Release Engineering
~~~~~~~~~~~~~~~~~~~
* SOFTWARE TO TEST
 + Use latest libburnia libraries code base from svn and bzr
   (see top-level README for aditional library dependencies)
 + Alternatively, use latest all-in-one development tarball from:
   http://www.gnu.org/software/xorriso/

* SETUP THE TEST ENVIRONMENT AND RUN THE TEST SUITE
 + All tests have to be run from the releng/ directory, within
   libisoburn source tree. Self-generated data are stored in
   ./releng_generated_data/ directory, and the required space for
   these data is about 300 megabytes. There is a 'master' script
   called run_all_auto, which runs all scripts prefixed with auto_*.
 + Any auto_* script can be run on its own, regardless.
 + Any manual_* script is to be run on its own, only.
 + All scripts support -h, -help, --help and
   print usage help when run without options.

* DELIVERING A NEW TEST SCRIPT
 + Start a new test script over the top of template_new_releng
 + Each completed script starts with auto_ or manual_ prefix
 + Each script' self-generated data are to be stored in
   ./releng_generated_data/scriptname/ directory
 + Keep the newly added script options in sync with other scripts
 + Throw FAIL string to stdout if any failure is detected
 + Return exit code 0 on success, non-zero on failure
 + Use different exit codes for any failure (range 0-31)