Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Cordova Wiki" for 
change notification.

The "RoadmapProjects" page has been changed by brianleroux:
http://wiki.apache.org/cordova/RoadmapProjects?action=diff&rev1=32&rev2=33

  
  This document outlines the general goals for Apache Cordova 2.x and beyond. 
We employ an agile release train with the following tentative schedule.
  
+ {{{
+ 
+ 2012 (Autumn-Winter)
+ 
-  * 2.1 ... Sept 2012 ... board report due
+  2.1 ... Sep ... board report due
-  * 2.2 ... Oct
+  2.2 ... Oct
-  * 2.3 ... Nov
+  2.3 ... Nov
-  * ..................... board report due
+          Dec ... board report due
+ 
+ 2013 (Spring-Summer)
+ 
-  * 2.4 ... Jan 2013
+  2.4 ... Jan 
-  * 2.5 ... Feb
+  2.5 ... Feb
-  * 2.6 ... Mar ......... board report due
+  2.6 ... Mar ... board report due
-  * 2.7 ... Apr
+  2.7 ... Apr
-  * 2.8 ... May
+  2.8 ... May
-  * 2.9 ... Jun ......... board report due
+  2.9 ... Jun ... board report due
-  * 3.0 ... July
+  3.0 ... Jul
+ 
+ }}}
  
  == What does 3.0 look like? ==
  
- General consensus on the mailing list is an Apache Cordova 3.0 that ships 
without any device API surface area: just the Cordova.exec bridge/ffi and its 
dependencies as found in CordovaJS. Additional APIs can be installed/removed by 
end developers using plugin cli tooling.
+ Apache Cordova 3.0 will ship without any Device API surface area and only the 
Cordova.exec FFI (and its dependencies as found in the CordovaJS subproject). 
Additional APIs can be installed/removed by end developers using plugin CLI 
tooling.
  
- == Nearterm ==
+ == Autumn (Sept-Nov) ==
  
-   * b2g prototype (herm)
+   * b2g prototype (herm) 
    * master cli script (anis, fil, brian, jesse, lunny)
    * plugin list (lists currently installed plugins for a given native project)
    * plugin remove (removes named plugin from a given native project)
    * plugin discovery (uses npm and the registry)
    * cli tools parity (currently ios requires installer to be run first [see 
https://issues.apache.org/jira/browse/CB-1091], behavior slightly differ b/t 
platforms)
-   * get plugin-install into labs and enable installation from a git repo 
(think anis did this already)
    * config and manifest metafile for all major platforms (required for 
plugin-install & plugin-remove reference)
    * InAppBrowser
    * add globalization plugin to core (Bryce, Simon, Becky, Drew)
-   * bridge performance by way of echo plugin
+   * bridge performance by way of echo plugin (andrew)
+ 
+ == Winter (Dec-Feb) ==
+ 
+   * plugin discovery (fil, anis, jesse, lunny)
+   * hosted Ripple ala weinre {{{ npm install -g ripple }}}
+   * html5 audio api fixing (jesse)
+   * core api audit (and begin refactor)
+   * remove plugins to discreet repos and use discovery mechanism to compose 
different releases
+ 
+ == Spring (March-June) ==
+ 
+   * notifications api: http://www.w3.org/TR/notifications/ (that works w/ 
push notification servers)
+   * App invocation w/ data/args (like intents or protocol handlers) 
https://github.com/PaulKinlan/WebIntents
+   * continue core api audit/refactor
+   * native pickers for contacts and file (w/ help of simon) 
+ 
+ == Summer ==
+ 
+   * Hardening and MAJOR release.
  
  === Core API Audit: lighter, faster, stronger ===
  
@@ -61, +88 @@

    * windows phone touch event polyfill
    * android multitouch polyfill: 
https://github.com/Philzen/webview-multitouch-polyfill 
    * sockets polyfill: http://caniuse.com/websockets
-   * notifications api: http://www.w3.org/TR/notifications/
-   * App invocation w/ data/args (like intents or protocol handlers) 
https://github.com/PaulKinlan/WebIntents
-   * remove plugins to discreet repos and use discovery mechanism to compose 
different releases
    * first class NFC API http://www.w3.org/wiki/Near_field_communications_(NFC)
- 
- === Future Unscheduled ===
- 
    * WebRTC
    * device capabilities api (see https://issues.apache.org/jira/browse/CB-753)
-   * native contact picker 
-   * native file picker
    * Menu api to build menus for all platforms (discussion on Planning: Menu 
API) mainline
    * enhance internationalization (i18n)
    * Device.exitApp() as device independent way of closing application (exists 
in android / ios makes no sense)

Reply via email to