-
Notifications
You must be signed in to change notification settings - Fork 577
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
Backporting test fixes to maintenance branches #205
Comments
My initial feeling on this is that we should only backport tests if:
So it would only apply to actual test-case issues, and it would only be included in a (vanishingly rare) non-security maintenance release. PRs could land on |
Seems reasonable to me. Its worth having the test suite in good order for when a release has to happen. Not worth landing the flood of test PRs. |
I'd be open to landing test fixes for things that are broken... in fact perhaps this is a bigger question about what we are willing to land on maintenance if people are requesting it. Looking forward to discussing this afternoon |
The maintenance phase is specifically limited to critical fixes. Updates to test do not count as critical. We did not update the tests in 0.12 or 0.10 unless those were tied to specific other changes that were being made. I'm -1 on backporting tests unless those changes fall into the "critical" category. |
I'm +1 to fixing things that are broken and causing people problems. The key being that people are asking for the fix. |
+1 for no |
Closing as agreed (no backporting by default, we can change our mind going forward if we want). |
See @MylesBorins comment in: nodejs/node#12567 (comment)
We should have the discussion and clarify whether we think any test fixes should be backported, and if so which ones.
This was originally in #188, but I thought we should record our decision separately.
The text was updated successfully, but these errors were encountered: