	THIS PAGE IS A WORKING DRAFT
	The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly. If you have any questions or ideas, please add them as a new topic on the discussion page.

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
	Jetpack Prototype	Jetpack SDK 0.1 - 0.5	Jetpack SDK 0.6 - 0.9	Jetpack SDK 1.0
ETA	DONE, 2009 Q4	IN PROGRESS, 2010 Q1/2	2010 Q3/4	2011 Q1/2
Firefox		Extension Manager no-restart API	Transparent content iframes	Support for Jetpack-native packages, Jetpack library in core?
Platform			chrome object wrappers	ECMAScript 5?
AMO			Stats on Jetpack-built extensions	Support for Jetpack-native packages
Security			Reduced-privilege security model	ES5-based API hardening?
L10N		Jetpack-native APIs/tools, web service?
API	Prototypes and proposals of various APIs	Implementation of high-level browser APIs	Robust library satisfying common add-on use-cases	Stable library
Dev Tools	Bespin-based editor in extension	Command line	FlightDeck web-based IDE
Distribution	Individual JS files	XPIs w/embedded Jetpack runtime		Jetpack-native packages (JPIs?)
Documentation		bundled w/SDK	MDC

SDK Release Roadmap

TBD. SDK versions 0.4 and 0.5 are currently targeting 2010 Q2. Once 0.3 is released, this space will fill in with the plan for those.

The SDK releases so far are available at Labs/Jetpack/SDK.

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