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>
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>
Use STAFF_CLIENT_STAMP_ID, not STAFF_CLIENT_BUILD_ID With recent changes to staff client builds, STAFF_CLIENT_STAMP_ID is now the preferred environment variable to use. 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>
Fixes to server_upgrade.txt provided by Dan Scott in bug https://bugs.launchpad.net/evergreen/+bug/974600. Thanks Dan!
Add some ESI documentation.
Move installation files into installation folder for 2.2 reorg.