Comment #10 on issue 3692 by [email protected]: function suddenly
becomes undefined
https://code.google.com/p/v8/issues/detail?id=3692
I def don't want to point fingers at any of the teams involved, and I hope
my frustration above didn't come across as finger pointing. It's the
situation that's unfortunate. At this point, I think it's important to ask
the question of how it came to be, and more importantly, what can be done
to ensure it doesn't happen in the future.
There just has to be a way to keep release versions of node within a
reasonable v8 version window. Like #8 and #9 mentioned, more frequent
releases, patch releases dedicated solely to v8 updates, internal node
abstractions to isolate v8 APIs so that changes to v8 have less of an
impact, or are easier to deal with, etc.
Does anyone know if there's a new plan already in place for doing that with
0.12?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
