Mailing-List: contact issues-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 3 Aug 2017 19:21:00 +0000 (UTC)
From: "Filip Maj (JIRA)" <jira@apache.org>
To: issues@cordova.apache.org
Message-ID: <JIRA.13092277.1501787705000.87693.1501788060586@Atlassian.JIRA>
In-Reply-To: <JIRA.13092277.1501787705000@Atlassian.JIRA>
References: <JIRA.13092277.1501787705000@Atlassian.JIRA> <JIRA.13092277.1501787705584@jira-lw-us.apache.org>
Subject: [jira] [Updated] (CB-13147) Integrate cordova-plugin-console
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Thu, 03 Aug 2017 19:21:07 -0000


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

Filip Maj updated CB-13147:
---------------------------
    Description:=20
Looks like the main work to be done here is for cordova-ios and cordova-win=
dows. There are also ubuntu, wp7, wp8 and win8 platform implementations in =
this plugin, but these are all deprecated platforms, so I would ignore thos=
e. 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 nee=
d to do the following:

1. Update README.md to reflect maintenance status:
=E2=80=93 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=20
4. Highlight in release notes and announcement blog posts about upgrade pat=
h:
=E2=80=93 potential conflicts in old cordova projects that explicitly added=
 the integrated plugin
=E2=80=93 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 tweakin=
g 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

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-win=
dows. There are also ubuntu, wp7, wp8 and win8 platform implementations in =
this plugin, but these are all deprecated platforms, so I would ignore thos=
e. 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 nee=
d to do the following:

1. Update README.md to reflect maintenance status:
=E2=80=93 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=20
4. Highlight in release notes and announcement blog posts about upgrade pat=
h:
=E2=80=93 potential conflicts in old cordova projects that explicitly added=
 the integrated plugin
=E2=80=93 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 tweakin=
g in config.xml

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
>              Labels: plugins-next
>
> Looks like the main work to be done here is for cordova-ios and cordova-w=
indows. There are also ubuntu, wp7, wp8 and win8 platform implementations i=
n this plugin, but these are all deprecated platforms, so I would ignore th=
ose. I believe next integration/implementation steps are:
> * integrate the plugin's {{www/logger.js}} and {{www/console-via-logger.j=
s}} 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, cappi=
ng cordova-ios and cordova-windows support
> Over and above the actual migration of the code into platform repos, we n=
eed to do the following:
> 1. Update README.md to reflect maintenance status:
> =E2=80=93 Direct users to file bugs/prs to the platforms that integrate t=
he plugin
> 2. Close out any PRs and issues
> 3. Deprecate the component from JIRA=20
> 4. Highlight in release notes and announcement blog posts about upgrade p=
ath:
> =E2=80=93 potential conflicts in old cordova projects that explicitly add=
ed the integrated plugin
> =E2=80=93 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 tweak=
ing in config.xml
> * https://cordova.apache.org/docs/en/latest/platform_plugin_versioning_re=
f/index.html#saving-plugins should not use cordova-plugin-console as exampl=
e
> 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-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org