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

PRs policy #1061

Open
raulsebastianmihaila opened this Issue Jan 6, 2018 · 4 comments

Comments

Projects
None yet
3 participants
@raulsebastianmihaila

raulsebastianmihaila commented Jan 6, 2018

Should TC39 have a policy w.r.t the time frame in which a PR should be merged? There's currently an open PR, which has consensus, for a confirmed bug that was reported one year and a half ago.

@ljharb

This comment has been minimized.

Show comment
Hide comment
@ljharb

ljharb Jan 6, 2018

Member

No. #666 says that it's blocked on test262 tests.

Member

ljharb commented Jan 6, 2018

No. #666 says that it's blocked on test262 tests.

@raulsebastianmihaila

This comment has been minimized.

Show comment
Hide comment
@raulsebastianmihaila

raulsebastianmihaila Jan 6, 2018

@ljharb Does that mean that it can take 20 years for a PR that achieved consensus to be merged?

raulsebastianmihaila commented Jan 6, 2018

@ljharb Does that mean that it can take 20 years for a PR that achieved consensus to be merged?

@littledan

This comment has been minimized.

Show comment
Hide comment
@littledan

littledan Jan 6, 2018

Member

@raulsebastianmihaila That PR is pretty tricky; if we merge it without good test262 tests, I'm worried implementations might not get everything right. Test262 has been very useful in the implementation of Proxies across engines so far. If you want to push this feature forward, contributing the tests could help get it landed in less than 20 years :)

Member

littledan commented Jan 6, 2018

@raulsebastianmihaila That PR is pretty tricky; if we merge it without good test262 tests, I'm worried implementations might not get everything right. Test262 has been very useful in the implementation of Proxies across engines so far. If you want to push this feature forward, contributing the tests could help get it landed in less than 20 years :)

@raulsebastianmihaila

This comment has been minimized.

Show comment
Hide comment
@raulsebastianmihaila

raulsebastianmihaila Jan 6, 2018

@littledan Unfortunatelly I don't have enough time, working full time as a JS dev, having to write tests for my own JS framework, taking bachata and salsa lessons etc. :) Joking aside, is TC39 in general lacking resources for testing? Also, being a tricky PR it would probably be a good idea for an experienced Test262 person to take care of this one.

raulsebastianmihaila commented Jan 6, 2018

@littledan Unfortunatelly I don't have enough time, working full time as a JS dev, having to write tests for my own JS framework, taking bachata and salsa lessons etc. :) Joking aside, is TC39 in general lacking resources for testing? Also, being a tricky PR it would probably be a good idea for an experienced Test262 person to take care of this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment