In bug 771763, Jake mentioned that... > In either case, there are some settings that will need to be updated... > various things (Kumascript, at least) point at "developer-new.mozilla.org". > This should be part of the the checklist in #1. We will need to prepare for this, at least making a list of all things pointing to developer-new and getting an understanding of how difficult each change would be. Once we have a list, we can add it to our launch checklist (https://etherpad.mozilla.org/kuma-launch-checklist) to be done right before we launch.
This is stated backwards... we need to find everything that *currently* points to developer-new, and re-point it at just developer.mozilla.org. The -new moniker is just temporary. Here's what I know of that currently refers directly to developer-new.m.o: MEDIA_URL in settings_local.py SITE_URL in settings_local.py (for BrowserID) DOMAIN in settings_local.py (for BrowserID) DEFAULT_AVATAR in settings_local.py document_url_template in kumascript_settings_local.json template_url_template in kumascript_settings_local.json The Apache config looks to be okay. There's a separate bug to implement a redirect from developer-new.m.o to developer.m.o after launch, so that doesn't need handled here.
I agree with jake: http://pastebin.mozilla.org/1729975
Was going to mention that all we really need is a grep. Saw that Luke already did that in comment 2. Carry on then... If we know that these are the only references, I'm happy to call this bug closed and open launch checklist items reminding ourselves to change them.
These references were changed, and no other references have been found. Kuma launched, so far nothing obviously broken. Closing this.