Initial duplication of PE manual to start on 2.8 docs.
Merge branch 'master' of github.com:puppetlabs/puppet-docs into pe2-8-0

Syncing up before doing 2.8 documentation.
Merge branch 'pe2-7-1' into pe2-8-0

Bringing 2.7.1 stuff into 2.8.0 branch.
Merge branch 'pe2-7-1' into pe2-8-0

Pulling most recent 2.7.1 edits into 2.8.0
Initial groundwork for starting 2.8.0 doc changes and additions.
Change a bunch of numbered manual links to /latest/

Whenever it looked like we wanted to link to latest and fell back to
linking a specific version because that was all we could do, I switched
to latest.
Point PuppetDB 1.1 manual to 1.1.x branch instead of master

Now that 1.1.x exists, we'll use it.
Specify Rakefile encoding to keep Ruby 1.9+ happy

The Rakefile contains a multi-byte character, thus it needs an encoding or
Ruby 1.9 and newer [will refuse to process the file][ref].

  [ref]: http://blog.grayproductions.net/articles/ruby_19s_three_default_encodings
Merge pull request #138 from Sharpie/rakefile-encoding

Guts: Specify Rakefile encoding to keep Ruby 1.9+ happy
Guts: Removing debug message
Correction: Fixed erroneous instructions for PE db:create_user rake task
Correction: Wrong variable name in rake command
PuppetDB: Change name of "administration" section

It's actually usage, administration, and troubleshooting. As we add other troubleshooting pages, this will make it more clear where to look for them.
Merge branch 'master' of github.com:puppetlabs/puppet-docs into pe2-8-0
Refining and writing on AIX stuff, and some stray edits to DG intro.
fix double quotes used for a strong.
Fixing useradd feature documentation

The manages password and manages password age features of useradd were
inaccurately documented.

Support to manage passwords was added for 'useradd' in 0.22.4
Support to manage password ages was added for 'useradd'  in 2.6.2

This change retrofits all documents to reflect the appropriate features at the
time they were introduced
Writing and revision of CVE documentation for PE 2.7.2
Add new boilerplate text to redmine workflow doc

This describes the 'code insufficient' state, where a user
has submitted a patch and someone (PL or another user) found it
not to completely address the problem or regress on something.
WIP: best practices in examples

Bringing release notes over from wiki to docs