Firefox/Features/PFS2 datasource: Difference between revisions

Revision as of 14:15, 10 May 2011

Feature	Status	ETA	Owner
Feature Page Structure	Needs input from webdev	Firefox 6-7	Kev Needham

Summary

Ensure PFS2 is ready for prime-time, and switch the pfs.datasource.url in Firefox (and update legacy URI, if possible) to use PFS2.

Team

Who's working on this?

Feature Manager: Kev Needham
Lead Developer: Mossop (?)
Product Manager: Kev Needham
QA: TBD
UX: TBD
Security: TBD
Privacy: N/A
WebDev: Morgamic

Release Requirements

Performance and load testing of PFS2 application to ensure its capable of meeting needs of Firefox users
WebDev signoff of above
Functional testing of PFS2 application
QA Signoff of above
Security review of PFS2 application
Commit preference change to trunk and test

Next Steps & Open Issues

The change to Firefox itself is relatively minor, and involves changing a single preference. The larger issues are on the back-end, where additional work may be required to ensure the service can meet demand, and stay responsive (see bugs 573775, 564803, and bug 564807, which outline some potential issues). Next steps require an assessment from WebDev on current state of PFS2, and what changes and/or development is required to bring it on-line.

The PFS Test Plan will need to be updated to identify test cases/scenarios.

Related Bugs & Dependencies

bug 573834 - Change PFS backend to use PFS2 bug 573775 - Load test PFS2 API for Firefox 4 integration bug 564803 - Directory needs better caching with per-plugin invalidation bug 564807 - Optimize the directory's gnarly slow DB queries

Risks

Readiness of PFS2 webapp is a blocker to implementation. Risks include resource availability with WebDev, and results of testing. The back-end must be ready to go before a product change is made, so the web service is a blocker for this feature.

This feature should be re-considered as a P2 given the unknown state of PFS2.

Use Cases

Everyone loves use cases, so you should provide them if you can (and where it makes sense). The Channel Switcher Feature Page has some good examples.

Designs

No designs required. Project has been scoped at https://wiki.mozilla.org/PFS2

Test Plans

The current test plan/method is documented on the PFS wiki page, and requires updating for PFS2 to identify platforms, mime-types, and expected behaviours.

Goals

Provide identical service as current PFS, but use new infrastructure which facilitates management of listed plugins through the directory-driven back-end.

Non-Goals

Plugin Update Checking
Plugin Updates

Legend (remove if you like)

	Healthy: feature is progressing as expected.
	Blocked: feature is currently blocked.
	At Risk: feature is at risk of missing its targeted release.
ETA	Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date.

Please remove this line and any non-relevant categories below. Add whatever other categories you feel are appropriate.

@@ Line 9: / Line 9: @@
 | [[Feature Page Structure]]
 | {{StatusHealthy|status=Needs input from webdev}}
-| 2011-05-02
+| Firefox 6-7
 | Kev Needham
 <section end="status" />
@@ Line 17: / Line 17: @@
 == Summary ==
-Switch the pfs.datasource.url to use PFS2.
+Ensure PFS2 is ready for prime-time, and switch the pfs.datasource.url in Firefox (and update legacy URI, if possible) to use PFS2.
 == Team ==
@@ Line 23: / Line 23: @@
 * '''Feature Manager''': ''Kev Needham''
-* '''Lead Developer''': ''TBD''
+* '''Lead Developer''': ''Mossop (?)''
-* '''Product Manager''': ''TBD''
+* '''Product Manager''': ''Kev Needham''
 * '''QA''': ''TBD''
 * '''UX''': ''TBD''
 * '''Security''': ''TBD''
-* '''Privacy''': ''TBD''
+* '''Privacy''': ''N/A''
-* '''WebDev''': ''TBD''
+* '''WebDev''': ''Morgamic''
 == Release Requirements ==
-Complete checklist of items that need to be satisfied before we can call this feature "done".
+* Performance and load testing of PFS2 application to ensure its capable of meeting needs of Firefox users
+* WebDev signoff of above
+* Functional testing of PFS2 application
+* QA Signoff of above
+* Security review of PFS2 application
+* Commit preference change to trunk and test
 == Next Steps & Open Issues ==
-Either the next set of tasks that need to happen to move this project along, or (ideally) the full list of project tasks/action items with things crossed off as they're finished.  Including the name of who's responsible for each item, and a rough ETA can be useful.
-Open issues include unanswered questions, things that need to be explored, decisions that still need to be made, etc.  Again, including the name of who's responsible for each item can be useful.
+The change to Firefox itself is relatively minor, and involves changing a single preference. The larger issues are on the back-end, where additional work may be required to ensure the service can meet demand, and stay responsive (see bugs {{bug||573775}}, {{bug||564803}}, and {{bug|564807}}, which outline some potential issues). Next steps require an assessment from WebDev on current state of PFS2, and what changes and/or development is required to bring it on-line.
+The [https://wiki.mozilla.org/PFS#Testing_PFS PFS Test Plan] will need to be updated to identify test cases/scenarios.
 == Related Bugs & Dependencies ==
@@ Line 46: / Line 52: @@
 {{bug|564807}} - Optimize the directory's gnarly slow DB queries
-Links to the feature tracking bug & other relevant bugs; links to related plans (test plan, product marketing plan, etc.); notes about things that depend on this, etc.
+== Risks ==
+Readiness of PFS2 webapp is a blocker to implementation. Risks include resource availability with WebDev, and results of testing. The back-end must be ready to go before a product change is made, so the web service is a blocker for this feature.
-== Risks ==
+This feature should be re-considered as a P2 given the unknown state of PFS2.
-Identify, prioritize, track and communicate any risks associated with this feature/project.
 == Use Cases ==
@@ Line 55: / Line 61: @@
 == Designs ==
-Any and all mockups, design specs, tech specs, etc.  Either inline or linked to.
+No designs required. Project has been scoped at https://wiki.mozilla.org/PFS2
 == Test Plans ==
-Any and all test plans and strategies.  Either inline or linked to.
+The current test plan/method is documented on the [https://wiki.mozilla.org/PFS#Testing_PFS PFS wiki page], and requires updating for PFS2 to identify platforms, mime-types, and expected behaviours.
 == Goals ==
-The high level goals for the feature (which the release requirements checklist should fulfill).  These are the guiding light and overall vision for the feature.  Refer to this if there is confusion or are disputes about direction, designs, planning, etc.
+* Provide identical service as current PFS, but use new infrastructure which facilitates management of listed plugins through the directory-driven back-end.
 == Non-Goals ==
-Things we are specifically not doing or building as part of this feature.
+* Plugin Update Checking
+* Plugin Updates
-== Other Stuff ==
-Can include things like:
-* Competitive landscape
-* Research & references
-* Whatever else is useful to the project.
 == Legend (remove if you like) ==