Add section about adding gem to Gemfile
Merge pull request #43 from arturtr/master

Add info about Gemfile to README
Update README.md
Merge pull request #45 from arturtr/patch-1

Update README.md
add mute to resque_scheduler startup
Merge pull request #47 from pavels/master

Fix resque_scheduler startup for master branch of resque_scheduler
Don't fail the deploy when Resque is dead - just move on
Convert tasks to new Capistrano 3 format
Load different set of tasks based on Capistrano's version
Compare the release version of Capistrano to accommodate pre-release versions
Check if Capistrano::VERSION is defined

V2 uses Capistrano::Version, not ::VERSION, so this would have thrown
an error when used in V2. (Thanks to @avaranovich for pointing this out)
Add instructions to have Bundler not load the gem by default
Merge pull request #62 from dmarkow/cap3

Capistrano V3 Support
Update README to include Cap v3 info
Update Changelog for upcoming gem release
Use resque_kill_signal setting when killing scheduler.
Merge pull request #66 from billymonk/use-resque_kill_signal-to-stop-scheduler

Use resque_kill_signal setting when killing scheduler.
Use resque_kill_signal setting when killing scheduler (Cap v3)

Incorporated changes from #66 to the v3 code.
Add an option to include the `environment` rake task.

With Rails, Resque requires loading the Rails environment task to have
access to your models, etc. (e.g. `QUEUE=* rake environment
resque:work`). However, Resque is often used without Rails (and even if
you are using Rails, you may not need/want to load the Rails
environment).

Additionally, some users might have already set up Resque to depend on
the environment task, e.g.:

task "resque:setup" => :environment

As such, the `environment` task is not automatically
included. However, you can now add this setting to your `deploy.rb` to
have capistrano-resque require the `environment` task:

set :resque_environment_task, true
Fix gem typo in bundler example