Skip to content

Change references to bugs.jquery.com to GitHub issues #1681

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.

Sign up for GitHub

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

Jump to bottom
Closed
mgol opened this issue Oct 6, 2014 · 10 comments
Closed

Change references to bugs.jquery.com to GitHub issues #1681

mgol opened this issue Oct 6, 2014 · 10 comments
Assignees
@mgol
Labels
Bug

Comments

@mgol
Copy link
Member

mgol commented Oct 6, 2014

There are at least references in CONTRIBUTING.md and in package.json (thx arthurvr!) but there may be more.

jquery.com & friends will need to be updated as well.
@mgol mgol added the Bug label Oct 6, 2014
@mgol mgol added this to the 1.12.0/2.2.0 milestone Oct 6, 2014
@mgol mgol self-assigned this Oct 6, 2014
@scottgonzalez
Copy link
Member

Created jquery/contribute.jquery.org#90, if you know of any other sites with links, we should make sure they're tracked as well.

@scottgonzalez
Copy link
Member

Created jquery/jquery.com#81.

@arthurvr arthurvr mentioned this issue Oct 9, 2014
Closed
@arthurvr
Copy link
Member

arthurvr commented Oct 9, 2014

Created jquery/api.jquery.com#571

@arthurvr
Copy link
Member

How are you guys going to handle release-notes.js?

@dmethvin
Copy link
Member

@arthurvr That script is replaced by the logic in jquery-release. The format will be a bit cleaner and consistent now because we're using CommitPlease for commit messages.

I also notice we have a reference to bugs on the npm page but there's no harm in leaving it. The bugs.jquery.com page is supposed to help people self-triage their issue and reduce the number of spurious tickets we handle in core. If that page is unclear we should work on fixing that.

@arthurvr
Copy link
Member

@dmethvin Correct.

I think all the references in other repos are removed now, so do I open a PR in jquery/jquery too? According to github search there aren't any other references to bugs.jquery.com.

@arthurvr arthurvr mentioned this issue Oct 17, 2014
Closed
@mgol mgol closed this as completed in 3e89a53 Oct 19, 2014
mgol pushed a commit that referenced this issue Oct 19, 2014
@arthurvr @mgol
Misc: Update all references to bugs.jquery.com
49c720e 
(cherry-picked from 3e89a53)

Fixes gh-1681
Closes gh-1716
@mgol
Copy link
Member Author

mgol commented Oct 19, 2014

Landed, thanks! I had to modify the commit message a little, please look at 3e89a53.

mescoda pushed a commit to mescoda/jquery that referenced this issue Nov 4, 2014
@arthurvr @mgol
Misc: Update all references to bugs.jquery.com
8a733ac 
(cherry-picked from 3e89a53)

Fixes jquerygh-1681
Closes jquerygh-1716
@arthurvr
Copy link
Member

arthurvr commented Dec 6, 2014

Little extra thing regarding this: the topic on the jquery-dev IRC channel must be changed.

@dmethvin
Copy link
Member

dmethvin commented Dec 6, 2014

Thanks, changed!

@arthurvr
Copy link
Member

arthurvr commented Dec 6, 2014

Thanks @dmethvin!

markelog pushed a commit that referenced this issue Nov 10, 2015
@arthurvr @markelog
Misc: Update all references to bugs.jquery.com
029be03 
Fixes gh-1681
Closes gh-1716
@dmethvin dmethvin removed this from the 3.0.0 milestone Jan 7, 2016
@cssmagic cssmagic mentioned this issue May 18, 2016
Open
@lock lock bot locked as resolved and limited conversation to collaborators Jun 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@mgol mgol

Labels
Bug
Milestone
No milestone
Development

No branches or pull requests
4 participants
@scottgonzalez @dmethvin @mgol @arthurvr