cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shazron Abdullah (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CB-12708) Core Plugins Roadmap 2017
Date Tue, 25 Apr 2017 20:53:04 GMT

     [ https://issues.apache.org/jira/browse/CB-12708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Shazron Abdullah updated CB-12708:
----------------------------------
    Description: 
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:
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.

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
>
> 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: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org


Mime
View raw message