[
https://issues.apache.org/jira/browse/CB-12708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shazron Abdullah updated CB-12708:
----------------------------------
Description:
h1. DEADLINE of June 1st 2017
All decisions should be wrapped up by then.
h2. This is an umbrella issue where we list all the core plugins we have, and
what we are to do with them:
1. Sunset
2. Continue Maintenance
3. Integrate into their respective platforms
The first two of these options will require migration steps (docs), if any, to
W3C API equivalents in the browser, when available. If not, the goal would be
for them (if we are still maintaining them) to be upgraded to a W3C API
standard.
h2. Actions:
1. Migration docs (if applicable)
2. Upgrade to W3C API standard (if applicable)
3. Update README with non-maintenance status (if applicable)
was:
h2. This is an umbrella issue where we list all the core plugins we have, and
what we are to do with them:
1. Sunset
2. Continue Maintenance
3. Integrate into their respective platforms
The first two of these options will require migration steps (docs), if any, to
W3C API equivalents in the browser, when available. If not, the goal would be
for them (if we are still maintaining them) to be upgraded to a W3C API
standard.
h2. Actions:
1. Migration docs (if applicable)
2. Upgrade to W3C API standard (if applicable)
3. Update README with non-maintenance status (if applicable)
> Core Plugins Roadmap 2017
> -------------------------
>
> Key: CB-12708
> URL: https://issues.apache.org/jira/browse/CB-12708
> Project: Apache Cordova
> Issue Type: Bug
> Components: AllPlugins
> Reporter: Shazron Abdullah
>
> h1. DEADLINE of June 1st 2017
> All decisions should be wrapped up by then.
> h2. This is an umbrella issue where we list all the core plugins we have, and
> what we are to do with them:
> 1. Sunset
> 2. Continue Maintenance
> 3. Integrate into their respective platforms
> The first two of these options will require migration steps (docs), if any,
> to W3C API equivalents in the browser, when available. If not, the goal would
> be for them (if we are still maintaining them) to be upgraded to a W3C API
> standard.
> h2. Actions:
> 1. Migration docs (if applicable)
> 2. Upgrade to W3C API standard (if applicable)
> 3. Update README with non-maintenance status (if applicable)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
