618189 - Update feedback server URL to input.mozilla.org

Status: NEW

(Firefox :: General, defect)

Description

[Reed Loden [:reed]]

The URL for the feedback server is changing in bug 618157 from input.mozilla.com to input.mozilla.org. Need to update Firefox to use the new hostname.

Comment 1

[Dave Dash [:davedash, :dd] (assign all bugs to mbrandt)]

This shouldn't have any blockers as we redirect i.m.o to i.m.c and as soon as this is in product we can flip the switch to minimize redirects.

Comment 2

[Aakash Desai [:aakashd]]

Attachment: patch for URL changes

We're moving Input to only be hosted under .org. The URL's are all re-directing properly to .com for now. They'll eventually just take it over.

Comment 3

[Aakash Desai [:aakashd]]

Attachment: patch for URL changes (now includes testpilot changes)

Just talked to Jono and learned that I should submit the patch to mozilla-central rather than testpilot's repo. These are just URL changes with some code cruft clean-up.

Comment 4

[Mark Finkle (:mfinkle) (use needinfo?)]

Comment on attachment 565564 [details] [diff] [review]
patch for URL changes (now includes testpilot changes)

Mobile parts look fine

Asking Gavin for the Desktop review

Comment 5

[:Gavin Sharp [email: [e-mail]]]

Comment on attachment 565564 [details] [diff] [review]
patch for URL changes (now includes testpilot changes)

This is going to wait until bug 618157 is fixed, presumably? input.mozilla.org currently redirects to input.mozilla.com.

Comment 6

[Aakash Desai [:aakashd]]

It doesn't need to. The client side needs to be fixed from IT's perspective before  moving completely over to .org. They don't want to have to deal with .com re-directs to .org.

Comment 7

[:Gavin Sharp [email: [e-mail]]]

Er, that seems like it will break a lot of links. Why is maintaining redirects difficult? Aren't they already in place?

Comment 8

[Dave Dash [:davedash, :dd] (assign all bugs to mbrandt)]

I don't think the order matters as long as this happens quickly.

I agree with Gavin that we will need to maintain redirects.

Comment 9

[Aakash Desai [:aakashd]]

(In reply to Gavin Sharp (use [e-mail] for email) from comment #7)
> Er, that seems like it will break a lot of links. Why is maintaining
> redirects difficult? Aren't they already in place?

This patch isn't going to break any links from the client over to the webapp. This patch might complicate things in the short-term, but its not going to bring out any major new issues other than a slight speed hit as users will need to go thru a re-direct first. 


We can wait for IT to make the flip first, if you want to wait on that. Though, I'd note that the speed hit would stay on the client longer because the patch would have to propagate through for 3 consecutive release cycles before getting to all our users.

Comment 10

[:Gavin Sharp [email: [e-mail]]]

I'm not really concerned about the time that it takes to land vs. actually ship the product changes - we can rely on the redirects for however long that is (the redirects will be in place forever anyways). I just want to actually make both changes at approximately the same time so that we're sure they both stick (or not) together, long-term.

Comment 11

[Shyam Mani [:fox2mike]]

FWIW, IT has switched over the domain from input.mozilla.com to input.mozilla.org

Comment 12

[Aakash Desai [:aakashd]]

Is this patch waiting on anything anymore?

Comment 13

[BugBot [:suhaib / :marco/ :calixte]]

The bug assignee didn't login in Bugzilla in the last 7 months, so the assignee is being reset.