[TEST] Use a sorted set since sets are compared and compare is order specific
[TEST] fix another rounding issue
[STORE] Turn unexpected exception into CorruptedIndexException

Today if we run into exception like NumberFormatException or IAE
when we try to open a commit point to retrieve checksums and calculate
store metadata we just bubble them up. Yet, those are very likely index
corruptions. In such a case we should really mark the shard as
corrupted.
[Version] Add Version 1.4.0-Beta
[VERSION] Added Version [1.5.0]
[CORE] Ensure GroupShardsIterator is consistent across requests

GroupShardsIterator is used in many places like the search execution
to determin which shards to query. This can hold shards of one index
as well as shards of multiple indices. The iteration order is used
to assigne a per-request shard ID for each shard that is used as a
tie-breaker when scores are the same. Today the iteration order is
soely depending on the HashMap iteration order which is undefined or
rather implementation dependent. This causes search requests to return
inconsistent results across requests if for instance different nodes
are coordinating the requests.

Simple queries like `match_all` may return results in arbitrary order
if pagination is used or may even return different results for the same
request even though there hasn't been a refresh call and preferences are
used.
Update update.asciidoc

The upserts section should be on the same page as updates.
Tests: add an awaitFix to IndicesLifecycleListenerTests
Tests: add a comment to DiscoveryWithServiceDisruptions.testAckedIndexing reminding to port it to 1.x once the awaitFix is removed
Fixed bug in es_release_notes script
[TEST] Adds tests for GeoUtils
Added support for github access tokens to es_release_notes
Geo: Fixes BoundingBox across complete longitudinal range

Adds a special case to the GeoBoundingBoxFilterParser so that the left of the box is not normalised in the case where left and right are 360 apart.  Before this change the left would be normalised to 180 in this case and the filter would only match points with a longitude of 180 (or -180).

Closes #5128
Discovery: restore preference to latest unicast pings describing the same node

Closes #7702
[TEST] added trace logging for index recovery in GeoBoundsTests
[TEST] Additional logging info for node with primary
Aggs enhancement - allow Include/Exclude clauses to use array of terms as alternative to a regex
Closes #6782
Parent/child: If a p/c query is wrapped in a query filter then CustomQueryWrappingFilter must always be used and any filter wrapping the query filter must never be cached.

Closes #7685
Fixed explanation for GaussDecayFunction

The explanation now gives the correct value instead of the negative.
[TEST] Fix test explain now that explanation is fixed