[H-GEN] Code development and documentation methods

[David Jericho]

[ Humbug *General* list - semi-serious discussions about Humbug and     ]
[ Unix-related topics. Posts from non-subscribed addresses will vanish. ]

I'm doing a fair bit of code development and bug chasing in my current
role, and I'm falling down in the documentation area.

Basically, as things are at the moment, the process for fixing a bug
is

* Identify bug and cause
* Specify the fix to happen, in plain english w/hardcopy
* Fix the code
* Test the code 
* Commit code
* Record test results, and diff of changes with log of
  changes w/hard copy

What methods of documentation and appeasing those who command thou do
other humbug members use? 

I'm experienced with system administration style documentation because 
that's what I primarily am, but have to admit I'm stumbling somewhat 
with code documentation.

-- 
David Jericho
Senior Systems Administrator, Bytecomm Pty Ltd


--
Scanned and found clear of viruses by ENTIREScan.  http://www.entirescan.com/

--
* This is list (humbug) general handled by majordomo at lists.humbug.org.au .
* Postings to this list are only accepted from subscribed addresses of
* lists 'general' or 'general-post'.  See http://www.humbug.org.au/