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

More rigor around fixing regressions in any release branch. #4380

Closed
Fishrock123 opened this issue Dec 21, 2015 · 1 comment
Closed

More rigor around fixing regressions in any release branch. #4380

Fishrock123 opened this issue Dec 21, 2015 · 1 comment
Labels
discuss Issues opened for discussions and feedbacks. meta Issues and PRs related to the general management of the project.

Comments

@Fishrock123
Copy link
Contributor

I think it is probably a good idea to not hold up releases at all if possible to fix API-breaking regressions in any (Major) branch where fixing it would be reasonable to do on a technical level.

This should include mondays and fridays but not weekends.

Perhaps we can state this somewhere?

(Inspired by #4316) (oops)

cc @nodejs/ctc

@Fishrock123 Fishrock123 added discuss Issues opened for discussions and feedbacks. meta Issues and PRs related to the general management of the project. labels Dec 21, 2015
@ljharb
Copy link
Member

ljharb commented Dec 21, 2015

That sounds like a great idea - imo it's ideal if the fix lands in the same minor in which it was introduced (LTS, or not, it should be treated with the same respect/quality/rigor).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss Issues opened for discussions and feedbacks. meta Issues and PRs related to the general management of the project.
Projects
None yet
Development

No branches or pull requests

2 participants