-
Notifications
You must be signed in to change notification settings - Fork 136
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
Looking for feedback on changing the default URL to install the latest Node.js version #48
Comments
I'd say the latest stable is still v4.. But thats probably is not the answer you want to hear. The reason why
So, I think |
So, basically the answer provided by semver.io reflects Heroku's opinion, "based on experience with customer apps running on the platform" - whatever that means (?!). I'm runnings apps on Heroku for a couple of customers, one is still running on v4, the other is on v6. They're both "stable" in my opinion.
Hmmm. There's no right or wrong answer, I know, but in the end, which one should we default to for this cartridge?... Should we switch to unstable? Personally, I'm leaning towards it, since the cartridge name itself implies you'll be getting the latest (while you'll still be able to expressly lock to a specific version, of course). I'll still be waiting for user feedback for a few more days before switching. |
+1 for using latest = version 6 |
I'm not sure why, but semver.io is constantly lagging behind on correctly reporting the latest Node.js version.
As of June 21st 2016, semver.io/node/stable still says
5.1.11
, while in reality we're at6.2.2
, which I'd say is stable enough.Therefore, I'm considering to switch the default semver URL to semver.io/node/resolve/6, which correctly reports
6.2.2
, but I'll wait a couple of days for user feedback before proceeding.Please note that you'll still be able to use
5.1.11
, or generally lock your application to a specific version by expressly setting theNODE_VERSION_URL
to something likehttps://semver.io/node/resolve/5.1.11
.The text was updated successfully, but these errors were encountered: