Mobile/Firefox for iOS/Status Report/05-Aug-2016: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
__NOTOC__
__NOTOC__
<big><big><big>'''Firefox for iOS - Program Status Report - June 28-2016'''</big></big></big>
<big><big><big>'''Firefox for iOS - Program Status Report - August 05-2016'''</big></big></big>


== Overall Project Health ==
== Overall Project Health ==
Line 18: Line 18:
[[File:Green-sm.jpg|frameless|25px]]<br>
[[File:Green-sm.jpg|frameless|25px]]<br>


|Target submission is Tuesday,July 5th.  
|Released on July 27th.  


|-
|-
Line 28: Line 28:
[[File:Green-sm.jpg|frameless|25px]]<br>
[[File:Green-sm.jpg|frameless|25px]]<br>


|On hold until otherwise advised by senior management.  
|Feature development it progressing, but final scope and timeline for the release is TBD.


|}
|}
Line 34: Line 34:
== Exec Summary/Hot Topics ==
== Exec Summary/Hot Topics ==
<!--Should explain WHY for the health/status reported above.  Items covered here may be covered in more detail further down in the report.  If senior management were to look at nothing but this section, they should be able to tell what is going on with the project.-->
<!--Should explain WHY for the health/status reported above.  Items covered here may be covered in more detail further down in the report.  If senior management were to look at nothing but this section, they should be able to tell what is going on with the project.-->
* V5.0 is targeting submission on Tuesday, July 5th. Release candidate build is planned for this Thursday, but will be given the weekend to soak on Testflight.   
 
* Tabs for iPad was considered for uplift to V5.0, but the decision was made to hold for further testing and launch in a later release.
* The team will continues to monitor and triage issues, and land bug-fixesThe triage page can be found  [https://wiki.mozilla.org/Mobile/Triage/iOS HERE].
* A decision has been made by senior management to continue to hold back on the release of bi-directional sync, so this feature will NOT be launching in V5.0 as initially planned.
* A 5.1 bug fix release is planned for submission soon, but the exact date is TBDOnce approved the release will follow immediately, with no accompanying campaign/promotion.
* Approval is expected 2-3 days post-submissionLaunch timing is TBD pending Marketing/PR recommendations
* Plans are still being developed for a 6.0 feature release, geared toward Sync and Activity Stream, but release date is still TBD.
* The team will continue to monitor and triage issues, and produce bug-fix releases, which may possibly include some limited number of foundational features as approved by senior management.
* The team is beginning to transition to two week sprintsFinal process details to align with other platforms are still in development.


== Risks & Issues ==
== Risks & Issues ==
Line 135: Line 135:
|-
|-
| Target Launch
| Target Launch
| July  
| July 27
| Complete
| Complete
|  
| Date chosen by Marketing/PM to align with promotion goals
|}
|}


== Important Links/References <!--Optional--> ==
== Important Links/References <!--Optional--> ==

Latest revision as of 19:14, 5 August 2016

Firefox for iOS - Program Status Report - August 05-2016

Overall Project Health

Green-sm.jpg On track, issues well managed Yellow-sm.jpg Some risks, unknowns without clear mitigations Red-sm.jpg Blocked on deliverables, needs decision, escalation required

Version Health Notes
V5.0

Green-sm.jpg

Released on July 27th.
V6.0

Green-sm.jpg

Feature development it progressing, but final scope and timeline for the release is TBD.

Exec Summary/Hot Topics

  • The team will continues to monitor and triage issues, and land bug-fixes. The triage page can be found HERE.
  • A 5.1 bug fix release is planned for submission soon, but the exact date is TBD. Once approved the release will follow immediately, with no accompanying campaign/promotion.
  • Plans are still being developed for a 6.0 feature release, geared toward Sync and Activity Stream, but release date is still TBD.
  • The team is beginning to transition to two week sprints. Final process details to align with other platforms are still in development.

Risks & Issues

Description of Risk/Issue State Owner Version Plan to Resolve/Mitigation Target Date

Cross-functional/Milestone Status

Version 5.0

Milestone/Area/Deliverable Target Date Status Notes
Feature Complete Mid-June Complete
L10N/Code Freeze Mid-June Complete
Release Candidate Build late-June Complete
App Store Submission Early - July Complete
Apple Approval ~ July 7/8 Complete
Comms/PR July 7 Complete
Marketing July 7 Complete
SUMO July 7 Complete
Legal July 7 On Track
Release Management July 7 Complete
Target Launch July 27 Complete Date chosen by Marketing/PM to align with promotion goals

Important Links/References