1.0.2

This release adds @Beta and @Experimental annotations to mark APIs that are not yet stable.

An example of how this looks in the Javadocs is:

@Experimental
public final Observable<T> onBackpressureBlock()

The lifecycle and stability of these are documented in the README as follows:

@beta

APIs marked with the @Beta annotation at the class or method level are subject to change. They can be modified in any way, or even removed, at any time. If your code is a library itself (i.e. it is used on the CLASSPATH of users outside your own control), you should not use beta APIs, unless you repackage them (e.g. using ProGuard, shading, etc).

@experimental

APIs marked with the @Experimental annotation at the class or method level will almost certainly change. They can be modified in any way, or even removed, at any time. You should not use or rely on them in any production code. They are purely to allow broad testing and feedback.

• Pull 1905 Beta & Experimental Annotations
• Pull 1907 Experimental: onBackpressureBlock
• Pull 1903 Fix TestScheduler Handling of Immediate vs Virtual Time
• Pull 1898 Scheduled action no interrupt
• Pull 1904 Fix the bug that Scan may request 0 when n is 1
• Pull 1912 Fixed retry without backpressure & test function to support bp

Artifacts: Maven Central