-
Notifications
You must be signed in to change notification settings - Fork 134
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
Reaching a decision on "drop minimum wait time" #921
Comments
I'm +-0 with my main concern being the "immediate revert" but not to the point where I'd block (and have not in the issue). I have some worries but am willing to see how the changes work out assuming the rest of the TSC feels its the right way to go. |
I think this is the best solution. |
+1 to this plan |
I'm +1 to what @mcollina suggested:
|
Believe this has been addressed, closing. @mmarchini let me know if you think that was not the right thing to do. |
nodejs/node#33879 has been blocked for a while, some suggestions to mitigate the concerns were raised but the objector hasn't commented on those suggestions. Therefore I would like for the TSC to step in the PR and decide if it should be closed, if it should move forward as is, or if it should move forward with modifications (and then list what those modifications should be).
PR Summary
PR reason
Proposed change
Objection
Compromise suggestions
nodejs/node#33879 (comment), nodejs/node#33879 (comment):
nodejs/node#33879 (comment):
cc @nodejs/tsc
The text was updated successfully, but these errors were encountered: