-
Notifications
You must be signed in to change notification settings - Fork 340
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
New scheduler #733
New scheduler #733
Conversation
@k-nasa overall this looks good; I can't spot any bugs through review. But still, the fact that a few bugs slipped through CI on an earlier round makes me feel a bit nervous about merging it as-is; I didn't write this part of the code, and don't trust myself to do a full review. What would help here is if we could add more tests -- at least some we know would have failed if we hadn't caught them during review. Having those would provide more confidence that these changes actually work as intended. Thanks! |
I think asking folks to test this branch in larger apps or libraries will also help to find bugs and build confidence
…On 22. Mar 2020, 12:42 +0100, Yoshua Wuyts ***@***.***>, wrote:
@k-nasa overall this looks good; I can't spot any bugs through review. But still, the fact that a few bugs slipped through CI on an earlier round makes me feel a bit nervous about merging it as-is; I didn't write this part of the code, and don't trust myself to do a full review.
What would help here is if we could add more tests -- at least some we know would have failed if we hadn't caught them during review. Having those would provide more confidence that these changes actually work as intended. Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
@yoshuawuyts @dignifiedquire What about publishing in version 1.6.0-alpha? |
@k-nasa yes, that is the current plan. Cutting an alpha prerelease with this and get folks testing. |
This has been merged to master, we will be releasing a |
This PR is a successor to #631 .
This PR contains only the following parts:
What we did in this PR