RxJava 1.x end-of-life

[akarnokd]

The end-of-life for the RxJava 1.x version is nearing, March 31, 2018. However, there are still a bunch of components marked as @Beta or @Experimental. Most of these have been made standard in 2.x from the beginning and users are encouraged to upgrade for some time now anyway.

There could be a final 1.4 release where these components are promoted to standard, however, the remaining 1-1.5 months aren't really that much time for support if some very latecommers start using them and find bugs.

Alternatively, the RxJava 1.x era could simply end with a 1.3.x patch version and without any promotion.

[davidmoten]

I agree that promoting @Beta or @Experimental features to standard doesn't mean much if the support life is so short. I'm not fussed about staying as is.

[artem-zinnatullin]

I'd keep @Beta and @Experimental annotations as is, end-of-life is end-of-life. Less changes we do - less we need to worry about.

[JakeWharton]

Since the annotations are indication of API stability, I see no reason to retain them for the final release as everything will become effectively stable. In fact, I'd argue that removing the annotations more clearly conveys the intention of the end-of-life release as a freezing of both API and implementation.

And since there is no risk in removing them I don't see a reason why they should be retained.

[davidmoten]

I prefer to keep them in the case of a fork that continues to release (I might do that to support my prod apps if required).

[akarnokd]

Closing via 1.3.8. No changes to the tags.