User talk:Dmose:Tb3 Driving Scratchpad

From MozillaWiki
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
  • get stuff possibly not tracked or not completely split out into bugzilla (please add [b3ux] to whiteboard of appropriate bugs so we can schedule for early landings)
    • autoconfig (bienvenu)
    • theming (clarkbw)
    • fallout from faceted search in tabs (clarkbw/asuth)
    • misc message reader stuff -- from irc discussion + collapsed header (dmose)
    • pop-tarts (davida/Standard8)
    • super-statusbar (davida/Standard8)
    • multiple selection using message pane (davida)
    • smart mailboxes (bienvenu)
  • remaining triage (please add [b3ux] whiteboard annotation, as above)
    • find std8 driving substitute for next 2 weeks (davida)
    • blocking+ four front-end components (dmose/clarkbw)
    • existing message reading bugs (dmose)
    • blocking3? across components (all drivers)
  • management (davida/dmose/clarkbw/drivers)
    • propose security review plan
    • look at distribution of bugs across b3 and rc1 (keeping in mind that NEW really means unowned)
    • include a fudge factor for stuff we don't know about yet
    • does everything fit into b3/rc1?
      • if so, set dates, including comm-central branch date and approval-only date
      • if not, figure out what we can cut or add a milestone
  • communications
    • update [Thunderbird:Thunderbird3:DevRoadmap] -- probably means moving most or all current content to some post-tb3 grabbag page (davida)
    • should this page just replace most of the content on Thunderbird:Thunderbird3?
  • driving 3.0b3
    • hold 3.0b2 post-mortem (clarkbw)
    • update 3.0b3 with overall dates (dmose)
    • set weekly milestone schedule for work that needs to land in b3 (dmose)
  • Localization
    • Need a decision on when we're going to freeze strings for the final release
    • Suggestion: Either together with beta3 or 1-2 weeks after beta3 to give localizers some time to correct obvious errors/mistakes