Project

General

Profile

Feature #340

hacking documentation

Added by Rogers, Chris over 12 years ago. Updated about 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Rogers, Chris
Category:
Documentation
Target version:
MAUS-v0.0.1
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)
#1

Updated by Rogers, Chris over 12 years ago

  • Assignee set to Rogers, Chris
#2

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?

#3

Updated by Tunnell, Christopher over 12 years ago

  • Category set to Documentation
#4

Updated by Tunnell, Christopher about 12 years ago

  • Target version set to Future MAUS release
#5

Updated by Tunnell, Christopher about 12 years ago

This done?

#6

Updated by Rogers, Chris about 12 years ago

  • Status changed from Open to Closed
  • % Done changed from 0 to 100

Completed

#7

Updated by Tunnell, Christopher about 12 years ago

  • Target version changed from Future MAUS release to MAUS-v0.0.2
#8

Updated by Tunnell, Christopher about 12 years ago

  • Target version changed from MAUS-v0.0.2 to MAUS-v0.0.1

Also available in: Atom PDF