Skip to content
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

Closed
gibfahn opened this issue Apr 24, 2017 · 7 comments
Closed

Backporting test fixes to maintenance branches #205

gibfahn opened this issue Apr 24, 2017 · 7 comments

Comments

@gibfahn
Copy link
Member

gibfahn commented Apr 24, 2017

See @MylesBorins comment in: nodejs/node#12567 (comment)

@gibfahn by the maintenance contract we are no longer supposed to be backporting fixes to tests. It didn't land because we have not been super adamant about making sure tests that don't land cleanly backport.

Personally I'm -1 on making exceptions for tests, but willing to reconsider if @nodejs/lts thinks this should land

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.

@gibfahn
Copy link
Member Author

gibfahn commented Apr 24, 2017

My initial feeling on this is that we should only backport tests if:

  • The test is failing (or failing intermittently) on that branch, and someone is actually requesting the backport, and
  • We're already doing a (non-security) release

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 v4.x-staging and sit there until we did a release, which might be never.

@sam-github
Copy link
Contributor

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.

@MylesBorins
Copy link
Contributor

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

@jasnell
Copy link
Member

jasnell commented Apr 24, 2017

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.

@mhdawson
Copy link
Member

mhdawson commented Apr 24, 2017

I'm +1 to fixing things that are broken and causing people problems. The key being that people are asking for the fix.

@refack
Copy link

refack commented Apr 24, 2017

+1 for no semver-minor (leave a window for an LTS WG consensus override vote)

@gibfahn
Copy link
Member Author

gibfahn commented Jun 14, 2017

Closing as agreed (no backporting by default, we can change our mind going forward if we want).

@gibfahn gibfahn closed this as completed Jun 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants