Firefox:2.0 Product Planning/LI Plan Template: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
(v2 based on comments from shaver, mconnor)
Line 1: Line 1:
''Please comment in the Talk page (use the Discussion tab above)''
''Please comment in the Talk page (use the Discussion tab above)''


= LI-000: Template Line Item =
= Line Item #000: Template Line Item =
 
Tracked by: [https://bugzilla.mozilla.org/show_bug.cgi?id=40000 bug 40000]
{| border="0" cellpadding="3" width="70%"
*''this bug would be used to track status, target, owner and various deliverables''
|-
! align=right width="10%" | '''Status:'''
| In Plan
|-
! align=right width="10%" | '''Target:'''
| December 31st, 2005
|-
! align=right width="10%" | '''Owner:'''
| James Brown
|-
! align=right width="10%" | '''Code:'''
| /browser/wherever, /browser/wherever/else
|-
|}


= Goals & Objectives =
= Goals & Objectives =
Line 25: Line 11:
# Sed ultrices sem erat eget metus. Vestibulum blandit elementum nibh.
# Sed ultrices sem erat eget metus. Vestibulum blandit elementum nibh.


== Schedule ==
== Planned Milestones ==
{| border="0" cellpadding="3" width="100%"
{| border="0" cellpadding="3" width="100%"
|-
|-
Line 57: Line 43:
* [[/User Interface Design|User Interface Design]]
* [[/User Interface Design|User Interface Design]]
* [[/Code Design|Code Design]]
* [[/Code Design|Code Design]]
* [[/l10n Requirements|l10n Requirements]]
* [[/Test Plan|Test Plan]]
* [[/Test Plan|Test Plan]]
* [[/Documentation Plan|Documentation Plan]]
* [[/Documentation Plan|Documentation Plan]]


== Related LIs ==
== API Changes Required ==
* this one
* that one
 
== Impact ==
The current design impacts the following areas of development ...
 
=== Extensions ===
* this way
* that way
 
=== Localization ===
* this way
* that way
 
=== Update ===
* n/a
 
== See Also ==
* [[LI001|LI-001]]
* [[LI001|LI-001]]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=200 bug 200]


= Discussion =
= Discussion & Implications =
Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Integer eget neque. Ut pulvinar, nisl ut dapibus euismod, dolor mi aliquam metus, sed ultrices sem erat eget metus. Vestibulum blandit elementum nibh.
Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Integer eget neque. Ut pulvinar, nisl ut dapibus euismod, dolor mi aliquam metus, sed ultrices sem erat eget metus. Vestibulum blandit elementum nibh.


== Caveats ==
== Caveats / What We've Tried Before ==
Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Integer eget neque. Ut pulvinar, nisl ut dapibus euismod, dolor mi aliquam metus, sed ultrices sem erat eget metus. Vestibulum blandit elementum nibh.
Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Integer eget neque. Ut pulvinar, nisl ut dapibus euismod, dolor mi aliquam metus, sed ultrices sem erat eget metus. Vestibulum blandit elementum nibh.



Revision as of 23:56, 22 November 2005

Please comment in the Talk page (use the Discussion tab above)

Line Item #000: Template Line Item

Tracked by: bug 40000

  • this bug would be used to track status, target, owner and various deliverables

Goals & Objectives

Lorem ipsum dolor sit amet, consectetuer adipiscing elit.

  1. Integer eget neque.
  2. Ut pulvinar, nisl ut dapibus euismod, dolor mi aliquam metus.
  3. Sed ultrices sem erat eget metus. Vestibulum blandit elementum nibh.

Planned Milestones

01/12/2005 This

That

08/12/2005 The other thing

And yet another thing

Overview

Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Integer eget neque. Ut pulvinar, nisl ut dapibus euismod, dolor mi aliquam metus, sed ultrices sem erat eget metus. Vestibulum blandit elementum nibh.

Background

Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Integer eget neque. Ut pulvinar, nisl ut dapibus euismod, dolor mi aliquam metus, sed ultrices sem erat eget metus. Vestibulum blandit elementum nibh.

Use Cases

  1. Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
  2. Integer eget neque.
  3. Ut pulvinar, nisl ut dapibus euismod, dolor mi aliquam metus, sed ultrices sem erat eget metus. Vestibulum blandit elementum nibh.

Functional Requirements

  1. Primi
  2. Secondi
  3. Dolce

Plans & Design Documents

API Changes Required

  • this one
  • that one

Impact

The current design impacts the following areas of development ...

Extensions

  • this way
  • that way

Localization

  • this way
  • that way

Update

  • n/a

See Also

Discussion & Implications

Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Integer eget neque. Ut pulvinar, nisl ut dapibus euismod, dolor mi aliquam metus, sed ultrices sem erat eget metus. Vestibulum blandit elementum nibh.

Caveats / What We've Tried Before

Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Integer eget neque. Ut pulvinar, nisl ut dapibus euismod, dolor mi aliquam metus, sed ultrices sem erat eget metus. Vestibulum blandit elementum nibh.

Security Implications

Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Integer eget neque. Ut pulvinar, nisl ut dapibus euismod, dolor mi aliquam metus, sed ultrices sem erat eget metus. Vestibulum blandit elementum nibh.

Privacy Considerations

Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Integer eget neque. Ut pulvinar, nisl ut dapibus euismod, dolor mi aliquam metus, sed ultrices sem erat eget metus. Vestibulum blandit elementum nibh.