Feature #340
hacking documentation
Start date:
23 February 2011
Due date:
% Done:
100%
Estimated time:
Workflow:
Description
The documentation needs hacking:
- old G4MICE stuff should go in a doxygen (perhaps separate from framework stuff)
- maus/doc should contain user documentation only at the top level
- one might consider putting doxygen generation in build script (but depends on doxygen exists)
Updated by Tunnell, Christopher over 12 years ago
I commit the doxygen check. Per our phonecall, we should make a script that creates a 'release' and generates doxygen/wiki-mirror for that. However, if people check out the trunk, do they need it?
Updated by Rogers, Chris about 12 years ago
- Status changed from Open to Closed
- % Done changed from 0 to 100
Completed
Updated by Tunnell, Christopher about 12 years ago
- Target version changed from Future MAUS release to MAUS-v0.0.2
Updated by Tunnell, Christopher about 12 years ago
- Target version changed from MAUS-v0.0.2 to MAUS-v0.0.1