RxScala: Fix recursive onStart call in Subscriber
Deprecate ParallelMerge

Removing in 1.0 as it is confusing and rarely useful.
Merge pull request #1646 from benjchristensen/deprecate-parallel-merge

Deprecate ParallelMerge
Merge pull request #1641 from jbripley/rxscala-onstart-recursive

RxScala: Fix infinite recursive onStart call in Subscriber
Operator Scan Backpressure Fix

Problem 1) The initial value was being emitted before subscription which caused issues with request/producer state, particularly if filter() was used to skip that initial value and then called request(1) before the real request had been sent.
Problem 2) The initial value was not accounted for by the request so it was sending 1 more value than requested. It now modifies the request to account for it.
Problem 3) Redo relied upon these nuances to work. I've fixed this by using a simpler implementation that just maintains state within a map function.
Fix that Subscriber.onStart isn't called
Merge pull request #1651 from zsxwing/rxscala-onstart

RxScala: Fix the problem that Subscriber.onStart isn't called
Update RxSwing use of Scan

The initial value is sent when first onNext is sent, not at subscription time.
Skip the empty Set being emitted

This is unnecessary and unexpected so skipping it.
Merge pull request #1648 from benjchristensen/scan-request-fix

Operator Scan Backpressure Fix
[Gradle Release Plugin] - pre tag commit:  '0.20.3'.
0.20.4-SNAPSHOT