Skip to content

Getting started instructions (versions) #1390

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

Closed
rubydesign opened this issue Jan 18, 2018 · 2 comments · Fixed by #1398
Closed

Getting started instructions (versions) #1390

rubydesign opened this issue Jan 18, 2018 · 2 comments · Fixed by #1398

Comments

@rubydesign
Copy link
Contributor

rubydesign commented Jan 18, 2018

Hi,
getting started is great in general, and it did just that.

The issue i would like to raise is about the versions. The script, and in fact all the links in that page, point to a latest version. And while that maybe seems good, it does have serious pitfalls. Which is why i feel it should not be encouraged.

Production apps can be extremely fiddly as to which versions actually work and which don't. Implicit update is setting oneself up for midnight calls and angry users.
What if 2.6 comes out. Or 3.0. And (small or large) incompatible changes break the app.

So the suggestion is to put explicit version numbers into the download links. Get people started off on the right foot.

@chrisvfritz
Copy link
Contributor

That sounds good to me. 🙂 A PR would be welcome to update the pre-deploy.js script to keep each CDN link up-to-date.

@rubydesign
Copy link
Contributor Author

fair enough, i dug that hole, so there it is

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants