Closed
Bug 429355
Opened 16 years ago
Closed 16 years ago
Revert static page redirect of Firefox 3 in-product help and point to SUMO again
Categories
(support.mozilla.org :: General, defect)
support.mozilla.org
General
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: djst, Assigned: laura)
References
Details
(Whiteboard: [server side] sumo_only)
Attachments
(1 file, 1 obsolete file)
8.30 KB,
patch
|
nkoth
:
review+
|
Details | Diff | Splinter Review |
After irc discussion with oremj and laura, it looks like we should be able to try pointing firefox3 help links back to SUMO again. This would effectively revert the patch submitted in bug 425372. If it turns out this doesn't work, we'll have to back this out again. justin: approval?
Assignee | ||
Comment 1•16 years ago
|
||
We need to push first, to r12331. Will file a separate bug for that.
Reporter | ||
Comment 2•16 years ago
|
||
Added the dependency. Is there anything else that's pending?
Depends on: 429429
Assignee | ||
Comment 3•16 years ago
|
||
I've asked oremj to load test trunk to see exactly where we stand right now, it's in https://bugzilla.mozilla.org/show_bug.cgi?id=429355. That will help IT to make the call. We'll continue to make improvements, the question is whether we have already done enough to get started with SUMO under a real load or not.
Assignee | ||
Comment 4•16 years ago
|
||
Sorry, that would be https://bugzilla.mozilla.org/show_bug.cgi?id=427573 (cut and paste error)
Comment 5•16 years ago
|
||
Unfortunately, we can't flag sumo bugs as blocking Firefox 3, but I would assume this is a blocker.
Severity: normal → blocker
Comment 6•16 years ago
|
||
Is there any update on this?
Comment 7•16 years ago
|
||
We talked about reverting the redirect on Monday and want to flip it back to support.mozilla.com. Morgamic, do we still want to flip it?
Comment 8•16 years ago
|
||
sam/marcia, can sumo bugs also get fx3 blocking flags? readiness of the support site ought to be on the final evaluation to pull the trigger on the release switch.
Reporter | ||
Comment 9•16 years ago
|
||
After discussing with Laura (who in turned discussed with morgamic and IT), the two blockers for this is bug 395271 and bug 433341. Hopefully those will be fixed by the end of this week, but a likely target for resolving this bug is Wednesday, May 21st.
Comment 10•16 years ago
|
||
I think the real blocker here is to get performance to an acceptable level. Last time we talked performance needed a 50x (or something very high) level improvement to even be on par with other apps. Are we sure the two blocking bugs will increase performance that much?
Comment 11•16 years ago
|
||
Right now SUMO is doing about 14 - 17 req/s on the load testing cluster. Let's see how these two bugs improve that number. Right now we are mostly concerned with the number of queries per second. We are seeing about 600 q/s on the production instance. bug 433341 will definitely add some scalability in that area and hopefully bug 395271 will decrease the number of queries substantially.
Reporter | ||
Comment 12•16 years ago
|
||
Moving to Firefox because this blocks the release.
Component: General → Help Documentation
Product: Sumo → Firefox
QA Contact: general → help.documentation
Target Milestone: --- → Firefox 3
Version: unspecified → 3.0 Branch
Reporter | ||
Updated•16 years ago
|
Flags: blocking-firefox3?
Updated•16 years ago
|
Component: Help Documentation → General
Product: Firefox → Sumo
QA Contact: help.documentation → general
Target Milestone: Firefox 3 → ---
Version: 3.0 Branch → unspecified
Comment 13•16 years ago
|
||
And back to the Firefox product, as the SUMO product doesn't show up in the triage queries.
Component: General → Help Documentation
Product: Sumo → Firefox
Target Milestone: --- → Firefox 3
Version: unspecified → 3.0 Branch
Comment 14•16 years ago
|
||
If that's true, then their queries are wrong and should be fixed to look for anything with the blocking-firefox3 flag.
Comment 15•16 years ago
|
||
Confirmed with beltzner that drivers are looking at all bugs with the blocking-firefox3 flag.
Component: Help Documentation → General
Product: Firefox → Sumo
Target Milestone: Firefox 3 → ---
Version: 3.0 Branch → unspecified
Comment 16•16 years ago
|
||
Well, we damned sure can't ship with what we have right now. Hit F1 and tell me if you think that's good enough :)
Flags: blocking-firefox3? → blocking-firefox3+
Updated•16 years ago
|
Whiteboard: [server side]
Comment 17•16 years ago
|
||
Any progress on this? David -- this is in your hands.
Assignee: nobody → djst
Comment 18•16 years ago
|
||
Laura? Any updates? We need to get this out ASAP.
Comment 19•16 years ago
|
||
re: comment 17 I think djst is OOO between Thursday May 29th and Saturday June 7th. I think its morgamic/laura, right?
Assignee | ||
Comment 20•16 years ago
|
||
In discussion with justin/oremj as to whether the dependency on 433341 is actually required. We should be able to go ahead without it IMO. Waiting on comment from oremj.
Comment 21•16 years ago
|
||
I'd like to get at least get the page count updates and inserts removed before we do this. Would that be possible? If Bug 433341 were done even better.
Assignee | ||
Comment 22•16 years ago
|
||
Yes, we can do that.
Comment 23•16 years ago
|
||
Jeremy's suggestion in comment #21 is now in production branch r14709. Also, session update/cleanup in db only occurs with logged in users.
Assignee | ||
Comment 24•16 years ago
|
||
Ok, the suggestion from comment #21 was pushed in bug 436911. Can we try reverting now? If not, the patch for bug 433341 is under review, so that shouldn't block it for long either.
Assignee | ||
Comment 25•16 years ago
|
||
Justin, oremj can we move on this?
Reporter | ||
Comment 26•16 years ago
|
||
It sounds to me that we're ready to do this now. I think it would be helpful to do this for a couple of reasons: * It's probably better at this point to try and fail, rather than waiting for something we _think_ is good, and then realize one day before the release it wasn't good enough * Localizers would benefit a lot from actually seeing the end result of their translations and figuring out any quirks there. Justin, thoughts?
Comment 27•16 years ago
|
||
if the read only patch is in, we should give it a go.
Comment 28•16 years ago
|
||
I assume you don't want the locales in the help-topic URIs. Also, last time we didn't use inproduct mode in the URIs. So the new ones should be: pageinfo_general http://support.mozilla.com/kb/Page+Info+window?style_mode=inproduct prefs-main http://support.mozilla.com/kb/Options+window#main_options?style_mode=inproduct prefs-clear-private-data http://support.mozilla.com/kb/Options+window#private_data?style_mode=inproduct prefs-fonts-and-colors http://support.mozilla.com/kb/Options+window#fonts_and_colors?style_mode=inproduct prefs-privacy http://support.mozilla.com/kb/Options+window#privacy_options?style_mode=inproduct prefs-applications http://support.mozilla.com/kb/Options+window#applications_options?style_mode=inproduct prefs-connection-settings http://support.mozilla.com/kb/Options+window#connection_settings?style_mode=inproduct prefs-tabs http://support.mozilla.com/kb/Options+window#tabs_options?style_mode=inproduct prefs-advanced-javascript http://support.mozilla.com/kb/Options+window#advanced_javascript?style_mode=inproduct prefs-languages http://support.mozilla.com/kb/Options+window#languages?style_mode=inproduct prefs-content http://support.mozilla.com/kb/Options+window#content_options?style_mode=inproduct prefs-security http://support.mozilla.com/kb/Options+window#security_options?style_mode=inproduct prefs-advanced-general http://support.mozilla.com/kb/Options+window#advanced_general?style_mode=inproduct prefs-advanced-network http://support.mozilla.com/kb/Options+window#advanced_network?style_mode=inproduct prefs-advanced-update http://support.mozilla.com/kb/Options+window#advanced_update?style_mode=inproduct prefs-advanced-encryption http://support.mozilla.com/kb/Options+window#advanced_encryption?style_mode=inproduct
Comment 29•16 years ago
|
||
Chris, these urls are coming out of Firefox 3 product. Are you telling beltzner we need an RC4 to change this?
Comment 30•16 years ago
|
||
Are these in the Firefox code? I thought the code used something like http://support.mozilla.com/1/firefox/3.0/mac/en-US/prefs-main.
Comment 31•16 years ago
|
||
Oh, sorry, right. Regarding the locale code, why not have it in there? Because we're not able to set it anyway? Same question goes for platform.
Comment 32•16 years ago
|
||
These should be http://support.mozilla.com/<locale>/kb/Page+Info+window?style_mode=inproduct and so on.... (the locale should be in there) (In reply to comment #28) > I assume you don't want the locales in the help-topic URIs. > > Also, last time we didn't use inproduct mode in the URIs. So the new ones > should be: > > pageinfo_general > http://support.mozilla.com/kb/Page+Info+window?style_mode=inproduct > > prefs-main > http://support.mozilla.com/kb/Options+window#main_options?style_mode=inproduct > > prefs-clear-private-data > http://support.mozilla.com/kb/Options+window#private_data?style_mode=inproduct > > prefs-fonts-and-colors > http://support.mozilla.com/kb/Options+window#fonts_and_colors?style_mode=inproduct > > prefs-privacy > http://support.mozilla.com/kb/Options+window#privacy_options?style_mode=inproduct > > prefs-applications > http://support.mozilla.com/kb/Options+window#applications_options?style_mode=inproduct > > prefs-connection-settings > http://support.mozilla.com/kb/Options+window#connection_settings?style_mode=inproduct > > prefs-tabs > http://support.mozilla.com/kb/Options+window#tabs_options?style_mode=inproduct > > prefs-advanced-javascript > http://support.mozilla.com/kb/Options+window#advanced_javascript?style_mode=inproduct > > prefs-languages > http://support.mozilla.com/kb/Options+window#languages?style_mode=inproduct > > prefs-content > http://support.mozilla.com/kb/Options+window#content_options?style_mode=inproduct > > prefs-security > http://support.mozilla.com/kb/Options+window#security_options?style_mode=inproduct > > prefs-advanced-general > http://support.mozilla.com/kb/Options+window#advanced_general?style_mode=inproduct > > prefs-advanced-network > http://support.mozilla.com/kb/Options+window#advanced_network?style_mode=inproduct > > prefs-advanced-update > http://support.mozilla.com/kb/Options+window#advanced_update?style_mode=inproduct > > prefs-advanced-encryption > http://support.mozilla.com/kb/Options+window#advanced_encryption?style_mode=inproduct >
Comment 33•16 years ago
|
||
Please, note that es-ES and es-AR have the same SUMO site: "es", so it should be redirected both to "es".
Reporter | ||
Comment 34•16 years ago
|
||
Yes, we should add style_mode=inproduct to the .htaccess rewrite rules. However, it's fine to be without it for now, as the main purpose of backing out the static page is to test performance. laura, if it's not a big deal to add the parameter to the rewrite rules, could you please do it before checking in the change?
Assignee: djst → laura
Comment 35•16 years ago
|
||
I see the master-slave patch was committed. How soon can we deploy that?
Reporter | ||
Comment 36•16 years ago
|
||
Upon further investigation, the previous rewrite rules before patch https://bugzilla.mozilla.org/attachment.cgi?id=312004 in bug 425372 was checked in were already using style_mode=inproduct, so fixing this should be as simple as backing out that patch.
Assignee | ||
Comment 37•16 years ago
|
||
Should be fine, I'd just like one other person to test this.
Attachment #324849 -
Flags: review?(nelson)
Assignee | ||
Comment 38•16 years ago
|
||
Attachment #324849 -
Attachment is obsolete: true
Attachment #324859 -
Flags: review?(nelson)
Attachment #324849 -
Flags: review?(nelson)
Updated•16 years ago
|
Attachment #324859 -
Flags: review?(nelson) → review+
Assignee | ||
Comment 39•16 years ago
|
||
Committed patch in r15402 (trunk), r15403 (production), r15417 (1.1)
Assignee | ||
Updated•16 years ago
|
Assignee | ||
Comment 40•16 years ago
|
||
Push requested in https://bugzilla.mozilla.org/show_bug.cgi?id=438947.
Comment 41•16 years ago
|
||
Works fine, but we need a couple more redirects for Page Info. Pressing F1 in Page Info-> Media/Permissions/Security results in 404 pages: "The requested URL /1/firefox/3.0pre/WINNT/en-US/pageinfo_media/ was not found on this server." "The requested URL /1/firefox/3.0pre/WINNT/en-US/pageinfo_feed/ was not found on this server." (Page Info->Feeds is only displayed on pages with RSS feeds like http://www.mozilla.org/) "The requested URL /1/firefox/3.0pre/WINNT/en-US/pageinfo_permissions/ was not found on this server." "The requested URL /1/firefox/3.0pre/WINNT/en-US/pageinfo_security/ was not found on this server." They should link on the respective #Media, #Feeds, #Permissions, #Security anchor of http://support.mozilla.com/en-US/kb/Page+Info+window?style_mode=inproduct. And pageinfo_general should link to the #General anchor.
Keywords: push-needed
Comment 42•16 years ago
|
||
Filed bug 439030 on the missing redirects. VERIFIED per local behaviour here from Berlin.
Status: RESOLVED → VERIFIED
Reporter | ||
Updated•15 years ago
|
Whiteboard: [server side] → [server side] sumo_only
You need to log in
before you can comment on or make changes to this bug.
Description
•