Marketing:Thunderbird Website

From MozillaWiki
Revision as of 12:43, 28 September 2009 by Rebron@gmail.com (talk | contribs)
Jump to navigation Jump to search

Tracking document for the release of Thunderbird/Thunderbird 3.0b4

Who

  • Overall lead: Standard8
  • Web pages lead: rebron
  • Release notes lead: rebron
  • Build lead: gozer
  • QA lead: _Tsk_
  • l10n lead: sipaq

What

Late l10n tracker

None.

General Planning

step start date end date status
planning meeting 2009-09-14 2009-09-14 Complete (only held blocker discussion)
Create Tracking Bugs - see below 2009-09-08 2009-09-14 Complete
Ensure in-tree extensions (Venkman, DOMi) have correct maxVersion numbers.
DOMI has general rs=sdwilsh for update to current version in trunk.
2009-09-14 2009-09-14 Complete
(DOMI 3.1a1pre, Venkman 3.0)
Heads up to QA testers 2009-09-14 2009-09-14 Complete

Tracking Bugs

Use New Beta Release Bug Creator to create the templates for the bugs.

Notes: Creation of Bouncer entries is assumed to be enough of a heads-up to MoCo IT of the pending release.

String & Code Freezes

For each step, ensure relevant Tinderboxes are updated with the current status.

step start date end date status
Slushy Code Freeze 2009-09-07 23:59 PDT 2009-09-14 02:00 PDT Complete
String Freeze 2009-09-09 23:59 PDT 2009-09-15 Complete
Final Code Freeze 2009-09-11 23:59 PDT (2009-09-14 02:00 PDT) 2009-09-15 Complete
L10n cut-off, shipped-locales & revisions closed off. 2009-09-14 23:59 PDT 2009-09-15 Complete
Send signoff to thunderbird-drivers for build to start 2009-09-15 2009-09-15 Complete

Build Revisions

Build

step start date est. duration end date status
Cut relbranch 2009-09-15 08:49 PDT - 2009-09-15 Completed
Candidates built (all locales), insert link below

Linux Windows (unsigned) Mac OS X

2009-09-15 23:30 PDT - 2009-09-15 Completed
Sign off to thunderbird-drivers for QA to start testing N/A - 2009-09-16 07:45 PDT Completed
Publish partial & full updates to betatest channel (fully-throttled so that QA can test throttling). 2009-09-17 - 2009-09-17 18:22 PDT Completed
Sign builds 2009-09-16 - 2009-09-16 19:30 PDT Completed
Sign off to thunderbird-drivers for signed builds N/A - 2009-09-17 18:22 PDT Completed

QA of Builds

step start date est. duration end date status
Check builds for crash symbols (crashme!) 2009-09-16
  10 min
2009-09-16
Completed
Verify correct branding of builds (checklist below) 2009-09-16
  10 min
2009-09-16
Completed
Announce Candidate builds ready for testing (newsgroups etc) 2009-09-16
  10 min
2009-09-16
Completed
QA tests Candidate builds (see QA Test Result Tracking bug) 2009-09-16
  7 days 2009-09-21
Completed
Partial update integrity check script run (typically by gozer) 2009-09-17 2009-09-17 Completed
QA spot checks updates on betatest channel 2009-09-18
- 2009-09-18
Completed

Branding Checklist

Note: where release version is referenced, this is only for alpha/beta builds. Final releases should not have it.

  • All Platforms
    • Check About dialog has correct image and name of application.
  • Windows
    • Check Window title has "... - <short name of brand> <release version>
    • Check Installer references brand and release version
    • Check executable has correct brand name in its properties
  • Linux
    • Check Window title has "... - <short name of brand> <release version>
  • Mac
    • Check Application bundle in .dmg has the brand name.

Website & Press

step start date est. duration end date status
Website changes on trunk 9/21/2009 - 9/21/2009 Completed
File Bug for setting up website redirects (live.momo.com start, what's new etc) 9/21/2009 - 9/21/2009 Completed
Website pushed to staging 9/22/2009 - 9/22/2009 Completed
Prepare announcement texts for mailing lists 09/22/2009 - 09/22/2009 Completed
QA tests website on staging (text, links etc) 9/22/2009 - 9/22/2009 Completed

Final Release Phase

step start date est. duration end date status
QA and release driver approve start of final release phase via thunderbird-drivers. 2009-09-22 - 2009-09-22 Complete
Build submits patch to mirrorstentry to MoCo IT 2009-09-22 - 2009-09-22 Completed
Build moves build to release area 2009-09-22 - 2009-09-22 Completed
Build pushes download files to mirrors (rsyncd-mozilla-current.exclude) 2009-09-22 - 2009-09-22 Completed
Wait for bouncer to pick up files 2009-09-22 1.5 hours for 25% 2009-09-22 Completed
Build pushes content from stage/ to production/ so that releasenotes, firstrun pages, early_releases, beta pages go live on mozillamessaging.com 2009-09-22 - 2009-09-22 Completed
QA download links and checks release notes, start page, what's new pages options from within TB - on en-US and non en-US locales. 2009-09-22 - 2009-09-22 Completed
Build pushes remaining content from stage/ to production/ 2009-09-22 - 2009-09-22 Completed
Build pushes update snippets to beta channel, fully-throttled so that it is only available for manual updates. 2009-09-22 - 2009-09-22 Completed
QA spot checks production site and updates on beta channel 2009-09-22 - 2009-09-22 Completed
Announce release (see locations below), and check the results 2009-09-22 - 2009-09-22 Completed

Release Announcements

Announce to:

  • mozilla.dev.apps.thunderbird
  • mozilla.dev.planning
  • mozilla.dev.l10n
  • mozilla.dev.apps.calendar
  • mozilla.support.thunderbird
  • mozilla.announce.prerelease (must be subscribed, see moderator info).
  • About:mozilla
  • Spread Thunderbird (poke #spreadthunderbird for getting post on the front page).
  • Blog

Post Release

step start date est. duration end date status
A couple of days after release, QA & Release Driver approve un-throttling of updates via thunderbird-drivers N/A - 2009-09-24 Completed
Build un-throttles updates. 2009-09-24 - 2009-09-24 Completed
Schedule and hold post-mortem meeting 2009-09-25 13:15 PDT 3/4 hour 2009-09-25 14:00 PDT Completed



This is the list to manage web site content in Thunderbird for our 51 lang/locales. The items to be localized include:

- download "landing" page and thank you page: all locales - product page: on a per locale basis depending on the amount of work they represent (localized graphics? amount of text, screen shots...) - start page: all locales - release notes - press release: same as sub-pages

We also need to check for account setup -- which email providers are included during account setup.

The start page must live on *.mozillamessaging.com. The ideal is support page and product pages all live on *.mozillamessaging.com. However, Community sites may point to support and product pages with the Thunderbird web site look and feel.

Feel free to add items to this list if you can think of something that would help things along.


Locale Priority Pages/URLs Bug(s) Completion
Afrikaans
Albanian
Arabic
Basque
Belarusian
Bengali (Bangladesh)
Bulgarian
Catalan
Chinese (Simplified) P1
Chinese (Traditional) P1
Czech
Danish
Dutch
English (British)
English (US) P1
Estonian
Finnish
French P1
Frisian
Galician
Georgian
German P1
Greek
Gujarati
Hebrew
Hungarian
Icelandic
Indonesian
Irish
Italian P2
Japanese P1
Korean P2
Lithuanian
Norwegian (Bokmal)
Norwegian (Nynorsk)
Polish
Portuguese (Brazil) P2
Portuguese (Portugal)
Punjabi
Romanian
Russian
Serbian
Sinhala
Slovak
Spanish (Argentina)
Spanish (Spain) P2
Swedish
Tamil (Sri Lanka)
Turkish
Ukrainian
Vietnamese

Note: time estimates are calculated in uninterrupted hour/days... Better use them for comparing relative effort.

          • Notes****

Localization of the site depends on several factors:

1/ possibility to communicate to localizers via the webdashboard, mozillamessaging is now a separate project there so no problem

2/ locale detection and general locale support on mozillamessaging, we have added the minimum requirements for that with the 2.0.0.21 release and the move of the localized start pages from mozilla.com to mozillamessaging, minor releases now happen on mozillamessaging for locales

3/ simplified templates (header/footer) for locales, to be done but shouldn't take me much time, a day to make and test them

4/ creation of TB3 content for localizers, this is highly dependent on the creation of en-US content that will be used as a basis for translation, essentially:

   - new start page
   - landing page for all locales that serves as a home page as we do on mozilla.com
   - minimum set of pages (essentially features pages) for top locales which will have a more complete set of pages

5/ creation of a simplified landing sub page on mozilla-europe to also propose downloads there

6/ some administrative work as I have to open bugs for all localizers to give them access to mozillamessaging repo

7/ QA