Add a $key_options parameter, which need to work apt-key via proxy.
Merge remote-tracking branch 'upstream/master'
add new puppet version to travis
Fix stdlib version dependency
Changed PPA manifest and tests for new package which started in Quantal
Merge pull request #96 from jnicolson/master

Modified the PPA code for changes in Quantal
Release 1.1.0 (Ubuntu 12.10 support)

Prior to this release, Ubuntu 12.10 (Quantal) was not supported.

This commit marks the Forge release of 1.1.0 which includes this
support, thanks to Jarl Nicolson.
Merge pull request #97 from puppetlabs/release/quantal_support

Release 1.1.0 (Ubuntu 12.10 support) -- Merging my own release-only commit.
fix minor comment typo
minor punctuation and quotation corrections in comments
Merge pull request #101 from ChrisRut/master

minor correction to comment
whitespace fixes
Merge pull request #102 from mmoll/lint_fixes

whitespace fixes
Update travis config file

This commit adds ruby 1.9.3, puppet 3.0.2 support and a
build status image to the README.
Merge pull request #105 from blkperl/update_travis

Update travis config file
Build all branches on travis

We should build all branches for travis, otherwise users won't be able to test
their own feature branches.
Merge pull request #106 from blkperl/build_all_branches

Build all branches on travis
Standardize travis.yml on pattern introduced in stdlib
Merge pull request #107 from blkperl/travis_update

Standardize travis.yml on pattern introduced in stdlib
Updated content to conform to README best practices template

*Note: I thought this was small enough to forgo a TOC. Please let me
know if one is desired and I can add it in.*

Before alterations, this content was the module author- determined
description of and instructions for use of the module.

As part of a joint Forge/Docs team effort to standardize formatting and
encourage quality module documentation, a best practices README
template was created via internal and external user testing. That
template was then applied to this module.

I pulled in content from the original README on GitHub. Standard
headings were added (Overview, Module Description, Setup, Usage,
Implementation, etc.) to organize content, existent content was moved
under its appropriate heading and edited for tone/flow/clarity, and
basic formatting was done to adhere to template standards.