Fix split command argument leading to error raised and incorrect path returned
Merge branch 'master' of https://github.com/capistrano/capistrano into fix_last_release_path_bug

Conflicts:
	lib/capistrano/tasks/deploy.rake
remove last_release_path and add check in rollback_release_path

- remove last_release_path task per seenmyfate
- add error check per seenmyfate
:panda_face: Updated the loading default config tasks and stages config tasks.

To show all tasks decalred in default config and stages files was missed from the tasks list.
Added default value for :stage and load all default configs. Also added cucumber tests.
:panda_face: Added ability to add args to callabcks after and before.
make sure deploying? method is available beofre testing it, fix #915
Update ´invoke()´ docu in README

Update following user report in #571
Call branch proc by default in deploy.rb template.

If a proc is used in an ask and no input is entered for the ask, `question.rb` will use the default value, which is a proc object and *not* its returned value. 

Without `.call`, we can get issues like the following, from `capistrano-rsync`:

Code:

```ruby
      checkout = %W[git reset --hard origin/#{fetch(:branch)}]
      Kernel.system *checkout
```

Error:

```
Please enter branch: |master|

fatal: Invalid object name 'origin/#<Proc'.
cap aborted!
```
Fixed a typo
Merge pull request #951 from caseyhelbling/spelling-error

Fixed a typo
Without this, the sentence doesn't quite make proper sense.
Merge pull request #960 from seanhandley/master

Without this, the sentence doesn't make proper sense.
No need to define a method that only calls "super"

It used to also define "@name = 'cap'" originally: https://github.com/capistrano/capistrano/commit/de6367af4ea3ea786fe78221cfd3838c827c5e0c
Merge pull request #965 from rosenfeld/patch-1

No need to define a method that only calls "super"
Don't ignore options passed to release_roles

Previously the merge wouldn't change the options in place.

I thought about changing it to merge! but I'm not sure if it's a good idea to have such side effect.
Added keys method to Server properties

When generating servers programmatically this provides a method
of determining what properties have been added.
Includes simple spec test
Merge pull request #969 from townsen/master

Added keys method to Server properties
Combined emphasis use underscores
Merge pull request #975 from nemesis/patch-1

Combined emphasis use underscores
Fix some typos