[
https://issues.apache.org/jira/browse/CB-12903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16097734#comment-16097734
]
Filip Maj commented on CB-12903:
--------------------------------
Interesting. Perhaps some of this can be mitigated by also doing one final
release of any INTEGRATE plugins, specifying with more detail the the cordova
versions supported (via engine tags), and capping the cordova version the
plugin supports to the last released version of platforms _before_ integrated
plugin code landed in the platform repos.
But, I see what you mean in that, if someone with a cordova project and
integrated-plugin-A goes to update their cordova version, shit will hit the
fan. I think that use case probably needs more attention than the use case of
project-using-new-cordova-with-integrated-plugin goes to add
deprecated-integrated-plugin.
I wonder if this could be a documentation issue? Like, as part of the next
major release of the platforms we will include the integrated plugins. And as
part of the release, we will make sure to highlight which plugins were
integrated, and if you are upgrading a previous project that includes the
integrated plugins as explicit standalone plugins, we ask that you first remove
the plugins before upgrading. Thoughts?
> INTEGRATEd plugins - tasks
> --------------------------
>
> Key: CB-12903
> URL: https://issues.apache.org/jira/browse/CB-12903
> Project: Apache Cordova
> Issue Type: Sub-task
> Components: AllPlugins
> Reporter: Shazron Abdullah
>
> 1. Update README.md to reflect maintenance status
> 2. Close out any PRs and issues
> 3. Deprecate the component from JIRA
> 3. Direct users to file bugs/prs to the platforms that integrate the plugin
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
