Closed Bug 842684 (metrofirefox) Opened 12 years ago Closed 11 years ago

Metro Firefox

Categories

(Tracking Graveyard :: Metro Operations, defect)

Product:
Tracking Graveyard
Component:
Metro Operations
Platform:
x86_64
Windows 8.1
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: MarcoM, Unassigned)

Details

All Epics, Stories and Work related to the development of Firefox for Metro - V2.
Depends on: metrov2planning
After our first version hits the release channel, we will be on the rapid release trains and will be shipping updates every six weeks containing all the work that lands on trunk during that period.  Does it make sense to use the same release planning process after that point, or should we move to a model more like desktop Firefox, or perhaps the Android Firefox team with their roadmap documents?
This is just for holding items for the future.  Don't worry about the model now.  We still have a long way to go for V1.
Component: General → Metro Operations
Product: Firefox for Metro → Tracking
Version: unspecified → ---
Depends on: metrobacklog
Depends on: metrov2epicbacklog
Depends on: metrov2defect&change
Assignee: asa → nobody
Depends on: 948012
Depends on: 948107
No longer depends on: 948012
No longer depends on: 948107
No longer depends on: metrov2planning
No longer depends on: metrov2epicbacklog
No longer depends on: metrov2defect&change
Alias: metrov2 → metrofirefox
Summary: Ship a Metro Firefox v.2 → Metro Firefox
Whiteboard: feature=product → [product]
Whiteboard: [product] → [metroproduct]
Depends on: metroiterations
Status: NEW → RESOLVED
Closed: 11 years ago
No longer depends on: metrobacklog, metroiterations
Priority: P1 → --
Resolution: --- → INVALID
Whiteboard: [metroproduct]
OS: Windows 8 Metro → Windows 8.1
Product: Tracking → Tracking Graveyard
You need to log in before you can comment on or make changes to this bug.