Planning for v6

[jasnell]

@nodejs/ctc @nodejs/lts - It's almost time to begin preparing the v6 release. What schedule do we want to target? I volunteer to do the actual release.

A quick run on changelog-maker looking at all semver-major changes since v5.0.0 was cut shows 48 semver-major commits:

• [85ab4a5] - (SEMVER-MAJOR) buffer: add .from(), .alloc() and .allocUnsafe() (James M Snell) buffer: add Buffer.from(), Buffer.alloc() and Buffer.allocUnsafe(), soft-deprecate Buffer(num) #4682
• [2c55cc2] - (SEMVER-MAJOR) buffer: remove deprecated Buffer.write branch (dcposch@dcpos.ch) Remove deprecated Buffer.write(...) #5048
• [101bca9] - (SEMVER-MAJOR) buffer: remove deprecated buffer.get/.set methods (Feross Aboukhadijeh) Remove deprecated buffer.get / buffer.set methods #4594
• [3b27dd5] - (SEMVER-MAJOR) buffer: throw if both length and enc are passed (Mathias Buus) buffer: throw if both length and enc are passed #4514
• [90a5fc2] - (SEMVER-MAJOR) build: remove lint/dotfiles from release tarball (Johan Bergström) Reduce tarball size, v2 #5695
• [66f4586] - (SEMVER-MAJOR) cluster: emit worker as first 'message' event arg (Ben Noordhuis) cluster: emit worker as first 'message' event arg #5361
• [a5cce79] - (SEMVER-MAJOR) console: delete timers that have ended (Vladimir Varankin) console: prevent internal timers storage from growing #3562
• [a37401e] - (SEMVER-MAJOR) crypto: simplify Certificate class bindings (Alexander Makarenko) crypto: simplify Certificate class bindings #5382
• [7c48cb5] - (SEMVER-MAJOR) crypto: Improve control of FIPS mode (Stefan Budeanu) crypto: Improve control of FIPS mode #5181
• [a116358] - (SEMVER-MAJOR) crypto: pbkdf2 deprecate digest overload. (Tom Gallacher) crypto: pbkdf.js deprecate digest overload. #4047
• [b010c87] - (SEMVER-MAJOR) crypto, string_bytes: treat buffer str as utf8 (Fedor Indutny) crypto, string_bytes: treat buffer str as utf8 #5522
• [dbdbdd4] - (SEMVER-MAJOR) dns: add resolvePtr to query plain DNS PTR records (Daniel Turing) Support resolving plain DNS PTR records #4921
• [c4ab861] - (SEMVER-MAJOR) dns: add failure test for dns.resolveXXX (Daniel Turing) Support resolving plain DNS PTR records #4921
• [f3be421] - (SEMVER-MAJOR) dns: coerce port to number in lookupService (Evan Lucas) dns: coerce port to number in lookupService #4883
• [d829028] - (SEMVER-MAJOR) doc: document deprecation of util._extend (Benjamin Gruenbaum) doc: document deprecation of util._extend #4903
• [90204cc] - (SEMVER-MAJOR) domains: clear stack when no error handler (Julien Gilli) domain: fix clearing domains stack #4659
• [8bb60e3] - (SEMVER-MAJOR) fs: improve error message for invalid flag (James M Snell) fs: improve error message for invalid flag #5590
• [1d79787] - (SEMVER-MAJOR) fs: add a temporary fix for re-evaluation support (Сковорода Никита Андреевич) fs: add a temporary fix for re-evaluation support #5102
• [1124de2] - (SEMVER-MAJOR) fs: deprecate fs.read's string interface (Sakthipriyan Vairamani) fs: deprecate fs.read's string interface #4525
• [2b15e68] - (SEMVER-MAJOR) fs: fs.read into zero buffer should not throw exception (Feross Aboukhadijeh) fs.read into zero buffer should not throw exception #4518
• [8b97249] - (SEMVER-MAJOR) fs: fix the error report on fs.link(Sync) (yorkie) fs: fix the error report on fs.link(Sync) #3917
• [d01eb68] - (SEMVER-MAJOR) lib: add 'pid' prefix in internal/util (Minwoo Jung) lib: add 'pid' prefix in internal/util #3878
• [20285ad] - (SEMVER-MAJOR) lib: Consistent error messages in all modules (micnic) Consistent error messages in all modules #3374
• [94b9948] - (SEMVER-MAJOR) lib,src: ensure '(node:pid)' prefix for stdout logging (Minwoo Jung) lib,src: Ensure '(node:pid)' prefix for stdout logging #3833
• [b70dc67] - (SEMVER-MAJOR) lib,test: remove publicly exposed freelist (cjihrig) lib,test: remove publicly exposed freelist #3738
• [71470a8] - (SEMVER-MAJOR) module: pass v8::Object to linked module initialization function (Phillip Kovalev) module: pass v8::Object to linked module initialization function #4771
• [18490d3] - (SEMVER-MAJOR) module: always decorate thrown errors (Brian White) module: always decorate thrown errors #4287
• [a78b334] - (SEMVER-MAJOR) net: type check createServer options object (Sam Roberts) net: type check createServer options object #2904
• [25751be] - (SEMVER-MAJOR) node: deprecate process.EventEmitter (Evan Lucas) node: deprecate process.EventEmitter #5049
• [d1000b4] - (SEMVER-MAJOR) path: make format() consistent and more functional (Nathan Woltman) path: make format() consistent and more functional #2408
• [72e3dd9] - (SEMVER-MAJOR) process: throw on non-function to nextTick() (yorkie) process: nextTick should not be handled lazily #3860
• [ca2e8b2] - (SEMVER-MAJOR) readline: deprecate undocumented exports (cjihrig) readline: deprecate undocumented exports #3862
• [5700352] - (SEMVER-MAJOR) src: attach error to stack on displayErrors (cjihrig) src: attach error to stack on displayErrors #4874
• [bfb2cd0] - (SEMVER-MAJOR) stream: add bytesRead property for readable (Jackson Tian) stream: add bytesRead property for readable #4372
• [cc0342a] - (SEMVER-MAJOR) streams: update .readable/.writable to false (Brian White) streams: update .readable/.writable to false #4083
• [5f76b24] - (SEMVER-MAJOR) http: overridable clientError (Fedor Indutny) Make clientError overridable #4557
• [a5aa7c1] - (SEMVER-MAJOR) test: expand test case for unknown file open flags (James M Snell) fs: improve error message for invalid flag #5590
• [2c33819] - (SEMVER-MAJOR) test: fix tests that check error messages (cjihrig) test: fix tests that check error messages #3727
• [ac153bd] - (SEMVER-MAJOR) timers: fail early when callback is not a function (Anna Henningsen) timers: Fail early when callback is not a function #4362
• [1ab6b21] - (SEMVER-MAJOR) tls: rename clientError to tlsClientError (Fedor Indutny) Make clientError overridable #4557
• [df268f9] - (SEMVER-MAJOR) tls: use SHA1 for sessionIdContext (Stefan Budeanu) tls: Use SHA1 for sessionIdContext #3866
• [a2c0aa8] - (SEMVER-MAJOR) tty: Remove deprecated setRawMode wrapper (Wyatt Preul) tty: Remove deprecated setRawMode wrapper #2528
• [e2f47f5] - (SEMVER-MAJOR) util: Change how Error objects are formatted (Mudit Ameta) util: Change how Error objects are formatted #4582
• [93d6b5f] - (SEMVER-MAJOR) util: use consistent Dates in inspect() (Xotic750) util,test: Use consistent Date representation for util/inspect #4318
• [24012a8] - (SEMVER-MAJOR) util: make inspect more reliable (Evan Lucas) util: make inspect more reliable #4098
• [007cfea] - (SEMVER-MAJOR) util: remove pump (Wyatt Preul) util: Remove pump #2531
• [4cf19ad] - (SEMVER-MAJOR) util: Remove exec, has been deprecated for years (Wyatt Preul) util: Remove exec, has been deprecated for years #2530
• [34a3591] - (SEMVER-MAJOR) util: improve typed array formatting (Ben Noordhuis) util: improve typed array formatting #3793

This, of course, does not include the v8 updates.

(BTW, According to changelog-maker, there have been around 1023 commits in master since v5.0.0 was tagged.)

[Fishrock123]

I'll handle writing up a more detailed breaking changes document shortly, just like I did for v4.

[chrisdickinson]

I'll spin up work on Promises again next week so I can give a status report on where they're at.

[Fishrock123]

cc @nodejs/v8 what version of v8 do we figure might be able to land in this?

[Fishrock123]

As a note, we should aim for mid April, late April at latest.

[jasnell]

+1 for mid April.

[ofrobots]

I would suggest targeting late April to make sure we can land V8 5.0.

[jasnell]

@ofrobots ... what's the current target date for v8 5.0?

[jbergstroem]

@jasnell The release page points to April 19th. End of April sounds like enough time to do a few RCs once it is 'officially' stable.

[jasnell]

Oh! I forgot there was a published release page ;) OK, that should work. We
might even be able to get away with cutting a RC before it goes stable as
long as it's close.
On Mar 17, 2016 3:11 PM, "Johan Bergström" notifications@github.com wrote:

@jasnell https://github.com/jasnell The release page
http://www.chromium.org/developers/calendar points to April 19th. End
of April sounds like enough time to do a few RCs once it is 'officially'
stable.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#5766 (comment)

[ofrobots]

As the release page mentions, April 19th is the estimated target date. Fine print:

These dates are subject to change without advance notice and provided here only for rough planning purposes. New bugs, security incidents, holiday schedules, partner dependencies and process changes can all affect these dates and move it in either direction. The date only estimates the week of 1st stable push of a release – it does not imply that all end points will be updated by this week.

[jasnell]

Yep, fine print understood. We definitely should try to get v5 in so let's
hope it doesn't slip.
On Mar 17, 2016 3:18 PM, "Ali Ijaz Sheikh" notifications@github.com wrote:

As the release page mentions, April 19th is the estimated target date.
Fine print:

These dates are subject to change without advance notice and provided here
only for rough planning purposes. New bugs, security incidents, holiday
schedules, partner dependencies and process changes can all affect these
dates and move it in either direction. The date only estimates the week of
1st stable push of a release – it does not imply that all end points will
be updated by this week.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#5766 (comment)

[MylesBorins]

@jasnell if their are RC releases for v5 of v8... would we not be able to cut an RC with that?

[bnoordhuis]

V8 doesn't have RCs, their development model is "it's unstable (API-wise) until the release branch is cut." I think it's fine to do a RC with a V8 development snapshot as long as we make it well-understood that there can be last-minute changes before the 6.0 GA.

BTW, I agree we should aim for V8 5.0.

[mhdawson]

V8 has dev, beta and stable. 5.0 is already in 'beta" so its better than "dev" but as @bnoordhuis mentions there could be last minute changes, although I think the likelihood on a API change is small, particularly as it gets close to the end of the beta period.

I'm + 1 on aiming for 5.0