Skip to content
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

Nightly builds on download page #510

Closed
silverwind opened this issue Feb 9, 2016 · 9 comments
Closed

Nightly builds on download page #510

silverwind opened this issue Feb 9, 2016 · 9 comments

Comments

@silverwind
Copy link
Contributor

Nightly builds are very hard to find right now and not even reachable through directory navigation from nodejs.org/dist. Can we agree to feature them more prominently on the downloads page, maybe in a small paragraph below the table?

@fhemberger
Copy link
Contributor

Good catch, let's do this. 👍

@rvagg
Copy link
Member

rvagg commented Feb 9, 2016

We'll have a new line that can go with this too soon, name uncertain but it'll be master on perhaps a weekly schedule with slightly less scary version strings than nightlies nodejs/node#4856

@silverwind
Copy link
Contributor Author

Oh, and we probably should mention that semver issue with npm warning because of the version string not matching.

@rvagg would you recommend linking to the current nightlies, or should we wait?

@rvagg
Copy link
Member

rvagg commented Feb 9, 2016

I think they did something about the semver warning in a recent 3.x didn't they? They should be pretty nice to use now.

@silverwind no point waiting, just keep in mind that we'll want to make room for another kind of download. It's unclear whether nightly should be off stable or master or both when we have this new channel. Currently nightlies are turned on for both, so you can get v5 and v6 from there.

@silverwind
Copy link
Contributor Author

The version issue still persists with the npm provided in the package:

npm WARN engine [email protected]: wanted: {"node":">=0.10"} (current: {"node":"6.0.0-nightly20160127fcae05e4b5","npm":"3.3.12"})
npm WARN engine [email protected]: wanted: {"node":">=0.4.7"} (current: {"node":"6.0.0-nightly20160127fcae05e4b5","npm":"3.3.12"})
npm WARN engine [email protected]: wanted: {"node":">=0.12"} (current: {"node":"6.0.0-nightly20160127fcae05e4b5","npm":"3.3.12"})

@rvagg
Copy link
Member

rvagg commented Feb 9, 2016

https://github.com/npm/npm/blob/master/CHANGELOG.md#better-node-pre-release-support

looks like it's in 3.6.0, which queued up in core waiting to be unblocked by some graceful-fs drama before it can land but will be in both v5 and v6 nightlies very soon

@silverwind
Copy link
Contributor Author

Ah, nice to hear. I'd say we defer linking until then, so we don't have to deal with this headache.

@Knighton910
Copy link
Contributor

👍 @silverwind I'd be nice to have on the downloads page.

justsml added a commit to justsml/nodejs.org that referenced this issue Mar 8, 2016
stevemao added a commit that referenced this issue Mar 8, 2016
@stevemao
Copy link
Contributor

stevemao commented Mar 8, 2016

Fixed by #559

@stevemao stevemao closed this as completed Mar 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants