docs($compile): fixed syntax error.

"how to" was written twice in a row.

Closes #6110
fix(ngResource): don't filter "$"-prefixed properties from ngResource requests/responses

ngResource no longer filters properties prefixed with a single "$" character from requests or
responses, correcting a regression introduced in 1.2.6 (cb29632a) which caused shallowCopy and
shallowClearAndCopy to ignore properties prefixed with a single "$".

Closes #5666
Closes #6080
Closes #6033
docs(CHANGELOG): add breaking change notice for 1.2.9 $http default headers change

Add a mention for the slightly breaking change introduced in 1.2.9.

Closes #6022
fix($http): ignore xhr.responseType setter exception if value is "json"

WebKit added support for the json responseType value on 09/03/2013
https://bugs.webkit.org/show_bug.cgi?id=73648. Versions of Safari prior to 7 are known to throw when
setting the value "json" as the response type. Other older browsers implementing the responseType.
Other browsers with infrequent update cycles may also be affected.

The json responseType value can be ignored if not supported, because JSON payloads are parsed on the
client-side regardless.

Closes #6115
Closes #6122
revert: "fix($http): ignore xhr.responseType setter exception if value is "json""

This reverts commit 431bad01835f0294eb159d5b08101d5904828147.
chore(release): be able to release any commit

The version information is now stored only in the tags.
By this we are able to release commits in the past, which
have already been tested, so we don't need a code freeze
or run tests any more. This is also the first step for
letting Travis do the releases in the future.

The package.json now contains the new
property 'branchVersion' that defines which tags are
valid on this branch.

Closes #6116
docs(log.js): param debugEnabled is a boolean and not a string
fix($http): ignore xhr.responseType setter exception if value is "json"

WebKit added support for the json responseType value on 09/03/2013
https://bugs.webkit.org/show_bug.cgi?id=73648. Versions of Safari prior to 7 are known to throw when
setting the value "json" as the response type. Other older browsers implementing the responseType.
Other browsers with infrequent update cycles may also be affected.

The json responseType value can be ignored if not supported, because JSON payloads are parsed on the
client-side regardless.

Closes #6115
Closes #6122
fix(jqLite): trim HTML string in jqLite constructor

jQuery will construct DOM nodes containing leading whitespace. Prior to this change, jqLite would
throw a nosel minErr due to the first character of the string not being '<'. This change corrects
this behaviour by trimming the element string in jqLite constructor before testing for '<'.

Closes #6053
fix(ngMock): return false from mock $interval.cancel() when no argument is supplied

Closes #6103.
Closed #6099.
chore(ngdoc): fix misspellling of Naturally in sortVersionsNatrually

Corrects "sortVersionsNatrually" method name in `ngdoc.js` in "sortVersionsNaturally"
docs(forEach): correct spelling error

Closes #6124
chore(build): remove `MINERR_ASSET` from source map

The actual change happened in ng-closure-runner.
The change here just includes the new version.

Closes #4675
chore(end2end): remove old references to the scenario runner and update to point to protractor
chore(testing): run end to end tests on firefox and safari as well as chrome

Update the Travis and Jenkins configs to run protractor tests on Safari and Firefox as well,
and make the Travis tests run output XML and turn off color.

Fix tests which were failing in Firefox due to clear() not working as expected.

Fix tests which were failing in Safari due to SafariDriver not understanding the minus key,
and disable tests which SafariDriver has no support for.
refactor(testing): run end to end tests on separate browsers in parallel
chore(testing): fix Jenkins breakage due to test directory already being present
docs(angular.forEach): add missing space in test

Closes #6130
fix(mocks): remove usage of $animate.flushNext in favour of queing

The flushNext method of testing is difficult and highly coupled with the behavior
of ngAnimate's $animate workflow. It is much better instead to just queue all
$animate animation calls into a queue collection which is available on the $animate
service when mock.animate is included as a module within test code.
fix(mocks): rename mock.animate to ngAnimateMock and ensure it contains all test helper code for ngAnimate

Closes #5822
Closes #5917