Update CHANGELOG

fix typo
asset_paths should be an Array, is a String

any? is called on asset_paths, which is a string due to an early call to
join for a run call to find
Merge pull request #452 from lidaobing/patch-1

Update CHANGELOG. (Typo.
Merge pull request #453 from joeycarmello/fix_runtime_error_with_true_normalize_asset_timestamps

asset_paths should be an Array, is a String
Preparing Release v2.15.0
Preparing Release v2.15.1
Preparing Release v2.15.2
For deploy:cleanup, use try_sudo with rm command.
Fixes parallel execution command logging, GH-434

branches when more than one is really an array of array and hence
must be treated as such.
Restore maintenance.rhtml

from 28c484f1f5e6a009d1b8ff07d85e924d6f947d3c^
Merge pull request #454 from joshstaiger/sudo_cleanup

For deploy:cleanup, use try_sudo with rm command.
Merge pull request #456 from chulkilee/fix-maintenance

Restore maintenance.rhtml
Merge pull request #455 from gnufied/master

Fixes GH-434, If branches is an array of array, iterate them separately.
Preparing Release v2.15.3
Fix parallel command execution logging parallely - GH434

Also add unit tests that reproduce the problem
Merge pull request #457 from gnufied/master

Fix parallel command logging properly
Raise error when more than one asset manifest file is detected

If a user is upgrading from Rails 3 to 4, the assets:precompile task will ignore the manifest.yml
that was generated in Rails 3 and generate its own JSON manifest. It's impossible for us to know
which manifest the user's current code requires, so it's important that we only have one manifest
in the assets directory at a time. When we detect two manifests, we raise an error pointing the
user towards a wiki entry explaining the problem and instructing them to remove the Rails 3.x manifest.
Properly deal with the asset manifest files when a user is rolling back from Rails 4 to 3.

If a user rolls back an application that was upgraded to Rails 4 to their Rails 3 code,
we need to remove their JSON Rails 4 asset manifest file and restore their YAML Rails 3
manifest instead of blindly restoring their manifest to whatever their current manifest
is named, as we do in all other cases.
Merge pull request #461 from jimryan/handle-assets-manifest-during-rails-upgrade

Handle assets manifest during rails upgrade.
Preparing Release v2.15.4