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

Filip Maj updated CB-13147:
---------------------------
    Description: 
Looks like the main work to be done here is for cordova-ios and 
cordova-windows. There are also ubuntu, wp7, wp8 and win8 platform 
implementations in this plugin, but these are all deprecated platforms, so I 
would ignore those.

I believe next integration/implementation steps are:
* add an <engine> (and cordovaDependencies ?) constraint to plugin, capping 
cordova-ios and cordova-windows support

Over and above the actual migration of the code into platform repos, we need to 
do the following:

1. Update README.md to reflect maintenance status:
– Direct users to file bugs/prs to the platforms that integrate the plugin
2. Close out any PRs and issues
3. Deprecate the component from JIRA 
4. Highlight in release notes and announcement blog posts about upgrade path:
– potential conflicts in old cordova projects that explicitly added the 
integrated plugin
– how to turn the integrated plugin off via feature tag tweaking in config.xml
5. cordova-docs need updating:
* should show how to turn the integrated plugin off via feature tag tweaking in 
config.xml
* 
https://cordova.apache.org/docs/en/latest/platform_plugin_versioning_ref/index.html#saving-plugins
 should not use cordova-plugin-console as example
* https://cordova.apache.org/docs/en/latest/plugin_ref/plugman.html

6. bump version, do a final release, and npm deprecate the plugin

We might want to split this all up into subtasks.

  was:
Looks like the main work to be done here is for cordova-ios and 
cordova-windows. There are also ubuntu, wp7, wp8 and win8 platform 
implementations in this plugin, but these are all deprecated platforms, so I 
would ignore those. I believe next integration/implementation steps are:
* integrate the plugin's {{www/logger.js}} and {{www/console-via-logger.js}} 
into cordova-ios and cordova-windows. How? It's been a while for me... or does 
this land in cordova-js?
* integrate plugin's {{src/ios/*}} into cordova-ios
* add an <engine> (and cordovaDependencies ?) constraint to plugin, capping 
cordova-ios and cordova-windows support

Over and above the actual migration of the code into platform repos, we need to 
do the following:

1. Update README.md to reflect maintenance status:
– Direct users to file bugs/prs to the platforms that integrate the plugin
2. Close out any PRs and issues
3. Deprecate the component from JIRA 
4. Highlight in release notes and announcement blog posts about upgrade path:
– potential conflicts in old cordova projects that explicitly added the 
integrated plugin
– how to turn the integrated plugin off via feature tag tweaking in config.xml
5. cordova-docs need updating:
* should show how to turn the integrated plugin off via feature tag tweaking in 
config.xml
* 
https://cordova.apache.org/docs/en/latest/platform_plugin_versioning_ref/index.html#saving-plugins
 should not use cordova-plugin-console as example
* https://cordova.apache.org/docs/en/latest/plugin_ref/plugman.html

6. bump version, do a final release, and npm deprecate the plugin

We might want to split this all up into subtasks.


> Integrate cordova-plugin-console
> --------------------------------
>
>                 Key: CB-13147
>                 URL: https://issues.apache.org/jira/browse/CB-13147
>             Project: Apache Cordova
>          Issue Type: Task
>          Components: cordova-plugin-console
>            Reporter: Filip Maj
>            Assignee: Filip Maj
>              Labels: plugins-next
>
> Looks like the main work to be done here is for cordova-ios and 
> cordova-windows. There are also ubuntu, wp7, wp8 and win8 platform 
> implementations in this plugin, but these are all deprecated platforms, so I 
> would ignore those.
> I believe next integration/implementation steps are:
> * add an <engine> (and cordovaDependencies ?) constraint to plugin, capping 
> cordova-ios and cordova-windows support
> Over and above the actual migration of the code into platform repos, we need 
> to do the following:
> 1. Update README.md to reflect maintenance status:
> – Direct users to file bugs/prs to the platforms that integrate the plugin
> 2. Close out any PRs and issues
> 3. Deprecate the component from JIRA 
> 4. Highlight in release notes and announcement blog posts about upgrade path:
> – potential conflicts in old cordova projects that explicitly added the 
> integrated plugin
> – how to turn the integrated plugin off via feature tag tweaking in config.xml
> 5. cordova-docs need updating:
> * should show how to turn the integrated plugin off via feature tag tweaking 
> in config.xml
> * 
> https://cordova.apache.org/docs/en/latest/platform_plugin_versioning_ref/index.html#saving-plugins
>  should not use cordova-plugin-console as example
> * https://cordova.apache.org/docs/en/latest/plugin_ref/plugman.html
> 6. bump version, do a final release, and npm deprecate the plugin
> We might want to split this all up into subtasks.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org

Reply via email to