Update doctrine/cache to the latest stable release

Just in general, we could avoid those updates given that they are not an explicit dependency. In case some other library requires a newer version, it will be updated automatically.
Later then, we could also update right before the release.

@dawehner,
I saw in one of the issue before regarding the updation of a vendor library which was dependent on the other third party vendor library and composer was not showing its latest version during composer update.
Exact similar issue here https://www.drupal.org/node/2488960#comment-9924124
Is it something else that was missed ? Thanks!

Looks good to me.

This one needs a quick re-roll because the other one went in.

Rerolled.

$ composer update doctrine/cache
Loading composer repositories with package information
Updating dependencies (including require-dev)
  - Removing doctrine/cache (v1.3.1)
  - Installing doctrine/cache (v1.4.1)
    Downloading: 100%         

Writing lock file
Generating autoload files

unassinging to myself.

Had some unrelated changes in core/Maintainers.txt. So rerolling this one again.

This is fixed https://www.drupal.org/node/2488960
composer update doctrine/cache

- Installing doctrine/cache (v1.4.1)
Downloading: 100%

Patch tested and composer installs v1.4.1 of doctrine/cache

1.4.2 is out and is a security release http://www.doctrine-project.org/2015/08/31/security_misconfiguration_vul...

Working on re-roll

We need to bump common, annotations and cache - given common relies on the other two, this is a duplicate.
Thanks for your work here, see you in #2105825: Update Doctrine/common Component to 2.5.1 (security) (includes cache/annotations too)