Labs/Jetpack/Reboot/JEP/Shell: Difference between revisions
Jump to navigation
Jump to search
Dandonkulous (talk | contribs) |
Dandonkulous (talk | contribs) |
||
| Line 4: | Line 4: | ||
* Status: Accepted/Pre-production | * Status: Accepted/Pre-production | ||
**Status field can be Proposed or Accepted | **Status field can be Proposed or Accepted | ||
***Accepted detail flags are: | ***Accepted detail flags are: Blocked, In-Queue, Pre-production, Production, Active, Deprecated | ||
***Proposed detail flags are: Needs Review, Under Review, Needs Revision, Declined | ***Proposed detail flags are: Needs Review, Under Review, Needs Revision, Declined | ||
* Type: Core | * Type: Core | ||
Revision as of 18:08, 27 January 2010
JEP Shell - Example JEP
- Champion: Testy McTest - mctest@mozilla.com
- Status: Accepted/Pre-production
- Status field can be Proposed or Accepted
- Accepted detail flags are: Blocked, In-Queue, Pre-production, Production, Active, Deprecated
- Proposed detail flags are: Needs Review, Under Review, Needs Revision, Declined
- Status field can be Proposed or Accepted
- Type: Core
- Type field can be Core or API
- JEP Index
Proposal
- What will it do?
- What does it enable internally/externally?
- How hard is it to implement?
Dependencies
- Are there any Firefox platform bugs blocking it?
- Does other Jetpack platform code need to be modified or added?
- Does its implementation affect any other projects or code?
Internal Methods
- What methods, mechanisms, or resources does this provide internally within the Jetpack platform code.
API Methods
- What are the pretty API wrapped methods externally exposed to Jetpack developers?