Jetpack/Roadmap-2011
< Jetpack
Jump to navigation
Jump to search
Jetpack High-Level Product Roadmap
Jetpack development comprises numerous releases of multiple products that achieve four major milestones, which this chart summarizes.
| Milestone One | Milestone Two | Milestone Three | Milestone Four | Milestone Five | |
|---|---|---|---|---|---|
| Jetpack Prototype | Jetpack SDK 0.1 | Jetpack SDK 0.2 - 1.0b | Jetpack SDK 1.0 | Jetpack SDK Future | |
| ETA | DONE, 2009 Q4 | DONE, 2010 Q1 | 2010 Q2 - Q3 | 2010 Q4 | 2011 Q1 |
| Firefox | Extension Manager no-restart API, transparent content iframes, addon bar | Support for Jetpack-native packages, Jetpack library in core? | |||
| Platform | Chrome object wrappers, OOP Jetpack | ECMAScript 5? | |||
| AMO | Stats on Jetpack-built extensions | Support for Jetpack-native packages | |||
| Security | Reduced-privilege security model | ES5-based API hardening? | |||
| L10N | web service | Jetpack-native APIs/tools | |||
| API | Prototypes and proposals of various APIs | Implementation of robust library satisfying common add-on use-cases | Stable core library, community library collections | ||
| Dev Tools | Bespin-based editor in extension | Command line | FlightDeck web-based IDE | Firefox HUD console integration | |
| Distribution | Individual JS files | XPIs w/embedded Jetpack runtime | Jetpack-native packages (JPIs?) | ||
| Documentation | bundled with SDK | bundled with Flightdeck | MDC |
SDK Release Roadmap
Included from Labs/Jetpack/SDK:
- SDK 0.2 - Released: 2010-03-26
- SDK 0.3 - Released: 2010-04-29
- SDK 0.4 - Released: 2010-05-26
- SDK 0.5 - Released: 2010-06-24
- SDK 0.6 - Released: 2010-07-28
- SDK 0.7 - Released: 2010-08-26
- SDK 0.8 - Released: 2010-09-27
- SDK 0.9 - Released: 2010-10-21
- SDK 0.10 - Released: 2010-11-?
- SDK 1.0b2 - Released: 2011-01-27
- SDK 1.0b3 - Released: 2011-03-01
- SDK 1.0b4 - Planned: 2011-03-24
- SDK 1.0b5 - Planned: 2011-05-04
- SDK 1.0 - Planned: 2011-05-04
SDK 1.0 Goals
NOTE: Some of these are already achieved by the move to the SDK approach, and some made obsolete/irrelevant. These goals need updating.
- A seamless install process: It defeats the purpose of Jetpack to first require users to install Jetpack, then install a particular Jetpack, before using its features. Instead, we need a solution which allows a seamless install process.
- Seamless debugging: No pointless error messages, and all relevant warnings, line numbers, and tracebacks, are displayed.
- Enabling API: An API deep enough to support a large range of add-ons. It is a non-goal in 1.0 to support everything, instead it is to support 80% of the long-tail of add-ons. The exact feature set of the API will be determined by a set of target add-ons (TBD) and feedback from Jetpack authors.
- Frozen API: Although the API may be versioned, we the API will be backwards compatible from 1.0 on.
- Beautiful by default: A set of OS-specific icons, as well as a beautiful look for Jetpacks.
- Security-sensitive Import mechanism: The strength of any API is measured in how easily 3rd parties can extend it. The 1.0 release will have a strong import mechanism, replete with security provisions.
- Security: A functioning security system that mixes code with social protections.
- An AMO-like service with social code-review
- Localization story
- Works on Fennec