fix(README): point to v1.4.0 release urls

[thgreasi]

No description provided.

[mention-bot]

By analyzing the blame information on this pull request, we identified @coliff, @scottgonzalez and @markelog to be potential reviewers

[jquerybot]

Thank you for your pull request. It looks like this may be your first contribution to a jQuery Foundation project, if so we need you to sign our Contributor License Agreement (CLA).

📝 Please visit http://contribute.jquery.org/CLA/ to sign.

After you signed, the PR is checked again automatically after a minute. If there's still an issue, please reply here to let us know.

---

If you've already signed our CLA, it's possible your git author information doesn't match your CLA signature (both your name and email have to match), for more information, check the status of your CLA check.

[coveralls]

Coverage remained the same at 89.655% when pulling 0f1fe01 on thgreasi:patch-1 into 89e461e on jquery:master.

[dmethvin]

This isn't the latest README on master. Take a look at that one. Is the information you need there?

[thgreasi]

I'm a bit puzzled by your answer.
I think that I'm targeting the README of the jquery:master branch which only includes references to v1.3.0.
Do you mean the file in the 1.x-stable branch (which I just realized that existed)?

So, I guess you can close this, if the master branch is only used for jquery v3.0 development...
On the other hand, others might get confused (like I did) when landing on the main page of the repo.

[dmethvin]

Oh okay I see what you mean. Those will be updated to the 3.0 branch as soon as the first 3.0 release is made, the build script does it. If you're looking for 1.x code then the link up top should point to the README for that branch, and it has accurate information for the 1.x branch since a release has already been run against it. I can land this for now though, but people looking for the 1.x code should not be reading further into the README here because it doesn't apply to the 1.x branch.

[dmethvin]

Landed at ee0a030

Thanks! Had you noticed the big link to 1.x before? I think this might become more of an issue when the first 3.0 release ships if a lot of people are looking for 1.x and get 3.x by accident, but I tried to make the link at the top as large as possible.

[thgreasi]

Interestingly enough I did notice the v3.0 header but it looks like my
brain just skipped that and searched for a cdn url. 👍

Thodoris Greasidis
Computer, Networking &
Communications Engineer