:modified: 2012-07-10 08:42:54+00:00 :tags: Red,Green,Blue Env Development Log ======================= :Version: |version| :Date: |today| Objectives for these pages. #. TODO list #. development log Major issues should continue to be tracked via env trac tickets but often a large number of smaller issues are dealt with when performing recoveries. The Trac interface is suited to long lived issues, whereas a more logging style of interface is useful to capture operational fixes and techniques. Have formerly been using Trac wiki pages for this purpose, but that looses the intimate context of having sources of documentation residing in the same repository as the code being developed, and suffers from inconvenient web interface text editing. Seeing **TODO** items and logged fixes in the same commits as the code changes is invaluable. Very structured information closely linked to bash functions should be logged within the bash functions themselves. For example: Disabled:: TODO Contents: .. toctree:: :maxdepth: 2 install base/index LOG TODO Sys Admin Plotting SCM Trac ROOT sphinxext/index matplotlib/index nose/index svn/index npy/index pypy/index tools/index mysqlhotcopy/index mysql/index sqlite/index db/index qxml/index fossil/index java/index cuda/index pycuda/index geant4/index muon_simulation/index chroma/index llvm/index graphics/index ggeoview/index oglrap/index cfg4/index cuda/index opencl/index linux/index cloud/index package_management/index ui/index debugging/index mercurial/index javascript/index nuwa/index ccgpu/index pygame/index zeromq/index doc/index python/index osx/index hg/index simoncblyth.bitbucket.org/index numpy/index presentation/index optix/index Indices and tables ================== * :ref:`genindex` * :ref:`modindex` * :ref:`search`