Merge the Evergreen docs into the code repository Rather than maintaining two separate repositories, with dual maintenance of what are essentially single-sourced files in the release notes and the install instructions, make better use of the docs/ subfolder of the Evergreen repository. If this crazy scheme works, DIG can commit to the docs/ subfolder, and devs can commit there too. Signed-off-by: Dan Scott <dscott@laurentian.ca>
Update Release Notes and Installation documents to match code We need to keep the release notes and installation instructions in sync with the code versions. To make our lives easier, use the "leveloffset" AsciiDoc macro so that we don't have to push all of the heading indicators in the single-sourced documents down one level manually. Signed-off-by: Dan Scott <dan@coffeecode.net>
Fix references to 2.2-beta2 throughout the upgrade document There were a number of references to 2.2.beta1 instead of 2.2-beta1; also, we're at beta2 now, so point to that. Also, point to the right version upgrade script (now living in a new directory). Signed-off-by: Dan Scott <dscott@laurentian.ca>
Server upgrade instructions Focus on the database schema first, as the longest part of the job. Qualify the instructions noting that they are currently oriented towards a default installation - not particularly realistic. Signed-off-by: Dan Scott <dscott@laurentian.ca>
Server upgrade refinement for 2.2 * Try to use "As the <foobar> user" consistently. * Remove trailing whitespace from lines * Use backticks to flag commands in context * Present names of prereqs and distros in definition lists in bold to set them apart visually * Small typo fixes Signed-off-by: Dan Scott <dscott@laurentian.ca>