This repository has been archived by the owner on Nov 9, 2017. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 27
Buffer constructor: random-fill in Node.js 8.0.0? #90
Comments
NO |
No (my vote is for zero-fill in Node.js 8.0.0) |
what james said |
abstain (favor zero-fill) |
Abstain (favour zero fill). |
Abstain (favor zero fill) |
No |
My vote is no. |
nope |
no |
If I’m counting correctly this has 9 No votes and 4 abstentions, which means that this can be closed with “No” as the result. |
3 tasks
No - Zero Fill. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
@nodejs/ctc Next vote that was started in the CTC meeting. If you are not listed below (or if your vote has changed or been recorded incorrectly), please comment! Thanks!
Should we random-fill in Node.js 8.0.0?
YES: @addaleax, @cjihrig, @targos, @fhinkel
NO: @mscdex, @ChALkeR, @indutny, @jasnell, @MylesBorins, @shigeki, @misterdjules, @trevnorris, @rvagg, @thefourtheye
ABSTAIN: @Trott, @Fishrock123, @ofrobots, @evanlucas
MY VOTE DEPENDS ON WHETHER OR NOT WE BACKPORT AND/OR WHICH RELEASE LINES WE BACKPORT TO:
There is a separate issue for the question of whether we zero-fill. If both pass and there's not consensus over which one to do, we'll have another vote.
The text was updated successfully, but these errors were encountered: