Content Skeleton

This Page

Next topic

Installing env

Env Development Log

Date:January 15, 2018

Objectives for these pages.

  1. TODO list
  2. 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:




Indices and tables