Closed Bug 554588 Opened 14 years ago Closed 13 years ago

Thunderbird 2.0.0.24 start page should be on mozillamessaging not mozilla.com

Categories

(www.mozilla.org Graveyard :: Thunderbird, defect)

defect
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: pascalc, Unassigned)

Details

Attachments

(1 file, 1 obsolete file)

in bug #553544 the 2.0.0.24 page was put on mozilla.com, it should be on mozillamessaging;com. The side effect is that people with non-english TB fallback to en-US since all these localized pages were migrated to mozillamessaging.com.

things to do:
1/ copy the 2.0.0.23 pages in new 2.0.0.24 folders on mozilla-messaging for all locales
2/ put them in production
3/ update the .htaccess on mozilla.com to add a redirect from moco to mome (last rule was for 2.0.0.23)
4/ remove the 2.0.0.24 TB start folder on mozilla.com

ideally, if there are future versions of 2.0.0.x, the start page url should be updated in the product with a url scheme similar to 3.0.x instead of pointing directly to mozilla.com

I will probably not have time to work on that this week so if somebody in mozillamessaging team can do that, that would be great.
Attached patch mozilla.com .htaccess patch (obsolete) — Splinter Review
Here is the rewrite patch for mozilla.com (step 3 or comment #0)
2.0.0.24 en-US start page copied to momo.com trunk in revision 64707.
Copied 2.0.0.23 l10n start pages to 2.0.0.24 on momo.com trunk in revision 64710.
all merged to momo stage in revision 64712.
(In reply to comment #0)
> [...]
> 
> ideally, if there are future versions of 2.0.0.x, the start page url should be
> updated in the product with a url scheme similar to 3.0.x instead of pointing
> directly to mozilla.com

Yeah, too bad we missed that for 2.0.0.24, but good to keep in mind. At least, we could provide moco with a set of redirect rules for, say, 2.0.0.2[4-9], so that we don't have to remember to add rewrite rules for each TB 2.0.0.x releases.
Who should we make the .htaccess patch reviewed by ?
Comment on attachment 434544 [details] [diff] [review]
mozilla.com .htaccess patch

>+RewriteRule ^(?:\w{2,3}(?:-\w{2}(?:-mac)?)?/)?thunderbird/2.0.0.24/start[/]?$ http://www.mozillamessaging.com/thunderbird/2.0.0.24/start/ [R=permanent]
>+RewriteRule ^(\w{2,3}(?:-\w{2}(?:-mac)?)?/)?thunderbird/2.0.0.24/releasenotes[/]?$ http://www.mozillamessaging.com/$1thunderbird/2.0.0.24/releasenotes/ [R=permanent]

This works, but I'd much rather see something such as:
RewriteRule ^(?:\w{2,3}(?:-\w{2}(?:-mac)?)?/)?thunderbird/2.0.0.(2\d)/start[/]?$ http://www.mozillamessaging.com/thunderbird/2.0.0.$1/start/ [R=permanent]
RewriteRule ^(\w{2,3}(?:-\w{2}(?:-mac)?)?/)?thunderbird/2.0.0.(2\d)/releasenotes[/]?$ http://www.mozillamessaging.com/$1thunderbird/2.0.0.$2/releasenotes/ [R=permanent]

That would future-proof it for all 2.0.0.20-29 builds and cut the rewrite rules down from 8 to 2. .19 seems to be a weird case (only redirecting for the release notes), so I left that rule alone. However, it would be easy to add it to one of the above rules so that it could be removed as well.
Attachment #434544 - Flags: review+
Reed, gozer is sleeping now shall I upload a new patch ? and could you check it in ?
(In reply to comment #4)
> all merged to momo stage in revision 64712.

I just backed out some revisions from that - changes to pages that we don't want to go live yet. See r64758 for details.
r64779 has pushed the start pages to production
Updated patch for .htaccess
Attachment #434858 - Flags: review+
Attachment #434544 - Attachment is obsolete: true
Summary: Thundebird 2.0.0.24 start page should be on mozillamessaging not mozilla.com → Thunderbird 2.0.0.24 start page should be on mozillamessaging not mozilla.com
patch applied on trunk in r64790
redirects working on trunk, merged to stage in r64792, waiting for stage to update to test it before pushing to production
works on stage, pushed to production in r64807, marking fixed
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
reopening, forgot about step 4 which is removing the tb 2.0.0.24 folder on mozilla.com, will do it later
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to comment #15)
> reopening, forgot about step 4 which is removing the tb 2.0.0.24 folder on
> mozilla.com, will do it later

Reminder ping for pascalc
Mark, there are many en-US/2.0.0.* folders on mozilla.com, could you check if they are all safe to remove now that there is a rewrite rule leading to mozillamessaging?
Status: REOPENED → RESOLVED
Closed: 14 years ago13 years ago
Resolution: --- → FIXED
Product: Websites → www.mozilla.org
Product: www.mozilla.org → www.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: