-
Notifications
You must be signed in to change notification settings - Fork 7.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 1.0.5 #2555
Comments
If all my open PRs could make it, that would be great.
|
Do you have any concerns with anything that has been merged? Here is the diff from last release: v1.0.4...1.x |
No. |
I think the correct behavior is what's now. Would you consider a test to be passed if it timed out silently? |
I think the current behavior is more reasonable. I just wonder the policy about changing the behavior of a method in TestObserver/TestSubscriber/TestScheduler. For the changing of |
These are test related code. You don't run unit tests in production, but only in development where you have access to your own tests and can update them according to the new behavior. |
I've reviewed all merged pull requests and am ready to release 1.0.5 except for a comment I added to #2465 about the naming convention of the system property. |
Here are the changes currently queued for release:
|
There are 3 bug fixes (2 trivial, 1 awaiting review) that should make it into 1.0.5. I've also created a PR to change the NewThreadWorker's system parameter names. |
Which of the 8 PRs should I look at? |
Most urgent: https://github.com/ReactiveX/RxJava/pulls?q=is%3Aopen+is%3Apr+label%3ABug |
Thanks, reviewing. |
Let's plan on releasing Wednesday if possible. I apologize for letting 1.0.5 drag on so long ... I've been swamped in other areas recently. Thank you very much @akarnokd @zsxwing @davidmoten and others for all the work on 1.0.5. |
Preparing to release 1.0.5 ...
The text was updated successfully, but these errors were encountered: