Mobile/Planning/2.0

Objectives

The main focus of Fennec 2.0 is on the platform side of things, focusing on Electrolysis and Layers and on Android integration. We'll continue to make front-end improvements that reflect a shift to more devices with broader capabilities.

Timeline

Important milestones (subject to change):

Alpha 1

• Shipped on August 27, 2010

Beta 1

• Shipped on October 7, 2010

Beta 2

• Shipped on November 4th, 2010
• Code freeze: Oct 19
• Major Requirements:
  • bug 596755 Re-enable YARR on ARM
  • bug 605415 Re-enable MonoICs on ARM
  • Page load improvements
  • bug 588607 Android size
  • bug 575403 New theme
  • bug 600103 Fonts don't look like crap
  • Software video (reach?)
    • libvpx neon optimizations
    • bug 511348 libtremor integration

Beta 3

• Shipped on December 22, 2010
• Code freeze: Nov 23
• Major Requirements:
  • Easy Sync setup
  • Crash reporting
  • bug 588021 PICs

Beta 4

Top Goals: Performance, Stability, Compatibility, Usability; Major Requirements:bug 598864 GL

• Jan 14: resolve all major Beta 4 blockers: 2.0b4+ bugs - open GL bugs - Places bugs
  
• Jan 20: code freeze (incorporate Places and sync changes; Open GL bugs if possible)
  --> waiting for Places fixes to land
  
• NEW: Wed, Jan 26: “go to build” B4 builds?
  
• Mon, Jan 31: expected launch date (Beta 4 goes to Android Market)

Beta 5

Top Goal: Launch Places changes

• Feb 8 - Code Freeze
  
• Feb 10 - Go to build
  
• Feb 15

RC 1

Top Goal: RC “as close as possible to final release”

• Feb 24: Code Freeze
• Feb 28: “go to build” RC1
• Mar 8: Launch, review RC user feedback

Call RC1 “final”

• Mar 15: Analyze RC feedback, make go/no-go decision
• Mar 21: Launch! Review user Feedback
  

RC 2 (if required)

Top Goal: RC “as close as possible to final release”

• Mar 3: Code Freeze
  
• Mar 17: Launch
  
• Mar 21: Review user Feedback

Projects

List of projects for Fennec 2.0

Front-end:

Description	Priority	Status	Details	Strings
Multitouch	P1	LANDED	details	yes
Virtual keyboard	P1	INFLIGHT	details	no
Sync integration	P1	LANDED	details	yes
Logging in to websites easier (need to be more specific)	P3	RUNWAY		yes
Contacts integration	P2	LANDED	details	no
Start page redesign
AwesomeScreen redesign	P1	LANDED	details	yes
Find in page	P3	LANDED	details	yes
Sharing	P2	LANDED	details	yes
Platform integration (notification systems, back button, helper apps)	P1	INFLIGHT	details	yes
Session Store & Undo Tab Close	P4	LANDED	details	no
Feedback and Help	P3	LANDED	details	yes
UI Transitions/animations (zooming, sliding panels, fade in/out, elastic edges)	P3	RUNWAY		no
Page interactions (direct use and/or cursor mode)	P1	INFLIGHT	details	no
Scroll indicators (content and chrome)	P2	INFLIGHT	details	no
Consistent use of tap-and-hold
Better error pages	P4	TAKEOFF	details	yes
Mobilize our messages/dialogs	P4	TAKEOFF	details	yes
Form Assistant refresh	P2	LANDED	details	no
RTL support	P1	LANDED	details	no
Basic RSS support	P3	INFLIGHT	details	yes
Basic webapp support	P4	INFLIGHT	details	yes
Android chrome theme	P1	LANDED	details	yes
Camera UI	P3	INFLIGHT	details	yes
Reflow on zoom	P3	RUNWAY	details	no
Remove TileManager from Frontend	P1	LANDED	details	no
Master Password	P4	INFLIGHT	details	yes
Updater	P1	LANDED	details	yes

Platform:

Description	Priority	Status	Details	Strings
Electrolysis	P1	INFLIGHT	details notes	no
Layers	P1	INFLIGHT	notes	no
Power Management	P1	RUNWAY		no
QT Widget		INFLIGHT
Plugins		RUNWAY
Video (and UI)
Camera (and UI)		INFLIGHT

Status Legend:

• RUNWAY - Waiting for design or initial planning
• TAKEOFF - Ready for work to begin
• INFLIGHT - Work is in progress. Patches should be in bugs.
• LANDED - Work has finished and is in the product.

See the projects page for the list of all potential projects.

QA

2.0. Test Coverage Wiki