Closed Bug 598783 Opened 15 years ago Closed 15 years ago

Fix link to "Firefox 4 for developers" from MDN main page HTML5 slide

Categories

(developer.mozilla.org Graveyard :: Wiki pages, defect)

defect
Not set
blocker

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: jswisher, Assigned: wenzel)

References

()

Details

On the main page of developer.mozilla.org, there is a link to https://developer.mozilla.org/Firefox_4_for_developers (in <li id="slide-two">). That page does not exist, and redirects the user back to the main page (thanks to MindTouch). This link needs to either: * Be hard-linked to https://developer.mozilla.org/en/Firefox_4_for_developers ; or * Resolve to the correct language page based on the user's settings.
See Also: → 595279, 588360, 583803, 591094
Fred: Can you help get this fixed ASAP? What is the process for getting a quick typo/link fix on stage and pushed to production after QA verification?
Assignee: nobody → fwenzel
Severity: major → blocker
Sorry this bug might have slipped under my radar somehow. I am fixing it now. (In reply to comment #1) > What is the process for getting a > quick typo/link fix on stage and pushed to production after QA verification? CCing fox2mike: How about we just repurpose our Input "push to prod" script for MDN? The process should be the same (including a locale/ submodule, soon). If that works for you, I could make a prod branch and tag stuff accordingly. That'd allow us to cherry-pick such minor fixes in between releases too. What do you think?
This is fixed in http://github.com/fwenzel/mdn/commit/eb388c3 . Should show up on staging shortly. Keeping this open until we find a way to push such changes to prod properly w/IT.
Status: NEW → ASSIGNED
Target Milestone: --- → 0.9.1
I made a prod branch like we have for input. Next time we push an update, we should just switch to the prod branch, that'll keep development on master separate from what's deployed, and allows us to cherry-pick commits into prod when necessary. Jay: If you want this fix pushed out, I'll file an IT bug to do the switch to the prod branch now (where we'll cherry-pick just this one fix for now), otherwise we can wait until 0.9.1 goes out. (Also CCing ozten for his information)
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Let's test out this process by having IT push this one cherry-picked fix to production. I want to make sure it works before we get 0.9.1 out... which I think is still a couple of weeks away.
Depends on: 604358
v.fixed. link works now... glad the push went smoothly.
Status: RESOLVED → VERIFIED
Version: MDN → unspecified
Component: Website → Landing pages
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.