Thanks for the quick feedback on this, we appreciate your responsiveness.
toggle quoted messageShow quoted text
We'll continue to follow the issue in the pivotal tracker.
On Wed, Sep 9, 2015 at 12:36 PM, Mike Dalessio <mdalessio(a)pivotal.io> wrote:
Great question, thanks for asking it.
The Buildpacks team has a Tracker story in its backlog to work on Node 4:
Generally our turnaround time on vanilla version updates is less than a
day; however, Node 4 isn't just a regular version update, as it comes from
io.js lineage which we haven't ever officially supported; and so we're
going to proceed carefully.
The story I linked to has some specific acceptance criteria:
* Does the binary build with our current tooling? If not, we'll have to
update our tooling.
* Does the binary dynamically link openssl? (This was a specific use case
we've had to work around in the past.) If not, we'll have to make sure it
does, so that rootfs updates will be sufficient to address openssl CVEs.
* Does the binary avoid statically linking any other rootfs libraries? If
not, see above.
* Does the binary pass BRATs? If not, we'll have to fix BRATs.
Only when all of the above look good will we ship; and since we haven't
worked with io.js and family before, I don't want to make any promises
about delivery. If things go well, it could ship as early as tomorrow,
though that's probably overly optimistic.
Additionally I'll likely delay committing it into cf-release until we have
positive feedback from the community.
I'm happy to keep this thread updated with our progress; or you can follow
along at the Tracker story.
On Wed, Sep 9, 2015 at 11:33 AM, Shawn Nielsen <sknielse(a)gmail.com> wrote:
NodeJS version 4 was released yesterday to the community.
Generally speaking, what is the typical release schedule for buildpack
binaries after new runtime releases are announced?
More specifically, I'd be curious if you have information on release
schedule of the NodeJS 4 buildpack binaries.