RE: [DISCUSS] Buildbot deprecation

[Nikhil Khandelwal]

+1. We should change ci.cordova.io to point to the new Jenkins server location 
for periodic build.

-Nikhil

-Original Message-
From: Shazron [mailto:shaz...@gmail.com] 
Sent: Thursday, June 23, 2016 11:18 AM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Buildbot deprecation

Thank you Vladimir and Alexander!
Looks great.

+1 to the deprecation.
For future reference, this is how Jenkins is set up:
https://github.com/apache/cordova-medic/blob/master/JENKINS.md


On Thu, Jun 23, 2016 at 9:57 AM, Alexander Sorokin (Akvelon) < 
v-als...@microsoft.com> wrote:

> Also, we now run tests (iOS and Android) on SauceLabs emulators!
>
> Here's recent camera plugin build on iOS for example:
>
> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fcordov
> a-ci.cloudapp.net%3a8080%2fjob%2fcordova-periodic-build%2flastBuild%2f
> PLATFORM%3dios%2cPLUGIN%3dcordova-plugin-camera%2fconsole=01%7c01
> %7cnikhilkh%40microsoft.com%7c16fd5665101342b3acda08d39b92c8e5%7c72f98
> 8bf86f141af91ab2d7cd011db47%7c1=HYIQNCM32KKFRgUDgLIu8jv2eZJjLF43
> rbciy6W%2b0Dk%3d
>
> -Original Message-
> From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com]
> Sent: Thursday, June 23, 2016 4:01 PM
> To: dev@cordova.apache.org
> Subject: [DISCUSS] Buildbot deprecation
>
> Hi guys,
>
> Last couple of weeks we've been polishing our Jenkins setup and 
> hopefully resolved all discovered issues w/ Paramedic, Saucelabs and 
> intermittent tests failures, so Jenkins/Paramedic CI process can now 
> be considered stable and reliable.
>
> In general this means that we no more depend on Medic/buildbot in our 
> CI process so I'd like to discuss deprecation of our Buildbot in favor 
> of Jenkins CI and propose to shutdown it in the near future.
>
> As main advantages of doing this we'll get a clear picture of current 
> plugins' health using dasboards for PR[1] and periodic[2] builds and 
> much more convenience and maintainability.
>
> Any thoughts?
>
> ---
> [1]
> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fcordov
> a-ci.cloudapp.net%3a8080%2fview%2fPull%2520requests%2f=01%7c01%7c
> v-alsoro%40microsoft.com%7c2f2902aa183845567b2b08d39b668529%7c72f988bf
> 86f141af91ab2d7cd011db47%7c1=aEA1op95WhYQwheEicBVSqkHcseXYHzeQ%2
> bX7fjQvFls%3d
> [2]
> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fcordov
> a-ci.cloudapp.net%3a8080%2fview%2fPeriodic%2520builds%2f=01%7c01%
> 7cv-alsoro%40microsoft.com%7c2f2902aa183845567b2b08d39b668529%7c72f988
> bf86f141af91ab2d7cd011db47%7c1=wWb4jNXelojhbOtKoy3CKsFHSp8lEaFgu
> RouMGPx9LI%3d
>
> ---
> best regards, Vladimir
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

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

RE: Apache Cordova Project Global Status Page

[Nikhil Khandelwal]

This is awesome, Shaz! Love it!

-Nikhil

-Original Message-
From: Shazron [mailto:shaz...@gmail.com] 
Sent: Monday, June 13, 2016 1:51 PM
To: dev@cordova.apache.org
Subject: Re: Apache Cordova Project Global Status Page

https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fstatus.cordova.io=01%7c01%7cnikhilkh%40microsoft.com%7c67bbaef2f4c646e0a95108d393cc96f9%7c72f988bf86f141af91ab2d7cd011db47%7c1=3KQVya3s5dT5d336iPyd3Ifc9qlHp41ZxGoubhB4img%3d
 points to it now

On Mon, Jun 13, 2016 at 11:34 AM, Shazron  wrote:

> What this tells me is, for Core Plugins, everything under iOS and 
> Android are failing -- which is unlikely that *all* are failing, and 
> more probably the CI setup or script is failing.
>
> On Mon, Jun 13, 2016 at 11:29 AM, Shazron  wrote:
>
>> https://github.com/cordova/cordova-status
>>
>> I added defunct platforms for completeness, maybe we should remove?
>>
>> Some plugins are missing any test badges, not sure if they are more 
>> "plugin tools" (last section).
>>
>> Some tools are missing tests - some have tests and no badge 
>> (cordova-common).
>>
>
>

RE: [DISCUSS] Cordova-Android 5.2.0 Release

[Nikhil Khandelwal]

As part of this release should we add a deprecation warning for --ant build 
support for Cordova-android?

As we make changes for the next major release of cordova-android we will likely 
not be able to support the ant build for much longer. It's best to start 
messaging it's end of life.

-Nikhil

-Original Message-
From: Nikhil Khandelwal [mailto:nikhi...@microsoft.com] 
Sent: Tuesday, May 31, 2016 1:35 PM
To: dev@cordova.apache.org
Subject: RE: [DISCUSS] Cordova-Android 5.2.0 Release

Support for incremental prepare (PR #295) has been merged. We should be ready 
for a release.

-Nikhil

-Original Message-
From: Joe Bowser [mailto:bows...@gmail.com]
Sent: Thursday, May 26, 2016 2:52 PM
To: dev <dev@cordova.apache.org>
Subject: Re: [DISCUSS] Cordova-Android 5.2.0 Release

Do we have an N PR yet? I've seen the proposal, but not the PR.

On Thu, May 26, 2016 at 2:47 PM, Steven Gill <stevengil...@gmail.com> wrote:

> Can we merge the android N PR too?
>
> On Wed, May 25, 2016 at 2:50 PM, Joe Bowser <bows...@gmail.com> wrote:
>
> > On Wed, May 25, 2016 at 1:47 PM, Homer, Tony <tony.ho...@intel.com>
> wrote:
> >
> > > +1
> > >
> > > Would like #307 to be merged in first
> > >
> > >
> > Done! Yay for tests!
> >
> > BTW, We need to re-write those to migrate to the new Android JUnit 
> > test framework (It's more deleting code than adding).
> >
> >
> >
> >
> > > On 5/25/16, 3:31 PM, "Carlos Santana" <csantan...@gmail.com> wrote:
> > >
> > > >+1
> > > >
> > > >- Carlos
> > > >@csantanapr
> > > >
> > > >> On May 25, 2016, at 3:08 PM, Shazron <shaz...@gmail.com> wrote:
> > > >>
> > > >> +1
> > > >>
> > > >> Release often
> > > >>
> > > >>> On Wed, May 25, 2016 at 10:33 AM, Joe Bowser 
> > > >>> <bows...@gmail.com>
> > > wrote:
> > > >>>
> > > >>> Hey
> > > >>>
> > > >>> I know that we haven't done a minor release for a few months 
> > > >>> for
> > > Android,
> > > >>> and I think that we have enough worthwhile changes in Android 
> > > >>> that
> we
> > > >>> should probably do a release soon.  If possible, I would like 
> > > >>> for
> us
> > > to do
> > > >>> a 5.2.0 release with the versioning fix, and the other build 
> > > >>> script
> > > fixes
> > > >>> that have been done recently.  There's not a lot of commits, 
> > > >>> but I
> do
> > > think
> > > >>> what we do have is worthy of being released.
> > > >>>
> > > >>> What do people think?
> > > >>>
> > > >>> Joe
> > > >>>
> > > >
> > > >-
> > > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > >For additional commands, e-mail: dev-h...@cordova.apache.org
> > > >
> > >
> > >
> >
>

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

RE: [DISCUSS] Cordova-Android 5.2.0 Release

[Nikhil Khandelwal]

Support for incremental prepare (PR #295) has been merged. We should be ready 
for a release.

-Nikhil

-Original Message-
From: Joe Bowser [mailto:bows...@gmail.com] 
Sent: Thursday, May 26, 2016 2:52 PM
To: dev 
Subject: Re: [DISCUSS] Cordova-Android 5.2.0 Release

Do we have an N PR yet? I've seen the proposal, but not the PR.

On Thu, May 26, 2016 at 2:47 PM, Steven Gill  wrote:

> Can we merge the android N PR too?
>
> On Wed, May 25, 2016 at 2:50 PM, Joe Bowser  wrote:
>
> > On Wed, May 25, 2016 at 1:47 PM, Homer, Tony 
> wrote:
> >
> > > +1
> > >
> > > Would like #307 to be merged in first
> > >
> > >
> > Done! Yay for tests!
> >
> > BTW, We need to re-write those to migrate to the new Android JUnit 
> > test framework (It's more deleting code than adding).
> >
> >
> >
> >
> > > On 5/25/16, 3:31 PM, "Carlos Santana"  wrote:
> > >
> > > >+1
> > > >
> > > >- Carlos
> > > >@csantanapr
> > > >
> > > >> On May 25, 2016, at 3:08 PM, Shazron  wrote:
> > > >>
> > > >> +1
> > > >>
> > > >> Release often
> > > >>
> > > >>> On Wed, May 25, 2016 at 10:33 AM, Joe Bowser 
> > > >>> 
> > > wrote:
> > > >>>
> > > >>> Hey
> > > >>>
> > > >>> I know that we haven't done a minor release for a few months 
> > > >>> for
> > > Android,
> > > >>> and I think that we have enough worthwhile changes in Android 
> > > >>> that
> we
> > > >>> should probably do a release soon.  If possible, I would like 
> > > >>> for
> us
> > > to do
> > > >>> a 5.2.0 release with the versioning fix, and the other build 
> > > >>> script
> > > fixes
> > > >>> that have been done recently.  There's not a lot of commits, 
> > > >>> but I
> do
> > > think
> > > >>> what we do have is worthy of being released.
> > > >>>
> > > >>> What do people think?
> > > >>>
> > > >>> Joe
> > > >>>
> > > >
> > > >-
> > > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > >For additional commands, e-mail: dev-h...@cordova.apache.org
> > > >
> > >
> > >
> >
>

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

RE: Proposal: Change Android Project Directory Structure to Android Studio style

[Nikhil Khandelwal]

It sounds like you are working on a plan to remap the older directory structure 
to a new one. Will look forward to updates on the design and code for that. In 
that case our expectation is that most plugins will not break - is that 
correct? It will be great to do some compat testing with say the top plugins. 

I understand it's hard to guarantee complete compat and we need to move forward 
but breaking the entire plugin ecosystem will cause a lot of issues for 
existing Cordova developers. 

-Nikhil

-Original Message-
From: Joe Bowser [mailto:bows...@gmail.com] 
Sent: Tuesday, May 31, 2016 8:22 AM
To: dev <dev@cordova.apache.org>
Subject: Re: Proposal: Change Android Project Directory Structure to Android 
Studio style

On Fri, May 27, 2016 at 12:22 PM, Nikhil Khandelwal <nikhi...@microsoft.com>
wrote:

> As I see it, a change to the directory structure will break almost 
> every Android plugin currently out there.
>
>
I know.  However, I don't think that's a good enough reason to not do this.


> There are atleast 20K references [1] on github where people use depend 
> on the current directory structure for android: "res/xml/config.xml".
>
> Taking the example of a config.xml manipulation that will now stop working:
> https://github.com/phonegap-build/PushPlugin/blob/master/plugin.xml#L3
> 4
>
> Can you explain how source-file and other tags that reference path 
> will continue to work? Looking at your current branch [2] there are 
> not changes to path old path references in plugin.xml to new path.
>

Actually, here's the thing.  They won't.  We're going to have to fix our 
tooling so that they remap.  After working on the exploratory branch, all our 
plugin installation code is stuck in plugman and really should be handled by 
the platforms so that we can actually handle changes to Android Studio and 
Xcode.

What I'm now proposing is that by default when we specify a source file, or a 
config file without specifying a target, it by default goes to a location 
specified by the project.  That means that when you are using an Android Studio 
project, it knows that we keep the config.xml in a different location than the 
old project.  That way, if Google decides that they don't like the current 
Android Studio project structure and they decide to change things again, we're 
not stuck holding the bag for years and being stuck having to do all this work 
so that we can actually allow native developers to be able to use Cordova, 
since it's almost completely unusable to these developers currently.


>
> If the path of the file changes it will break lots of plugins and if 
> the plugins change to work with the new directory structure they will 
> not work with older versions of Cordova. Let me know if I missed some 
> part of this change which ensures most plugins for Android do not stop 
> working.
>
> [1]
> https://github.com/search?q=%22res%2Fxml%2Fconfig.xml%22+filename%3Apl
> ugin.xml=searchresults=Code=%E2%9C%93
> [2]
> https://github.com/apache/cordova-android/compare/master...infil00p:st
> udio_project_structure
>
>
> -Original Message-
> From: Joe Bowser [mailto:bows...@gmail.com]
> Sent: Tuesday, May 17, 2016 8:14 PM
> To: dev <dev@cordova.apache.org>
> Subject: Re: Proposal: Change Android Project Directory Structure to 
> Android Studio style
>
> On Tue, May 17, 2016 at 5:35 PM, Richard Knoll <rikn...@microsoft.com>
> wrote:
>
> > Does that mean the plan is to provide a mapping from old file 
> > locations to new ones? For example, if I have this in my plugin.xml:
> >
> > 
> >
> > Will the new cordova-android automatically convert the target value 
> > to the new location of "app/src/main/res/values/strings.xml"?
> >
>
>
> I'm pretty sure that config-file targets like that won't work 
> properly, but I think that source, resource and assets should.  I 
> would have added that as a resource file, since it's strings.xml.
>
>
> >
> > Thanks,
> > Richard
> >
> > -Original Message-
> > From: Joe Bowser [mailto:bows...@gmail.com]
> > Sent: Tuesday, May 17, 2016 3:51 PM
> > To: dev <dev@cordova.apache.org>
> > Subject: Re: Proposal: Change Android Project Directory Structure to 
> > Android Studio style
> >
> > @Richard: The changes to the Android files in cordova-common should 
> > allow for config-file, source-file and resource-file to work fine.  
> > I already did something similar in February, but I should have 
> > checked it in on an Cordova-Android branch instead of the other repo.
> >
> > https://github.com/infil00p/cordova-android-studio
> >
> > @Parashuram: Does this drop the JAR is libs?  I couldn't quite 

RE: Proposal: Change Android Project Directory Structure to Android Studio style

[Nikhil Khandelwal]

As I see it, a change to the directory structure will break almost every 
Android plugin currently out there.

There are atleast 20K references [1] on github where people use depend on the 
current directory structure for android: "res/xml/config.xml". 

Taking the example of a config.xml manipulation that will now stop working:
https://github.com/phonegap-build/PushPlugin/blob/master/plugin.xml#L34

Can you explain how source-file and other tags that reference path will 
continue to work? Looking at your current branch [2] there are not changes to 
path old path references in plugin.xml to new path.

If the path of the file changes it will break lots of plugins and if the 
plugins change to work with the new directory structure they will not work with 
older versions of Cordova. Let me know if I missed some part of this change 
which ensures most plugins for Android do not stop working.

[1] 
https://github.com/search?q=%22res%2Fxml%2Fconfig.xml%22+filename%3Aplugin.xml=searchresults=Code=%E2%9C%93
[2] 
https://github.com/apache/cordova-android/compare/master...infil00p:studio_project_structure


-Original Message-
From: Joe Bowser [mailto:bows...@gmail.com] 
Sent: Tuesday, May 17, 2016 8:14 PM
To: dev 
Subject: Re: Proposal: Change Android Project Directory Structure to Android 
Studio style

On Tue, May 17, 2016 at 5:35 PM, Richard Knoll 
wrote:

> Does that mean the plan is to provide a mapping from old file 
> locations to new ones? For example, if I have this in my plugin.xml:
>
> 
>
> Will the new cordova-android automatically convert the target value to 
> the new location of "app/src/main/res/values/strings.xml"?
>


I'm pretty sure that config-file targets like that won't work properly, but I 
think that source, resource and assets should.  I would have added that as a 
resource file, since it's strings.xml.


>
> Thanks,
> Richard
>
> -Original Message-
> From: Joe Bowser [mailto:bows...@gmail.com]
> Sent: Tuesday, May 17, 2016 3:51 PM
> To: dev 
> Subject: Re: Proposal: Change Android Project Directory Structure to 
> Android Studio style
>
> @Richard: The changes to the Android files in cordova-common should 
> allow for config-file, source-file and resource-file to work fine.  I 
> already did something similar in February, but I should have checked 
> it in on an Cordova-Android branch instead of the other repo.
>
> https://github.com/infil00p/cordova-android-studio
>
> @Parashuram: Does this drop the JAR is libs?  I couldn't quite tell 
> from looking at the JS code doing the installation.  If it does, that 
> won't change at all.
>
> On Tue, May 17, 2016 at 3:03 PM, Parashuram N 
> wrote:
>
> > This is an example -
> > https://github.com/ConnectSDK/Connect-SDK-Cordova-Plugin. This 
> > actually has a hook that downloads and places the source code based 
> > on the current directory structure.
> >
> > On 5/17/16, 2:53 PM, "Richard Knoll"  wrote:
> >
> > >We have a lot of plugin.xml elements that depend on the old file
> > structure. Tags like config-file, source-file, resource-file, etc. 
> > all have target elements that take arbitrary paths to project files.
> > Looking at the new project structure, it seems like most of the 
> > relevant folders have moved around. Does your proposal handle that 
> > or do plugins need to update to reflect the new structure? I figure 
> > there isn't much we can do for plugins that use hooks.
> > >
> > >Richard
> > >
> > >-Original Message-
> > >From: Joe Bowser [mailto:bows...@gmail.com]
> > >Sent: Tuesday, May 17, 2016 2:07 PM
> > >To: dev 
> > >Subject: Re: Proposal: Change Android Project Directory Structure 
> > >to
> > Android Studio style
> > >
> > >On Tue, May 17, 2016 at 2:01 PM, Parashuram N 
> > >
> > >wrote:
> > >
> > >> I think the proposal is great. Our gradle is pretty big, and it 
> > >> does make sense to just do the defaults.
> > >> +1 (personally speaking) to this – will save soo much of my time 
> > >> +as I
> > >> depend on this for my react-native-cordova-plugin adapter. Your 
> > >> changes will make life so much easier ☺
> > >>
> > >> How do the plugins break? Will plugins have to make change? In a 
> > >> way, it may make sense to do this with big changes at Google I/O 
> > >> – that way, we just have 1 breaking change, and plugin authors 
> > >> have to look at the changes just once.
> > >>
> > >
> > >Ideally they shouldn't break, but I can't guarantee that.  I do 
> > >have to
> > change how plugins are installed in the Android cordova scripts, but 
> > the cordova-common work abstracted all that out and made that easier.
> > A user who hasn't tweaked their app shouldn't notice the difference.
> > >
> > >That said, the users who have may notice stuff, and I have no idea 
> > >how
> > Crosswalk would work with this yet.  It'd be good to 

RE: [DISCUSS] Cordova-windows release

[Nikhil Khandelwal]

I agree this qualifies for a minor version bump. I feel like these are the 
inner workings of the clean command and not a very explicit contract that we 
know anyone depends on.

-Nikhil

-Original Message-
From: Jason Ginchereau [mailto:jason...@microsoft.com] 
Sent: Friday, May 27, 2016 9:26 AM
To: dev@cordova.apache.org
Subject: RE: [DISCUSS] Cordova-windows release

How is that a breaking change? Note it doesn't affect a platform-centric 
workflow.

I had expected only a minor version bump would be appropriate.


-Original Message-
From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] 
Sent: Friday, May 27, 2016 2:21 AM
To: dev@cordova.apache.org
Subject: [DISCUSS] Cordova-windows release

Hey, guys
We're planning to do a major cordova-windows v.5.0.0 release. The major version 
bump is mostly required due to changed behavior of 'clean' command which now 
wipes 'www' contents as well as build artifacts which can be considered as a 
breaking change for some users. 

Here is the list of changes to be included:
CB-7: Optimize prepare for windows platform, clean prepared files
CB-11259: Improving build output
CB-11204: Catch when SDK not present on build and give appropriate error message
CB-11156 Change default FadeSplashScreenDuration value
CB-11176 Fix windows-splashscreen compatibility with older plugin versions
CB-11139 Use PluginManager from common to install/uninstall plugins
CB-10653 Making the windows activation context complete
CB-11150 CI Error - Windows Platform - Could not find XHR config file
CB-8056 Implement splashscreen for Windows platform
CB-11066 Remove uap prefixed capabilities along with regular ones
CB-11022 Duplicate www files on plugin installtion
CB-10964 Handle build.json file starting with a BOM. This closes #166
CB-11024: Add preference to set the min UAP target version in the JSProj File

Does anyone have any reason to delay a this release? Any other patches to land? 
Any objections?
If not, I will start the vote on Monday

-
Best regards, Vladimir


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


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


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

RE: [DISCUSS] Cordova-Android 5.2.0 Release

[Nikhil Khandelwal]

+1. It will be great to get this PR merged now that cordova-common has been 
released: https://github.com/apache/cordova-android/pull/295/files

-Nikhil 

-Original Message-
From: Simon MacDonald [mailto:simon.macdon...@gmail.com] 
Sent: Wednesday, May 25, 2016 10:38 AM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Cordova-Android 5.2.0 Release

+1
On May 25, 2016 1:33 PM, "Joe Bowser"  wrote:

> Hey
>
> I know that we haven't done a minor release for a few months for 
> Android, and I think that we have enough worthwhile changes in Android 
> that we should probably do a release soon.  If possible, I would like 
> for us to do a 5.2.0 release with the versioning fix, and the other 
> build script fixes that have been done recently.  There's not a lot of 
> commits, but I do think what we do have is worthy of being released.
>
> What do people think?
>
> Joe
>

RE: Node v6 support

[Nikhil Khandelwal]

The only known issue with Node v6 and Cordova is: CB-11200.  The bug breaks 
uninstallation of plugins with custom frameworks for iOS platform, such as 
Facebook plugin.

This JIRA has been resolved in corodva-ios master. We'll need a release of 
cordova-ios and a tools release pinning that version (unless the next release 
is a patch release).

-Nikhil

-Original Message-
From: Victor Sosa [mailto:sosah.vic...@gmail.com] 
Sent: Monday, May 16, 2016 7:54 AM
To: dev@cordova.apache.org
Subject: Node v6 support

Hi Community.

Node.js v6 was released early this month 
https://github.com/nodejs/LTS#lts_schedule

When is Cordova going to support it as official runtime? Same thing that 
happened when Cordova CLI v5.x.x (don't remember the exact version) claimed 
support for Node.js v4.

Cheers!

Extended LTS version

[Nikhil Khandelwal]

I wanted to bring this to the dev list's attention: 
https://github.com/cordova/cordova-discuss/issues/39.

The idea is to have an LTS version of cordova. It might be a good idea to 
re-visit & document our release cadence as well.

-Nikhil

RE: [DISCUSS] Cordova tools release

[Nikhil Khandelwal]

We'll need a cordova-ios release to make that happen. However, cordova-ios has 
a recent regression that needs to be fixed before we make a release: 
https://github.com/apache/cordova-ios/commit/cab0baa0f7c4d789171b0147da41a85471660c85

-Nikhil

-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com] 
Sent: Thursday, May 12, 2016 2:02 PM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Cordova tools release

Do we fully support node6 now?
If we do might be good to highlight in blog post

- Carlos
@csantanapr

> On May 12, 2016, at 5:00 PM, Steven Gill  wrote:
> 
> Excellent! I shall proceed.
> 
> The website will also get updated when I do the release blog post.
> 
> Cheers,
> -Steve
> 
>> On Thu, May 12, 2016 at 12:52 PM, Mefire O.  wrote:
>> 
>> Hey Steve,
>> Telemetry has been merged in!
>> We can move forward with the release process.
>> 
>> We'll also have to initiate a docs/website release, as they host our 
>> privacy policy.
>> Raghav will help with that.
>> 
>> Thanks for your patience, All.
>> 
>> Thanks,
>> Omar Mefire
>> 
>> -Original Message-
>> From: Mefire O. [mailto:ommen...@microsoft.com]
>> Sent: Tuesday, May 10, 2016 5:25 PM
>> To: dev@cordova.apache.org
>> Subject: RE: [DISCUSS] Cordova tools release
>> 
>> I expect it to be merged in by tomorrow EOD or day Thursday morning.
>> If it's still not merged in by then, I wouldn't want to hold the 
>> release any longer.
>> 
>> Thanks,
>> Omar Mefire
>> 
>> -Original Message-
>> From: Steven Gill [mailto:stevengil...@gmail.com]
>> Sent: Tuesday, May 10, 2016 2:39 PM
>> To: dev@cordova.apache.org
>> Subject: Re: [DISCUSS] Cordova tools release
>> 
>> When do you expect to merge it in?
>> 
>>> On Tue, May 10, 2016 at 2:19 PM, Mefire O.  wrote:
>>> 
>>> I'd like to get the telemetry feature out with this release.
>>> 
>>> Thanks,
>>> Omar Mefire
>>> 
>>> -Original Message-
>>> From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com]
>>> Sent: Tuesday, May 10, 2016 12:47 AM
>>> To: dev@cordova.apache.org
>>> Subject: RE: [DISCUSS] Cordova tools release
>>> 
>>> +1
>>> 
>>> Thanks for handling cordova-common release - there is probably not 
>>> much sense in releasing it separately (as I was planning initially) 
>>> when other components also need to be released.
>>> 
>>> -
>>> Best regards, Vladimir
>>> 
>>> -Original Message-
>>> From: julio cesar sanchez [mailto:jcesarmob...@gmail.com]
>>> Sent: Tuesday, May 10, 2016 1:14 AM
>>> To: dev@cordova.apache.org
>>> Subject: Re: [DISCUSS] Cordova tools release
>>> 
>>> +1
>>> 
>>> El martes, 10 de mayo de 2016, Shazron  escribió:
>>> 
 +1
 
 On Mon, May 9, 2016 at 12:32 PM, Steven Gill 
 > wrote:
 
> Any objections or concerns?
> 
> Doing a cli, lib, plugman, common and fetch release.
> 
> -Steve
>>> 
>>> 
>>> - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>>> For additional commands, e-mail: dev-h...@cordova.apache.org
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>> For additional commands, e-mail: dev-h...@cordova.apache.org
>> 

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

RE: proposal for new core plugin to control screen orientation

[Nikhil Khandelwal]

+1. This feels like a "core" capability.

-Nikhil

-Original Message-
From: Suraj Pindoria [mailto:suraj.pindo...@yahoo.com.INVALID] 
Sent: Wednesday, May 11, 2016 9:08 AM
To: dev@cordova.apache.org
Subject: Re: proposal for new core plugin to control screen orientation

+1
I have been looking into this plugin for the last few days in order to add it 
to the PhoneGap Developer App. I think it would make a great addition to the 
core plugins and wouldn't mind volunteering to help bring it up to spec.
Regards,Suraj. 

On Tuesday, May 10, 2016 8:56 AM, "Homer, Tony"  
wrote:
 

 The proposal is to create a new core plugin that enables the user to 
dynamically control the orientation of their app.
This plugin would be based on the W3C screen-orientation spec [1].
This was originally proposed via CB-9528 [2] (which currently has 10 votes and 
16 watchers, indicating strong community interest).


There is an existing community plugin [3] that implements an older version of 
the W3C screen-orientation spec.
The author has graciously agreed to contribute this plugin to Apache Cordova.
The plan is, pending consensus, to update the existing code and then migrate it 
to a new Apache Cordova repo; required preparatory work is underway.

What do you think?  Please provide feedback!

[1] 
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fwww.w3.org%2fTR%2fscreen-orientation%2f=01%7c01%7cnikhilkh%40microsoft.com%7c6996ef6f14d14dd2dcf808d379b6f051%7c72f988bf86f141af91ab2d7cd011db47%7c1=40DTHHr2BkCO03sYSdD%2bUtWGNHF71XbIMz6B%2f8d%2bWSY%3d
[2] 
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fbrowse%2fCB-9528=01%7c01%7cnikhilkh%40microsoft.com%7c6996ef6f14d14dd2dcf808d379b6f051%7c72f988bf86f141af91ab2d7cd011db47%7c1=y6hEKuDiMfYElLI4v0KPcvivAyr1IXyyrvtw6KefTEc%3d
[3] https://github.com/gbenvenuti/cordova-plugin-screen-orientation

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


  

RE: Github issue and PR templates

[Nikhil Khandelwal]

I have submitted a PR to add a pull request to cordova-plugin-camera: 
https://github.com/apache/cordova-plugin-camera/pull/213

Please review and provide feedback. I intend to add this to all other repos.

-Nikhil

-Original Message-
From: Dmitry Blotsky [mailto:dblot...@microsoft.com] 
Sent: Thursday, February 18, 2016 6:39 PM
To: dev@cordova.apache.org
Subject: RE: Github issue and PR templates

I like the idea. I suggest starting small and expanding as necessary. Right now 
the two most important pieces of information that I think our PRs could use are:

Did you sign the ICLA? [ ] Yes / [ ] No
Related JIRA: CB-[ ]

Kindly,
Dmitry

-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com]
Sent: Thursday, February 18, 2016 5:55 PM
To: dev@cordova.apache.org
Subject: Re: Github issue and PR templates

I agree, Running tests as easy as npm install && npm run config && npm test
 :-)


On Thu, Feb 18, 2016 at 4:40 PM Nikhil Khandelwal <nikhi...@microsoft.com>
wrote:

> I think for plugins, platform name should be required as part of title 
> of the PR and commit message in addition to JIRA number.
>
> Checklist:
> [ ] Tests that were added or run for a new feature/regressions [ ] 
> Does the new feature broadly apply to multiple platforms?
>
> We probably need to make it easier for contributors to run tests for 
> plugins.
>
> -Nikhil
>
> -Original Message-
> From: Steven Gill [mailto:stevengil...@gmail.com]
> Sent: Wednesday, February 17, 2016 1:42 PM
> To: dev@cordova.apache.org
> Subject: Github issue and PR templates
>
> Cool new feature from github!
> https://github.com/blog/2111-issue-and-pull-request-templates
>
> Since we don't do issues on github, that feature isn't useful to us. 
> But providing PR templates sounds like a good idea. Just need to add a 
> PULL_REQUEST_TEMPLATE.md to the root of our repos.
>
> What type of information would we ask for from PRs?
>
> * Issue number
>
> If it is a plugin
> * which platforms
>
> Thoughts?
>

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

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

RE: [Android] Ending support for Ice Cream Sandwich?

[Nikhil Khandelwal]

+1. Let's do that!

-Nikhil

-Original Message-
From: Kerri Shotts [mailto:kerrisho...@gmail.com] 
Sent: Friday, May 6, 2016 7:58 AM
To: dev@cordova.apache.org; dev@cordova.apache.org
Subject: Re: [Android] Ending support for Ice Cream Sandwich?

+1
~Kerri
  

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

RE: [DISCUSS] CI Builds on PRs submitted for cordova plugins

[Nikhil Khandelwal]

I want to call attention to this proposal. Please help review this and provide 
feedback. It adds the critical ability to run tests using paramedic on every PR.

-Nikhil

-Original Message-
From: Sarangan Rajamanickam [mailto:saraj...@microsoft.com] 
Sent: Wednesday, April 27, 2016 5:01 PM
To: dev@cordova.apache.org
Subject: [DISCUSS] CI Builds on PRs submitted for cordova plugins

Hi All,

I have created a proposal for adding CI builds on PRs submitted for cordova 
plugins. You could find the details in this PR: 
https://github.com/cordova/cordova-discuss/pull/42. Please review the proposal 
and provide your feedback.

Thanks in advance.

Regards
Sarangan Rajamanickam

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

Re: Users mailing list

[Nikhil Khandelwal]

I’m hearing two purposes of a user list:
- Key announcements
- Self-help for users

I’m not totally convinced that slack + stack overflow are not sufficient for 
finding resources & common answers for cordova issues. Creating another channel 
will just fragment the community.

FWIW, our blog got about 50K pageviews for all blog entries (and blog listing) 
in the last month or so. That’s very low compared to over a million hits on our 
docs. I agree that we need to find better ways to reach out to users with key 
announcements. Perhaps the blog needs to be improved – write more engaging 
content, find opportunities for guest posts (cross posting – Raymond?), have an 
option to subscribe for notifications to it. We’ve added disqus to our blogs 
already – but we need to probably route the disqus comments to the “dev” list 
or slack to ensure enough people get to see it and we respond to those comments.

On a related note, we might want to consider a user list for plugin developers. 
In particular, we need to have conversations and discussions about breaking 
changes, design discussions etc. with this highly important, smaller target 
audience. There is no targeted forum for these developers currently. 

-Nikhil

On 4/29/16, 9:31 AM, "kerrisho...@gmail.com on behalf of Kerri Shotts" 
 wrote:

>Thought I'd throw in my 2¢ worth:
>
>- If a user list is created, I'll gladly participate.
>
>- Having a Cordova-branded user list could be useful from a "branding"
>perspective. The Adobe Forums are "PhoneGap" branded, and the Google Group
>is named "phonegap" (although the welcome text makes clear that it is for
>both environments). Personally, I don't have a problem with the difference
>in branding, but for newcomers, I'm sure it raises a few questions ("why am
>I going to a phonegap group for a cordova question?").
>
>- As for the blog, as much as I like that the announcements show up there,
>not everyone is into feed readers (for whatever reason. I'm not one of of
>them -- I'm a feedly addict). For those who prefer email subscriptions, a
>user list for announcements would be handy.
>
>- Google Group is still going, but activity is falling off as people
>discover the Adobe Forums. The group may need to become r/o at some point
>in the future, especially if use declines to next-to-nothing.
>
>- Getting people to read is always the catch -- they just don't. Sometimes
>I'm guilty of the same. Human nature, I suspect!
>
>​~ Kerri​
>
>
>On Fri, Apr 29, 2016 at 9:26 AM, julio cesar sanchez > wrote:
>
>> ​...
>>

RE: [Android] Need a solution to config.xml and AndroidManifest.xml feature requests

[Nikhil Khandelwal]

Oh great! I have not taken a close look at the implementation itself. Perhaps 
you already had some of this in mind.

As for the syntax for changing attributes, I would recommend something like 
this:



Also, we should always prioritize config.xml edits over plugin.xml (giving the 
end developer the full control). In case of conflicts, between plugins & 
config.xml we should warn and mention which one we picked (config.xml)

Thanks,
Nikhil

-Original Message-
From: Karen Tran [mailto:ktop...@gmail.com] 
Sent: Wednesday, April 20, 2016 12:40 PM
To: dev@cordova.apache.org
Subject: Re: [Android] Need a solution to config.xml and AndroidManifest.xml 
feature requests

Hi,

I made an attempt at the functionality of being able to add attributes with the 
config-file tag. It's not completed yet, but I wanted to get some review before 
I proceed.
With my changes, you can add an attribute through the config-file tag in 
plugin.xml when the plugin is added, and when the plugin is removed, the 
attribute will get removed.
https://github.com/ktop/cordova-lib/tree/cb-11023

This is what the tag looks like:
**
*android:name="MyApplication"*

**

Added *attr* attribute to let Config-File know that we want to add an 
attribute. Default should be false and will expect an element rather than an 
attribute.

One issue I have is that it can only add 1 attribute per config-file tag.
This is the part that I still need to fix.

Can someone review what I have so far?

Thanks,
Karen

On Tue, Apr 5, 2016 at 6:54 PM, Simon MacDonald 
wrote:

> I would love to but I have a few other things to handle first. If 
> someone else picks it up before I get to it then that's cool with me.
>
>
> Simon Mac Donald
> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fhi.im%
> 2fsimonmacdonald=01%7c01%7cnikhilkh%40microsoft.com%7c379bf4c2dae
> 4454ee13008d369539a2b%7c72f988bf86f141af91ab2d7cd011db47%7c1=TvJ
> lf2LDyl%2bfSbRMDPjmLe%2fMBQf7PnAzRao5QANRrH4%3d
>
> On Tue, Apr 5, 2016 at 6:51 PM, Carlos Santana 
> wrote:
>
> > Oh so it means you don't want to work on the code :-p
> >
> >
> > On Tue, Apr 5, 2016 at 6:50 PM Simon MacDonald <
> simon.macdon...@gmail.com>
> > wrote:
> >
> > > Thanks, I put a watch on that.
> > >
> > >
> > > Simon Mac Donald
> > > https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fhi
> > > .im%2fsimonmacdonald=01%7c01%7cnikhilkh%40microsoft.com%7c379
> > > bf4c2dae4454ee13008d369539a2b%7c72f988bf86f141af91ab2d7cd011db47%7
> > > c1=TvJlf2LDyl%2bfSbRMDPjmLe%2fMBQf7PnAzRao5QANRrH4%3d
> > >
> > > On Tue, Apr 5, 2016 at 6:48 PM, Carlos Santana 
> > > 
> > > wrote:
> > >
> > > > Simon, I was not able to find a JIRA, I created a new JIRA [1] 
> > > > to
> > enhance
> > > > plugin.xml to allow  to add attributes
> > > >
> > > > [1]: 
> > > > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2
> > > > fissues.apache.org%2fjira%2fbrowse%2fCB-11023=01%7c01%7cnik
> > > > hilkh%40microsoft.com%7c379bf4c2dae4454ee13008d369539a2b%7c72f98
> > > > 8bf86f141af91ab2d7cd011db47%7c1=qdtAQlq84gu4iot23V%2bdCyw4
> > > > yAtardggCzFXJutYDzU%3d
> > > >
> > > >
> > > > On Wed, Mar 23, 2016 at 11:30 AM Simon MacDonald < 
> > > > simon.macdon...@gmail.com>
> > > > wrote:
> > > >
> > > > > Seems like editing attributes in a config-file is a wanted
> > enhancement.
> > > > Do
> > > > > we have a JIRA for it?
> > > > >
> > > > >
> > > > > Simon Mac Donald
> > > > > https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%
> > > > > 2fhi.im%2fsimonmacdonald=01%7c01%7cnikhilkh%40microsoft.c
> > > > > om%7c379bf4c2dae4454ee13008d369539a2b%7c72f988bf86f141af91ab2d
> > > > > 7cd011db47%7c1=TvJlf2LDyl%2bfSbRMDPjmLe%2fMBQf7PnAzRao5Q
> > > > > ANRrH4%3d
> > > > >
> > > > > On Tue, Mar 22, 2016 at 5:09 PM, Carlos Santana <
> > csantan...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > I agree to enable config.xml to be able to set or override 
> > > > > > using config-file (i.e. any xml file including strings.xml) 
> > > > > > I also think that adding support in config.xml and 
> > > > > > plugin.xml to
> > edit
> > > > > > attributes is very helpful, this is exactly what we are 
> > > > > > doing for
> > one
> > > > of
> > > > > > our plugin to add the attribute android:name for 
> > > > > > 
> and
> > it
> > > > > was a
> > > > > > pain, and I think we still have problems doing it from 
> > > > > > before_plugin_install hook, it would be easier from 
> > > > > > plugin.xml
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Tue, Mar 22, 2016 at 10:55 AM julio cesar sanchez < 
> > > > > > jcesarmob...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Yes, Simon, that's my opinion, and we should show the
> conficting
> > > > values
> > > > > > and
> > > > > > > the id of the plugin with the conficting values so the 
> > > > > > > user
> knows
> > > he
> > > > > has
> > > > > > to
> > > > > > > change the values on 

RE: Apache Con NA May 11-13 in Vancouver, BC

[Nikhil Khandelwal]

As far as I am aware, no one from Microsoft Cordova team will be able to make 
it.

+1 for a google hangout.

-Nikhil

-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com] 
Sent: Friday, April 15, 2016 2:47 PM
To: dev@cordova.apache.org
Subject: Re: Apache Con NA May 11-13 in Vancouver, BC

No one from IBM MobileFirst going we don't have travel budget :-(

A Cordova Face 2 Face might be useful and there might be a better chance to get 
approval than Apache Con, also we stop doing the Monthly Hangouts I think they 
we're useful and community builder. 

- Carlos
@csantanapr

> On Apr 15, 2016, at 4:13 PM, Simon MacDonald  
> wrote:
> 
> I decided not to go as ApacheCon is sandwiched between two other trips 
> I need to make in May.
> 
> That being said it would be nice to get another Cordova Face 2 Face 
> sometime in the next few months.
> 
> Simon Mac Donald
> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fhi.im%
> 2fsimonmacdonald=01%7c01%7cnikhilkh%40microsoft.com%7c389d0b8fb6c
> 3452c75db08d365776f66%7c72f988bf86f141af91ab2d7cd011db47%7c1=iAJ
> Ahhd40KZLswjpdffkO6eXUw37GtP4O8iiK5%2bh1bM%3d
> 
>> On Fri, Apr 15, 2016 at 3:35 PM, Steven Gill  wrote:
>> 
>> Hey Tony,
>> 
>> Due to the lack of committer response and the upcoming PGDAY EU 
>> event, I ended up not submitting a talk. I don't believe anyone from 
>> the Adobe Cordova team is going.
>> 
>> 
>> 
>>> On Fri, Apr 15, 2016 at 6:21 AM, Homer, Tony  wrote:
>>> 
>>> I haven't seen any discussion about this lately - is anyone going?
>>> I think I'm going to go and I need to book my travel today.
>>> 
>>> I was in Austin at the same time as ApacheCon and dropped in to meet 
>>> up with some of you but I wasn't an attendee.
>>> How is the conference itself?
>>> 
>>> This year there is one Cordova session on the schedule (Advanced 
>>> Apache Cordova - Hazem Saleh, IBM[1]).
>>> It would be nice to meet up again this year.
>>> 
>>> [1]
>> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fapach
>> econ2016.sched.org%2fevent%2f6OIr%2fadvanced-apache-cordova-hazem-sal
>> eh-ibm=01%7c01%7cnikhilkh%40microsoft.com%7c389d0b8fb6c3452c75db
>> 08d365776f66%7c72f988bf86f141af91ab2d7cd011db47%7c1=qX14O%2f%2f
>> PfvkmE%2fAs5480huFjB%2b43aIWnDuIrmi8B7A4%3d
>>> 
>>> Tony
>>> 
>>> 
>>> 
>>> 
 On 1/20/16, 1:48 AM, "Simon MacDonald" 
>>> wrote:
>>> 
 Yup, that was exactly what I was thinking. Check in see if we've 
 made progress on what we talked about last time.
 
 
 Simon Mac Donald
 https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fhi.
 im%2fsimonmacdonald=01%7c01%7cnikhilkh%40microsoft.com%7c389d0
 b8fb6c3452c75db08d365776f66%7c72f988bf86f141af91ab2d7cd011db47%7c1&
 sdata=iAJAhhd40KZLswjpdffkO6eXUw37GtP4O8iiK5%2bh1bM%3d
 
 On Tue, Jan 19, 2016 at 10:05 PM, Parashuram N 
 
 wrote:
 
> Like another Cordova Face to Face ? It would be almost 6 months 
> since
>> we
> had the last one.
> 
> -Original Message-
> From: Simon MacDonald [mailto:simon.macdon...@gmail.com]
> Sent: Tuesday, January 19, 2016 6:02 PM
> To: dev@cordova.apache.org
> Subject: Re: Apache Con NA May 11-13 in Vancouver, BC
> 
> I would be interested in going as well. Might be an easier sell if 
> we could schedule a Cordova check up around the same time.
> 
> Simon Mac Donald
>> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fhi.im
>> %2fsimonmacdonald=01%7c01%7cpanarasi%40microsoft.com%7c2adb8eb8a
>> cd348e2632108d3213dc71f%7c72f988bf86f141af91ab2d7cd011db47%7c1=
>> OSg6OMGtiPCppvOA4TuM5hv%2fjkfa8mqcyk1WqT8VSn4%3d
> 
> On Tue, Jan 19, 2016 at 4:20 PM, Anis KADRI 
>>> wrote:
> 
>> I'd be down to go. I went last year and our project had a few 
>> talks but still was super under represented so everyone that can 
>> make it should go I think.
>> 
>> On Tue, Jan 19, 2016 at 11:49 AM Steven Gill <
>> stevengil...@gmail.com>
>> wrote:
>> 
>>> I'm planning on going but it seems i'm the only one so far.
>>> 
>>> On Tue, Jan 19, 2016 at 11:23 AM, Joe Bowser 
> wrote:
>>> 
 As usual, I'm not going to be attending this conference.  I'm 
 pretty
>> sure
 I'm banned from attending this.
 
 On Tue, Jan 19, 2016 at 11:16 AM, Ryan J. Salva 
 
 wrote:
 
> If we can get critical mass among other committers, I'd love
>> to
> head
>> up
 to
> Vancouver for a few days. Without other Cordova committers 
> attending,
>>> I'm
> not sure I could justify attending solo.
> 
> 
> -Original Message-
> From: Steven Gill 

RE: Roadmap for next few weeks - Microsoft - April Edition

[Nikhil Khandelwal]

Yes, I noticed these updates too. I plan to reach out to Eddy to see if we can 
consolidate fixes into one github repo here[1]. We're fixing Windows 
implementation in that repo.

[1]: https://github.com/phonegap/phonegap-plugin-barcodescanner

-Nikhil

-Original Message-
From: julio cesar sanchez [mailto:jcesarmob...@gmail.com] 
Sent: Tuesday, April 12, 2016 5:36 AM
To: dev@cordova.apache.org
Subject: Re: Roadmap for next few weeks - Microsoft - April Edition

Hello Parashuram.
I find your mails useful.

About the BarcodeScanner plugin, this weekend I saw that Eddy updated one, not 
sure if that's the same that you are planning to work on 
https://github.com/Telerik-Verified-Plugins/BarcodeScanner


2016-04-07 20:46 GMT+02:00 Parashuram N :

> Hey folks,
>
> Last month, we sent out a list of things that the team at Microsoft 
> was working on, for the Apache Cordova project. You can find that list 
> here - 
> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fapache
> .markmail.org%2fthread%2flqvfduev3ib2ob62=01%7c01%7cnikhilkh%40mi
> crosoft.com%7c1c41944c643c4f1609e008d362cf0bdb%7c72f988bf86f141af91ab2
> d7cd011db47%7c1=aZpq9sodfdnTZHhgwEL6Gjz347feowY9Zz2%2f3R%2b%2fUH
> 0%3d
>
> We made a lot of progress, and I wanted to keep up the cadence, 
> telling people what we plan to work on. I am hoping that with this 
> list available, folks can tell us if there are interesting things we 
> should look at, or even better – join us on working on all the fun stuff.
>
> From last week
> 
> Last week, most of our focus was on making documentation better. We 
> made some good progress on that, and now have an improved look for the 
> documentation. We also started adding much more detailed examples to 
> our plugins so that anyone getting started with plugins could simply 
> copy the examples and see them in action.
> We worked on the splash screen and camera bugs, and have closed a 
> large number. Many folks told us that plugins bugs are a cause of 
> concern, and we would like to cause a dent in that bug debt.
>
>
> In the near Future
> ===
> Cordova’s power it its community and I think that we would like to 
> encourage more people in making Cordova better. We are looking at 
> building a system to run tests when someone submits a PR – a method 
> that most open source projects follow to easily respond to pull 
> request. We would like to continue fixing bugs on Camera plugins.
> We would also like to switch gears a little bit an focus on the 
> phonegap barcode scanner plugin, and the phonegap push plugin. 
> Typically, we are looking to add features like background support for 
> Windows in the push plugin, android M support in Barcode scanner, etc. 
> While these plugins are not core Cordova plugins, these are super 
> popular and people have even asked that they be core plugins !
> We would also like to work on things like Plugin compatibility when 
> folks update their platforms, etc.
>
>
> P.S: Please do let us know if these emails from us are useful and if 
> we should continue sending them. Would also love to hear what you fine 
> folks are working on, in the near future :)
>

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

RE: Publishing the AAR after the next release of Cordova

[Nikhil Khandelwal]

This seems useful.

I'm guessing publishing the AAR requires us to establish a release process for 
it? Are you planning to document the guidelines for releasing, signing, 
building & versioning of this?  Do you propose - every time cordova-android is 
released we well release AAR as well? Or this is an experiment and we will see 
download numbers before we go full throttle have this be a supported way to 
consume cordova-android as AAR.

So far we have only published node modules and all of our release process 
revolves around this and is well documented on cordova-coho repo.

-Nikhil

-Original Message-
From: Jason Ginchereau [mailto:jason...@microsoft.com] 
Sent: Friday, April 8, 2016 3:39 PM
To: dev@cordova.apache.org
Subject: RE: Publishing the AAR after the next release of Cordova

+1
This will make it much easier to develop and unit-test plugins as a 
self-contained lib project.

-Original Message-
From: julio cesar sanchez [mailto:jcesarmob...@gmail.com]
Sent: Friday, April 8, 2016 12:43 PM
To: dev@cordova.apache.org
Subject: Re: Publishing the AAR after the next release of Cordova

+1 to adding it

El viernes, 8 de abril de 2016, Joe Bowser  escribió:

> BTW: I contacted asfinfra to be added to the ASF org on BinTray, so 
> we'll see how that goes.
>
> On Fri, Apr 8, 2016 at 11:31 AM, Joe Bowser  > wrote:
>
> > Hey
> >
> > So, here's something that I want to put on the dev list before we do 
> > it, which is that for the next release of Apache Cordova, we publish 
> > an AAR
> on
> > JCenter/BinTray and/or MavenCentral/Sonatype with the new release.
> >
> > Basically, this is a convenience package and we could technically do 
> > it now, but I want to make sure that I'm above board with this so 
> > that
> there's
> > no "WTF? You're doing something wrong" thing that happens here that 
> > seems to constantly happen.
> >
> > What do people think about adding a cordova-android AAR to jcenter 
> > next release?
> >
> > Joe
> >
>
B CB  [  
X  ܚX KK[XZ[
 ] ][  X  ܚX P ܙݘK \X K ܙ B  ܈Y][ۘ[  [X[  K[XZ[
 ] Z[ ܙݘK \X K ܙ B

RE: cordova-plugin-remote-inject release

[Nikhil Khandelwal]

There are some docs here: 
1. 
http://cordova.apache.org/docs/en/latest/guide/hybrid/plugins/index.html#publishing-plugins
2. 
http://cordova.apache.org/docs/en/latest/guide/hybrid/plugins/index.html#integrating-with-plugin-search

-Nikhil

-Original Message-
From: Brad Reynolds [mailto:bradleyja...@gmail.com] 
Sent: Thursday, April 7, 2016 9:19 AM
To: dev@cordova.apache.org
Subject: Re: cordova-plugin-remote-inject release

Will do.  Thanks for the pointer.

On Thu, Apr 7, 2016 at 11:13 AM, Shazron  wrote:

> Hi,
> Check out the official plugins, they have a package.json which is the 
> npm package format for publishing to their registry. Most plugins 
> would publish to that so users can just install a plugin by name.
>
> On Thursday, April 7, 2016, Brad Reynolds  wrote:
>
> > If there's an official way to release a plugin let me know but I 
> > just pushed a plugin we developed to github.  It allows for a 
> > cordova app to inject cordova into a remote site.  This allows us to 
> > have a cordova app with native integration and a mobile app for 
> > older devices and platforms
> we
> > don't support in app form.
> >
> > https://github.com/TruckMovers/cordova-plugin-remote-injection
> >
> > -bradr
> >
>

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

RE: [DISCUSS] cordova-ios release

[Nikhil Khandelwal]

I noticed there is an issue with ios-deploy/cordova-ios & Xcode 7.3. This seems 
fairly high priority: CB-10962.

If the fix/workaround happens to be in cordova-ios - we might have to do 
another release or add it to this release.

-Nikhil

-Original Message-
From: Shazron [mailto:shaz...@gmail.com] 
Sent: Tuesday, April 5, 2016 12:17 PM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] cordova-ios release

When I do a "cordova run --device" and I don't have ios-deploy installed, I 
don't get the warning anymore to install it, just a "Error: spawn ios-deploy 
ENOENT". Not sure when this behaviour changed. Don't think it should stall the 
release though.

On Tue, Apr 5, 2016 at 9:33 AM, Edna Y Morales  wrote:

> Thanks, Mefire!
>
> So there is an issue with the archive that I published on dist/dev. I 
> don't see the issue when I install from git so it must be something in 
> the packaging that I'll need to investigate. I'll close the vote as 
> Failed, republish and restart the vote.
>
> Thanks,
> *Edna Morales*
>
> [image: Inactive hide details for "Mefire O." ---04/04/2016 02:02:29 
> PM---LGTM! Thanks,]"Mefire O." ---04/04/2016 02:02:29 PM---LGTM! 
> Thanks,
>
> From: "Mefire O." 
> To: "dev@cordova.apache.org" 
> Date: 04/04/2016 02:02 PM
> Subject: RE: [DISCUSS] cordova-ios release
> --
>
>
>
> LGTM!
>
> Thanks,
> Mefire
>
> From: Edna Y Morales [mailto:eymor...@us.ibm.com 
> ]
> Sent: Monday, April 4, 2016 10:47 AM
> To: dev@cordova.apache.org
> Subject: Re: [DISCUSS] cordova-ios release
>
>
> Can someone review the blog post?
> https://github.com/apache/cordova-docs/pull/571
>
> Thanks,
> Edna Morales
>
> [Inactive hide details for Shazron ---03/30/2016 08:28:03 PM---Thanks 
> Edna
> - appreciated :) On Wed, Mar 30, 2016 at 8:15 AM, Edn]Shazron 
> ---03/30/2016
> 08:28:03 PM---Thanks Edna - appreciated :) On Wed, Mar 30, 2016 at 
> 8:15 AM, Edna Y Morales 
>  >> w
>
> From: Shazron  >>
> To: "dev@cordova.apache.org >"  mailto:dev@cordova.apache.org >>
> Date: 03/30/2016 08:28 PM
> Subject: Re: [DISCUSS] cordova-ios release
>
> 
>
>
>
> Thanks Edna - appreciated :)
>
> On Wed, Mar 30, 2016 at 8:15 AM, Edna Y Morales  mailto:eymor...@us.ibm.com >> wrote:
>
> > Hi,
> >
> > I'd like to drive the release for cordova-ios 4.1.1. Does anyone 
> > have any oppositions or any reason to wait?
> >
> > Thanks,
> > *Edna Morales*
> >
> > [image: Inactive hide details for Edna Y Morales---03/24/2016 
> > 09:41:54 AM---bump to this discussion since cordova-common has been 
> > relea]Edna Y
> > Morales---03/24/2016 09:41:54 AM---bump to this discussion since 
> > cordova-common has been released Thanks,
> >
> > From: Edna Y Morales/Durham/IBM@IBMUS
> > To: dev@cordova.apache.org >
> > Date: 03/24/2016 09:41 AM
> > Subject: Re: [DISCUSS] cordova-ios release
> > --
> >
> >
> >
> > bump to this discussion since cordova-common has been released
> >
> > Thanks,
> > *Edna Morales*
> >
> > Shazron ---03/18/2016 10:34:07 PM---Another issue, the bundled 
> > ios-sim should be updated: 
> > *https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fis
> > sues.apache.org%2fjira%2fbrowse%2fCB-10912*=01%7c01%7cnikhilkh%
> > 40microsoft.com%7c4a29ffd994df47e66dcf08d35d86fc89%7c72f988bf86f141a
> > f91ab2d7cd011db47%7c1=hWsxSWxXwjFcl%2ftP3XY04Emzg%2bnEgt6xN8MW
> > 9ghN0uU%3d 
> >  > sues.apache.org%2fjira%2fbrowse%2fCB-10912=01%7c01%7cnikhilkh%4
> > 0microsoft.com%7c4a29ffd994df47e66dcf08d35d86fc89%7c72f988bf86f141af
> > 91ab2d7cd011db47%7c1=gIwwkud1HusezoWEVChconGHAfe96DyiSPnYW6xRm
> > No%3d<
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissue
> s.apache.org%2fjira%2fbrowse%2fCB-10912=01%7c01%7commenjik%40micr
> osoft.com%7c245cd1554777444c794c08d35cb10aae%7c72f988bf86f141af91ab2d7
> cd011db47%7c1=b2DfQhpWhLbsxXZEoWdT9hEPte9ex2zshJndNU8k0F4%3d
> >>
> >
> > From: Shazron  >>
> > To: "dev@cordova.apache.org >"  mailto:dev@cordova.apache.org >>
> > Date: 03/18/2016 10:34 PM
> > Subject: Re: [DISCUSS] cordova-ios release
> > --
> >
> >
> >
> > Another issue, the bundled ios-sim should be updated:
> > *https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fis
> > 

RE: Simplifying cordova-cli README

[Nikhil Khandelwal]

I don't fully follow what about --template I should add? Could you elaborate? 
Feel free to comment on the PR and we can have more follow up conversations on 
github.

-Nikhil

-Original Message-
From: Tommy Williams [mailto:to...@devgeeks.org] 
Sent: Thursday, March 10, 2016 7:33 PM
To: dev@cordova.apache.org
Subject: Re: Simplifying cordova-cli README

Might want to add the --template stuff?




> On 11 Mar 2016, at 1:31 PM, Carlos Santana <csantan...@gmail.com> wrote:
> 
> Thanks Nikhil this looks very clean now
> 
> +1
> 
> - Carlos
> @csantanapr
> 
>> On Mar 10, 2016, at 8:22 PM, Nikhil Khandelwal <nikhi...@microsoft.com> 
>> wrote:
>> 
>> Our cordova-cli readme has become super long & not been maintained over the 
>> years. It repeats a lot of content from the docs. I have simplified it 
>> significantly by linking to relevant getting started, filing issues, 
>> contribution etc. sections that are part of our website. This should help 
>> maintenance as we do not repeat ourselves. However, there is a loss of some 
>> inline content.
>> 
>> Please review and comment on this PR: 
>> https://github.com/apache/cordova-cli/pull/240/files
>> 
>> -Nikhil
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
> 


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

Simplifying cordova-cli README

[Nikhil Khandelwal]

Our cordova-cli readme has become super long & not been maintained over the 
years. It repeats a lot of content from the docs. I have simplified it 
significantly by linking to relevant getting started, filing issues, 
contribution etc. sections that are part of our website. This should help 
maintenance as we do not repeat ourselves. However, there is a loss of some 
inline content.

Please review and comment on this PR: 
https://github.com/apache/cordova-cli/pull/240/files

-Nikhil

RE: mobilespec problems with ios??

[Nikhil Khandelwal]

This is a regression in Node 5.7.0 that they fixed as part of Node 5.7.1:

https://issues.apache.org/jira/browse/CB-10675
https://github.com/nodejs/node/blob/v5.7.1/CHANGELOG.md

Move to Node 5.7.1

-Nikhil

-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com] 
Sent: Wednesday, March 9, 2016 2:26 PM
To: dev@cordova.apache.org
Subject: Re: mobilespec problems with ios??

Don't think so because it works on android

I think is related on processing the confit.xml during prepare to do add the 
ATS white list to Info.plist

On Wed, Mar 9, 2016 at 5:19 PM Shazron  wrote:

> Not sure if this is related:
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissue
> s.apache.org%2fjira%2fbrowse%2fCB-10718=01%7c01%7cnikhilkh%40micr
> osoft.com%7ccf4e3a7a448b48cc578908d34869df77%7c72f988bf86f141af91ab2d7
> cd011db47%7c1=wT0l9UPpAypXOm%2bturcbbkqgQZEWCiQfmDfYzYtILrQ%3d
>
> On Wed, Mar 9, 2016 at 2:00 PM, Carlos Santana 
> wrote:
> > I'm having problems creating a mobilespec app using ios platform, 
> > anyone else have tried latetly
> >
> >  $ node cordova-mobile-spec/createmobilespec/createmobilespec.js 
> > --ios --global --globalplugins -d Creating project. Using globally 
> > installed tools, downloadable platforms and plugins, and local 
> > mobile-spec.
> > To clone needed repositories:
> >   ./cordova-coho/coho repo-clone -r mobile-spec To update all 
> > repositories:
> >   ./cordova-coho/coho repo-update -r mobile-spec Creating project 
> > mobilespec...
> > Creating a new cordova project.
> > Adding platforms...
> > Adding Platform: ios
> > platformArg: cordova ios
> > Executing "before_platform_add"  hook for all plugins.
> > No version supplied. Retrieving version from config.xml...
> > Platform files for "ios" previously downloaded not from npm. Using 
> > that copy.
> > Adding ios project...
> > PlatformApi successfully found for platform ios iOS project created 
> > with cordova-ios@4.0.1 Executing "before_prepare"  hook for all 
> > plugins.
> > Searching PlatformJson files for differences between project vs. 
> > platform installed plugins No differences found between project and 
> > ios platform. Continuing...
> > Generating config.xml from defaults for platform "ios"
> > Error: TypeError: Cannot read property 'indexOf' of null
> > at parseWhitelistUrlForATS
> >
> (/Users/csantana23/Documents/dev/cordova/mobilespec/platforms/ios/cord
> ova/lib/prepare.js:448:26)
> > at
> >
> /Users/csantana23/Documents/dev/cordova/mobilespec/platforms/ios/cordo
> va/lib/prepare.js:400:19
> > at Array.reduce (native)
> > at processAccessAndAllowNavigationEntries
> >
> (/Users/csantana23/Documents/dev/cordova/mobilespec/platforms/ios/cord
> ova/lib/prepare.js:399:6)
> > at writeATSEntries
> >
> (/Users/csantana23/Documents/dev/cordova/mobilespec/platforms/ios/cord
> ova/lib/prepare.js:488:14)
> > at updateProject
> >
> (/Users/csantana23/Documents/dev/cordova/mobilespec/platforms/ios/cord
> ova/lib/prepare.js:148:15)
> > at
> >
> /Users/csantana23/Documents/dev/cordova/mobilespec/platforms/ios/cordo
> va/lib/prepare.js:47:16
> > at _fulfilled
> >
> (/Users/csantana23/Documents/dev/cordova/mobilespec/platforms/ios/cord
> ova/node_modules/q/q.js:787:54)
> > at self.promiseDispatch.done
> >
> (/Users/csantana23/Documents/dev/cordova/mobilespec/platforms/ios/cord
> ova/node_modules/q/q.js:816:30)
> > at Promise.promise.promiseDispatch
> >
> (/Users/csantana23/Documents/dev/cordova/mobilespec/platforms/ios/cord
> ova/node_modules/q/q.js:749:13)
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

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

RE: [PROPOSAL] 'cordova platform update' alias for rm, add in cordova-ios

[Nikhil Khandelwal]

In Visual Studio, we have a feature similar to "merges" to allow users to 
override content of platform folder. We use hooks to copy the contents of the 
folder to the platforms directory. Other than that VS does consider platforms/ 
directory a build artifact and often ends up deleting it on behalf of the user 
- especially when cordova CLI version is changed.

Perhaps we can add a similar feature to cordova CLI, to allow overrides of 
certain files and move to having platforms/ as a true build artifact.

Thanks,
Nikhil

-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com] 
Sent: Tuesday, March 8, 2016 3:16 PM
To: dev@cordova.apache.org
Subject: Re: [PROPOSAL] 'cordova platform update' alias for rm, add in 
cordova-ios

I was never a fan of the "platform update" command since it was not fully 
tested across the board.
like all the permutations possible to/from upgrade. meaning going for very old 
like 3.6 to 5.1

If we do this I think it will break a lot of people that got used to changing 
files inside platform/ios/ in terms of changing XCode settings in pbxproj like:
- use story board to launch app to be able to support ipad pro
- some initialization code in AppDelegate
- Any native code they added like NativeUI to mix web and native
- Changes to StoryBoard to adjust webview inside native view
- Build and Signing settings in project or target in XCode
- Installation of cocoapods
- Xcode Build phases scripts

Meaning that they will need to restore or generate all this things with hooks 
or plugins.

I know that Darryl Pogue and Tommy have  projects where they can successfully 
treat platfforms folder as 100% build artifact that they can throw away. But to 
get there is not super easy

"platform update ios" has being scoped to only touch the CordovaLib xcode 
project, leaving the app xcode project not touched that's why it's being safe 
all along

What was the root cause of the recent problems with 4.1.0 for update?

Maybe we can restrict update command to major version,  meaning going from 4.x 
to 4.x is OK but from 3.x to 4.x is not OK.

In the current release of the IBM MobileFirst, were we have a CLI to wrap 
cordova commands we had a "$ mfp cordova platform update"
We took a backup of the platform folder and create a zip with a timestamp (like 
ios_1457477724404.zip) We did this just in case the command was destructive and 
user didn't lost files just in case they didn't have all files checked-in/backup

So doing a backup would be good if we move forward with this destructive action 
of doing a platform remove


On Tue, Mar 8, 2016 at 5:36 PM So, Byoungro  wrote:

> I second that. +1
>
> Byoungro So
> SSG / DPD / Mobile Computing and Compilers Intel Corporation
>
> From: Anis KADRI >
> Reply-To: "dev@cordova.apache.org" < 
> dev@cordova.apache.org>
> Date: Tuesday, March 8, 2016 at 2:34 PM
> To: "dev@cordova.apache.org" < 
> dev@cordova.apache.org>
> Subject: Re: [PROPOSAL] 'cordova platform update' alias for rm, add in 
> cordova-ios
>
> I support this as well. Real updates never work. Better to remove/add.
>
> On Tue, Mar 8, 2016 at 12:04 PM Steven Gill  > wrote:
>
> I would also like to see this happen. Would this cause problems if we 
> did this for other platforms?
>
> On Tue, Mar 8, 2016 at 11:55 AM, Shazron > wrote:
>
> > See:
> > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fiss
> > ues.apache.org%2fjira%2fbrowse%2fCB-10775=01%7c01%7cnikhilkh%40
> > microsoft.com%7c0f81ee3188ce4f6de3cf08d347a797a4%7c72f988bf86f141af9
> > 1ab2d7cd011db47%7c1=Yn8Lqnh4gBDOe5996%2bQKvpZfI308xq%2fO73BUD1
> > U%2b7xI%3d
> >
> > Problem:
> > For cordova-ios, "cordova platform update" does its own thing, which 
> > causes problems.
> >
> > Proposal:
> > Change "cordova platform update ios@version" to be basically an 
> > alias
> for:
> > "cordova platform rm ios"
> > "cordova platform add ios@version"
> >
> > 
> > - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org dev-unsubscr...@cordova.apache.org>
> > For additional commands, e-mail: dev-h...@cordova.apache.org dev-h...@cordova.apache.org>
> >
> >
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>

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

RE: Edit to Edit on Github for Docs

[Nikhil Khandelwal]

+1 for trying "Edit on Github" - anything that _may_ increase contributions to 
the docs is welcome. :)

-Nikhil

-Original Message-
From: Shazron [mailto:shaz...@gmail.com] 
Sent: Tuesday, March 8, 2016 10:26 AM
To: dev@cordova.apache.org
Subject: Re: Edit to Edit on Github for Docs

I'm ambivalent. "Edit" is concise, and I would think most are curious enough to 
just click and see?

On Tue, Mar 8, 2016 at 8:50 AM, Carlos Santana  wrote:
> The other day I was looking like crazy the doc source code that 
> corresponded to the page that a user was asking here in dev list where 
> was the source code, so I assume he also didn't see the "Edit"
>
> Then someone pointed out there is an "Edit" link/button at the top 
> right side of each page.
>
> Then I saw another website, can't remember now, but they had "Edit on 
> Github" and having the "on Github" capture my attention.
>
> What you guys think about change it from "Edit" to "Edit on Github" is 
> that a good change or it's just me

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


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

RE: Can we please kill the Battery Plugin on Android

[Nikhil Khandelwal]

What's our deprecation policy? Should we log a deprecation message before 
remove this support. What alternatives do Cordova developers have - are there 
other plugins which provide the equivalent functionality - perhaps with a 
better API - as opposed to polling events every 1% battery drop.

-Nikhil

-Original Message-
From: Shazron [mailto:shaz...@gmail.com] 
Sent: Monday, March 7, 2016 5:27 PM
To: dev@cordova.apache.org
Subject: Re: Can we please kill the Battery Plugin on Android

+1
If no one has concerns by the end of the week, I'd say we would have lazy 
consensus and you can delete the Android part of the plugin (maybe prep the PR 
now)

On Mon, Mar 7, 2016 at 12:12 PM, Joe Bowser  wrote:
> Hey
>
> Once again, I ran into someone using the Battery Plugin that actively 
> kills the Battery on Android, and can we please discourage people from 
> using this very broken plugin that we have no ability or intention of fixing?
>
> The reason I don't want to fix it because the browser already supports 
> it on the latest versions of Chromium, and because it's impossible to 
> fix without changing the API entirely.  We really need to kick this 
> harmful plugin to the curb so that people stop making applications 
> that drain the battery of their devices.
>
> I know that we've talked about it at length, but I don't ever remember 
> us coming to a conclusion regarding killing the battery plugin on Android.
>
> Any thoughts?
>
> Joe

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

RE: DISCUSS cordova-paramedic

[Nikhil Khandelwal]

Thanks, Jesse!

-Nikhil

-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com] 
Sent: Friday, March 4, 2016 1:58 PM
To: dev@cordova.apache.org
Subject: Re: DISCUSS cordova-paramedic

+1 Jesse for the contribution

On Fri, Mar 4, 2016 at 4:01 PM Jesse  wrote:

> Repo created here:
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgit-w
> ip-us.apache.org%2frepos%2fasf%3fp%3dcordova-paramedic.git=01%7c0
> 1%7cnikhilkh%40microsoft.com%7c6620abb4e0ce4610593708d34478d05c%7c72f9
> 88bf86f141af91ab2d7cd011db47%7c1=zaYIE1U%2frw4LzP2LACCfGFABxGPX2
> 9hWESb%2fgxzJUXM%3d
> and github mirror here:
> https://github.com/apache/cordova-paramedic
>
>
> @purplecabbage
> https://na01.safelinks.protection.outlook.com/?url=risingj.com=01
> %7c01%7cnikhilkh%40microsoft.com%7c6620abb4e0ce4610593708d34478d05c%7c
> 72f988bf86f141af91ab2d7cd011db47%7c1=lfQjstYvcfeC%2fhH2SDsZBD6gS
> L%2ber9o%2f1hia7xWMuDo%3d
>
> On Thu, Mar 3, 2016 at 3:59 PM, Jesse  wrote:
>
> > Nikhil and team have expressed interest in using cordova-paramedic 
> > for more of our cordova CI work. This is approach that I explored 
> > last year
> but
> > ultimately dropped because I couldn't keep up with changes needed to 
> > keep it running as a CI. The main issue I had was that TravisCI 
> > could only
> build
> > for iOS OR Android, and could not do both.  Similarily, AppVeyor 
> > could do Windows OR Android, but not both.  This lead to tests that 
> > looked as if they had passed, even though changes had been committed 
> > to untested platforms. Given that there is more interest, we can 
> > probably find a way
> to
> > push through these issues, and have true github integration so we 
> > can see if a pull request is failing tests. I was also not able to 
> > get the WP8 emulator running in a CI environment, although this is 
> > now not a much of
> a
> > concern as it is deprecated. Some stuff is also harder to test in a 
> > CI emulator/simulator, like camera, where some user interaction is needed.
> >
> > Currently cordova-paramedic is managed through my own repo, although 
> > Apache licenced. This was so that I could iterate quickly, and 
> > publish to npm without going through voting procedures. Given that 
> > others will be committing, I have asked infra to create a new repo 
> > [1] for it to live
> in.
> > This way we can all commit without legal hurdles.
> >
> >
> >
> > [1] 
> > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fiss
> > ues.apache.org%2fjira%2fbrowse%2fINFRA-11371=01%7c01%7cnikhilkh
> > %40microsoft.com%7c6620abb4e0ce4610593708d34478d05c%7c72f988bf86f141
> > af91ab2d7cd011db47%7c1=WatUkF01A0PuGXb4ncTmKrsmqTkGIkFBUeBsMTd
> > mGbY%3d
> >
> > @purplecabbage
> > https://na01.safelinks.protection.outlook.com/?url=risingj.com=
> > 01%7c01%7cnikhilkh%40microsoft.com%7c6620abb4e0ce4610593708d34478d05
> > c%7c72f988bf86f141af91ab2d7cd011db47%7c1=lfQjstYvcfeC%2fhH2SDs
> > ZBD6gSL%2ber9o%2f1hia7xWMuDo%3d
> >
>

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

Re: Test Plugin on npm

[Nikhil Khandelwal]

I agree - this is for testing purposes only - no VOTE required.

-Nikhil




On 3/4/16, 11:08 AM, "Steven Gill"  wrote:

>The real question is do we vote on it before posting to npm.
>
>Since it isn't for general release distribution, but just for testing, I
>would say you don't have to vote on it.
>
>Thoughts?
>
>-Steve
>
>On Fri, Mar 4, 2016 at 10:43 AM, Richard Knoll 
>wrote:
>
>> Yep, I would like to test with a plugin on npm to support the new version
>> selection feature I'm about to merge.
>>
>> Thanks,
>> Richard
>>
>> -Original Message-
>> From: Steven Gill [mailto:stevengil...@gmail.com]
>> Sent: Friday, March 4, 2016 10:41 AM
>> To: dev@cordova.apache.org
>> Subject: Re: Test Plugin on npm
>>
>> Hey Byoungro,
>>
>> We already test local plugins. I think the point of Richard asking is so
>> we actually test our npm fetching and installing.
>>
>> Cheers,
>> -Steve
>>
>> On Fri, Mar 4, 2016 at 10:37 AM, So, Byoungro 
>> wrote:
>>
>> > Hi Richard,
>> >
>> > Do you know you can add the plugin from your local disk path?
>> > “cordova plugin add ” might be easier for you than publishing
>> > your test plugin on the NPM registry and test using NPM.
>> >
>> > Byoungro So
>> > SSG / DPD / Mobile Computing and Compilers Intel Corporation
>> >
>> > From: Richard Knoll
>> > >
>> > Reply-To: "dev@cordova.apache.org" <
>> > dev@cordova.apache.org>
>> > Date: Friday, March 4, 2016 at 10:30 AM
>> > To: "dev@cordova.apache.org" <
>> > dev@cordova.apache.org>
>> > Subject: Test Plugin on npm
>> >
>> > Hey all,
>> >
>> > I'd like to have some better end-to-end tests for "cordova plugin add"
>> > in cordova-lib, so I wanted to publish a test plugin to npm. The
>> > plugin itself will be empty besides a plugin.xml, I just need it to
>> > exist and have engine information I can test against. Do we have an
>> > official npm account that I should be using for the publishing? I can
>> > store the plugin itself in cordova-plugins.
>> >
>> > Thanks,
>> > Richard
>> >
>> >
>>

RE: Personal Introduction: Jerroyd Moore

[Nikhil Khandelwal]

Welcome! Looking forward to your contributions!

-Nikhil

-Original Message-
From: So, Byoungro [mailto:byoungro...@intel.com] 
Sent: Wednesday, March 2, 2016 8:16 PM
To: dev@cordova.apache.org
Subject: Re: Personal Introduction: Jerroyd Moore

Welcome on board, Jerroyd.

Byoungro So
SSG / DPD / Mobile Computing and Compilers Intel Corporation









On 3/2/16, 2:03 PM, "Carlos Santana"  wrote:

>Welcome Jerroyd !
>
>
>On Wed, Mar 2, 2016 at 4:56 PM Jerroyd Moore  wrote:
>
>> Hello Apache Cordova!
>>
>> I am a member of the HTML5 Tools Team at Intel. My main 
>> responsibilities include managing the backend build system, including 
>> the tools that build cordova applications for windows platforms. I 
>> used to dabble in HTML5 apps, but am moving away from user 
>> application development and more into a devops role.
>>
>> I live and work in San Francisco, CA. When I'm not working, I spend 
>> my time snowboarding, camping, watching broadway performances. I also 
>> have an extensive board game collection and more Steam games than I 
>> have time to play.
>>
>> Nice to meet you!
>> --Jerroyd
>>

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

RE: cordova-cli Travis CI

[Nikhil Khandelwal]

Yes, I don't see a reason to disable this.

-Nikhil

-Original Message-
From: dharmendra sharma [mailto:dharam.accent...@gmail.com] 
Sent: Tuesday, March 1, 2016 5:31 AM
To: dev@cordova.apache.org
Subject: Re: cordova-cli Travis CI

I suggest we should keep Travis CI. That will enhance the code quality of 
commit.

What other have opinion about the same ?


On Tue, Mar 1, 2016 at 6:31 PM, Sergey Shakhnazarov (Akvelon) < 
v-ses...@microsoft.com> wrote:

> Hi guys,
>
> I wonder why Travis CI is disabled [1] for cordova-cli and whether we 
> should enable it?
> 5 tests are failing currently.
>
> [1]: 
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2ftravi
> s-ci.org%2fapache%2fcordova-cli=01%7c01%7cnikhilkh%40microsoft.co
> m%7c698e46d5e1504678a7e408d341d67f5e%7c72f988bf86f141af91ab2d7cd011db4
> 7%7c1=zQbt%2bRnCjEoKQSyYwGTDvwWwTOzL8OczM6bPGVVlMiA%3d
>
> Please let me know if you have any questions or considerations.
>
> Best regards,
> Sergey Shakhnazarov.
>
>

Pinned plugins and releases

[Nikhil Khandelwal]

I think pinning plugins in the CLI is causing a bunch of confusion (see 
CB-10677) as cordova plugin add might not get you the latest released plugin. 
This is a change in behavior - perhaps - we should log when the plugin is 
different from the latest released version. Also, there is an issue with our 
release strategy - should we change our policy to release TOOLS with every 
minor plugin release bump in addition to platform release?

With new plugin version constraint matching behavior implemented as part of 
this PR: https://github.com/apache/cordova-lib/pull/363 . Is there still a use 
case for pinning core plugins in package.json? Presumably, we could specify the 
constraints for a new plugin release and plugins will be "effectively" pinned.

Thanks,
Nikhil
My team is hiring.

RE: [DISCUSS] Cordova-iOS release

[Nikhil Khandelwal]

Since this is a bug we encountered previously as well - should we block on it? 
Also, looks like it will not be a patch release and we may need an accompanying 
tools release. Is that correct?

-Nikhil

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Wednesday, February 24, 2016 7:00 PM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Cordova-iOS release

Ran into a bug while testing upgrading from 3.9.2 to 4.1.0

https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fbrowse%2fCB-9254=01%7c01%7cnikhilkh%40microsoft.com%7caa36706be39e4022069108d33d8fd2f9%7c72f988bf86f141af91ab2d7cd011db47%7c1=zLWtMl89ZwXQIJcBpcZ2XnBlqMfO4OcwJKBN2xEvhDA%3d



On Wed, Feb 24, 2016 at 5:00 PM, Steven Gill  wrote:

> Changes:
>
> * CB-10693 added missing header license
> * CB-10693 Updated checked-in node_modules
> * CB-10530 - Updated cordova.js. This closes #193
> * CB-10530 - App freezes sometimes directly after starting on iOS
> * CB-10668 checked in node_modules
> * CB-10668 removed bin/node_modules
> * CB-10668 updated create.js to grab node_modules from root, updated
> package.json
> * CB-10138  Adds missing plugin metadata to plugin_list module
> * CB-10493: [iOS] Missing icon.png
> * CB-10184: Images.xcassets: A 83.5x83.5@2x app icon is required for iPad
> apps targeting iOS 9.0 and later
> * Disable ios-deploy wifi mode when deploying to a device
> * CB-10272 - Improve  and  error logs
> * Updated bundled iso-sim to 5.0.6
> * CB-10233: Support different config.xml file per CDVViewController
> instance
> * Add additional valid targets for simulation
> * Trigger mirror push of tag
> * Update JS snapshot to version 4.1.0-dev (via coho)
> * Updated CDV version macro to 4.0.1
> * CB-10185 - Update CordovaLib.xcodeproj to recommended settings in Xcode
> 7.2
> * CB-10171 - WebKit Error after migration to iOS@4.0.0
> * CB-10155 - DisallowOverscroll not working
> * CB-10168: CDVViewController appURL is nil if wwwFolderName is the path
> to a resource bundle
> * CB-10162 update reference url for icon images (closes #182)
> * CB-10162 correct the paths for iOS icon and splashscreen resources
> * This closes #172
> * Update JS snapshot to version 4.1.0-dev (via coho)
> * Set VERSION to 4.1.0-dev (via coho)
>
> I'm going to set the version to 4.1.0
>
> On Wed, Feb 24, 2016 at 4:03 PM, Steven Gill 
> wrote:
>
>> Merged it in after chatting with Shaz
>>
>> On Wed, Feb 24, 2016 at 12:55 PM, Darryl Pogue  wrote:
>>
>>> I think we're still waiting for
>>> https://github.com/apache/cordova-ios/pull/193 to land (but it's
>>> probably
>>> good to merge)
>>>
>>> On 24 February 2016 at 12:53, Steven Gill 
>>> wrote:
>>>
>>> > Any blockers? Going to aim to send this out this afternoon.
>>> >
>>> >
>>> > -Steve
>>> >
>>>
>>
>>
>

RE: [DISCUSS] Cordova-Android 5.2.0 Release

[Nikhil Khandelwal]

These commands look great - it will be good to add them to release process docs 
if they are not already there.

-Nikhil

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Wednesday, February 24, 2016 10:03 AM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Cordova-Android 5.2.0 Release

Definitely. Already committed the update.

My new strategy with bundled/checked in dependencies

* update package.json dep version if required
* rm -rf node_modules
* npm install --production (skips dev dependencies)
* git add node_modules/* (checkin all modules needed for platform add git
url)
* git commit
* npm install (Readd dev dependencies for ability to run tests locally)



On Wed, Feb 24, 2016 at 9:52 AM, Vladimir Kotikov (Akvelon) < 
v-vlk...@microsoft.com> wrote:

> Steve, do you plan to update bundled `cordova-common` as a part of 
> this release?
>
> -
> Best regards, Vladimir
>
> -Original Message-
> From: Steven Gill [mailto:stevengil...@gmail.com]
> Sent: Wednesday, February 24, 2016 8:12 PM
> To: dev@cordova.apache.org
> Subject: Re: [DISCUSS] Cordova-Android 5.2.0 Release
>
> Issue:
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissue
> s.apache.org%2fjira%2fbrowse%2fCB-10687=01%7c01%7cv-vlkoti%40064d
> .mgd.microsoft.com%7ccae1efca7e784a54d81808d33d3da913%7c72f988bf86f141
> af91ab2d7cd011db47%7c1=vfYpULSQtiavVeNfQeua394TiKTci0OfKXWRYxXdH
> fE%3d
>
> I'm going to make this version 5.1.1. I'll update here if I decide to 
> go with 5.2.0 instead.
>
> On Wed, Feb 17, 2016 at 10:49 AM, Joe Bowser  wrote:
>
> > OK, are we sure we didn't add any new minor features?
> >
> > On Wed, Feb 17, 2016 at 10:47 AM, Steven Gill 
> > 
> > wrote:
> >
> > > Well we should be following semver.
> > >
> > >
> > >- Bug fixes and other minor changes: Patch release, increment 
> > > the
> last
> > >number, e.g. 1.0.1
> > >- New features which don't break existing features: Minor release,
> > >increment the middle number, e.g. 1.1.0
> > >- Changes which break backwards compatibility: Major release,
> > increment
> > >the first number, e.g. 2.0.0
> > >
> > >
> > > On Wed, Feb 17, 2016 at 9:09 AM, Carlos Santana 
> > > 
> > > wrote:
> > >
> > > > +1 to wait for cordova-common, then to platforms
> > > >
> > > >
> > > >
> > > > On Tue, Feb 16, 2016 at 7:48 PM Steven Gill 
> > > > 
> > > > wrote:
> > > >
> > > > > Any issues with me starting this release?
> > > > >
> > > > > I think I will wait for the cordova-common release to finish 
> > > > > so I can bundle it in.
> > > > >
> > > > > Changes:
> > > > > * CB-10510: Add an optional timeout to emu start script
> > > > > * CB-10498: Resume event should be sticky if it has a plugin 
> > > > > result
> > > > > * fix HtmlNotFoundTest so that it passes when file not found 
> > > > > is
> > handled
> > > > > correctly This Closes #256
> > > > > * CB-10472 NullPointerException:
> > > > > org.apache.cordova.PluginManager.onSaveInstanceState check if
> > > > pluginManager
> > > > > is null before using it This closes #255
> > > > > * CB-10138 Adds missing plugin metadata to plugin_list module.
> > > > > This
> > > > closes
> > > > > #254
> > > > > * CB-10443 Pass original options instead of remaining
> > > > > * CB-10443 Fix `this.root` null reference
> > > > > * CB-10421 Fixes exception when calling run script with --help 
> > > > > option
> > > > > * updated .gitignore
> > > > > * CB-10406 Fixes an exception, thrown when building using Ant.
> > > > > This
> > > > closes
> > > > > #250
> > > > > * CB-10157 Uninstall app from device/emulator only when signed 
> > > > > apk is already installed
> > > > >
> > > >
> > >
> >
>

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

RE: Ask for advice about 'cordova build' command

[Nikhil Khandelwal]

I think you have to invoke cordova build with the CALL command to ensure it 
does not cause your script to exit.

call cordova build

-Nikhil

-Original Message-
From: So, Byoungro [mailto:byoungro...@intel.com] 
Sent: Wednesday, February 24, 2016 12:19 PM
To: dev@cordova.apache.org
Subject: RE: Ask for advice about 'cordova build' command

After-build hook is a reasonable solution, Qiang.

You may want to check if the source directory
"D: 
\cordovaWorkSpace\MyApp\platforms\android\build\outputs\apk\android-debug.apk".
It seems there is a space between "D:" and "\".
Another possible cause would be the permission issue on the target directory " 
C:\Users\Administrator\Desktop\myApp.apk"
Enjoy.

Byoungro So
SSG / DPD / Mobile Computing and Compilers Intel Corporation

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com]
Sent: Wednesday, February 24, 2016 11:56 AM
To: dev@cordova.apache.org
Subject: Re: Ask for advice about 'cordova build' command

Hey!

Why not use a after_build hook instead?
https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fcordova.apache.org%2fdocs%2fen%2flatest%2fguide%2fappdev%2fhooks%2findex.html=01%7c01%7cnikhilkh%40microsoft.com%7c544416d17eb0443eae1008d33d5878af%7c72f988bf86f141af91ab2d7cd011db47%7c1=n5t%2fvu1oJM8WGrif0FZlZ8eLIVXUgm%2bLnO3sISf2yGA%3d

On Wed, Feb 24, 2016 at 11:04 AM, Raphael Bircher 
wrote:

> Hi
>
> I remember that we have had a similar issue on a other project 
> (OpenOffice Testtool) The only solution was to switch to VBA. As I 
> know the Batch interpreter has issues with external processes.
>
> Have a nice day
> Raphael
>
> On Wed, Feb 24, 2016 at 11:54 AM, QiangOffice 
> 
> wrote:
> > Hi Sir,
> >   I have used cordova develop my app for five months, thank you 
> > support
> this nice framework for us.
> >   For convenience, I wrote a batch file to build app automatically, 
> > but
> there is a catch, after the 'cordova build' command executed, the 
> batch will end, commands which after 'cordova build' line cannot be 
> executed, so what can I do to solve this problem?
> >   Below is my batch file:
> >   d:
> > cd cordovaWorkSpace\MyApp
> > cordova build
> > copy /y D: \cordovaWorkSpace\MyApp
> \platforms\android\build\outputs\apk\android-debug.apk
>  C:\Users\Administrator\Desktop\myApp.apk
> >
> >   The last line can never be executed because after the 'cordova build'
> executed, the cmd window will exit. So please tell me a way to solve 
> this problem.
> >
> > Thanks
> >
> > Name:Qiang
> > Email:qiangoff...@office2016.cc
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

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

RE: Android and iOS bug release

[Nikhil Khandelwal]

Where are we with releases here? Can we still do a patch release (not requiring 
a TOOLS update)?

Looks like there is also this JIRA: 
https://issues.apache.org/jira/browse/CB-10493 which is causing iOS apps to be 
rejected.

Thanks,
Nikhil

-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com] 
Sent: Thursday, February 18, 2016 4:05 AM
To: dev@cordova.apache.org
Subject: Re: Android and iOS bug release

Frederico 

I didn't want unnecessary pressure on anyone to work on a bug by putting a 
release  on hold. 

I spent some time with Mike from Ionic and I was not able to reproduce or make 
heads or tail out of this bug. 

I'm glad to hear progress on the bug, thanks to Torsten and Shaz :-)

- Carlos
@csantanapr

> On Feb 17, 2016, at 4:34 AM, Frederico Galvão 
>  wrote:
> 
> It seems Shaz sorted the bug out already [1]. And I agree with and 
> understand every point you made, Carlos. Thank you.
> 
> 
> [1] - https://github.com/apache/cordova-ios/pull/193
> 
> 2016-02-16 16:22 GMT-02:00 Carlos Santana :
> 
>> Cutting releases don't cost $$, just some time
>> 
>> We just try to minimize effort and consolidate many bugs that are 
>> ready for one release.
>> 
>> if we have a fix that can make it in the release window that's OK to 
>> wait, but we can always do a bug release today, and another bug 
>> release when that bug is fix
>> 
>> If there is outlook to get the bug fix soon, I would say we wait but 
>> if not then we just pick it up on the next bug release.
>> 
>> Looking at the JIRA the bug is still under investigation
>> 
>> 
>> 
>> On Tue, Feb 16, 2016 at 9:18 AM Frederico Galvão < 
>> frederico.gal...@pontoget.com.br> wrote:
>> 
>>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fiss
>>> ues.apache.org%2fjira%2fbrowse%2fCB-10530=01%7c01%7cnikhilkh%40
>>> microsoft.com%7cf84eec968ce545b6208f08d3385bc476%7c72f988bf86f141af9
>>> 1ab2d7cd011db47%7c1=QTC05NEPHkr99mis1G6Rfg1fLpLXYUMTI2UsnRsxNN
>>> k%3d is a showstopper for
>> quite
>>> a
>>> few people. If that ever requires changes to cordova-ios, I'm voting 
>>> that the bugfix releases wait for it or that we find a workaround 
>>> that isn't uninstalling every plugin.
>>> 
>>> 2016-02-16 1:58 GMT-02:00 Carlos Santana :
>>> 
 Tomorrow is my birthday, I will take them as gifts :-)
 
 
 On Mon, Feb 15, 2016 at 10:55 PM Steven Gill 
 
 wrote:
 
> Yeah, I can start these releases. Hopefully tomorrow.
> 
> -Steve
> 
> On Mon, Feb 15, 2016 at 7:46 PM, Carlos Santana <
>> csantan...@gmail.com>
> wrote:
> 
>> +1
>> Steve would you mind doing these bug release?
>> 
>> Should we wait to see what happens with the ios freeze bug [1],? 
>> or
 just
> do
>> a bug release now, and then do another later when that one is
>>> resolved
> and
>> keep the train going
>> 
>> [1] : 
>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2f
>> issues.apache.org%2fjira%2fbrowse%2fCB-10530=01%7c01%7cnikhi
>> lkh%40microsoft.com%7cf84eec968ce545b6208f08d3385bc476%7c72f988bf
>> 86f141af91ab2d7cd011db47%7c1=QTC05NEPHkr99mis1G6Rfg1fLpLXYU
>> MTI2UsnRsxNNk%3d
>> 
>> 
>>> On Mon, Feb 15, 2016 at 6:01 PM Dan Polivy 
>>> 
>> wrote:
>> 
>>> Is there any progress on an android bugfix release? It looks 
>>> like Richard's PR has been merged in, and I'm waiting for that 
>>> (and
>> the
 fix
>> for
>>> CB-10138) to be pushed out in a production release.
>>> 
>>> Thanks,
>>> Dan
>>> 
>>> -Original Message-
>>> From: Carlos Santana [mailto:csantan...@gmail.com]
>>> Sent: Thursday, February 04, 2016 5:23 PM
>>> To: dev@cordova.apache.org
>>> Subject: Re: Android and iOS bug release
>>> 
>>> I will take a look
>>> 
>>> On Thu, Feb 4, 2016 at 1:23 PM Richard Knoll <
>>> rikn...@microsoft.com>
>>> wrote:
>>> 
 I have a PR open in cordova-android that should probably be
>>> merged
>> first.
 It addresses a bug in the save/restore API that a few people
>> are
>>> hitting. I
 still have some updates/testing to do but I hope to merge it in
 soon.
>>> Would
 love some feedback if anyone has a chance to review.
 
 The PR is here:
 https://github.com/apache/cordova-android/pull/257
 
 And the JIRA is here:
 https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%
 2fissues.apache.org%2fjira%2fbrowse%2fCB-10498=01%7c01%7cn
 ikhilkh%40microsoft.com%7cf84eec968ce545b6208f08d3385bc476%7c72
 f988bf86f141af91ab2d7cd011db47%7c1=DSCu44DFTYYL9D1VsoxsjJ
 xWNTejAPzVeApam9CKtd8%3d
 
 Thanks,
 Richard
 
 -Original Message-

RE: Github issue and PR templates

[Nikhil Khandelwal]

I think for plugins, platform name should be required as part of title of the 
PR and commit message in addition to JIRA number. 

Checklist:
[ ] Tests that were added or run for a new feature/regressions
[ ] Does the new feature broadly apply to multiple platforms?

We probably need to make it easier for contributors to run tests for plugins.

-Nikhil

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Wednesday, February 17, 2016 1:42 PM
To: dev@cordova.apache.org
Subject: Github issue and PR templates

Cool new feature from github!
https://github.com/blog/2111-issue-and-pull-request-templates

Since we don't do issues on github, that feature isn't useful to us. But 
providing PR templates sounds like a good idea. Just need to add a 
PULL_REQUEST_TEMPLATE.md to the root of our repos.

What type of information would we ask for from PRs?

* Issue number

If it is a plugin
* which platforms

Thoughts?

RE: package discovery

[Nikhil Khandelwal]

When we were building cordova plugin search, we had ideas to have a page 
dedicated to listing plugins under meaningful categories. However, we could not 
do that unless plugins had the correct keywords. I want to piggyback on this 
call for plugins to add the correct keywords.

How about these specific keywords describing different categories of plugins:
- Storage
- Monetization
- Authentication
- Device interaction (can keywords have spaces?)
- Cloud services

Any other categories?

-Nikhil


-Original Message-
From: Raymond Camden [mailto:raymondcam...@gmail.com] 
Sent: Sunday, February 7, 2016 7:37 AM
To: dev@cordova.apache.org
Subject: Re: package discovery

+1!

On Fri, Feb 5, 2016 at 3:18 PM, Carlos Santana  wrote:
> +1 !!
>
> On Fri, Feb 5, 2016 at 4:01 PM Steven Gill  wrote:
>
>> Sorry I meant cordova:tool but I also like cordova:tooling better
>>
>> On Fri, Feb 5, 2016 at 12:34 PM, Jesse  wrote:
>>
>> > +1
>> > Shouldn't cordova-tool be cordova:tool ?
>> > I might like cordova:tooling better, not sure ...
>> >
>> >
>> > @purplecabbage
>> > https://na01.safelinks.protection.outlook.com/?url=risingj.com=01%7c01%7cnikhilkh%40microsoft.com%7c9df8ae65b94f4961968e08d32fd476bc%7c72f988bf86f141af91ab2d7cd011db47%7c1=fE7CO4My9KkegwpdJ5sUDUunrBIretM9cPR%2bYsVk7ow%3d
>> >
>> > On Fri, Feb 5, 2016 at 12:26 PM, Tommy-Carlos Williams <
>> to...@devgeeks.org
>> > >
>> > wrote:
>> >
>> > > +1
>> > >
>> > >
>> > > > On 6 Feb 2016, at 6:51 AM, Steven Gill 
>> wrote:
>> > > >
>> > > > Hey everyone!
>> > > >
>> > > > With templates out now, I wanted to propose a few keywords for
>> > improving
>> > > > discoverability.
>> > > >
>> > > > Firstly, every package should contain 'ecosystem:cordova'.
>> > > >
>> > > > I suggest we add these new keywords.
>> > > > 'cordova:platform'
>> > > > 'cordova:plugin'
>> > > > 'cordova:template'
>> > > > 'cordova-tool' (don't really need this one)
>> > > >
>> > > > then we can eventually create a new 
>> > > > https://na01.safelinks.protection.outlook.com/?url=template.cordova.io=01%7c01%7cnikhilkh%40microsoft.com%7c9df8ae65b94f4961968e08d32fd476bc%7c72f988bf86f141af91ab2d7cd011db47%7c1=u6XJ05wCmIy0wRUtgEcGTidjwQOWP6wTofUb7tnAQeg%3d
>> > > >  search site
>> > > based
>> > > > off the plugins search site that uses the 'cordova:template'.
>> > > >
>> > > > I'm going to blog about templates next week as long as we can land
>> some
>> > > > consensus on this.
>> > >
>> > >
>> >
>>



-- 
===
Raymond Camden, Developer Advocate for MobileFirst at IBM

Email : raymondcam...@gmail.com
Blog : 
https://na01.safelinks.protection.outlook.com/?url=www.raymondcamden.com=01%7c01%7cnikhilkh%40microsoft.com%7c9df8ae65b94f4961968e08d32fd476bc%7c72f988bf86f141af91ab2d7cd011db47%7c1=t18BhEWmRngIfacVEGVdrYyl8cYvv37irLRoUApY2Vg%3d
Twitter: raymondcamden

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

RE: package discovery

[Nikhil Khandelwal]

Also, there is "Social" category. Here's the old mockup for this: 
http://imgur.com/rhcjBTG

-Nikhil

-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com] 
Sent: Monday, February 8, 2016 10:19 AM
To: dev@cordova.apache.org
Subject: Re: package discovery

Push Notifications
Analytics
Security
Cloud :-) just kidding


On Mon, Feb 8, 2016 at 12:50 PM Nikhil Khandelwal <nikhi...@microsoft.com>
wrote:

> When we were building cordova plugin search, we had ideas to have a 
> page dedicated to listing plugins under meaningful categories. 
> However, we could not do that unless plugins had the correct keywords. 
> I want to piggyback on this call for plugins to add the correct keywords.
>
> How about these specific keywords describing different categories of
> plugins:
> - Storage
> - Monetization
> - Authentication
> - Device interaction (can keywords have spaces?)
> - Cloud services
>
> Any other categories?
>
> -Nikhil
>
>
> -Original Message-
> From: Raymond Camden [mailto:raymondcam...@gmail.com]
> Sent: Sunday, February 7, 2016 7:37 AM
> To: dev@cordova.apache.org
> Subject: Re: package discovery
>
> +1!
>
> On Fri, Feb 5, 2016 at 3:18 PM, Carlos Santana <csantan...@gmail.com>
> wrote:
> > +1 !!
> >
> > On Fri, Feb 5, 2016 at 4:01 PM Steven Gill <stevengil...@gmail.com>
> wrote:
> >
> >> Sorry I meant cordova:tool but I also like cordova:tooling better
> >>
> >> On Fri, Feb 5, 2016 at 12:34 PM, Jesse <purplecabb...@gmail.com> wrote:
> >>
> >> > +1
> >> > Shouldn't cordova-tool be cordova:tool ?
> >> > I might like cordova:tooling better, not sure ...
> >> >
> >> >
> >> > @purplecabbage
> >> >
> https://na01.safelinks.protection.outlook.com/?url=risingj.com=01
> %7c01%7cnikhilkh%40microsoft.com%7c9df8ae65b94f4961968e08d32fd476bc%7c
> 72f988bf86f141af91ab2d7cd011db47%7c1=fE7CO4My9KkegwpdJ5sUDUunrBI
> retM9cPR%2bYsVk7ow%3d
> >> >
> >> > On Fri, Feb 5, 2016 at 12:26 PM, Tommy-Carlos Williams <
> >> to...@devgeeks.org
> >> > >
> >> > wrote:
> >> >
> >> > > +1
> >> > >
> >> > >
> >> > > > On 6 Feb 2016, at 6:51 AM, Steven Gill 
> >> > > > <stevengil...@gmail.com>
> >> wrote:
> >> > > >
> >> > > > Hey everyone!
> >> > > >
> >> > > > With templates out now, I wanted to propose a few keywords 
> >> > > > for
> >> > improving
> >> > > > discoverability.
> >> > > >
> >> > > > Firstly, every package should contain 'ecosystem:cordova'.
> >> > > >
> >> > > > I suggest we add these new keywords.
> >> > > > 'cordova:platform'
> >> > > > 'cordova:plugin'
> >> > > > 'cordova:template'
> >> > > > 'cordova-tool' (don't really need this one)
> >> > > >
> >> > > > then we can eventually create a new
> https://na01.safelinks.protection.outlook.com/?url=template.cordova.io
> =01%7c01%7cnikhilkh%40microsoft.com%7c9df8ae65b94f4961968e08d32fd
> 476bc%7c72f988bf86f141af91ab2d7cd011db47%7c1=u6XJ05wCmIy0wRUtgEc
> GTidjwQOWP6wTofUb7tnAQeg%3d
> search site
> >> > > based
> >> > > > off the plugins search site that uses the 'cordova:template'.
> >> > > >
> >> > > > I'm going to blog about templates next week as long as we can 
> >> > > > land
> >> some
> >> > > > consensus on this.
> >> > >
> >> > >
> >> >
> >>
>
>
>
> --
> ==
> = Raymond Camden, Developer Advocate for MobileFirst at IBM
>
> Email : raymondcam...@gmail.com
> Blog :
> https://na01.safelinks.protection.outlook.com/?url=www.raymondcamden.c
> om=01%7c01%7cnikhilkh%40microsoft.com%7c9df8ae65b94f4961968e08d32
> fd476bc%7c72f988bf86f141af91ab2d7cd011db47%7c1=t18BhEWmRngIfacVE
> GVdrYyl8cYvv37irLRoUApY2Vg%3d
> Twitter: raymondcamden
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

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

[DISCUSS] Plugin patch release

[Nikhil Khandelwal]

Looks like we might need another plugins release. I have been triaging JIRAs 
after the latest set of releases and these look like high priority enough to 
get a release out for them. There are number of regressions/bug fixes that we 
want to get released. These changes are simple and probably require a patch 
update:

cordova-plugin-file:
CB-10419 cordova-plugin-file 4.0.0 error with browserify workflow

cordova-plugin-wkwebview-engine:
CB-10269: Replace cordova exec only when present in wkwebview

cordova-plugin-media:
CB-10476 cordova-plugin-media 2.1.0 dos not fire mediaSuccess
CB-10455 android: Adding permission helper to remove cordova-android 5.0.0 
constraint

Are there other regressions/JIRAs that need to be included? Ideally, we should 
keep this release scoped to keep the quality high.

Thanks,
Nikhil

RE: package discovery

[Nikhil Khandelwal]

I like the idea. However, currently plugins are being identified with 
"ecosystem:cordova" keyword. We might have to maintain that for all plugins 
that do not switch to these new keyword below.

For "tool" there is at least one example of a tool which currently shows up in 
plugin search: https://www.npmjs.com/package/cordova-hot-code-push-cli

So let's add the keyword anyway. 

-Nikhil

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Friday, February 5, 2016 11:52 AM
To: dev@cordova.apache.org
Subject: package discovery

Hey everyone!

With templates out now, I wanted to propose a few keywords for improving 
discoverability.

Firstly, every package should contain 'ecosystem:cordova'.

I suggest we add these new keywords.
'cordova:platform'
'cordova:plugin'
'cordova:template'
'cordova-tool' (don't really need this one)

then we can eventually create a new 
https://na01.safelinks.protection.outlook.com/?url=template.cordova.io=01%7c01%7cnikhilkh%40microsoft.com%7c2cf20074433d482eead908d32e65dce6%7c72f988bf86f141af91ab2d7cd011db47%7c1=csk3hOeXJ%2bJSp1lZCkUba1zeVF51mFCAhjOJ7B8wVa8%3d
 search site based off the plugins search site that uses the 'cordova:template'.

I'm going to blog about templates next week as long as we can land some 
consensus on this.

RE: Docs versioning scheme

[Nikhil Khandelwal]

Looks we did a release for the docs with the tools release. Is it possible to 
name it 6.x instead of 6.0.0? All URLs to 6.0.0 will break if we do that but we 
should do that sooner rather than later to minimize impact.

As discussed, micro-versioning of docs does not buy us much. I'll enhance our 
cordova-docs readme and editorial guide for docs with details on how we handle 
versioning.

-Nikhil

-Original Message-
From: Jesse [mailto:purplecabb...@gmail.com] 
Sent: Thursday, January 21, 2016 2:50 PM
To: dev@cordova.apache.org
Subject: Re: Docs versioning scheme

SGTM! +1


@purplecabbage
https://na01.safelinks.protection.outlook.com/?url=risingj.com=01%7c01%7cnikhilkh%40microsoft.com%7c82dab60846b14dded12d08d322b54957%7c72f988bf86f141af91ab2d7cd011db47%7c1=fiC5HqwZWlaOSZD4ipn97isk7hjFjVCht9IzgKZKnFA%3d

On Thu, Jan 21, 2016 at 1:47 PM, Steven Gill <stevengil...@gmail.com> wrote:

> +1
>
> On Thu, Jan 21, 2016 at 1:38 PM, Nikhil Khandelwal 
> <nikhi...@microsoft.com
> >
> wrote:
>
> > Should we version our docs on every major version (instead of minor
> > version) of cordova CLI that comes out? Should the next version of 
> > the
> docs
> > be "6.x"? Honestly, not much changes every minor release and 
> > maintaining multiple copies has quite a few downsides w.r.t. SEO 
> > (referring to older versions of docs), slow docs builds, huge website 
> > duplication.
> >
> > Lot of our docs relate to platform updates and we need clear 
> > sections within them that specify the version of the platform for 
> > which the docs apply to. For example, Android 5.1 will introduce new 
> > lifetime concepts which will be part of Cordova 6.0 docs release. 
> > It's best for the text of the docs itself to have something along 
> > the lines of "This applies to cordova-android > 5.1"
> >
> > Similarly, significant future updates to CLI/Lib features can 
> > contain the same "This applies to cordova > 6.2".
> >
> > I think it will lead to a simpler model on our website and prevent 
> > future version explosion [1].
> >
> > Thanks,
> > Nikhil
> >
> > [1] 
> > https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fimgu
> > r.com%2fvkeNvUL=01%7c01%7cnikhilkh%40microsoft.com%7c82dab60846
> > b14dded12d08d322b54957%7c72f988bf86f141af91ab2d7cd011db47%7c1=
> > Yh%2b9h4MUN9VfUADA1unTmUExqioMs75xG1HjVYmDSBc%3d
> >
> >
>

RE: [DISCUSS] Cordova Style Guide

[Nikhil Khandelwal]

Rob,
I appreciate your enthusiasm. Cordova docs need a lot of improvement. We did a 
survey in October and 70% of negative comments focused on problems with our 
docs. 

Committers at Microsoft are pushing hard to improve the Cordova docs - but we 
need a lot of help from the community. We are using a JIRA Kanban board [1] 
that we are using to track documentation tasks/bugs. This captures all the work 
referenced in creating a new information architecture for our docs [2].

There are a number of ways to help in this effort:
- Pick one of the JIRA bug/task to improve the current docs. Start small - any 
help here would be fantastic!
- Review doc updates for styling etc. issues. PRs are filed against 
cordova-docs repo [3].
- File JIRAs for issues that you find in current docs.
- Identify high priority topics that are currently missing and need to be added.
- Help organize document scrubs within the community.

It's critical for a dev platform to have good docs and our goal is to make that 
happen for Cordova in the upcoming months.

[1] 
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=108=detail=CB-10348
[2] 
https://github.com/cordova/cordova-discuss/pull/31/files?short_path=b589504#diff-b589504f1eedbd87c81f38ce873d5d85
[3] https://github.com/apache/cordova-docs

Thanks,
Nikhil

-Original Message-
From: Ryan J. Salva [mailto:rsa...@microsoft.com] 
Sent: Tuesday, January 26, 2016 5:54 PM
To: dev@cordova.apache.org
Subject: RE: [DISCUSS] Cordova Style Guide

Rob,

Any contributions you can provide would be most welcome... especially if you 
can help us apply that style guide to existing docs. We're making a big push to 
improve the documentation this year, but it's hard work and often gets 
prioritized below things like bug fixes to the actual framework. 

It all starts with a pull request :-)

rjs

-Original Message-
From: Robert Posener [mailto:rposen...@gmail.com]
Sent: Tuesday, January 26, 2016 5:45 PM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Cordova Style Guide

Gerday, Dmitry,
I'm a bit of a documentation pedant.
I have been "monitoring" Cordova development for a few months now, with the 
initial intent of wanting to contribute to improving the documentation (and 
then, perhaps to contributing to the code base).
The thing that has struck me in this time is that there appears to be NO 
documentation style standards.  Yes, the documents you reference go some of the 
way towards what I am looking for but they could be a lot better (eg, is it 
"E.g.,", "eg,", "e.g.,", is it "Cordova" or "cordova", is it "database" or 
"data base", do you put a comma before the "and" in the last of a list of comma 
separated items (eg, is it "a, b, c, and d" or is it "a, b, c and d"), do we 
employ USA-English or UK-English (or both), etc).
Further, it appears that some contributors "pick up" others with their code 
style standard breaches (I have seen "please insert a space here", "please lint 
this", etc), but I rarely see anyone picking up documentation style standards 
beaches.
Without letting my ego get in the way, I'm happy to contribute a suggested list 
of style standards (that I use when developing Android and Windows apps using 
Cordova) as well as acting in a Quality Assurance role with the documentation.
As you probably know, the Cordova documentation is quite regularly critcised 
all over the web.  Rather than be just another one of these criicisers, I'm 
happy "to put my time where my mouth is" and contribute.  I (and others) 
believe we can do a lot better here.  What do you think?

Rob

Regards
*Rob Posener*
0419 012 627

On 27 January 2016 at 11:55, Dmitry Blotsky  wrote:

> Hey folks,
>
> I know we used to have a style guide on the wiki, but that seems long 
> dead. I created a JIRA for a new Cordova-wide style guide, covering 
> most of the languages we use (feel free to add others). The JIRA is here:
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissue
> s.apache.org%2fjira%2fbrowse%2fCB-10448.=01%7c01%7crsalva%40micro
> soft.com%7cdb95d5df3d7545a54e1008d326bb7ca9%7c72f988bf86f141af91ab2d7c
> d011db47%7c1=iBwCcS7cBzD%2fnsj79mTPQCFzWUTUUm%2fkBlSTPmBBBFk%3d
>
> Kindly,
> Dmitry
>

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

RE: [DISCUSS] Old platforms support deprecation

[Nikhil Khandelwal]

+1 for 6-month deprecation (or even earlier) for platforms where we have 
already released a platform with Platform API. Duplicated code can be a real 
maintenance problem here.

For other platforms that we have not released a platform API implementation and 
do not plan to e.g. WP8, WebOS, Ubuntu - we should support them for longer 
unless the cost is significant.

-Nikhil

-Original Message-
From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] 
Sent: Friday, January 22, 2016 11:36 AM
To: dev@cordova.apache.org
Subject: RE: [DISCUSS] Old platforms support deprecation

Agree about 6 months. I suggested next Cordova major version as a deadline due 
to two reasons: this definitely will be a breaking change, so we'll need for 
major bump anyway; also the Cordova 5.0 lives for about 8 months (since Apr 
2015), so I think Cordova 6 will live for approximately the same time.

Regarding the other platforms (WebOS, Ubuntu) - I was thinking about "soft" 
deprecation - i.e. drop support only for that platforms where we have an 
implementation for PlatformApi (Android, iOS, Windows, probably OSX), and leave 
other platforms as-is. But if everybody is ok about total platform-specific 
code removal, this might be even better, because then we'll be able to cut out 
a great chunk of legacy code and, probably, get rid of a number of dependencies.

---
Best regards, Vladimir

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com]
Sent: Friday, January 22, 2016 8:39 PM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Old platforms support deprecation

I think depreciation should be our usual 6 months instead of cordova 7. Who 
knows how fast or slow cordova 7 will come out.

Doing this, it would mean we would drop support for the platforms that don't 
update to PlatformAPI.

We have already started the process for deprecating amazon-fireos and wp8.
We would need to include FFOS since I don't see anyone working on it at all. We 
can contact LG about webos and see if they will update. Ubuntu might get the 
update by then. OSX already has a PR for PlatformAPI changes.

I think this sounds fine. Deprecated platforms would still work with old 
versions of cordova.
On Jan 22, 2016 6:58 AM, "Vladimir Kotikov (Akvelon)" < v-vlk...@microsoft.com> 
wrote:

> Hi guys.
>
> Starting from upcoming cordova release (6.0.0) we have PlatformApi 
> implemented and used by three major platforms (Android, iOS and Windows).
> This means that we now have a lot of code in cordova-lib which exists 
> there only for maintaining compatibility with previous platforms 
> versions.  I'd love to remove this duplicates from lib, but this means 
> that we'll lose the support for previous platforms in newer cli, and 
> hence we'd need to deprecate this support first.
>
> So I propose to add a deprecation message about removing support for 
> old platforms into upcoming cordova@6.0.0 and remove this support 
> totally in next major cordova version (7.0.0). The message will be 
> emitted each time when polyfill is instantiated for these platforms 
> instead of platform's Api class and might look like this:
>
> "The support for old platforms via PlatformApi polyfill is deprecated 
> and will be removed in next versions of cordova.
> Consider upgrading your platform to cordova-android@5.0.0 or newer."
>
> -
> Best regards, Vladimir.
>
>
>

RE: [DISCUSS] inAppBrowser plugin release

[Nikhil Khandelwal]

I'm curious what caused the regression? Why do we not have tests for this 
important scenario?

-Nikhil

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Monday, January 25, 2016 1:19 AM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] inAppBrowser plugin release

+1 Lets do it!

On Mon, Jan 25, 2016 at 1:00 AM, julio cesar sanchez  wrote:

> On latest release of inAppBrowser plugin the loadstart event stopped 
> working on android.
> It has been fixed on the 1.2.1-dev.
> Should we release it?
>
> I think loadstart is very important and a lot of apps rely on it for 
> closing the window.
>

RE: --browserify workflow status?

[Nikhil Khandelwal]

Great! Looks like we just need to update the help text then. I sent a PR for 
this: https://github.com/apache/cordova-cli/pull/231

Anyone wants to talk about the merits of using the browserify workflow? Our 
blog might be a good place for that.

-Nikhil

-Original Message-
From: dvpdin...@gmail.com [mailto:dvpdin...@gmail.com] On Behalf Of Darryl Pogue
Sent: Thursday, January 21, 2016 11:35 AM
To: dev@cordova.apache.org
Subject: Re: --browserify workflow status?

I've been using the --browserify flag for several months and it's been working 
great

On 21 January 2016 at 11:02, Anis KADRI <anis.ka...@gmail.com> wrote:
> YES YES YES! Please cordova_plugins.js is killing me.
>
> On Wed, Jan 20, 2016 at 4:10 PM Nikhil Khandelwal 
> <nikhi...@microsoft.com>
> wrote:
>
>> Where are we with --browserify support? From what I can see, most or 
>> all the work has been completed:
>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissu
>> es.apache.org%2fjira%2fbrowse%2fCB-8801=01%7c01%7cnikhilkh%40mic
>> rosoft.com%7c530238f80e1c41e776d308d32299e90a%7c72f988bf86f141af91ab2
>> d7cd011db47%7c1=p1p5LVB7ywO29s8%2bmU%2fmhaiN9guzvp5qHDqroc2p1QU
>> %3d
>>
>> Should it move out of experimental now?[1]
>>
>> It will help to document it and perhaps blog about its benefits as 
>> opposed to the current default workflow.
>>
>> [1] 
>> https://github.com/apache/cordova-cli/blob/master/doc/build.txt#L27
>>
>> Thanks,
>> Nikhil
>>

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

Docs versioning scheme

[Nikhil Khandelwal]

Should we version our docs on every major version (instead of minor version) of 
cordova CLI that comes out? Should the next version of the docs be "6.x"? 
Honestly, not much changes every minor release and maintaining multiple copies 
has quite a few downsides w.r.t. SEO (referring to older versions of docs), 
slow docs builds, huge website duplication.

Lot of our docs relate to platform updates and we need clear sections within 
them that specify the version of the platform for which the docs apply to. For 
example, Android 5.1 will introduce new lifetime concepts which will be part of 
Cordova 6.0 docs release. It's best for the text of the docs itself to have 
something along the lines of "This applies to cordova-android > 5.1"

Similarly, significant future updates to CLI/Lib features can contain the same 
"This applies to cordova > 6.2".

I think it will lead to a simpler model on our website and prevent future 
version explosion [1].

Thanks,
Nikhil

[1] http://imgur.com/vkeNvUL

RE: --browserify workflow status?

[Nikhil Khandelwal]

Thanks, Steve for taking up on writing the blog post. It would be great to use 
that to drive some usage and feedback loop. Also,  we might want to do JIRA 
triage of related issues to ensure that it does not result in any regressions. 
I took a quick look and most of it is not relevant currently [1]. Though 
CB-9967 might be a good one to fix.

I believe one of the advantages of browserify is that it results in lesser file 
loads - while this is mildly beneficial for local apps, it's perhaps a big deal 
for remote hosted cordova apps. Are there any downsides to using browserify?

Also, can a user reference arbitrary browserifiable[2] supported js libraries 
from node_modules in their cordova app with this. Docs and some walkthrough 
would be useful here. On a similar note, with this could a plugin add a 
reference to a nodejs module in its code? Of course, in that case, the plugin 
will *require* browserify workflow to function.

[1] 
https://issues.apache.org/jira/browse/CB-9967?jql=project%20%3D%20CB%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20text%20~%20browserify%20ORDER%20BY%20created%20DESC
[2] http://browserifysearch.org/

Thanks,
Nikhil

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Thursday, January 21, 2016 4:14 PM
To: dev@cordova.apache.org
Subject: Re: --browserify workflow status?

Should we set a rough goal/timeline on when to make this default? Cordova 
6.1.0? Put the non browserify workflow behind a --no-browserify flag.

I'll plan to write a blog post and put it up for review week after PGDAY.

On Thu, Jan 21, 2016 at 1:19 PM, Nikhil Khandelwal <nikhi...@microsoft.com>
wrote:

> Great! Looks like we just need to update the help text then. I sent a 
> PR for this: https://github.com/apache/cordova-cli/pull/231
>
> Anyone wants to talk about the merits of using the browserify workflow?
> Our blog might be a good place for that.
>
> -Nikhil
>
> -Original Message-
> From: dvpdin...@gmail.com [mailto:dvpdin...@gmail.com] On Behalf Of 
> Darryl Pogue
> Sent: Thursday, January 21, 2016 11:35 AM
> To: dev@cordova.apache.org
> Subject: Re: --browserify workflow status?
>
> I've been using the --browserify flag for several months and it's been 
> working great
>
> On 21 January 2016 at 11:02, Anis KADRI <anis.ka...@gmail.com> wrote:
> > YES YES YES! Please cordova_plugins.js is killing me.
> >
> > On Wed, Jan 20, 2016 at 4:10 PM Nikhil Khandelwal 
> > <nikhi...@microsoft.com>
> > wrote:
> >
> >> Where are we with --browserify support? From what I can see, most 
> >> or all the work has been completed:
> >>
> >> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fis
> >> su 
> >> es.apache.org%2fjira%2fbrowse%2fCB-8801=01%7c01%7cnikhilkh%40m
> >> ic
> >> rosoft.com%7c530238f80e1c41e776d308d32299e90a%7c72f988bf86f141af91a
> >> b2 
> >> d7cd011db47%7c1=p1p5LVB7ywO29s8%2bmU%2fmhaiN9guzvp5qHDqroc2p1
> >> QU
> >> %3d
> >>
> >> Should it move out of experimental now?[1]
> >>
> >> It will help to document it and perhaps blog about its benefits as 
> >> opposed to the current default workflow.
> >>
> >> [1]
> >> https://github.com/apache/cordova-cli/blob/master/doc/build.txt#L27
> >>
> >> Thanks,
> >> Nikhil
> >>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

--browserify workflow status?

[Nikhil Khandelwal]

Where are we with --browserify support? From what I can see, most or all the 
work has been completed:

https://issues.apache.org/jira/browse/CB-8801

Should it move out of experimental now?[1]

It will help to document it and perhaps blog about its benefits as opposed to 
the current default workflow.

[1] https://github.com/apache/cordova-cli/blob/master/doc/build.txt#L27

Thanks,
Nikhil

RE: [DISCUSS] Android@5.1.0

[Nikhil Khandelwal]

We have customers who have an existing C++ code base and looking to use NDK in 
their plugins. 

From what I can see the property android.useDeprecatedNdk=true needs to be part 
of gradle.properties and not .gradle file itself. I am aware that a plugin can 
add .gradle files - but I'm not sure they can add a gradle.properties file. Of 
course, hooks can be used to just about anything but it sounds hacky.

Another option would be to have cordova build.js invoke the gradle compiler 
with -Pandroid.useDeprecatedNdk=true.

I have a PR for this: https://github.com/apache/cordova-android/pull/249

Let's release once we are OK with merging this.

-Nikhil

-Original Message-
From: Joe Bowser [mailto:bows...@gmail.com] 
Sent: Tuesday, January 19, 2016 10:36 AM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Android@5.1.0

Yes, it probably can. I'm thinking that Google once again put us in dependency 
hell with the new NDK functionality, which is why I'm not super stoked about 
this file existing at all.

On Tue, Jan 19, 2016, 10:29 AM Simon MacDonald <simon.macdon...@gmail.com>
wrote:

> Can't the crosswalk plugin deliver the Gradle files via the framework 
> tag of its plugin. Xml to fix this?
>
> Simon
> On Jan 19, 2016 13:26, "Joe Bowser" <bows...@gmail.com> wrote:
>
> > I really don't want to add this file and use the deprecated NDK,
> especially
> > since we don't know if this is a plugin or platform responsibility.  
> > I
> also
> > don't want to delay a release for people not using Crosswalk.
> >
> > Do we know of any other plugins that use the NDK? If there aren't 
> > any,
> I'm
> > more agreeable to adding the file since it won't break others.
> >
> >
> > On Tue, Jan 19, 2016, 10:13 AM Nikhil Khandelwal 
> > <nikhi...@microsoft.com
> >
> > wrote:
> >
> > > If this is a regression in behavior and CrossWalk will not work 
> > > out of
> > the
> > > box - we should consider fixing it. Sounds like it is a simple 
> > > fix. Is there  JIRA for this?
> > >
> > > Overall, we shouldn't require/expect Cordova JS developers to 
> > > modify gradle files.
> > >
> > > -Nikhil
> > >
> > > -Original Message-
> > > From: Carlos Santana [mailto:csantan...@gmail.com]
> > > Sent: Tuesday, January 19, 2016 9:00 AM
> > > To: dev <dev@cordova.apache.org>
> > > Subject: Re: [DISCUSS] Android@5.1.0
> > >
> > > What you guys think of making MIN SDK VER 15 instead of 14 as the
> default
> > > for this Android@5.1.0 ?
> > >
> > > We have a couple of plugins that required minsdk 15 [1], I also 
> > > see
> that
> > > phonegap push plugin have problems with min sdk 14 here [2]
> > >
> > > Instead of anoying user with readme instructions to change it to 
> > > 15,
> why
> > > not make the default 15, this way more stuff would work out of the 
> > > box
> > with
> > > less trouble.
> > > I guess if there is someone for a particular reason wants minsdk 
> > > 14,
> they
> > > can change the default the same way as today using config.xml
> > >
> > >
> > > [1]:
> > >
> > >
> >
> https://github.com/ibm-bluemix-mobile-services/bms-clientsdk-cordova-p
> lugin-push/blob/master/README.md
> > > [2]:
> > >
> > >
> >
> https://github.com/phonegap/phonegap-plugin-push/blob/master/docs/INST
> ALLATION.md#minsdkversion--14
> > >
> > > On Mon, Jan 18, 2016 at 6:38 PM Joe Bowser <bows...@gmail.com> wrote:
> > >
> > > > I don't think the gradle build issue should block the release, 
> > > > as annoying as it is, the workaround is literally adding a
> > > >
> > >
> >
> https://na01.safelinks.protection.outlook.com/?url=gradle.properties
> ata=01%7c01%7cnikhilkh%40microsoft.com%7c08ad0056c7e24290e0e508d320f20
> 60f%7c72f988bf86f141af91ab2d7cd011db47%7c1=Ifi7afmy86ZZTmwxUjkWa
> 7guies16P67hnK7hD%2b4hSs%3d
> > > file with a single line.
> > > >
> > > > As far as who owns it, I think Cordova should probably own that, 
> > > > but are there any other plugins that need NDK support?
> > > >
> > > > (I just ran into this less than an hour ago. It's annoying that
> Google
> > > > deprecates something without something else to replace it.)
> > > >
> > > > On Mon, Jan 18, 2016 at 3:34 PM, Darryl Pogue <dar...@dpogue.ca>
> > wrote:
> > > >
> > > > > With cordova-an

RE: [DISCUSS] Android@5.1.0

[Nikhil Khandelwal]

If this is a regression in behavior and CrossWalk will not work out of the box 
- we should consider fixing it. Sounds like it is a simple fix. Is there a JIRA 
for this?

Overall, we shouldn't require/expect Cordova JS developers to modify gradle 
files.

-Nikhil

-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com] 
Sent: Tuesday, January 19, 2016 9:00 AM
To: dev 
Subject: Re: [DISCUSS] Android@5.1.0

What you guys think of making MIN SDK VER 15 instead of 14 as the default for 
this Android@5.1.0 ?

We have a couple of plugins that required minsdk 15 [1], I also see that 
phonegap push plugin have problems with min sdk 14 here [2]

Instead of anoying user with readme instructions to change it to 15, why not 
make the default 15, this way more stuff would work out of the box with less 
trouble.
I guess if there is someone for a particular reason wants minsdk 14, they can 
change the default the same way as today using config.xml


[1]:
https://github.com/ibm-bluemix-mobile-services/bms-clientsdk-cordova-plugin-push/blob/master/README.md
[2]:
https://github.com/phonegap/phonegap-plugin-push/blob/master/docs/INSTALLATION.md#minsdkversion--14

On Mon, Jan 18, 2016 at 6:38 PM Joe Bowser  wrote:

> I don't think the gradle build issue should block the release, as 
> annoying as it is, the workaround is literally adding a 
> https://na01.safelinks.protection.outlook.com/?url=gradle.properties=01%7c01%7cnikhilkh%40microsoft.com%7c08ad0056c7e24290e0e508d320f2060f%7c72f988bf86f141af91ab2d7cd011db47%7c1=Ifi7afmy86ZZTmwxUjkWa7guies16P67hnK7hD%2b4hSs%3d
>  file with a single line.
>
> As far as who owns it, I think Cordova should probably own that, but 
> are there any other plugins that need NDK support?
>
> (I just ran into this less than an hour ago. It's annoying that Google 
> deprecates something without something else to replace it.)
>
> On Mon, Jan 18, 2016 at 3:34 PM, Darryl Pogue  wrote:
>
> > With cordova-android master, the Crosswalk Webview plugin fails to 
> > build because gradle was updated and now NDK support has been removed.
> >
> > It can be re-enabled by providing a 
> > https://na01.safelinks.protection.outlook.com/?url=gradle.properties
> > =01%7c01%7cnikhilkh%40microsoft.com%7c08ad0056c7e24290e0e508d320f2060f%7c72f988bf86f141af91ab2d7cd011db47%7c1=Ifi7afmy86ZZTmwxUjkWa7guies16P67hnK7hD%2b4hSs%3d
> >  file, but I'm not sure whether that should be the responsibility of 
> > Cordova-Android or the Crosswalk Webview plugin.
> >
> > On 18 January 2016 at 15:12, Steven Gill  wrote:
> >
> > > Going to start this today. Let me know if you have any concerns.
> > >
> > > -Steve
> > >
> >
>

RE: [DISCUSS] Core Plugins and Android API 23

[Nikhil Khandelwal]

We had a good discussion about this offline with Joe, Simon, Steve, Jesse, 
Parashu and Jason. We came to the following agreement: 
This is a temporary fix to the plugins which we need to take to ensure Cordova 
5.x tools behavior of using the edge plugins does not break for our users. We 
will pursue the change for all the affected plugins. This will go out in the 
next PLUGINS release which will happen before the Cordova 6.0 release. Since 
this a temporary fix, we aim to remove it in 6 months (giving reasonable time 
for our user base to move to Cordova 6.x+ which will have a better plugin 
version pinning mechanism).

Thanks,
Nikhil

-Original Message-
From: Simon MacDonald [mailto:simon.macdon...@gmail.com] 
Sent: Thursday, January 7, 2016 4:00 PM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Core Plugins and Android API 23

I'm going to play devils advocate a bit here:


> There are valid reasons why many app developers might not be ready to 
> move to API level 23:
>   1) They have an app which is stabilizing or in maintenance mode and 
> they don't want to risk destabilization by moving to a new major 
> Cordova version, Cordova Android platform, and Android API level.
>

If the developer is not ready to move to a new version of Cordova Android or 
the Android API would it not also follow that they shouldn't be changing their 
plugin versions?


>   2) They are using a 3rd-party plugin which has not yet been updated 
> to request Android permissions as required by API level 23. There are 
> probably a lot of plugins affected, since access to any of the 
> following things on Android M requires runtime permission requests: 
> calendar, contacts, phone, camera, microphone, location, beacons, sensors, 
> SMS, storage.
>

Right, so if the 3rd party plugin they are using doesn't support Android M they 
should either a) not upgrade or b) send a PR to the plugin maintainer so 
everyone can benefit.


>   3) They might not have the capacity or ability to test their app on 
> devices running Android M. Because API 23 enables the new permissions 
> model only on Android M, it requires testing on that platform.
>
>
Everyone has access to the Android emulator.


> In any of the above cases, developers might still like to benefit from 
> some of the major bug fixes in those 5 popular core plugins mentioned 
> below. Or even if they weren't specifically looking for bug fixes, it 
> would be a much better experience if adding or updating one of those 
> plugins would just work, rather than failing on Android. The 
> explanation for the failure will not be obvious to many users, if they 
> overlooked the warning when installing the plugin or if they were 
> using another tool to add the plugin where the warning wasn't surfaced.
>

 Seems like you are describing a tooling problem here. If the tool doesn't 
surface the warning or allows the user to add a plugin that is incompatible 
with the version of Cordova Android that is being used really sounds like a bug 
in the tooling to me.


> Of course developers should be encouraged to upgrade to the latest 
> most secure highest-quality version of Cordova. But the encouragement 
> does not need to be so forceful. This proposed change gives developers 
> more time to upgrade, and allows for more choice about when to upgrade 
> individual parts
> (plugins) rather than limiting them to all-or-nothing.


 I would argue that the developer has an infinite amount of time to upgrade. 
Nothing is forcing you to upgrade to the latest Cordova Android or Android API. 
They can continue to use the same version of Cordova Android and plugins that 
are currently working in their app. If the developer is using semver properly 
and we do our job right they shouldn't pick up breaking changes. For instance, 
if the API of a plugin changes we bump the major version of the plugin so users 
who setup their config.xml to use:



will effectively prevent the user from picking up the breaking change in camera 
version 2.0.0.

Simon Mac Donald
https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fhi.im%2fsimonmacdonald=01%7c01%7cnikhilkh%40microsoft.com%7c84fb6405edf74f47453208d317beb5e5%7c72f988bf86f141af91ab2d7cd011db47%7c1=B8DuMuPF8aUU6xvIlpYTi3LJPs1HbENcHXS8JrHqEu0%3d

RE: CB-10201: Why is gradlew not executable? Design reason?

[Nikhil Khandelwal]

I don’t think there was a design reason. As Bill mentions in CB-10201 - for 
some odd reason gradlew from the android SDK directory (the source of the file) 
does not have the execute permissions. It makes sense for us to set the 
permissions either after copying or before invoking it. We do this is a number 
of places in cordova-lib as well.

Let's go ahead and fix this.

Thanks,
Nikhil

-Original Message-
From: Joe Bowser [mailto:bows...@gmail.com] 
Sent: Thursday, January 7, 2016 1:14 PM
To: dev 
Subject: CB-10201: Why is gradlew not executable? Design reason?

Hey

I'm wondering if we have a design reason for the gradle executable to not be 
executable? Does anyone know? If not, I'm probably going to change it if nobody 
else gets to it first.

Re: [DISCUSS] Plugins release

[Nikhil Khandelwal]

Sorry for being late to respond. It will be great if we can publish the plugins 
release on npm at the same time as the tools release which pins android 5.0. 
Not publishing at the same time will break a very simple use case that Alex 
described below.

-Nikhil




On 11/20/15, 12:43 PM, "Steven Gill"  wrote:

>Manually update until we released tools with android 5 pinned.
>
>The failure is expected. Users will have to manually update to android 5 or
>use an older version of file.
>
>This was discussed before.
>
>Steps:
>* android 5 release
>* plugins release
>* tools release
>On Nov 20, 2015 8:26 AM, "Alexander Sorokin (Akvelon)" <
>v-als...@microsoft.com> wrote:
>
>> Hi guys,
>>
>> Currently we have Android ~4.1.0 pinned in CLI but the file plugin (and
>> all plugins that depend on file plugin) depends on Android@5.0.0 or
>> higher, so after this release, this will fail:
>>
>> cordova platform add android
>> cordova plugin add cordova-plugin-file
>>
>> The output would be:
>> Installing "cordova-plugin-file" for android
>> Plugin doesn't support this project's cordova-android version.
>> cordova-android: 4.1.1, failed version requirement: >=5.0.0-dev
>> Skipping 'cordova-plugin-file' for android
>>
>> So, should Android@5.0.0 be pinned first or are we expecting users to
>> manually update android to 5.0.0 ?
>>
>> Thanks,
>> Alexander Sorokin
>>
>> -Original Message-
>> From: Steven Gill [mailto:stevengil...@gmail.com]
>> Sent: Friday, November 20, 2015 2:04 AM
>> To: dev@cordova.apache.org
>> Subject: Re: [DISCUSS] Plugins release
>>
>> Thanks Joe!
>>
>> P.S. The "r" prefixed tags messed up my coho commands to create the tgz
>> and print the corresponding tags. I have now fixed that problem by not
>> stripping the "r" for plugin tags so those tags fail the semver check.
>>
>> Attempt 2 for plugins vote is now out.
>>
>>
>> On Thu, Nov 19, 2015 at 11:03 AM, Joe Bowser  wrote:
>>
>> > I just did the test again on this end, and the only test failures I
>> > got were the ones where I was expected to approve permissions.  It
>> > seems that these tests will keep running and that the permission
>> > dialog won't block the UI.  This is the correct behaviour, but it does
>> > mean that we have to make sure that we give the permissions for the
>> > tests to work before we run them.
>> >
>> > After I approved all the permissions, I just get three Contacts
>> > failures and a Media plugin failure.  One of the Contacts failures
>> > comes from running on a device that I use day-to-day, since I don't
>> > get that one on the HTC One M8, but the other three errors are
>> consistent.
>> >
>> > Furthermore, the manual tests for Media work fine, so I don't think
>> > that this should block the release.
>> >
>> > On Wed, Nov 18, 2015 at 11:24 PM, Steven Gill 
>> > wrote:
>> >
>> > > Oh and 1 failing cordova-plugin-file-transfer test.
>> > >
>> > > I'll look more into the failures tomorrow.
>> > >
>> > >
>> > > On Wed, Nov 18, 2015 at 11:12 PM, Steven Gill
>> > > 
>> > > wrote:
>> > >
>> > > > all the plugins have been updated and are ready to be voted on.
>> > > >
>> > > > I am getting 10 failing tests on my nexus 5X
>> > > > (cordova-android@5.0.0, running marshmallow on phone).
>> > > > * contacts (always failing for me)
>> > > > * media
>> > > >
>> > > > Can someone else try running mobile spec and tell me what they are
>> > > seeing?
>> > > >
>> > > > I can start the vote thread once these are resolved or we decide
>> > > > they
>> > are
>> > > > expected. Everything has been tagged but I can easily update tags
>> > > > if
>> > > needed.
>> > > >
>> > > >
>> > > >
>> > > > On Tue, Nov 10, 2015 at 11:50 PM, julio cesar sanchez <
>> > > > jcesarmob...@gmail.com> wrote:
>> > > >
>> > > >> Any more iOS experts can review my pull request?
>> > > >>
>> > > >> 2015-11-11 6:59 GMT+01:00 Steven Gill :
>> > > >>
>> > > >> > Going to move forward with this tomorrow. Any holdups, let me
>> know.
>> > > >> Here or
>> > > >> > #plugins on slack.
>> > > >> >
>> > > >> > On Fri, Nov 6, 2015 at 2:51 PM, Richard Knoll <
>> > rikn...@microsoft.com>
>> > > >> > wrote:
>> > > >> >
>> > > >> > > I plan on merging in
>> > > >> > > https://github.com/apache/cordova-plugin-camera/pull/135 for
>> > > >> > > the
>> > > >> camera
>> > > >> > > plugin if there are no objections.
>> > > >> > >
>> > > >> > > Thanks,
>> > > >> > > Richard
>> > > >> > >
>> > > >> > > -Original Message-
>> > > >> > > From: Steven Gill [mailto:stevengil...@gmail.com]
>> > > >> > > Sent: Friday, November 6, 2015 11:38 AM
>> > > >> > > To: dev@cordova.apache.org
>> > > >> > > Subject: Re: [DISCUSS] Plugins release
>> > > >> > >
>> > > >> > > With plugin changes, it is always nice to get reviews since
>> > > >> > > it
>> > could
>> > > >> > > affect every platform.
>> > > >> > >
>> > > >> > > file:146 is merged
>> > > >> > > file: 119 LGTM
>> 

RE: [DISCUSS] Tools Release

[Nikhil Khandelwal]

Great. Good quick fix. Let's get this out soon. Node.js 5.0 just got released 
and it uses npm@3+ by default. Currently, cordova create fails with npm@3. 
Let's release soon to address that.

-Nikhil

-Original Message-
From: Shazron [mailto:shaz...@gmail.com] 
Sent: Thursday, October 29, 2015 1:52 PM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Tools Release

Breakage: 
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fbrowse%2fCB-9902=01%7c01%7cnikhilkh%40microsoft.com%7cb3fabc4510a84924082708d2e0a2f56d%7c72f988bf86f141af91ab2d7cd011db47%7c1=l5roCBV0kQT%2b%2fylFBwBrd5I9IhnpfVcvIRjSss0KaQ0%3d
Sent a PR: 
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fapache%2fcordova-lib%2fpull%2f335=01%7c01%7cnikhilkh%40microsoft.com%7cb3fabc4510a84924082708d2e0a2f56d%7c72f988bf86f141af91ab2d7cd011db47%7c1=6n3jtKymyZyqnu7WGJDyZD2phxtNuHFwsVokZ5d94l4%3d

On Thu, Oct 29, 2015 at 12:46 PM, Carlos Santana <csantan...@gmail.com> wrote:
> Thanks Alex and Tim !
>
> - Carlos
> @csantanapr
>
>> On Oct 29, 2015, at 2:50 PM, Tim Barham <tim.bar...@microsoft.com> wrote:
>>
>> There was still a problem with the tests in cordova-lib. Alex's fix has just 
>> been merged and tests are now green.
>>
>> -Original Message-
>> From: Carlos Santana [mailto:csantan...@gmail.com]
>> Sent: Wednesday, October 28, 2015 7:49 PM
>> To: dev@cordova.apache.org
>> Subject: Re: [DISCUSS] Tools Release
>>
>> What's the latest status on this? cordova-android master being fixed to make 
>> it green again?
>>
>>> On Wed, Oct 28, 2015 at 7:28 AM Vladimir Kotikov (Akvelon) < 
>>> v-vlk...@microsoft.com> wrote:
>>>
>>> This is fixed in
>>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgit
>>> hu
>>> b.com%2fapache%2fcordova-android%2fcommit%2f78fa7374d97ad9ed85c5c857
>>> a7
>>> 7a8f3830d600f9.=01%7c01%7cTBARHAM%40064d.mgd.microsoft.com%7c4f
>>> 38 
>>> f6ba36884c66bc2b08d2e00b8584%7c72f988bf86f141af91ab2d7cd011db47%7c1&
>>> sd ata=K7eLyX5rvUBrS1NAp7rpMyXX9aAIOMYvNe6rv4JmfJ4%3d
>>> However tests are still failing locally, but this seems to be a 
>>> problem with tests, not LIB/Android. Alex Sorokin is looking into this.
>>>
>>> -
>>> Best regards, Vladimir
>>>
>>> -Original Message-
>>> From: Tim Barham [mailto:tim.bar...@microsoft.com]
>>> Sent: Tuesday, October 27, 2015 8:36 PM
>>> To: dev@cordova.apache.org
>>> Subject: RE: [DISCUSS] Tools Release
>>>
>>> This appears to be a cordova-android issue (I followed the steps in 
>>> that test and filed 
>>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fbrowse%2fCB-9880=01%7c01%7cv-vlkoti%40064d.mgd.microsoft.com%7c0244e3527d6b45a4881308d2def52abb%7c72f988bf86f141af91ab2d7cd011db47%7c1=3fDroGSY1qWwUtl6JusJiD6JgJR6wJw8iITxXGovBdU%3d).
>>> Although I agree we should fix the cordova-android issue and get 
>>> cordova-lib green before proceeding.
>>>
>>> -Original Message-
>>> From: Steven Gill [mailto:stevengil...@gmail.com]
>>> Sent: Tuesday, October 27, 2015 10:33 AM
>>> To: dev@cordova.apache.org
>>> Subject: Re: [DISCUSS] Tools Release
>>>
>>> Held up currently with
>>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fiss
>>> ue 
>>> s.apache.org%2fjira%2fbrowse%2fCB-9872=01%7c01%7cTBARHAM%40064d
>>> .m 
>>> gd.microsoft.com%7cc4dbc8e54ea148e81f6b08d2def4a97e%7c72f988bf86f141
>>> af 
>>> 91ab2d7cd011db47%7c1=wCOMC8m5jTXPqjbYJUS9ESk5%2fM4g3mG1BZQb0ys
>>> rr
>>> fU%3d
>>>
>>> On Mon, Oct 26, 2015 at 11:05 AM, Steven Gill 
>>> <stevengil...@gmail.com>
>>> wrote:
>>>
>>>> Sounds good. I'll be going through the process today.
>>>>
>>>> On Mon, Oct 26, 2015 at 8:45 AM, Nikhil Khandelwal 
>>>> <nikhi...@microsoft.com
>>>>> wrote:
>>>>
>>>>> Looking forward to the release today.
>>>>>
>>>>> Btw, cordova-app-hello-world also needs to be released at the same 
>>>>> time and cordova-lib needs to take a dependency on the new version.
>>>>> This will resolve the npm@3 bug that I’ve seen being reported by
>>> multiple people.
>>>>> We should push to get that resolved and should be part of our 
>>>>> release blog – support for npm@3.
>>>>>
>>>&g

RE: [BUG] Plugin Device Motion breaking on WP8

[Nikhil Khandelwal]

It seems to be caused by this commit: 
https://github.com/apache/cordova-plugin-device-motion/commit/90ef274ea8cae2a5639d148b769f7718f33b7134

-Nikhil

-Original Message-
From: Dmitry Blotsky [mailto:dblot...@microsoft.com] 
Sent: Tuesday, October 27, 2015 9:24 PM
To:  
Subject: [BUG] Plugin Device Motion breaking on WP8

Hey folks,

WP8 build is breaking due an error in the device-motion plugin. JIRA: 
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fbrowse%2fCB-9886.=01%7c01%7cnikhilkh%40microsoft.com%7cebbf180b3c8b4b85ce1808d2df4fa73a%7c72f988bf86f141af91ab2d7cd011db47%7c1=RrBGC5MzGRKIDw2vVPToR3jxwQ89IIVIU6lPxWpuzmE%3d

Kindly,
Dmitry

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

RE: [DISCUSS] Removing blog posts repo

[Nikhil Khandelwal]

Steve,
Did you mean you will shut this down? 
https://github.com/cordova/apache-blog-posts

And not https://github.com/apache/cordova-docs

-Nikhil

-Original Message-
From: Shazron [mailto:shaz...@gmail.com] 
Sent: Wednesday, October 28, 2015 6:53 PM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Removing blog posts repo

+1

On Wednesday, October 28, 2015, Steven Gill  wrote:

> Sounds good to me.
>
> For reference, we are going to shut down 
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithu
> b.com%2fcordova%2fapache-blog-posts=01%7c01%7cnikhilkh%40microsof
> t.com%7c70b3b806ea524b58ac3e08d2e003bc80%7c72f988bf86f141af91ab2d7cd01
> 1db47%7c1=5VwlxQeBvnxj6Eyo89ZRZXOoHemnMzpKRChID181Fh0%3d in 
> favor of 
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithu
> b.com%2fapache%2fcordova-docs.=01%7c01%7cnikhilkh%40microsoft.com
> %7c70b3b806ea524b58ac3e08d2e003bc80%7c72f988bf86f141af91ab2d7cd011db47
> %7c1=Uw%2b6qOSifOmMuTvbB2jYieYwmmiYaYzm03BIvZR6KS8%3d
>
> On Wed, Oct 28, 2015 at 5:25 PM, Dmitry Blotsky 
> >
> wrote:
>
> > Hey folks,
> >
> > Now that the website, blog, and docs are all in one Git repo, can we 
> > discontinue the blog posts repo? Contributions can be made just as
> before,
> > by committing to the Git repo. Moreover, there is no more 
> > clone-then-copy-over procedure.
> >
> > Kindly,
> > Dmitry
> > 
> > - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> 
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> 
> >
> >
>

RE: [DISCUSS] Jira triage

[Nikhil Khandelwal]

I made some updates based on feedback. Please review this version: 
https://github.com/apache/cordova-coho/pull/97

I'm hoping we can agree on a JIRA triage process in the next couple of days.

-Nikhil

-Original Message-
From: Joe Bowser [mailto:bows...@gmail.com] 
Sent: Tuesday, October 20, 2015 9:24 AM
To: dev <dev@cordova.apache.org>
Subject: Re: [DISCUSS] Jira triage

I've added my feedback at the pull request.  I do think that 2 days is too soon 
to close something, since I can close almost all the current issues on JIRA if 
that was the case.

On Tue, Oct 20, 2015 at 9:12 AM, Nikhil Khandelwal <nikhi...@microsoft.com>
wrote:

> I am fine with all these recommendations. The key is to be consistent. 
> I have documented this and more details here:
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithu
> b.com%2fapache%2fcordova-coho%2fpull%2f97=01%7c01%7cnikhilkh%40mi
> crosoft.com%7c234742a2be054f60290708d2d96af314%7c72f988bf86f141af91ab2
> d7cd011db47%7c1=FV7OkZ85gneTNfrSPYmWAZvZjWkO%2bPTmPGYThsuqAkI%3d
>
> Let's continue discussion on the PR or this thread. I don't want the 
> process to be heavy-weight - though my goal is to address few key things:
> - Consistent process for JIRA triage
> - Accountability for who does JIRA triage? Is it component owner or a 
> rotating duty appropriate for a tech lead? Either way this is a fair 
> amount of work - but absolutely important for maintaining high level of 
> quality.
> - We identify and raise critical regressions and release patch 
> versions to fix them. I think we need to respond faster to higher pri issues.
>
> -Nikhil
>
> -Original Message-
> From: Shazron [mailto:shaz...@gmail.com]
> Sent: Monday, October 19, 2015 12:11 PM
> To: dev@cordova.apache.org
> Subject: Re: [DISCUSS] Jira triage
>
> Thanks Steve.
> Three recommendations below.
>
> A.
> I recommend a "Platform" pre-fix for platform issues. ie rename "iOS", 
> "Android" etc to "Platform iOS", "Platform Android" (like plugins have 
> a prefix of "Plugin" already).
>
> This however would not prevent people from assigning these components 
> to non-platform issues however :/ So it will be up to us to triage it 
> appropriately.
>
> I've been treating a "Component" as equivalent to filing an issue 
> against the appropriate repo (1:1 correspondence).
> This makes it easier to focus on a particular repo's issues without 
> the noise of unrelated plugin issues.
>
> B.
> For issues that are related to a platform implementation of a plugin, 
> my recommendation is to tag it with the component related to the 
> plugin, i.e "Plugin Contacts", then add a label for the platform 
> "ios". Currently I've been adding it to the Environment field, which may not 
> be as searchable.
>
> So from our Cordova project search:
>
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissue
> s.apache.org%2fjira%2fissues%2f%3fjql%3dproject%2520%253D%2520CB=
> 01%7c01%7cnikhilkh%40microsoft.com%7c097b79948b2141e4ff7508d2d8b9393c%
> 7c72f988bf86f141af91ab2d7cd011db47%7c1=K%2bHGeNnNg400WtWEK4vYlHK
> CZzboEGVs1wC7LJoHR50%3d
>
> (maybe we can alias this to
> https://na01.safelinks.protection.outlook.com/?url=search.cordova.io%3
> f=01%7c01%7cnikhilkh%40microsoft.com%7c097b79948b2141e4ff7508d2d8
> b9393c%7c72f988bf86f141af91ab2d7cd011db47%7c1=ufesrrJ81qVLwYL80a
> qMpEsWAU5QmagI6eHvuw88Vc4%3d
> )
>
> Add the Component - "Plugin Contacts"
> Add the Label - "ios".
>
> You'll get this result:
>
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissue
> s.apache.org%2fjira%2fissues%2f%3fjql%3dproject%2520%253D%2520CB%2520A
> ND%2520component%2520%253D%2520%2522Plugin%2520Contacts%2522%2520AND%2
> 520labels%2520%253D%2520ios=01%7c01%7cnikhilkh%40microsoft.com%7c
> 097b79948b2141e4ff7508d2d8b9393c%7c72f988bf86f141af91ab2d7cd011db47%7c
> 1=BN4b8GeohG%2bplE5Q2MXi6V%2bSv0mlgyDKI21dhiOV62g%3d
>
> C.
> One component per issue - hard rule. It can start out as a discussion 
> involving more than one Component, but MUST evolve into multiple 
> issues (or
> subtasks) -- one per component. I've seen issues where it affects 
> multiple components and the communication on what has been done for 
> what platform gets muddled, resulting in inaction for one platform.
>
>
> Shaz
>
> On Sat, Oct 17, 2015 at 10:53 PM, Steven Gill <stevengil...@gmail.com>
> wrote:
> > At the Cordova F2F, some discrepancies were found in how we are 
> > triaging issues on Jira. Especially in terms of plugin issues and if 
> > they should have platform related components. This email is to 
> 

RE: [DISCUSS] Tools Release

[Nikhil Khandelwal]

Looking forward to the release today.

Btw, cordova-app-hello-world also needs to be released at the same time and 
cordova-lib needs to take a dependency on the new version. This will resolve 
the npm@3 bug that I’ve seen being reported by multiple people. We should push 
to get that resolved and should be part of our release blog – support for npm@3.

-Nikhil

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Friday, October 23, 2015 2:35 PM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Tools Release

Okay. I will start work on this release Monday unless anyone has concerns.

-Steve

On Fri, Oct 23, 2015 at 12:57 PM, Nikhil Khandelwal <nikhi...@microsoft.com>
wrote:

> +1 - I'm hoping we'll release iOS as well before the next CLI release.
>
> -Nikhil
>
> -Original Message-
> From: Carlos Santana [mailto:csantan...@gmail.com]
> Sent: Friday, October 23, 2015 12:48 PM
> To: dev@cordova.apache.org
> Subject: [DISCUSS] Tools Release
>
> I think we should release a version of the CLI now, from what Steve 
> told me there is a lot changes going in, and also contains the switch 
> to use npm instead of CPR, and other changes around npm3 and nodejs4
>
> This will allow for trains to move forward and get feedback on the 
> releases.
>
> Propose sequence:
> 1. Release CLI
> 2. Release Android
> 3. Release Plugins
> 4. Release CLI with latest released platformed pinned
>
> Rinse and repeat while singing choo choo !
>

RE: [DISCUSS] Tools Release

[Nikhil Khandelwal]

+1 - I'm hoping we'll release iOS as well before the next CLI release.

-Nikhil

-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com] 
Sent: Friday, October 23, 2015 12:48 PM
To: dev@cordova.apache.org
Subject: [DISCUSS] Tools Release

I think we should release a version of the CLI now, from what Steve told me 
there is a lot changes going in, and also contains the switch to use npm 
instead of CPR, and other changes around npm3 and nodejs4

This will allow for trains to move forward and get feedback on the releases.

Propose sequence:
1. Release CLI
2. Release Android
3. Release Plugins
4. Release CLI with latest released platformed pinned

Rinse and repeat while singing choo choo !

RE: [Android][Discuss] Change name of CordovaWebView to CordovaWebInterface

[Nikhil Khandelwal]

I understand that it won't break currently and it will break on the next major 
version bump. IMHO it's just not worth it for this name change.

Historically, we've had challenges with giving sufficient notice from breaking 
changes. I would avoid them unless absolutely needed. 

-Nikhil

-Original Message-
From: Simon MacDonald [mailto:simon.macdon...@gmail.com] 
Sent: Thursday, October 22, 2015 12:14 PM
To: dev@cordova.apache.org
Subject: Re: [Android][Discuss] Change name of CordovaWebView to 
CordovaWebInterface

Let's just be clear that in Cordova Android 5.0 nothing will break.
The interface CordovaWebView has been renamed to CordovaWebInterface but that 
won't break anything as we introduce a new class called, wait for it, 
CordovaWebView that extends the new CordovaWebInterface. This way all current 
code that uses CordovaWebView will continue to work without modification.

If we start updating our documentation, i.e. how to write a CordovaPlugin for 
Android, and give people plenty of notice that this is going to happen then I 
don't see why we wouldn't want to move forward.

That's just my 2 cents.

Simon Mac Donald
https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fhi.im%2fsimonmacdonald=01%7c01%7cnikhilkh%40microsoft.com%7caf6077fb55224d7b1d2c08d2db1508fe%7c72f988bf86f141af91ab2d7cd011db47%7c1=50aLt1e0sp9z4TrrSBiMnAaBdSj1RrUuIEcnPaHGD1U%3d


On Wed, Oct 21, 2015 at 6:13 PM, Nikhil Khandelwal <nikhi...@microsoft.com> 
wrote:
> Thanks, Joe for the summary of the impact later.
>
> -1. IMO - a naming change is no worth the effort and future breakage.
>
> -Nikhil
>
> -Original Message-
> From: Joe Bowser [mailto:bows...@gmail.com]
> Sent: Wednesday, October 21, 2015 11:06 AM
> To: dev <dev@cordova.apache.org>
> Subject: Re: [Android][Discuss] Change name of CordovaWebView to 
> CordovaWebInterface
>
> Yes, I do.  I had to search through mobilespec, but here it is:
>
> private static final boolean HAS_BUILT_IN_SPLASH_SCREEN =
> Integer.valueOf(CordovaWebView.CORDOVA_VERSION.split("\\.")[0]) < 4;
>
> Also, every plugin that calls initialize requires a CordovaWebView passed 
> into it.  That's a pretty big change.  I also haven't touched on Third Party 
> WebViews like Crosswalk, which would have to do the change.
>
>
> On Tue, Oct 20, 2015 at 1:59 PM, Steven Gill <stevengil...@gmail.com> wrote:
>
>> Joe, do you have a small example of what could break with this change.
>> What is a usecase for someone to reference CordovaWebView
>>
>> On Tue, Oct 20, 2015 at 1:38 PM, Joe Bowser <bows...@gmail.com> wrote:
>>
>> > I'll pull this in at the end of the day.  This small change may 
>> > break
>> stuff
>> > further down the road, so people should comment on it now.
>> >
>> > On Tue, Oct 20, 2015 at 1:37 PM, Joe Bowser <bows...@gmail.com> wrote:
>> >
>> > > OK, Going to pull this in.
>> > >
>> > > On Tue, Oct 20, 2015 at 10:02 AM, Simon MacDonald < 
>> > > simon.macdon...@gmail.com> wrote:
>> > >
>> > >> +1 from me as I'm the one that initiated the PR.
>> > >>
>> > >> Simon Mac Donald
>> > >> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2f
>> > >> h
>> > >> i.im%2fsimonmacdonald=01%7c01%7cnikhilkh%40microsoft.com%7c
>> > >> 8
>> > >> 619031b1eef484bd48508d2da425e41%7c72f988bf86f141af91ab2d7cd011db
>> > >> 4 7%7c1=IXoWw2z2L7EhCorf4kK4EJ7Ux89hdUjmP%2bKsF%2bJdwf0%3d
>> > >>
>> > >> On Tue, Oct 20, 2015 at 12:23 PM, Darryl Pogue 
>> > >> <dar...@dpogue.ca>
>> > wrote:
>> > >>
>> > >> > +1 for doing this with the major version bump
>> > >> >
>> > >> > On 20 October 2015 at 09:15, Joe Bowser <bows...@gmail.com> wrote:
>> > >> >
>> > >> > > Hey
>> > >> > >
>> > >> > > We're close to getting 5.0.x ready for release, but I want 
>> > >> > > to add
>> > one
>> > >> > more
>> > >> > > pull request:
>> > >> > >
>> > >> > > https://na01.safelinks.protection.outlook.com/?url=https%3a%
>> > >> > > 2
>> > >> > > f%2fgithub.com%2fapache%2fcordova-android%2fpull%2f227=
>> > >> > > 0 
>> > >> > > 1%7c01%7cnikhilkh%40microsoft.com%7c8619031b1eef484bd48508d2
>> > >> > > d 
>> > >> > > a425e41%7c72f988bf86f141af91ab2d7cd011db47%7c1=w5TY

RE: [DISCUSS] cordova-ios 4.0.0 release

[Nikhil Khandelwal]

What are good tasks to be poached on cordova-ios-4.x? In particular, my team 
can help out with cordova-lib related ios tasks. Also, fixing plugins or filing 
issues for upcoming breakages are great areas we can help out. ios 4.x has 
critical fixes for XCode 7 usage which people need sooner rather than later 
[1]. Could you mark them with a tag 'poachable'? We can follow up on slack as 
well if this requires back and forth. I'll ping you later today.

As for breaking change below, I've not been keeping up ios-4.x as closely - I 
must've missed the communication on it. I understand there is a possibility of 
breaking because of how "categories" work in Objective-C (I just read up on it 
- it's a nifty feature). I also understand that they were not *intended* to be 
used. AFAIK we do not document our platform APIs and even our core plugins 
(camera) was using this particular API. As we discussed in cordova F2F

As far as I understand, Cordova-ios 3.9.x is not usable with XCODE 7 - ATS, 
ENABLE_BITCODE being two issues[2]. Cordova-ios 4.x is not ready and will 
likely break the third-party plugins they use when it releases. Should we 
really push for a patch release for cordova-ios 3.9.x to fix XCODE 7 issues? 
@Shaz: How feasible would this be?

[1] http://stackoverflow.com/search?q=ENABLE_BITCODE+%5Bcordova%5D
[2] http://stackoverflow.com/search?q=%22XCODE+7%22+%5Bcordova%5D 

-Nikhil

-Original Message-
From: Shazron [mailto:shaz...@gmail.com] 
Sent: Tuesday, October 20, 2015 10:34 PM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] cordova-ios 4.0.0 release

This release will not be complete as long as the cordova-ios-4.x board has 
issues. The only major issue is the plugin building stuff plus docs.

The removal was projected for some time - you might not have remembered the 
discussions in JIRA. NSData+Base64 are "Categories" in Objective-C parlance. 
These were *never* documented to be used outside of Cordova and are fair game 
for removal, particularly a major version release. The problem with Categories 
are, other non-Cordova code can implement these Categories with the same names 
as well -- and during runtime the implementation that is "chosen" is 
indeterminate. We can't have that with Cordova since JSON serialization and 
deserialization are important for the bridge.

Yes, a blog post and "migration guide" is coming, among other things on my 
plate -- see 
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fbrowse%2fCB-9785=01%7c01%7cnikhilkh%40microsoft.com%7c65695fee7d4149d0fd4108d2d9d9507f%7c72f988bf86f141af91ab2d7cd011db47%7c1=sGf5ya8dvvT2BxunFhyA0X7IzCXRdEG4bxmbZT0rgu0%3d
My plan is to send pull requests to some plugins with the common issues, so 
people can see how to update.



On Tue, Oct 20, 2015 at 9:45 PM, Nikhil Khandelwal <nikhi...@microsoft.com> 
wrote:
> Where are we with this release?
>
> Alexander Sorokin did some analysis on plugin build failures because of this 
> ios-4.0-dev and there are quite a few.
>
> This spreadsheet summarizes the build failures with the build log in a 
> comment:
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fdocs.
> google.com%2fspreadsheets%2fd%2f1sm8ioXY21z3RdyqT7J9n1Q_hmm9zgod5awToF
> F_X66U%2fedit%3fusp%3dsharing=01%7c01%7cnikhilkh%40microsoft.com%
> 7c65695fee7d4149d0fd4108d2d9d9507f%7c72f988bf86f141af91ab2d7cd011db47%
> 7c1=PTiv%2bPvncuJ4g0b%2bj8GTO1ovdCKL8Y%2fHFW4QEQt%2b6i8%3d
>
> Quite a few of the failures are because of the removal of NsData+Base64.h 
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fapache%2fcordova-ios%2fblob%2fmaster%2fguides%2fAPI%2520changes%2520in%25204.0.md%23nsdatabase64h.=01%7c01%7cnikhilkh%40microsoft.com%7c65695fee7d4149d0fd4108d2d9d9507f%7c72f988bf86f141af91ab2d7cd011db47%7c1=GS43mbEp5TKlUWs4A2mRMZ36sMaBxniFC%2fQbRkzzg24%3d
>  What's the rationale behind removing this? Did we deprecate these methods 
> before we removed them?
>
> I understand the changes for plugin developers are simple - but it does seem 
> to require a number of plugins to be updated to ensure apps are not broken.
>
> It will be great to publish a blog post on cordova blog about these breaking 
> changes.
>
> -Nikhil
>
>
> -Original Message-
> From: Carlos Santana [mailto:csantan...@gmail.com]
> Sent: Wednesday, September 2, 2015 10:22 PM
> To: dev@cordova.apache.org
> Subject: Re: [DISCUSS] cordova-ios 4.0.0 release
>
> +1 Choo Choo ...
>
> I reviewed all links in your proposal and they look and don't have 
> concerns
>
> IBM MobileFirst was affected only by the API change of using 
> webviewengine now but that's so far the only major change
>
> In the kaban board for 4.0 there are some issues I consider nice to 
> have that are not blockers to get a 4.0 out for i

RE: [Discuss] Cordova-common release

[Nikhil Khandelwal]

It should not - it's a good change for Android 5.0. However, it does represent 
a big change and we need more testing. From what I understand, it's release 
ready with no known issues. Vladimir: Is that correct?

As for the cordova-common dependency, cordova-android will bundle it. And we 
don't have to wait for a cordova-common release to release cordova-android.

-Nikhil

-Original Message-
From: Joe Bowser [mailto:bows...@gmail.com] 
Sent: Wednesday, October 21, 2015 9:19 AM
To: dev <dev@cordova.apache.org>
Subject: Re: [Discuss] Cordova-common release

OK, how will this impact the 5.0 release of Android?

On Tue, Oct 20, 2015 at 6:07 PM, Nikhil Khandelwal <nikhi...@microsoft.com>
wrote:

> It got checked in earlier this morning.
>
> -Nikhil
>
> -Original Message-
> From: Joe Bowser [mailto:bows...@gmail.com]
> Sent: Tuesday, October 20, 2015 2:34 PM
> To: dev <dev@cordova.apache.org>
> Subject: Re: [Discuss] Cordova-common release
>
> So, when did the PlatformAPI change land in Android?
>
> On Tue, Oct 20, 2015 at 2:32 PM, Parashuram N <panar...@microsoft.com>
> wrote:
>
> > +1 - YES please. Requiring cordoba-common for my
> > react-native-cordova-plugin adapter was a nightmare !!
> >
> >
> >
> >
> > On 10/20/15, 2:23 PM, "Nikhil Khandelwal" <nikhi...@microsoft.com>
> wrote:
> >
> > >+1 to publishing cordova-common to npm.
> > >
> > >-Nikhil
> > >
> > >-Original Message-
> > >From: Steven Gill [mailto:stevengil...@gmail.com]
> > >Sent: Tuesday, October 20, 2015 2:20 PM
> > >To: dev@cordova.apache.org
> > >Subject: Re: [Discuss] Cordova-common release
> > >
> > >I want to revisit this.
> > >
> > >So cordova-android has a dependency now on cordova-common. It is a
> > bundledDependency so when we generate a tar to release 
> > cordova-android, it will be included. It will also be in the 
> > cordova-android package that gets downloaded with cordova platform add.
> > >
> > >This is fine for released work, but more annoying for development. 
> > >I need
> > to npm link cordova-common into cordova-android (and soon every 
> > platform which implements common platformAPI). We could check in 
> > cordova-common into cordova-android but that isn't a great solution
> either.
> > >
> > >I agree that we should be going towards smaller modules and not 
> > >having a
> > case of cordovaLib1, cordovaLib2, etc. I think this is still going 
> > to be a work in progress and will take some time.
> > >
> > >For the interim, I recommend we publish cordova-common. Of course,
> > continue to add it as a bundledDependency so users don't need to npm 
> > install it with released packages.
> > >
> > >On Wed, Sep 30, 2015 at 7:24 AM, Vladimir Kotikov (Akvelon) <
> > v-vlk...@microsoft.com> wrote:
> > >
> > >> > I still do not understand what are you trying to solve by 
> > >> > having all
> > >> that content published as big blob.
> > >> Code deduplication is the main reason. All the things from 
> > >> 'cordova-common' will be used by platforms intensively, so we 
> > >> need to share this code and keep it separately from LIB to share easily.
> > >> Publishing is basically doesn't required for this, and bundling 
> > >> 'cordova-common' into LIB is enough for this purpose.
> > >>
> > >> Another reason was that third-party tool might want to use some 
> > >> of this functionality (like your example with ConfigParser), so 
> > >> we need to have this package on NPM to allow them to get it. For 
> > >> this case I now do agree with you that separate packages for 
> > >> ConfigParser, PluginInfo and other stuff looks better than 
> > >> putting it into one big
> > package.
> > >>
> > >> -
> > >> Best regards, Vladimir
> > >>
> > >>
> > >> -Original Message-
> > >> From: Carlos Santana [mailto:csantan...@gmail.com]
> > >> Sent: Wednesday, September 30, 2015 2:07 PM
> > >> To: dev@cordova.apache.org
> > >> Subject: Re: [Discuss] Cordova-common release
> > >>
> > >> Yes temporary, maybe we can discuss some more in F2F
> > >>
> > >> I still do not understand what are you trying to solve by having 
> > >> all that content published as big blob.
> > >>
> > >> If the packages are only

RE: [DISCUSS] cordova-ios 4.0.0 release

[Nikhil Khandelwal]

Sent the message before completing it.

What are good tasks to be poached on cordova-ios-4.x? In particular, my team 
can help out with cordova-lib related ios tasks. Also, fixing plugins or filing 
issues for upcoming breakages are great areas we can help out. ios 4.x has 
critical fixes for XCode 7 usage which people need sooner rather than later 
[1]. Could you mark them with a tag 'poachable'? We can follow up on slack as 
well if this requires back and forth. I'll ping you later today.

As for breaking change below, I've not been keeping up ios-4.x as closely - I 
must've missed the communication on it. I understand there is a possibility of 
breaking because of how "categories" work in Objective-C (I just read up on it 
- it's a nifty feature). I also understand that they were not *intended* to be 
used. AFAIK we do not document our platform APIs and even our core plugins 
(camera) was using this particular API. As we discussed in cordova F2F, 
developers do not have high confidence with the version of plugins 
(particularly third party) to pick and choose and anything we could do in how 
we version our API/manage breaking changes - will make Cordova a smoother 
experience. The impact of this breaking change is HIGH from the small sample 
set of plugins we tested. 

As far as I understand, Cordova-ios 3.9.x is not usable with XCODE 7 - ATS, 
ENABLE_BITCODE being two issues[2]. Cordova-ios 4.x is not ready and will 
likely break the third-party plugins they use when it releases. Should we 
really push for a patch release for cordova-ios 3.9.x to fix XCODE 7 issues? 
@Shaz: How feasible would this be? I know some of us at Microsoft can help do 
this with guidance.

[1] http://stackoverflow.com/search?q=ENABLE_BITCODE+%5Bcordova%5D
[2] http://stackoverflow.com/search?q=%22XCODE+7%22+%5Bcordova%5D

-Original Message-----
From: Nikhil Khandelwal [mailto:nikhi...@microsoft.com] 
Sent: Wednesday, October 21, 2015 7:09 AM
To: dev@cordova.apache.org
Subject: RE: [DISCUSS] cordova-ios 4.0.0 release

What are good tasks to be poached on cordova-ios-4.x? In particular, my team 
can help out with cordova-lib related ios tasks. Also, fixing plugins or filing 
issues for upcoming breakages are great areas we can help out. ios 4.x has 
critical fixes for XCode 7 usage which people need sooner rather than later 
[1]. Could you mark them with a tag 'poachable'? We can follow up on slack as 
well if this requires back and forth. I'll ping you later today.

As for breaking change below, I've not been keeping up ios-4.x as closely - I 
must've missed the communication on it. I understand there is a possibility of 
breaking because of how "categories" work in Objective-C (I just read up on it 
- it's a nifty feature). I also understand that they were not *intended* to be 
used. AFAIK we do not document our platform APIs and even our core plugins 
(camera) was using this particular API. As we discussed in cordova F2F

As far as I understand, Cordova-ios 3.9.x is not usable with XCODE 7 - ATS, 
ENABLE_BITCODE being two issues[2]. Cordova-ios 4.x is not ready and will 
likely break the third-party plugins they use when it releases. Should we 
really push for a patch release for cordova-ios 3.9.x to fix XCODE 7 issues? 
@Shaz: How feasible would this be?

[1] 
https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fstackoverflow.com%2fsearch%3fq%3dENABLE_BITCODE%2b%255Bcordova%255D=01%7c01%7cnikhilkh%40microsoft.com%7cea1259c06ea744fff37e08d2da213c72%7c72f988bf86f141af91ab2d7cd011db47%7c1=EssE%2b0BTiymN1aS7HtBoOVM%2busvcGAKZHanRs9QZXYw%3d
[2] 
https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fstackoverflow.com%2fsearch%3fq%3d%2522XCODE%2b7%2522%2b%255Bcordova%255D=01%7c01%7cnikhilkh%40microsoft.com%7cea1259c06ea744fff37e08d2da213c72%7c72f988bf86f141af91ab2d7cd011db47%7c1=PBGhQ3sro1fE6Ft3ZOHBv3RkLdNMOg%2fp4gFgSq2Eets%3d
 

-Nikhil

-Original Message-
From: Shazron [mailto:shaz...@gmail.com]
Sent: Tuesday, October 20, 2015 10:34 PM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] cordova-ios 4.0.0 release

This release will not be complete as long as the cordova-ios-4.x board has 
issues. The only major issue is the plugin building stuff plus docs.

The removal was projected for some time - you might not have remembered the 
discussions in JIRA. NSData+Base64 are "Categories" in Objective-C parlance. 
These were *never* documented to be used outside of Cordova and are fair game 
for removal, particularly a major version release. The problem with Categories 
are, other non-Cordova code can implement these Categories with the same names 
as well -- and during runtime the implementation that is "chosen" is 
indeterminate. We can't have that with Cordova since JSON serialization and 
deserialization are important for the bridge.

Yes, a blog post and "migration guide" is coming, among other things on my 
plate -- see 
https://na01

RE: [Android][Discuss] Change name of CordovaWebView to CordovaWebInterface

[Nikhil Khandelwal]

Thanks, Joe for the summary of the impact later.

-1. IMO - a naming change is no worth the effort and future breakage.

-Nikhil

-Original Message-
From: Joe Bowser [mailto:bows...@gmail.com] 
Sent: Wednesday, October 21, 2015 11:06 AM
To: dev 
Subject: Re: [Android][Discuss] Change name of CordovaWebView to 
CordovaWebInterface

Yes, I do.  I had to search through mobilespec, but here it is:

private static final boolean HAS_BUILT_IN_SPLASH_SCREEN =
Integer.valueOf(CordovaWebView.CORDOVA_VERSION.split("\\.")[0]) < 4;

Also, every plugin that calls initialize requires a CordovaWebView passed into 
it.  That's a pretty big change.  I also haven't touched on Third Party 
WebViews like Crosswalk, which would have to do the change.


On Tue, Oct 20, 2015 at 1:59 PM, Steven Gill  wrote:

> Joe, do you have a small example of what could break with this change. 
> What is a usecase for someone to reference CordovaWebView
>
> On Tue, Oct 20, 2015 at 1:38 PM, Joe Bowser  wrote:
>
> > I'll pull this in at the end of the day.  This small change may 
> > break
> stuff
> > further down the road, so people should comment on it now.
> >
> > On Tue, Oct 20, 2015 at 1:37 PM, Joe Bowser  wrote:
> >
> > > OK, Going to pull this in.
> > >
> > > On Tue, Oct 20, 2015 at 10:02 AM, Simon MacDonald < 
> > > simon.macdon...@gmail.com> wrote:
> > >
> > >> +1 from me as I'm the one that initiated the PR.
> > >>
> > >> Simon Mac Donald
> > >> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fh
> > >> i.im%2fsimonmacdonald=01%7c01%7cnikhilkh%40microsoft.com%7c8
> > >> 619031b1eef484bd48508d2da425e41%7c72f988bf86f141af91ab2d7cd011db4
> > >> 7%7c1=IXoWw2z2L7EhCorf4kK4EJ7Ux89hdUjmP%2bKsF%2bJdwf0%3d
> > >>
> > >> On Tue, Oct 20, 2015 at 12:23 PM, Darryl Pogue 
> > wrote:
> > >>
> > >> > +1 for doing this with the major version bump
> > >> >
> > >> > On 20 October 2015 at 09:15, Joe Bowser  wrote:
> > >> >
> > >> > > Hey
> > >> > >
> > >> > > We're close to getting 5.0.x ready for release, but I want to 
> > >> > > add
> > one
> > >> > more
> > >> > > pull request:
> > >> > >
> > >> > > https://na01.safelinks.protection.outlook.com/?url=https%3a%2
> > >> > > f%2fgithub.com%2fapache%2fcordova-android%2fpull%2f227=0
> > >> > > 1%7c01%7cnikhilkh%40microsoft.com%7c8619031b1eef484bd48508d2d
> > >> > > a425e41%7c72f988bf86f141af91ab2d7cd011db47%7c1=w5TYcbCH
> > >> > > %2fhLIhbrZImOsVFgGMfp%2bIk0Dl6Qk6ADzMVc%3d
> > >> > >
> > >> > > This is a trivial pull request, but I want to get buy-in from 
> > >> > > the
> > list
> > >> > for
> > >> > > doing the rename for CordovaWebView class to be changed 
> > >> > > before we
> > >> start
> > >> > > deprecating it.  This means we're probably going to remove 
> > >> > > the
> shim
> > in
> > >> > the
> > >> > > next major version.
> > >> > >
> > >> > > Thoughts?
> > >> > >
> > >> > > Joe
> > >> > >
> > >> >
> > >>
> > >
> > >
> >
>

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

RE: [DISCUSS] Jira triage

[Nikhil Khandelwal]

I am fine with all these recommendations. The key is to be consistent. I have 
documented this and more details here: 
https://github.com/apache/cordova-coho/pull/97

Let's continue discussion on the PR or this thread. I don't want the process to 
be heavy-weight - though my goal is to address few key things:
- Consistent process for JIRA triage
- Accountability for who does JIRA triage? Is it component owner or a rotating 
duty appropriate for a tech lead? Either way this is a fair amount of work - 
but absolutely important for maintaining high level of quality.
- We identify and raise critical regressions and release patch versions to fix 
them. I think we need to respond faster to higher pri issues.

-Nikhil

-Original Message-
From: Shazron [mailto:shaz...@gmail.com] 
Sent: Monday, October 19, 2015 12:11 PM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Jira triage

Thanks Steve.
Three recommendations below.

A.
I recommend a "Platform" pre-fix for platform issues. ie rename "iOS", 
"Android" etc to "Platform iOS", "Platform Android" (like plugins have a prefix 
of "Plugin" already).

This however would not prevent people from assigning these components to 
non-platform issues however :/ So it will be up to us to triage it 
appropriately.

I've been treating a "Component" as equivalent to filing an issue against the 
appropriate repo (1:1 correspondence).
This makes it easier to focus on a particular repo's issues without the noise 
of unrelated plugin issues.

B.
For issues that are related to a platform implementation of a plugin, my 
recommendation is to tag it with the component related to the plugin, i.e 
"Plugin Contacts", then add a label for the platform "ios". Currently I've been 
adding it to the Environment field, which may not be as searchable.

So from our Cordova project search:
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fissues%2f%3fjql%3dproject%2520%253D%2520CB=01%7c01%7cnikhilkh%40microsoft.com%7c097b79948b2141e4ff7508d2d8b9393c%7c72f988bf86f141af91ab2d7cd011db47%7c1=K%2bHGeNnNg400WtWEK4vYlHKCZzboEGVs1wC7LJoHR50%3d

(maybe we can alias this to 
https://na01.safelinks.protection.outlook.com/?url=search.cordova.io%3f=01%7c01%7cnikhilkh%40microsoft.com%7c097b79948b2141e4ff7508d2d8b9393c%7c72f988bf86f141af91ab2d7cd011db47%7c1=ufesrrJ81qVLwYL80aqMpEsWAU5QmagI6eHvuw88Vc4%3d)

Add the Component - "Plugin Contacts"
Add the Label - "ios".

You'll get this result:
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fissues%2f%3fjql%3dproject%2520%253D%2520CB%2520AND%2520component%2520%253D%2520%2522Plugin%2520Contacts%2522%2520AND%2520labels%2520%253D%2520ios=01%7c01%7cnikhilkh%40microsoft.com%7c097b79948b2141e4ff7508d2d8b9393c%7c72f988bf86f141af91ab2d7cd011db47%7c1=BN4b8GeohG%2bplE5Q2MXi6V%2bSv0mlgyDKI21dhiOV62g%3d

C.
One component per issue - hard rule. It can start out as a discussion involving 
more than one Component, but MUST evolve into multiple issues (or subtasks) -- 
one per component. I've seen issues where it affects multiple components and 
the communication on what has been done for what platform gets muddled, 
resulting in inaction for one platform.


Shaz

On Sat, Oct 17, 2015 at 10:53 PM, Steven Gill  wrote:
> At the Cordova F2F, some discrepancies were found in how we are 
> triaging issues on Jira. Especially in terms of plugin issues and if 
> they should have platform related components. This email is to discuss 
> the discrepancies and for recommendations to be made and agreed upon.
>
> According to the F2F minutes[1], Joe, Shaz and Nikhil would lead the 
> discussion and make recommendations for the triage workflow. And of 
> course, everyone is encouraged and welcomed to participate.
>
> [1]
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fdocs.
> google.com%2fdocument%2fd%2f1MArKRmnLS052LBbhPxJF57_4ZivghOj8znWo5sTCk
> bU%2fedit%3fusp%3dsharing=01%7c01%7cnikhilkh%40microsoft.com%7c09
> 7b79948b2141e4ff7508d2d8b9393c%7c72f988bf86f141af91ab2d7cd011db47%7c1&
> sdata=60eBbnJVRZEa4nHlxOMHmSsHn0I1saLnL4%2bgvuwqhnk%3d

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

RE: [Discuss] Cordova-common release

[Nikhil Khandelwal]

ova-common release
> >
> > Do we need to absolutely publish this to npm?
> >
> > Can we just include the dependency in the platform as a bundle
> dependency?
> >
> > We just need to update coho to npm install/link the cordoba-common 
> > package when doing a release of what ever component need it? (i.e.
> > cordova-android)
> >
> > Will this get you what you want? Why does it absolutely need to be 
> > in
> npm registry?
> >
> > I really don't think will be a good idea to publish two npm packages
> "cordova-lib" and "cordova-common"
> >
> > Sorry if I'm being a pain in the ass, maybe I'm something obvious 
> > here
> >
> >
> >> On Tue, Sep 29, 2015 at 1:34 PM Steven Gill 
> >> <stevengil...@gmail.com>
> wrote:
> >>
> >> Sounds good. Let's move forward
> >> On Sep 29, 2015 10:21 AM, "Nikhil Khandelwal"
> >> <nikhi...@microsoft.com>
> >> wrote:
> >>
> >>> +1. I understand the value of Carlos' proposal, but in the spirit 
> >>> +of
> >>> moving forward with this which is fairly complicated refactor 
> >>> involving multiple releases and repos, I would like us to make 
> >>> progress on this
> >> soon
> >>> and not add significant scope to this effort.
> >>>
> >>>
> >>> -Nikhil
> >>>
> >>> -Original Message-
> >>> From: Sergey Grebnov (Akvelon) [mailto:v-seg...@microsoft.com]
> >>> Sent: Tuesday, September 29, 2015 1:34 AM
> >>> To: dev@cordova.apache.org
> >>> Subject: RE: [Discuss] Cordova-common release
> >>>
> >>> +1
> >>>
> >>> -Original Message-
> >>> From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com]
> >>> Sent: Tuesday, September 29, 2015 11:27 AM
> >>> To: dev@cordova.apache.org
> >>> Subject: RE: [Discuss] Cordova-common release
> >>>
> >>> Agree with you, guys.
> >>>
> >>> Unfortunately, the underlying modules in `cordova-common` are not 
> >>> really atomic, since they depending on each other. For example 
> >>> ConfigParser requires `xmlHelpers`, `events` and `CordovaError` as 
> >>> a
> dependencies.
> >>> Reworking them to be truly separated might be sort of problematic, 
> >>> especially in context of message logging (as they use shared event
> >> emitter
> >>> to log output to console).
> >>>
> >>> So I still propose is to release `common` module as-is and then 
> >>> gradually move inner modules out to separate packages.
> >>>
> >>> -
> >>> Best regards, Vladimir.
> >>>
> >>> -Original Message-
> >>> From: Carlos Santana [mailto:csantan...@gmail.com]
> >>> Sent: Friday, September 25, 2015 7:33 PM
> >>> To: dev@cordova.apache.org
> >>> Subject: Re: [Discuss] Cordova-common release
> >>>
> >>> Sorry a typo
> >>> to use "bundleDependencies" you will have a node_modules/ 
> >>> directory directly under "common/node_modules/cordova-error/"
> >>>
> >>> and the the small modules (i.e. cordoba-util, cordova-plugin-info,
> >>> etc..) will be located there.
> >>>
> >>> then have explicit ignores for the dependencies you don't want to 
> >>> be source control like npm [2]
> >>>
> >>> [2]:
> >> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgi
> >> th
> >> u
> >> b.com%2fnpm%2fnpm%2fblob%2fmaster%2f.gitignore%23L24=01%7c01%7
> >> cv
> >> -
> >> vlkoti%40064d.mgd.microsoft.com%7c73b4ff38f0fe41e1f18608d2c5c70e0f%
> >> 7c
> >> 7
> >> 2f988bf86f141af91ab2d7cd011db47%7c1=tU%2bFHDUJZXzXnbG%2fUP7AY
> >> 4q
> >> E
> >> CnvsbnsJ%2bvEriJvqYcU%3d
> >>>
> >>>
> >>> On Fri, Sep 25, 2015 at 12:24 PM Carlos Santana 
> >>> <csantan...@gmail.com>
> >>> wrote:
> >>>
> >>>> Yes after reviewing the changes, I understood the purpose of the 
> >>>> code that you seperated to avoid duplicate code between the other 
> >>>> top level modules (i.e. platforms, lib, cli)
> >>>>
> >>>> I still think small modules is the way to go.
> >>>>
> >>>> Do

RE: [Discuss] Cordova-common release

[Nikhil Khandelwal]

It got checked in earlier this morning.

-Nikhil

-Original Message-
From: Joe Bowser [mailto:bows...@gmail.com] 
Sent: Tuesday, October 20, 2015 2:34 PM
To: dev <dev@cordova.apache.org>
Subject: Re: [Discuss] Cordova-common release

So, when did the PlatformAPI change land in Android?

On Tue, Oct 20, 2015 at 2:32 PM, Parashuram N <panar...@microsoft.com>
wrote:

> +1 - YES please. Requiring cordoba-common for my
> react-native-cordova-plugin adapter was a nightmare !!
>
>
>
>
> On 10/20/15, 2:23 PM, "Nikhil Khandelwal" <nikhi...@microsoft.com> wrote:
>
> >+1 to publishing cordova-common to npm.
> >
> >-Nikhil
> >
> >-Original Message-
> >From: Steven Gill [mailto:stevengil...@gmail.com]
> >Sent: Tuesday, October 20, 2015 2:20 PM
> >To: dev@cordova.apache.org
> >Subject: Re: [Discuss] Cordova-common release
> >
> >I want to revisit this.
> >
> >So cordova-android has a dependency now on cordova-common. It is a
> bundledDependency so when we generate a tar to release 
> cordova-android, it will be included. It will also be in the 
> cordova-android package that gets downloaded with cordova platform add.
> >
> >This is fine for released work, but more annoying for development. I 
> >need
> to npm link cordova-common into cordova-android (and soon every 
> platform which implements common platformAPI). We could check in 
> cordova-common into cordova-android but that isn't a great solution either.
> >
> >I agree that we should be going towards smaller modules and not 
> >having a
> case of cordovaLib1, cordovaLib2, etc. I think this is still going to 
> be a work in progress and will take some time.
> >
> >For the interim, I recommend we publish cordova-common. Of course,
> continue to add it as a bundledDependency so users don't need to npm 
> install it with released packages.
> >
> >On Wed, Sep 30, 2015 at 7:24 AM, Vladimir Kotikov (Akvelon) <
> v-vlk...@microsoft.com> wrote:
> >
> >> > I still do not understand what are you trying to solve by having 
> >> > all
> >> that content published as big blob.
> >> Code deduplication is the main reason. All the things from 
> >> 'cordova-common' will be used by platforms intensively, so we need 
> >> to share this code and keep it separately from LIB to share easily.
> >> Publishing is basically doesn't required for this, and bundling 
> >> 'cordova-common' into LIB is enough for this purpose.
> >>
> >> Another reason was that third-party tool might want to use some of 
> >> this functionality (like your example with ConfigParser), so we 
> >> need to have this package on NPM to allow them to get it. For this 
> >> case I now do agree with you that separate packages for 
> >> ConfigParser, PluginInfo and other stuff looks better than putting 
> >> it into one big
> package.
> >>
> >> -
> >> Best regards, Vladimir
> >>
> >>
> >> -Original Message-
> >> From: Carlos Santana [mailto:csantan...@gmail.com]
> >> Sent: Wednesday, September 30, 2015 2:07 PM
> >> To: dev@cordova.apache.org
> >> Subject: Re: [Discuss] Cordova-common release
> >>
> >> Yes temporary, maybe we can discuss some more in F2F
> >>
> >> I still do not understand what are you trying to solve by having 
> >> all that content published as big blob.
> >>
> >> If the packages are only for Cordova components to depend on then 
> >> we control the release and we can include them easily.
> >>
> >> If the code is to be share by third party or anyone out there then 
> >> it make sense to put in npm.
> >>
> >> One concrete example is cordova-configparser, Our IBM tool is using 
> >> it in our own models code so today we taking a copy, if it's 
> >> available thru npm then we can stated as a dependency and manage it 
> >> as a npm package vs a loosely node module js file
> >>
> >> Maybe not all classes need to be converted to npm packages maybe it 
> >> can be some cordova-configparser cordova-utils cordova-helper
> >>
> >> Also do some refactoring and dependency cleaning, I saw a node 
> >> module dependeding on underscore and the file only had one simple 
> >> call to
> >> _.find()
> >>
> >> We were going to use that module, but then decided not to since it 
> >> depended on underscore for a simple thing, this creates legal 
> >> clearance work and more de

RE: [DISCUSS] cordova-ios 4.0.0 release

[Nikhil Khandelwal]

Where are we with this release? 

Alexander Sorokin did some analysis on plugin build failures because of this 
ios-4.0-dev and there are quite a few.

This spreadsheet summarizes the build failures with the build log in a comment:
https://docs.google.com/spreadsheets/d/1sm8ioXY21z3RdyqT7J9n1Q_hmm9zgod5awToFF_X66U/edit?usp=sharing

Quite a few of the failures are because of the removal of NsData+Base64.h 
https://github.com/apache/cordova-ios/blob/master/guides/API%20changes%20in%204.0.md#nsdatabase64h.
 What's the rationale behind removing this? Did we deprecate these methods 
before we removed them?

I understand the changes for plugin developers are simple - but it does seem to 
require a number of plugins to be updated to ensure apps are not broken.

It will be great to publish a blog post on cordova blog about these breaking 
changes.

-Nikhil


-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com] 
Sent: Wednesday, September 2, 2015 10:22 PM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] cordova-ios 4.0.0 release

+1 Choo Choo ...

I reviewed all links in your proposal and they look and don't have concerns

IBM MobileFirst was affected only by the API change of using webviewengine now 
but that's so far the only major change

In the kaban board for 4.0 there are some issues I consider nice to have that 
are not blockers to get a 4.0 out for iOS if we get closed to the ios9 launched 
date they can be deferred to a 4.0.1

On Tue, Sep 1, 2015 at 7:38 PM Shazron  wrote:

> Gotta get the train going again, it's been too long.
>
> The kanban board for this is at:
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissue
> s.apache.org%2fjira%2fsecure%2fRapidBoard.jspa%3frapidView%3d76=0
> 1%7c01%7cnikhilkh%40microsoft.com%7c457cbbc8d60c461beede08d2b41fb286%7
> c72f988bf86f141af91ab2d7cd011db47%7c1=b11%2bCUSw4d5Q9SN%2b8roAWo
> Ra2plB0lJXeCJb9RC2Sqw%3d
>
> Please help if you can by assigning an issue to yourself, and 
> selecting the "Start Progress" button. This will show who is working 
> on what in the middle "In Progress" column.
>
> I've trimmed this and it includes cordova-ios platform issues, and 
> some plugin issues. Priority given to platform issues of course, and 
> issues with iOS 9. If there is a pressing issue that needs to go in, 
> assign it the label "cordova-ios-4.0.x" but propose it to this thread 
> first so we don't get de-railed, there's only so much room on the 
> train. Similarly if you think an issue can get thrown off the train to 
> cordova-ios-5.0.x, post on this thread.
>
> Focus is on core plugin stability with the new platform, since it does 
> have API changes. If downstream distribution people are on this list, 
> this concerns your third-party plugins too.
>
> The easiest way to test if it affects your plugin building:
>
> ```
> cordova platform add 
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithu
> b.com%2fapache%2fcordova-ios.git=01%7c01%7cnikhilkh%40microsoft.c
> om%7c457cbbc8d60c461beede08d2b41fb286%7c72f988bf86f141af91ab2d7cd011db
> 47%7c1=%2fyEILBHFok2F6BK9aeOOd3ibr3V4GNFhvhWWek%2fRqjs%3d
> cordova plugin add your-plugin-id
> cordova build
> ```
>
> Plugin updates and highlights:
> - API changes doc:
>
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fapache%2fcordova-ios%2fblob%2fmaster%2fguides%2fAPI%2520changes%2520in%25204.0.md=01%7c01%7cnikhilkh%40microsoft.com%7c457cbbc8d60c461beede08d2b41fb286%7c72f988bf86f141af91ab2d7cd011db47%7c1=oc6rb7Mbb2%2bDmKRPwtRBd3jyl0gh74mA5I%2fwiHLpqhM%3d
> - 3 new private core plugins to the platform:
>
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fapache%2fcordova-ios%2ftree%2fmaster%2fCordovaLib%2fClasses%2fPrivate%2fPlugins=01%7c01%7cnikhilkh%40microsoft.com%7c457cbbc8d60c461beede08d2b41fb286%7c72f988bf86f141af91ab2d7cd011db47%7c1=xoM2X4%2bcjp9oqKHhtviNfEdimxiIR%2bTJrg80tI1Fbek%3d
> - Plugin localized strings and resource loading:
>
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fapache%2fcordova-ios%2fblob%2fmaster%2fCordovaLib%2fClasses%2fPublic%2fCDVPlugin%252BResources.h=01%7c01%7cnikhilkh%40microsoft.com%7c457cbbc8d60c461beede08d2b41fb286%7c72f988bf86f141af91ab2d7cd011db47%7c1=m2xhhALHTJ8rb2aPg68hMWVcU9ebo51zGXwihQEr1LY%3d
>- Preferences helper:
>
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fapache%2fcordova-ios%2fblob%2fmaster%2fCordovaLib%2fClasses%2fPublic%2fNSDictionary%252BCordovaPreferences.h=01%7c01%7cnikhilkh%40microsoft.com%7c457cbbc8d60c461beede08d2b41fb286%7c72f988bf86f141af91ab2d7cd011db47%7c1=jUUM60Yks2vRWVPJdeUc8Hhek3CuH6bYKwQlbXDZSxM%3d
>- WebViews as plugins. UIWebView is a private core plugin (see above).
> WKWebView as a plugin installable
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithu
> 

RE: Merging smores branch into Cordova-Android TODAY

[Nikhil Khandelwal]

Thanks Joe! 

Most of the changes look good. I did leave a comment on the design of the 
CordovaPlugin base class - I don’t want to block progress on that. Feel free to 
merge it - but let's see if we can rationalize why we are adding the base class 
methods - it seems only for the Geoloc plugin - but I don’t know enough about 
this area to understand this fully.

I would love to see the guidance for what changes a plugin developer should 
make to work in Marshmallow - Perhaps even giving them a link to our commit to 
fix one of the plugins.

-Nikhil

-Original Message-
From: Joe Bowser [mailto:bows...@gmail.com] 
Sent: Friday, October 16, 2015 2:33 PM
To: dev 
Subject: Re: Merging smores branch into Cordova-Android TODAY

I guess that I'm going to have to write the blog post for this release, 
including how permissions work on Android.

On Fri, Oct 16, 2015 at 11:36 AM, Parashuram N 
wrote:

> As discussed in the Cordova Face to Face yesterday, we said that we 
> want our users to be aware of changes like these that will hit them. 
> Is someone looking at writing a blog post for this ?
>
> -Original Message-
> From: Joe Bowser [mailto:bows...@gmail.com]
> Sent: Friday, October 16, 2015 10:35 AM
> To: dev 
> Subject: Merging smores branch into Cordova-Android TODAY
>
> Hey
>
> I'm going to be merging the smores branch into master by 3:00 PM today.
> I've left this pull request open for the past week, so we should be 
> ready to go.  Please let me know if there's any reason I shouldn't 
> merge this in.  Once this is merged, there will be a discuss thread 
> for Cordova-Android 5.0.0.
>
> If you have a Nexus device, please update it to Marshmallow and start 
> testing Cordova applications and filing those issues in our JIRA.  If 
> there's third party plugins, please let me know, and I will look at 
> them and see if there's any major issues with that plugin being 
> upgraded and will try to contact the author.
>
> If we can be a bit more pro-active with this one to try and avoid 
> breakage (there shouldn't be much breakage, since most plugins don't 
> ask for more permissions), that would be awesome.
>
> Thanks
>
> Joe
>

RE: Merging smores branch into Cordova-Android TODAY

[Nikhil Khandelwal]

I think there are two aspects of the CI. I think Dmitry is handling the 
BuildBOT CI update to support android-23.

Travis CI need android 23 which is causing Joe's change to fail in PR state: 
https://travis-ci.org/apache/cordova-android/builds/83964922

Joe you need to update Travis, as part of your change. In the file, 
https://github.com/apache/cordova-android/blob/master/.travis.yml replace 
android-22 with android-23.

Thanks,
Nikhil



-Original Message-
From: Joe Bowser [mailto:bows...@gmail.com] 
Sent: Friday, October 16, 2015 2:41 PM
To: dev 
Subject: Re: Merging smores branch into Cordova-Android TODAY

OK, I'll push this monday.

On Fri, Oct 16, 2015 at 2:37 PM, Dmitry Blotsky 
wrote:

> I’m installing 23 on the CI right now. Should be done, conservatively, 
> in
> 2 hours.
>
> > On Oct 16, 2015, at 1:38 PM, Joe Bowser  wrote:
> >
> > OK, I locally did the rebase.  How soon can we get the CI to have
> > android-23 installed so that Travis no longer fails?
> >
> > On Fri, Oct 16, 2015 at 11:36 AM, Parashuram N 
> > 
> > wrote:
> >
> >> As discussed in the Cordova Face to Face yesterday, we said that we 
> >> want our users to be aware of changes like these that will hit 
> >> them. Is
> someone
> >> looking at writing a blog post for this ?
> >>
> >> -Original Message-
> >> From: Joe Bowser [mailto:bows...@gmail.com]
> >> Sent: Friday, October 16, 2015 10:35 AM
> >> To: dev 
> >> Subject: Merging smores branch into Cordova-Android TODAY
> >>
> >> Hey
> >>
> >> I'm going to be merging the smores branch into master by 3:00 PM today.
> >> I've left this pull request open for the past week, so we should be
> ready
> >> to go.  Please let me know if there's any reason I shouldn't merge 
> >> this in.  Once this is merged, there will be a discuss thread for 
> >> Cordova-Android 5.0.0.
> >>
> >> If you have a Nexus device, please update it to Marshmallow and 
> >> start testing Cordova applications and filing those issues in our 
> >> JIRA.  If there's third party plugins, please let me know, and I 
> >> will look at them and see if there's any major issues with that 
> >> plugin being upgraded and will try to contact the author.
> >>
> >> If we can be a bit more pro-active with this one to try and avoid
> breakage
> >> (there shouldn't be much breakage, since most plugins don't ask for 
> >> more permissions), that would be awesome.
> >>
> >> Thanks
> >>
> >> Joe
> >>
>
>

RE: [DISCUSS] Survey Banner on Main Site

[Nikhil Khandelwal]

If we look at GA for survey vs GA for website, there is a huge difference in 
the demographics. For example, there are almost no survey impressions from 
India, while India contributes the largest % of website users of any country. 

I'm all for using other channels to promote the survey, however, the website 
represents the biggest userbase that we should ideally ensure gets a look at 
the survey to ensure we have captured our target segment's opinions.

As for theming, I would maintain the same elegant theme as our current website 
and make it unobtrusive and dismissable.

-Nikhil

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Saturday, October 10, 2015 1:14 PM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Survey Banner on Main Site

Personally, I think the site looks too good for a banner that doesn't fit with 
the theme. Why don't we just do a blog post about the survey instead and 
promote it on other channels (google groups, framework mailing lists + their 
slacks)

On Fri, Oct 9, 2015 at 6:07 PM, Dmitry Blotsky 
wrote:

> Hey folks,
>
> A suggestion came up to put a dismissible banner on the Cordova 
> website that points to the survey we’ve put up, so that it will reach 
> a broader audience than Twitter. Raghav Katyal is working on this 
> right now. However in discussing styling, we had an idea...
>
> What do you folks think of making the banner in the great nostalgic 
> style of 2000’s “you are the 1000th visitor” ads, with flashing colors 
> and Comic Sans? We think it would be hilarious. What do you all think?
>
> Kindly,
> Dmitry
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>

RE: Is CPR going offline

[Nikhil Khandelwal]

I am in favor of keeping it running without making any updates. There is fairly 
high % of users using cordova cli version < cordova 5 (~25% based on survey 
responses). Since our survey is not yet broadly publicized, but only using 
twitter, this number is likely higher.

We should look at download numbers from CPR and when they become sufficiently 
low, then we should decide to take it offline.

Our switch to plugins.cordova.io use the new plugin search will likely push 
people to upgrade to the new CLI versions and phase out CPR - but it's going to 
take more time than another week (our initial phase out date).

-Nikhil

-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com] 
Sent: Friday, October 9, 2015 2:49 PM
To: Cordova Dev 
Subject: Re: Is CPR going offline

If there is no reason to keep it alive, I was already handing out obituaries 
for CPR, it served a good purpose for his lifetime

On Fri, Oct 9, 2015 at 9:43 AM Gorkem Ercan  wrote:

>
> Hi,
> Our announced date Oct 15 is next week.
> Will CPR be go offline as planned or do we see that we should give it 
> more time.
> --
> Gorkem
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

RE: Cordova Face to Face Meeting

[Nikhil Khandelwal]

Thanks, Martijn! This is a great outline. I merged most of what you mentioned 
here: 
https://github.com/cordova/cordova-discuss/blob/master/proposals/Face2Face-Oct15.md

Feel free to send a PR if I missed out anything. It will be great if others can 
add or +1 areas of their interest for the Face2Face.

-Nikhil

-Original Message-
From: Martijn Walraven [mailto:martijnwalra...@meteor.com] 
Sent: Monday, October 5, 2015 6:35 AM
To: dev@cordova.apache.org
Subject: Re: Cordova Face to Face Meeting

I’m new here, and I don’t know how these meetings usually work, but I thought 
it might make sense to structure the sessions around questions instead of 
smaller topics. This way, we can get a more open discussion going and talk 
about these topics within a larger context.

Some of the questions I would be interested in discussing are:

- How can we improve the development experience?
  - What can we learn from the React Native developer experience?
- Replacing 'white screen of death' with an error reporting screen
- Adding a development/debugger menu
  - How can we make platform installation easier?
- Improve requirements checking and error messages
- Install SDKs with one command (TACO)
  
- How can we improve the plugin ecosystem?
  - Plugin dependencies and version constraints
  - Validated platforms and plugins (TACO)
  - Improving native dependencies (CocoaPods for iOS?)
  - What can we learn from the React Native plugin API?
  
- How can we better support hybrid apps?
  - Is the distinction between the CLI vs. platform-centered workflow still 
valid?
  - What is needed to allow customizing native (Xcode/Gradle/...) projects when 
using the CLI?
  - Can we share tools or plugins with React Native?

- What do integrators need from Cordova?
  - PlatformApi refactoring
  - Standardized logging and error/progress reporting
  
> On 03 Oct 2015, at 00:11, Carlos Santana <csantan...@gmail.com> wrote:
> 
> Joe updated the Agenda with topics, I added more topics.
> 
> I put my name on all of them, at this time is just proposals.
> 
> Please add more as you think is appropriate
> 
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithu
> b.com%2fcordova%2fcordova-discuss%2fblob%2fmaster%2fproposals%2fFace2F
> ace-Oct15.md=01%7c01%7cnikhilkh%40microsoft.com%7c5ec42e93003f4d7
> 594c908d2cd89dd17%7c72f988bf86f141af91ab2d7cd011db47%7c1=oCL1RTj
> 5gDcnX7QgSQL4rgdmCYnCmeFfoB97R9idm8s%3d
> 
> 
> 
> On Fri, Oct 2, 2015 at 4:50 PM Parashuram N <panar...@microsoft.com> wrote:
> 
>> @Joe - I think we should do that too. I think we do need to do that 
>> session. At the moment, there are 2 time slots when we could have 
>> "breakout" sessions, I think this could be on the first day. Can you 
>> update the agenda with this as a breakout session please ?
>> 
>> -Original Message-
>> From: Joe Bowser [mailto:bows...@gmail.com]
>> Sent: Friday, October 2, 2015 1:47 PM
>> To: dev <dev@cordova.apache.org>
>> Subject: Re: Cordova Face to Face Meeting
>> 
>> Is it possible to have PMC/Committer only sessions?  There's some 
>> stuff that I want to make sure we cover w.r.t. how to deal with 
>> Apache Security policy, but I'm pretty sure if you're not a 
>> PMC/Committer, it'd have almost no value to anyone else unless 
>> they're really into the fine details of how the sausage gets made and 
>> how we get screen out the sausage links that contain nasty bits.
>> 
>> Also, we should probably have a Cordova workflow discussion, since 
>> I'm getting the impression that a lot of people don't even know how 
>> to work on Cordova itself, or that we do it all differently.
>> 
>> On Fri, Oct 2, 2015 at 1:38 PM, Homer, Tony <tony.ho...@intel.com> wrote:
>> 
>>> I think this would be a great way to spur discussion about shared
>> concerns.
>>> It would be great if we could identify some opportunities to make 
>>> changes that would be beneficial for downstream distributors.
>>> 
>>> I can certainly provide a quick survey of what we do in Intel XDK.
>>> 
>>> 
>>> Tony
>>> 
>>> On 10/2/15, 4:36 PM, "Nikhil Khandelwal" <nikhi...@microsoft.com> wrote:
>>> 
>>>> +1 to Martijn/Carlos mentioned. Please send PRs to the agenda 
>>>> +document
>>>> here with your thoughts and agenda items
>>>> 
>>>> 
>>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgit
>>> hu 
>>> b.com%2fcordova%2fcordova-discuss%2fblob%2fmaster%2fproposals%2fFace
>>> 2F
>>> ace=01%7c01%7cpanarasi%40microsoft.com%7c701024943b444795468008
>>> d2 
>>

RE: Understanding the Cordova developer better - Cordova developer survey

[Nikhil Khandelwal]

Thanks for all the input! Here's the final public facing URL: 
https://apachecordovabot.typeform.com/to/BCc5co. 

It will be great to get some of this data before the F2F meeting. Let's all 
tweet about it, post it on slack etc.

In couple of days we can see if we can want to make more tweaks to this and 
then put out a v2 on the cordova website as a banner. 

-Nikhil

-Original Message-
From: Andrey Kurdumov [mailto:kant2...@googlemail.com] 
Sent: Saturday, October 3, 2015 10:42 PM
To: dev@cordova.apache.org
Subject: Re: Understanding the Cordova developer better - Cordova developer 
survey

Would be good separate 4.a question "Documentation for the Cordova platforms 
and CLI" on two separate questions.
Since I have different opinion on both of CLI and platform docs. CLI I would 
range on the 8 or 9 9 (nobody perfect), but platform docs are closer to 4 (need 
significant improvements) for me.
Both are very strong feeling, and I have to or average results, or select which 
part is more important for me.

2015-10-04 11:04 GMT+06:00 Carlos Santana :

> Yeah I like "released"
>
> Yeah no need to get usage info on this survey now.
>
> - Carlos
> Sent from my iPhone 6s
>
> > On Oct 4, 2015, at 12:51 AM, Jesse  wrote:
> >
> > Great feedback, you're right, I was thinking totally app-store-centric.
> > How about 'released' instead of 'published'?
> >
> > I'm not sure if usage info is relevant here, it is interesting no 
> > doubt, but I think the goal of this survey was to get info on making 
> > the app developer experience better. There is a multitude of 
> > non-cordova factors that affect usage; (price, design, app type, 
> > market competition, ... ) Personally I think usage stats are 
> > probably more relevant in the app showcase pages, or in another usage 
> > targeted survey.
> >
> >
> >
> >
> > My team is hiring!
> > @purplecabbage
> > https://na01.safelinks.protection.outlook.com/?url=risingj.com=
> > 01%7c01%7cnikhilkh%40microsoft.com%7ca0dc759ec823485986cc08d2cc7e942
> > 7%7c72f988bf86f141af91ab2d7cd011db47%7c1=ygxQ5M9xh2NY%2fGKr5eM
> > EdWpaHVPZ5RrMFs6s6F0Yos4%3d
> >
> >> On Sat, Oct 3, 2015 at 3:40 AM, Carlos Santana 
> >> 
> wrote:
> >>
> >> For the question on how many published, don't know if it will be 
> >> good to use a different word than "published". I personally 
> >> associate that with
> a
> >> App Store on quick read
> >>
> >> Most of our customers don't published their apps to a store, they 
> >> have them in production internally because they are business to 
> >> employee or business to business.
> >>
> >> What about using "apps currently in production" or "apps currently 
> >> being actively  user by users" or another term to be inclusive of 
> >> apps not
> being
> >> distributed by public store
> >>
> >> Another question, how many users using your app in a monthly basis? 
> >> Is that important to know how many users is the app being used by? 
> >> Like I
> have
> >> one app but that one app being downloaded 1,000 monthly and used by
> 50,000
> >> users :-)
> >>
> >> - Carlos
> >> Sent from my iPhone 6s
> >>
> >>> On Oct 3, 2015, at 3:34 AM, Jesse  wrote:
> >>>
> >>> I was able to update the survey.
> >>>
> >>> 1. I made some minor grammatical corrections and added some missing '?'
> >>> 2. Moved the 'What do you love/hate about cordova to the end"
> >>> 3. And added my plugins question. Which ones do you use?
> >>> 4. Also added Dave's 'would you recommend Cordova' question.
> >>>
> >>> Conceptually, I am having trouble with this one:
> >>> How far along are you in the development of your Cordova app?
> >>> I added a 'How many cordova apps have you published?' question as 
> >>> I
> think
> >>> it more relevant. Unfortunately we cannot make 'How far along ..'
> >>> conditional on 'How-many' being <1 because we are using the free
> version.
> >>>
> >>> I *expect* that we will see roughly half of respondents have 
> >>> published
> >> more
> >>> than 1 app, which would make the 'How far along...' question moot, 
> >>> but
> I
> >>> could be wrong.
> >>>
> >>>
> >>>
> >>>
> >>> My team is hiring!
> >>> @purplecabbage
> >>> https://na01.safelinks.protection.outlook.com/?url=risingj.com
> >>> a=01%7c01%7cnikhilkh%40microsoft.com%7ca0dc759ec823485986cc08d2cc7
> >>> e9427%7c72f988bf86f141af91ab2d7cd011db47%7c1=ygxQ5M9xh2NY%2f
> >>> GKr5eMEdWpaHVPZ5RrMFs6s6F0Yos4%3d
> >>>
> >>> On Thu, Oct 1, 2015 at 11:46 AM, Parashuram N 
> >>> 
> >>> wrote:
> >>>
>  Sure, I guess we will have to create a new account and put the
> >> credentials
>  in SVN, right ?
> 
> 
> 
> 
> > On 10/1/15, 11:43 AM, "Jesse"  wrote:
> >
> > So, I was not able to log in and make the changes.
> > Can we change the typeform account login to not use google SSO?
> >
> >
> > My team is hiring!
> > @purplecabbage
> 
> 

RE: Merging latest pull requests into Master today

[Nikhil Khandelwal]

Sorry for not responding earlier. I like where this is going. I have a bunch of 
comments on the PRs.

I have some confusion around how CordovaPlugin has a protected field 
'permissions' and what a derived CordovaPlugin is supposed to do with it. None 
of our core plugins seem to use it.

Thanks,
Nikhil

-Original Message-
From: Joe Bowser [mailto:bows...@gmail.com] 
Sent: Monday, October 5, 2015 9:05 AM
To: dev 
Subject: Merging latest pull requests into Master today

Hey

I'm going to pull the 5.0.x proposed pull requests into Master today.  Can 
anyone take a look at them before I do this.  I'm going to wait until after
1 PM to do it, so if you can check out the new pull requests and comment on 
them before then, that would be greatly appreciated, otherwise I'm going to 
assume all is good and merge them into the master.

You've been warned. ;)

Joe

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

RE: Deploying New Cordova Website

[Nikhil Khandelwal]

Wohoo! Let's do it!

-Nikhil

-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com] 
Sent: Friday, October 2, 2015 6:06 PM
To: dev@cordova.apache.org
Subject: Re: Deploying New Cordova Website

But I wanted to +1

Launched !!

- Carlos
Sent from my iPhone

> On Oct 2, 2015, at 8:21 PM, Steven Gill  wrote:
> 
> Sweet!
> 
> You don't have to vote for website updates.
> 
> I can update the cordova DNS. Just let me know what the links are and 
> when you want it done.
> 
> Thanks!
> 
> Let me know if you want any assistance.
> 
> On Fri, Oct 2, 2015 at 3:45 PM, Dmitry Blotsky 
> 
> wrote:
> 
>> Hey folks,
>> 
>> I’m planning to deploy the new website on top of the old one over 
>> this weekend (blog posts are synchronised on every deploy, so they 
>> will be up to date). Any objections to this? Should I call for a vote?
>> 
>> Some things that will need to happen shortly after the deployment:
>> - Pointing 
>> https://na01.safelinks.protection.outlook.com/?url=plugins.cordova.io
>> =01%7c01%7cnikhilkh%40microsoft.com%7c99e748bfefa44861245308d2cb
>> 8edff7%7c72f988bf86f141af91ab2d7cd011db47%7c1=NcnPnk82TZniP%2fi
>> Cj9E1cNFL29FGWMO1djsvtceRV%2fo%3d to 
>> https://na01.safelinks.protection.outlook.com/?url=cordova.apache.org
>> %2fplugins=01%7c01%7cnikhilkh%40microsoft.com%7c99e748bfefa44861
>> 245308d2cb8edff7%7c72f988bf86f141af91ab2d7cd011db47%7c1=CN7amiG
>> uuxUyUVJ6031Vc9fy6dlBR%2fS8iI9tSv%2b3TuU%3d
>> - Pointing 
>> https://na01.safelinks.protection.outlook.com/?url=docs.cordova.io
>> ta=01%7c01%7cnikhilkh%40microsoft.com%7c99e748bfefa44861245308d2cb8ed
>> ff7%7c72f988bf86f141af91ab2d7cd011db47%7c1=D3vMNPcGKbEgDtYIvtJs
>> LEEfs9bFvFsF2fIDhM%2frWzM%3d to 
>> https://na01.safelinks.protection.outlook.com/?url=cordova.apache.org
>> %2fdocs%2fen=01%7c01%7cnikhilkh%40microsoft.com%7c99e748bfefa448
>> 61245308d2cb8edff7%7c72f988bf86f141af91ab2d7cd011db47%7c1=SZbwT
>> k8lYSeVZ4KgIDD2txrFdwXoMg2n01stMJRVMpQ%3d
>> - Merging all the code back into master
>> - Replacing the files on Crowdin with the new files
>> 
>> Kindly,
>> Dmitry
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>> For additional commands, e-mail: dev-h...@cordova.apache.org
>> 

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

RE: cordova-plugin-whitelist ios issue

[Nikhil Khandelwal]

I'm up for a hangout on this subject. I do think e-mail is making it hard to 
communicate this. I am with Carlos - we should not have warnings that cannot be 
resolved for unreleased platform versions. This is particularly, a problem for 
a new web developer to Cordova who does not understand the history of whitelist 
and the user of it and is confronted with it upfront. There is not the first 
time this feedback has been voiced. [1][2]

Carlos does raise some other important concerns. I've heard a lot of confusion 
from Cordova devs on whitelist changes. This is especially painful for Android 
4.0 which has no network access without whitelist. I think we are making better 
defaults (of having network access)  with Cordova IOS 4.0. Perhaps we should 
change the behavior for Android with Android 5.0.

-Nikhil

[1] 
https://github.com/apache/cordova-plugin-whitelist/commit/72a067c96e4e54efb8f1f152220d4a5fdf404324#commitcomment-11624636
[2] http://callback.markmail.org/thread/w2pjyndljbdng23f

-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com] 
Sent: Wednesday, September 30, 2015 9:03 AM
To: dev@cordova.apache.org
Subject: Re: cordova-plugin-whitelist ios issue

People are already getting surprised today that their apps do not connect to 
any network when they create an app that contains cordova-android@4.x because 
the whitelist plugin is not included by default.
Why whitelist is not included by default?
- the don't use the cordova-cli, the use cordova-android/bin/create (shell
mode)
- because they use their own templates, for example I created an app with my 
own template that has my config.xml that doesn't have whitelist plugin because 
I created the template in the cordova-android@3.x time frame.
- people creating apps with other CLIs, for example ionic cli, whitelist plugin 
is not one of the default plugins added with their ionic templates, etc..


On Wed, Sep 30, 2015 at 11:48 AM Carlos Santana 
wrote:

> So this mean I can add this engine tag today to the whitelist plugin 
> with some code specific to firefoxos?
>  
>
> I know cordova-firefoxos@4.0.0-dev or ordova-firefoxos@4.0.0 is not on 
> npm but is very useful to give users the warning now.
> This will avoid the user from upgrading the plugin ever in the future 
> when
> cordova-firefoxos@4.0.0 is published to npm, I might get c
> ordova-firefoxos@4.0.0 around december or longer  so I don't think it 
> will be a problem for them to see the warning until then.
>
> If everyone is OK I will put this code today? this will avoid user 
> from having to upgrade the plugin in the future :-p
>
> This is the point I want to make, and guess email communication is not 
> being our friend to express my point of view.
> Will those interested on this topic up for a quick Hangout? Simon, 
> Shaz, Nikhil
>
>
> On Wed, Sep 30, 2015 at 10:55 AM Simon MacDonald < 
> simon.macdon...@gmail.com> wrote:
>
>> -1 to this proposal IMHO
>>
>> Warnings are useful. If someone sees this and is confused as to why 
>> there is a new whitelist plugin then looks into it some more detail 
>> that will be beneficial. I think the warning should be more explicit. 
>> Put an info tag into the plugin.xml for the whitelist linking to the 
>> docs and what the upcoming change is in cordova-ios 4.0.0. That way people 
>> will be "less"
>> surprised that they need to install this plugin in the future.
>>
>>
>>
>> Simon Mac Donald
>> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fhi.im
>> %2fsimonmacdonald=01%7c01%7cnikhilkh%40microsoft.com%7caa884ed39
>> 282462add6208d2c9b0f4ab%7c72f988bf86f141af91ab2d7cd011db47%7c1=
>> NW%2bD7WmSnLFc9L9nYI6Q%2fabIiY6GjTci8x49Tsve%2biw%3d
>>
>> On Tue, Sep 29, 2015 at 11:35 PM, Tommy Williams 
>> wrote:
>>
>> > This.
>> >
>> > +1
>> >
>> >
>> > On 30 September 2015 at 12:31:29, Carlos Santana 
>> > (csantan...@gmail.com)
>> > wrote:
>> >
>> > In summary I proposed that we update the plugin with a version that 
>> > only contains the android code.
>> > When we publish cordova-ios@4.0.0 then we publish a new version 
>> > that contains the ios code and contains engine tag stating that it 
>> > needs minimum
>> > cordova-ios@4.0.0
>> >
>> > I'm OK if you want to have two branches to make it clear to devs, 
>> > 1.x it contains android only, branch 2.x contains both android and ios.
>> >
>>
>

RE: cordova-plugin-whitelist ios issue

[Nikhil Khandelwal]

+1 to changing the tag. We should not release the plugin with the engine tag 
for ios until cordova-ios 4.0 is released.

-Nikhil

-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com] 
Sent: Wednesday, September 30, 2015 1:00 PM
To: dev@cordova.apache.org
Subject: Re: cordova-plugin-whitelist ios issue

+1
OK I guess I did a hoorible job doing an example :-)

I compare 1.0.0 vs. 1.1.0
And it looks like android didn't change. And the solution is that plugin.xml 
doesn't have the  and it doesn't have the offending 


OK so still my position is that version 1.1.0 is a good version of the plugin. 
It adds ios feature and this feature required > cordova-ios@4.0.0-dev Just wait 
until cordova-ios@4.0.0 is released to make 1.1.0 public


On Wed, Sep 30, 2015 at 3:27 PM Shazron <shaz...@gmail.com> wrote:

> +1 to the dist-tag change until we sort this out :)
>
> On Wed, Sep 30, 2015 at 12:25 PM, Steven Gill <stevengil...@gmail.com>
> wrote:
> > I can change whitelist back to version 1 which only has the engine 
> > check for android. I can do that now if everyone is okay with it. We 
> > can change it back once cordova-ios@4 releases.
> >
> > On Wed, Sep 30, 2015 at 12:13 PM, Shazron <shaz...@gmail.com> wrote:
> >
> >> -1.
> >> We can just update the dist-tag so @latest goes to a previous version.
> >> All released versions have been voted on, so its a matter of 
> >> dist-tag carousel.
> >>
> >>
> >>
> >> On Tue, Sep 29, 2015 at 7:31 PM, Carlos Santana 
> >> <csantan...@gmail.com>
> >> wrote:
> >> > In summary I proposed that we update the plugin with a version 
> >> > that
> only
> >> > contains the android code.
> >> > When we publish cordova-ios@4.0.0 then we publish a new version 
> >> > that contains the ios code and contains engine tag stating that 
> >> > it needs
> >> minimum
> >> > cordova-ios@4.0.0
> >> >
> >> > I'm OK if you want to have two branches to make it clear to devs, 
> >> > 1.x
> it
> >> > contains android only, branch 2.x contains both android and ios.
> >> >
> >> >
> >> > On Tue, Sep 29, 2015 at 10:26 PM Carlos Santana 
> >> > <csantan...@gmail.com
> >
> >> > wrote:
> >> >
> >> >> Here are my two cents, and I'm aware of the situation.
> >> >>
> >> >> publish a new version of cordova-plugin-whitelist  that only 
> >> >> contains
> >> the
> >> >> android code and only supports android platform (means to remove 
> >> >> any
> ios
> >> >> code from the plugin)
> >> >>
> >> >> Currently the plugin is public and published on npm as latest, 
> >> >> and it states in the README:
> >> >>
> >> >>- Android 4.0.0 or above
> >> >>- iOS 4.0.0 or above
> >> >>
> >> >> Guess what iOS 4.0.0 is it doesn't exist, it's not out, it's not 
> >> >> born
> >> yet.
> >> >> I guess you get the picture. The day that cordova-ios@4.0.0 
> >> >> get's published to npm is the day that it exist, then is valid 
> >> >> to published plugins that depend on that version of the platform.
> >> >>
> >> >> The day we published cordova-ios@4.0.0 to npm, on the same day 
> >> >> we
> >> publish
> >> >> cordova-plugin-whitelist that has code for ios and depends on
> >> >> cordova-ios@4.0.0
> >> >>
> >> >> In general to my eyes we should NOT published plugins that 
> >> >> depends
> (i.e.
> >> >> engines) depend on a version of a component that it's not born yet.
> >> >>
> >> >>
> >> >>
> >> >> On Tue, Sep 29, 2015 at 8:57 PM Shazron <shaz...@gmail.com> wrote:
> >> >>
> >> >>> This has nothing to do with cordova-ios being released. Think 
> >> >>> of it solely by the plugin's requirements: it requires 
> >> >>> cordova-android 4, and cordova-ios 4. I have cordova-android 4, 
> >> >>> so it installs. I have cordova-ios 3.9 so it doesn't, and it warns me.
> >> >>>
> >> >>> We *will* have this problem later with plugins, guaranteed, we
> should
> >> >>> not try to hide this problem for our own convenience.
> >> >>>
> >> >>> Let's sa

cordova-plugin-whitelist ios issue

[Nikhil Khandelwal]

1.   cordova create test

2.   cordova platform add ios

WARNING: Applications for platform ios can not be built on this OS - win32.
Adding ios project...
iOS project created with cordova-ios@3.9.1
Discovered plugin "cordova-plugin-whitelist" in config.xml. Installing to the 
project
Fetching plugin "cordova-plugin-whitelist@1" via npm
Installing "cordova-plugin-whitelist" for ios
Plugin doesn't support this project's cordova-ios version. cordova-ios: 3.9.1, 
failed version requirement: >=4.0.0-dev
Skipping 'cordova-plugin-whitelist' for ios
Installing "cordova-plugin-whitelist" for ios
Plugin doesn't support this project's cordova-ios version. cordova-ios: 3.9.1, 
failed version requirement: >=4.0.0-dev
Skipping 'cordova-plugin-whitelist' for ios

Looks like we have a rogue version of cordova-plugin-whitelist published that 
requires iOS 4.0.0. What's the best way to fix it? Can we unpublish this 
whitelist plugin version from npm to fix this? Alternatively, we should release 
another version of the plugin that does not get this warning. It's misleading 
and confusing for developers to see this warning.

Thanks,
Nikhil

RE: cordova-plugin-whitelist ios issue

[Nikhil Khandelwal]

I understand the warning w.r.t. plugins and android 5.0 as we will release 
android 5.0 along with the plugin update and there would be a path for people 
to resolve the warning.

In this case, ios 4.0 is not even released and users have no way to work around 
this warning. We're getting feedback from customers about this.

IMO we should never release a plugin which always emits a warning that cannot 
be resolved.

-Nikhil

-Original Message-
From: Shazron [mailto:shaz...@gmail.com] 
Sent: Tuesday, September 29, 2015 5:17 PM
To: dev@cordova.apache.org
Subject: Re: cordova-plugin-whitelist ios issue

No its not a "rogue version". cordova-plugin-whitelist requires cordova-ios 4.0 
and cordova-android 4.0.
It's just a warning and is expected to work this way.
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fapache%2fcordova-plugin-whitelist%2fblob%2fmaster%2fREADME.md=01%7c01%7cnikhilkh%40microsoft.com%7cd638675115ae4fa7be2d08d2c92c9d89%7c72f988bf86f141af91ab2d7cd011db47%7c1=iO9NDS0BgD53OVEDyxGv0zNW5SKXLVK0loo8ZAEmfOM%3d

On Tue, Sep 29, 2015 at 5:08 PM, Nikhil Khandelwal <nikhi...@microsoft.com> 
wrote:
> 1.   cordova create test
>
> 2.   cordova platform add ios
>
> WARNING: Applications for platform ios can not be built on this OS - win32.
> Adding ios project...
> iOS project created with cordova-ios@3.9.1 Discovered plugin 
> "cordova-plugin-whitelist" in config.xml. Installing to the project 
> Fetching plugin "cordova-plugin-whitelist@1" via npm Installing 
> "cordova-plugin-whitelist" for ios Plugin doesn't support this 
> project's cordova-ios version. cordova-ios: 3.9.1, failed version 
> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for ios 
> Installing "cordova-plugin-whitelist" for ios Plugin doesn't support 
> this project's cordova-ios version. cordova-ios: 3.9.1, failed version 
> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for ios
>
> Looks like we have a rogue version of cordova-plugin-whitelist published that 
> requires iOS 4.0.0. What's the best way to fix it? Can we unpublish this 
> whitelist plugin version from npm to fix this? Alternatively, we should 
> release another version of the plugin that does not get this warning. It's 
> misleading and confusing for developers to see this warning.
>
> Thanks,
> Nikhil

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


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

RE: cordova-plugin-whitelist ios issue

[Nikhil Khandelwal]

I think the first version of the whitelist plugin was released without the 
corodva-ios 4.0 check, so that developers do not see this warning because 
cordova-ios 4.0 was not released. I agree with Tommy, that the wording of the 
warning seems to suggest there is a way for me to fix this issue:
"Plugin doesn't support this project's cordova-ios version. cordova-ios: 3.9.1, 
failed version requirement: >=4.0.0-dev."

However, with this plugin we do not have a way to fix it because ios 4.0 is not 
released. 

I suggest we do the following:
- Unpublish the version that has a dependency on ios 4.x
- Release cordova-plugin-whitelist v2 which has an ios 4.x depdency
- In the tools release, that pins cordova-ios 4.x we should ship a 
cordova-app-hello-world template that targets v2 of this plugin.

Thanks,
Nikhil

-Original Message-
From: Shazron [mailto:shaz...@gmail.com] 
Sent: Tuesday, September 29, 2015 5:28 PM
To: dev@cordova.apache.org
Subject: Re: cordova-plugin-whitelist ios issue

This is only happening because we have two engine requirements - 
cordova-android 4.x and cordova-ios 4.x. This is correct for 
cordova-plugin-whitelist.

Like I mentioned before, cordova-android+ios 3.x *do not* require this plugin 
as it is built in. Perhaps this could be communicated better, but the warning 
is generic, and there's no way to communicate this in an  tag.

We could release core plugins that have different core platform version 
requirements as well in the future (like android 5 plugin
changes) and this will occur again.


On Tue, Sep 29, 2015 at 5:21 PM, Shazron <shaz...@gmail.com> wrote:
> "IMO we should never release a plugin which always emits a warning 
> that cannot be resolved."
>
> There is nothing to resolve. The resolution is to ignore it. It's 
> supposed to warn you, as it is working as expected.
>
> On Tue, Sep 29, 2015 at 5:19 PM, Nikhil Khandelwal 
> <nikhi...@microsoft.com> wrote:
>> I understand the warning w.r.t. plugins and android 5.0 as we will release 
>> android 5.0 along with the plugin update and there would be a path for 
>> people to resolve the warning.
>>
>> In this case, ios 4.0 is not even released and users have no way to work 
>> around this warning. We're getting feedback from customers about this.
>>
>> IMO we should never release a plugin which always emits a warning that 
>> cannot be resolved.
>>
>> -Nikhil
>>
>> -Original Message-
>> From: Shazron [mailto:shaz...@gmail.com]
>> Sent: Tuesday, September 29, 2015 5:17 PM
>> To: dev@cordova.apache.org
>> Subject: Re: cordova-plugin-whitelist ios issue
>>
>> No its not a "rogue version". cordova-plugin-whitelist requires cordova-ios 
>> 4.0 and cordova-android 4.0.
>> It's just a warning and is expected to work this way.
>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgith
>> ub.com%2fapache%2fcordova-plugin-whitelist%2fblob%2fmaster%2fREADME.m
>> d=01%7c01%7cnikhilkh%40microsoft.com%7cd638675115ae4fa7be2d08d2c
>> 92c9d89%7c72f988bf86f141af91ab2d7cd011db47%7c1=iO9NDS0BgD53OVED
>> yxGv0zNW5SKXLVK0loo8ZAEmfOM%3d
>>
>> On Tue, Sep 29, 2015 at 5:08 PM, Nikhil Khandelwal <nikhi...@microsoft.com> 
>> wrote:
>>> 1.   cordova create test
>>>
>>> 2.   cordova platform add ios
>>>
>>> WARNING: Applications for platform ios can not be built on this OS - win32.
>>> Adding ios project...
>>> iOS project created with cordova-ios@3.9.1 Discovered plugin 
>>> "cordova-plugin-whitelist" in config.xml. Installing to the project 
>>> Fetching plugin "cordova-plugin-whitelist@1" via npm Installing 
>>> "cordova-plugin-whitelist" for ios Plugin doesn't support this 
>>> project's cordova-ios version. cordova-ios: 3.9.1, failed version
>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for ios 
>>> Installing "cordova-plugin-whitelist" for ios Plugin doesn't support 
>>> this project's cordova-ios version. cordova-ios: 3.9.1, failed 
>>> version
>>> requirement: >=4.0.0-dev Skipping 'cordova-plugin-whitelist' for ios
>>>
>>> Looks like we have a rogue version of cordova-plugin-whitelist published 
>>> that requires iOS 4.0.0. What's the best way to fix it? Can we unpublish 
>>> this whitelist plugin version from npm to fix this? Alternatively, we 
>>> should release another version of the plugin that does not get this 
>>> warning. It's misleading and confusing for developers to see this warning.
>>>
>>> Thanks,
>>> Nikhil
>>
>> -

RE: [Android] Cordova-Android 5.0 changes and merging into master?

[Nikhil Khandelwal]

I'm fine with merging cordova-android to master. For the plugins, that have 
marshmallow changes if we merge now we cannot release them till cordova-android 
& the corresponding tools release happens. On the other side, if we do not 
merge them CI will be broken.

It makes sense to merge it all if the design is final and we don’t expect much 
flux before the release. 

-Nikhil

-Original Message-
From: Joe Bowser [mailto:bows...@gmail.com] 
Sent: Monday, September 28, 2015 3:15 PM
To: dev 
Subject: [Android] Cordova-Android 5.0 changes and merging into master?

Hey

So, after looking at the pull requests, how do people feel about merging it 
into master, doing the last changes there and releasing it in the next few 
weeks.  If we do this, the 4.1.x branch will be the supported branch for 
approximately six months, and if we do any security updates, we will have to 
fix both the 4.1.x branch and the master branch.

That said, Google has their Nexus event tomorrow where they're announcing the 
new devices, and there's going to be updates on Oct 5, so I think we should 
start merging this stuff into master sooner rather than later.

Thoughts?

Joe

RE: [Android] XDA is reporting that Marshmallow is out October 5th on TELUS

[Nikhil Khandelwal]

+1 to major version rev. for plugins. It also is a signal these plugins will 
not work with any previous version of cordova.

For reviewing changes, can you submit a PR perhaps from your topic branch to 
apache/cordova-android 5.x-dev branch? It's hard to review and comment on 
branch diffs - PRs allow for easy commenting and discussions.

Thanks,
Nikhil


-Original Message-
From: Joe Bowser [mailto:bows...@gmail.com] 
Sent: Thursday, September 24, 2015 1:36 PM
To: dev 
Subject: [Android] XDA is reporting that Marshmallow is out October 5th on TELUS

Hey

So, this is really weird.  TELUS, just leaked that the OTA for the Nexus 5 and 
Nexus 6 is Oct 5.

https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fwww.xda-developers.com%2fxda-external-link%2ftelus-says-android-6-0-ota-update-starts-on-october-5th%2f=01%7c01%7cnikhilkh%40microsoft.com%7c0496829a7a764d2da4ee08d2c51fc129%7c72f988bf86f141af91ab2d7cd011db47%7c1=Isrv93diSPs28%2bh3arfZT6L2%2f4fjWF9X3PFM5qnsBoc%3d

I don't like to rush things, but if people could review all the Smores changes 
while I finish up File before I do a release, that'd be awesome.
I've already contacted Ninging Hu on the Crosswalk team about the upcoming 
Cordova release and Marshmallow, and we should be hearing more about that soon. 
 Once I go through the File plugin we should be good for a preliminary run.

I MIGHT write a utility method for plugins, because there is a lot of possible 
code repetition, but other than that, I think we're mostly good to go.

For the plugins, I think the plugins affected by the permissions changes should 
get a major version update.  Not because there's an API change, but because 
there's a slight behaviour change.  Developers who are unfamiliar with 
Marshmallow who are using the plugins may be wondering why we're showing the 
prompts, and we should bump the majors just so that we can make sure they 
understand that Marshmallow is a big deal, despite how Google is underplaying 
it.

What do people think?

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

RE: [Android] 5.0.x release branch?

[Nikhil Khandelwal]

Merging threads. I was no aware of any security implications of using 
reflection - Perhaps if the reflection target can be controlled through 
external data. In any case, I understand your hesitation with use of 
reflection. I would love to have longer discussions on the F2F on what 
approaches we could use to make this easier for Cordova developers.

Joe: Could you add the appropriate engine tags in any case? That's how Cordova 
currently handles versioning between plugins & platforms. Also, does this imply 
that the plugins should have a major version bump as it is a breaking change? 
Please create the 5.x branches and if you could submit a PR - I had other minor 
code review comments on the diffs below.

Carlos: I understand in the extreme case it can be a fairly complicated 
implementation with lots of criteria to use to determine the ideal plugin that 
might work given a set of platforms. However, trying a couple of previous 
versions of the plugins might work 80% of the time and that might be good 
enough. This requires more thought as there are quite a few scenarios here.

As for plugin search website helping you find the correct engine tags - I like 
the idea. But this might requires us maintaining a backend for plugin search as 
this is specified in plugin.xml (and not package.json - or did we finally move 
this?). 

Thanks,
Nikhil

-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com] 
Sent: Tuesday, September 22, 2015 6:14 PM
To: dev@cordova.apache.org
Subject: Re: [Android] 5.0.x release branch?

+1 we should always use the engine tag to mark the minimum compatible 
+version at least

-1 for cordova CLI to automagically to install an older version. It will be a 
pain to get this implemented right, we would need to download all the 
package.json for multiple versions of the plugin and pick the lowest common 
denominator based on engine tags and remember that one plugin support multiple 
engine tags across different platform versions and CLI/plugman. 

This brings an interesting feature to implement In the plugin search website, 
to display the engine tags for a specific plugin version. Allowing a developer 
to search for a compatible plugin for their current app. 

- Carlos
Sent from my iPhone


-Original Message-
From: Joe Bowser [mailto:bows...@gmail.com] 
Sent: Tuesday, September 22, 2015 6:17 PM
To: dev@cordova.apache.org
Subject: Re: [Android] 5.0.x release branch?

I'm completely against using reflection for this purpose.  Version codes were 
invented for a reason and we don't have any mechanism in place to unit test any 
Android code (or any other native code on any of the platforms).

I will vote against any release that includes reflection for this purpose since 
reflection has only brought us security issues and extreme WebView breakage 
when used (Simon can tell you the tales of the HTC console.log reflection 
code.).  Reflection is a worst-case scenario tool like when a method in WebView 
marked as deprecated completely disappears, not something we should make a 
habit of using often.  If we open the door for this, we'll get reflection 
creeping elsewhere, like the Plugins API.

Just say no to reflection.


On Tue, Sep 22, 2015, 5:57 PM Nikhil Khandelwal <nikhi...@microsoft.com>
wrote:

> Thanks, Joe for the detailed explanation. I understand why we've taken 
> this route. It's good that this is only a build failure. One of the 
> complaints we commonly hear from Cordova developers is that "I have a 
> cordova project with a certain version of the platform, I need to find 
> the plugin that will work with it". Our CLI always defaults to add the 
> latest released version of the plugin.
>
> After this breaking change, an existing cordova project with 
> cordova-android < 5.x, cannot build with the latest version of the 
> following plugins:
> - camera
>- geolocation
>- contacts.
> These are some of the most popular plugins in cordova plugin ecosystem [1].
>
> I propose that we should do our best to avoid disruptive breaking 
> changes here. Some ideas that come to mind:
> - As Joe mentioned below - reflection. It has the downsides that Joe 
> mentioned. No one likes to write code like this it but results in 
> least grief for Cordova users. Some pain here for plugin developers 
> will simplify the experience for large number of corodva JS 
> developers. I know we are doing some of this in cordova-ios [2] and 
> would love to find ways on how to make this manageable and not super ugly.
> - Add an  ' '  to 
> the plugins - failure happens at plugin add in this scenario. 
> Cordova-lib could be more intelligent to detect this error and resort 
> to using an older version of the plugin. The downside of this is that 
> these projects cannot use the latest and greatest of these plugins.
>
> Thanks

RE: [Android] 5.0.x release branch?

[Nikhil Khandelwal]

Thanks, Joe for the detailed explanation. I understand why we've taken this 
route. It's good that this is only a build failure. One of the complaints we 
commonly hear from Cordova developers is that "I have a cordova project with a 
certain version of the platform, I need to find the plugin that will work with 
it". Our CLI always defaults to add the latest released version of the plugin.

After this breaking change, an existing cordova project with cordova-android < 
5.x, cannot build with the latest version of the following plugins:
- camera
   - geolocation
   - contacts.
These are some of the most popular plugins in cordova plugin ecosystem [1].

I propose that we should do our best to avoid disruptive breaking changes here. 
Some ideas that come to mind:
- As Joe mentioned below - reflection. It has the downsides that Joe mentioned. 
No one likes to write code like this it but results in least grief for Cordova 
users. Some pain here for plugin developers will simplify the experience for 
large number of corodva JS developers. I know we are doing some of this in 
cordova-ios [2] and would love to find ways on how to make this manageable and 
not super ugly.
- Add an  ' '  to the 
plugins - failure happens at plugin add in this scenario. Cordova-lib could be 
more intelligent to detect this error and resort to using an older version of 
the plugin. The downside of this is that these projects cannot use the latest 
and greatest of these plugins. 

Thanks,
Nikhil

[1] http://cordova.apache.org/use-the-force-luke/plugins/?sortBy=Downloads
[2] 
https://github.com/apache/cordova-plugin-camera/blob/master/src/ios/CDVCamera.m#L44

Thanks,
Nikhil


-Original Message-
From: Joe Bowser [mailto:bows...@gmail.com] 
Sent: Monday, September 21, 2015 6:32 PM
To: dev@cordova.apache.org
Subject: Re: [Android] 5.0.x release branch?

On Mon, Sep 21, 2015 at 5:43 PM Nikhil Khandelwal <nikhi...@microsoft.com>
wrote:

> Can you explain why latest plugins will not be compatible with older 
> versions of Cordova?


They won't be compatible because Cordova-Android compiles against API 22, and 
these plugins will require API 23 so that they can detect permissions and 
support Marshmellow.


> Can this be avoided by any means?


Only with a lot of Java reflection, and I'd rather not subject plugin 
developers to that, or try to hide it under the hood in some awful utility 
class that everyone will want to see die.  I'm very much a fan of if statements 
because they work, and they're easy to read and debug, unlike when bad things 
happen to things you reflect into.  Plugins that require API 23 will only work 
with Cordova-Android 5.0 and up.  This only impacts five of our core plugins, 
but any plugin that requires permissions from the Android Manifest will have to 
be updated.  If we can avoid using advanced language tricks to make the APKs 
compatible, we should do that.

When you mean they would not be compatible - will it result in a build or
> runtime failure?
>
>
This will be a build failure, since API 22 does not have these permissions, nor 
does it have the code required for API 23.


> For marshmallow, what is the guidance that we need to issue to the 
> larger Cordova plugin ecosystem? Joe you are ahead of the curve here 
> compared to most other plugin developers - a blot post explaining what 
> are known gotchas would be great. I really hope we can use our Cordova 
> blog to communicate these changes actively to the plugin ecosystem. 
> This mailing list only gets 400+ subscribers.
>
>
There will be a blog post once 5.0 is released.  We're not forcing people to 
upgrade to 5.0, and we will be supporting the 4.x branch for six months.  This 
does mean we're stuck supporting 3.x, 4.x and 5.x for a brief window, but I 
have no control over when Marshmallow is released, only whether we want to 
support it or not.  I think we do, but I could be wrong.

At least this should be easier than the jump from 3.x to 4.x for most people, 
but the alternative is that your plugin just doesn't work at all on 
Marshmallow.  We need to at least give plugin developers this option, since 
it'll roll out on all the Nexus devices in the next two weeks, and we'll hear 
more about it.


> Can you re-base your cordova-android over the current master? It's 
> hard to see a diff in the current form:
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithu
> b.com%2fapache%2fcordova-android%2fcompare%2fmaster...infil00p%3asmore
> s=01%7c01%7cnikhilkh%40microsoft.com%7cb451a04dccc64fabdb9608d2c2
> edb23c%7c72f988bf86f141af91ab2d7cd011db47%7c1=j0bxz39itXdtylHJlv
> PYoJpZqXMhFjyTV35I9X5Yxzs%3d
>
>
I had to do a merge commit to get this to happen (boo), but it should be mostly 
cleaned up now.  It seems some style cleanup creeped into the most recent 
changes, but this should be a bit m

RE: [Android] 5.0.x release branch?

[Nikhil Khandelwal]

Can you explain why latest plugins will not be compatible with older versions 
of Cordova? Can this be avoided by any means? When you mean they would not be 
compatible - will it result in a build or runtime failure?

For marshmallow, what is the guidance that we need to issue to the larger 
Cordova plugin ecosystem? Joe you are ahead of the curve here compared to most 
other plugin developers - a blot post explaining what are known gotchas would 
be great. I really hope we can use our Cordova blog to communicate these 
changes actively to the plugin ecosystem. This mailing list only gets 400+ 
subscribers.

Can you re-base your cordova-android over the current master? It's hard to see 
a diff in the current form:
https://github.com/apache/cordova-android/compare/master...infil00p:smores

-Nikhil

-Original Message-
From: Joe Bowser [mailto:bows...@gmail.com] 
Sent: Monday, September 21, 2015 2:14 PM
To: dev 
Subject: [Android] 5.0.x release branch?

Hey

In the next two weeks, Marshmallow will most likely getting released with the 
brand new Nexus 6P being released from Huawei.  Given that most of the Nexus 
devices will be getting this release, we should probably release the 5.0.x 
branch of Android soon, and get the new plugins updated.

It should be noted that the latest plugins will not be compatible with older 
versions of Cordova, which is a big deal.  This is due to the use of various 
compatibility checks to make sure they support Marshmallow and older versions 
of Android.

So, if everyone can look over the smores branches of my GitHub before I create 
the 5.0.x branch and pull the changes into it, that would be awesome.

https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2finfil00p%2fcordova-android%2ftree%2fsmores=01%7c01%7cnikhilkh%40microsoft.com%7c1785194b1f82494fc2d908d2c2c99f36%7c72f988bf86f141af91ab2d7cd011db47%7c1=%2fPKmL8KTsz5dnC3A75yMatXLQUnfK0Nv07%2bve4PVcCE%3d
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2finfil00p%2fcordova-plugin-geolocation%2ftree%2fsmores=01%7c01%7cnikhilkh%40microsoft.com%7c1785194b1f82494fc2d908d2c2c99f36%7c72f988bf86f141af91ab2d7cd011db47%7c1=o6cLXM4f3kpUGCTlIv65ft8lKv6pc5qbeY%2bdUxiP4bc%3d
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2finfil00p%2fcordova-plugin-camera%2ftree%2fsmores=01%7c01%7cnikhilkh%40microsoft.com%7c1785194b1f82494fc2d908d2c2c99f36%7c72f988bf86f141af91ab2d7cd011db47%7c1=kNsHIv6Uw2ITcT1ABmNq1JCmPTSigCGRb4zWC8maWpE%3d
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2finfil00p%2fcordova-plugin-contacts%2ftree%2fsmores=01%7c01%7cnikhilkh%40microsoft.com%7c1785194b1f82494fc2d908d2c2c99f36%7c72f988bf86f141af91ab2d7cd011db47%7c1=rZ%2f1AALPAtUwgSXyOL1uk1b0Y%2feEmqLOdU%2fwua2TbLU%3d

Work on audio is still outstanding, BUT for some reason Audio broke recently on 
both Lollipop and Marshmallow.  I didn't test it out on KitKat or Jellybean 
yet, but I'm wondering whether we should keep maintaining this or support the 
standard HTML5 audio and deal with the asset issue somehow (which isn't 
straight forward).

I hopefully want to get a 5.0.x branch happening this week if we can.

What do people think?

Joe

RE: Marshmallow Update and Cordova-Android 5.0

[Nikhil Khandelwal]

Yes, it is but it only runs on an emulator which has an API-19 level OS. At the 
very least we'll need to run tests on marshamallow OS emulator/device.

From what I understood, marshamallow will break a number of plugins as we make 
those fixes it will be great to see those tests pass. 

Thanks,
Nikhil


-Original Message-
From: Joe Bowser [mailto:bows...@gmail.com] 
Sent: Wednesday, September 9, 2015 8:28 AM
To: dev@cordova.apache.org
Subject: Re: Marshmallow Update and Cordova-Android 5.0

Android is already there, isn't it?

On Tue, Sep 8, 2015, 9:16 PM Nikhil Khandelwal <nikhi...@microsoft.com>
wrote:

> It would be great to add this platform matrix to our buildbot CI. Any 
> volunteers?
>
> -Nikhil
>
> -Original Message-
> From: Karen Tran [mailto:ktop...@gmail.com]
> Sent: Monday, September 7, 2015 7:32 PM
> To: dev@cordova.apache.org
> Subject: Re: Marshmallow Update and Cordova-Android 5.0
>
> I tested your camera plugin through mobilespec and the permissions are 
> working.
>
> On Thu, Sep 3, 2015 at 12:10 PM, Joe Bowser <bows...@gmail.com> wrote:
>
> > On Thu, Sep 3, 2015 at 8:07 AM Karen Tran <ktop...@gmail.com> wrote:
> >
> > > Hi Joe,
> > >
> > > I tested your patch and it works for the most part using 
> > > mobilespec's manual test for contacts. I do see the prompt for 
> > > permissions contacts,
> > but
> > > not explicitly to read or write contacts like you mentioned.
> > >
> > > I don't either, even though I'm explicitly promoting for the
> permission.
> > Also, I found that if you prompt for READ permissions, you get both 
> > READ and WRITE.
> >
> >
> > > One thing that doesn't work is if you click "Deny" permission, the 
> > > app crashes. I don't think we'd want that to happen, so we'll have 
> > > to handle that case.
> > >
> >
> > It should work now.  I forgot to return out of the method once the 
> > permission is denied.
> >
> >
> > >
> > > And as for the contact autotests, they're a bit finicky now with a 
> > > couple of failures.
> > >
> >
> > Contacts has always been finicky, and needs a full re-write.  I 
> > wasn't intending to fully fix this plugin (because of time), just 
> > get the permissions working because it's the low hanging fruit.  Any 
> > change to the flow of the tests will break the tests because of 
> > concurrency issues with the Android Contacts API.
> >
> > I also have the Camera using the plugin, since we rely on external 
> > storage for determining whether we're going to produce duplicates.
> >
> > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgit
> > hu 
> > b.com%2finfil00p%2fcordova-plugin-camera%2ftree%2fsmores=01%7c0
> > 1%
> > 7cnikhilkh%40microsoft.com%7c30099748db0849137b6b08d2b7f5b4e5%7c72f9
> > 88
> > bf86f141af91ab2d7cd011db47%7c1=HQYKeY5Xnkqpr0xnwsNH8wGvtNduDAl
> > 59
> > FUYbH7WQHo%3d
> >
> >
> >
> > > On Tue, Sep 1, 2015 at 9:39 AM, Carlos Santana 
> > > <csantan...@gmail.com>
> > > wrote:
> > >
> > > > Joe I understand the feeling. One part of me saying that we 
> > > > should name
> > > the
> > > > version 4.2 since there are no API changes.
> > > > But my other part says that if developer's ignore because is 4.x 
> > > > stuff
> > > will
> > > > break in new major release of Android M (23)
> > > >
> > > > I would say that also agree that best option is to name is
> > > > cordova-android@5
> > > > , then is clear to developers that they can use targetsdk=23 and 
> > > > also
> > new
> > > > major versions for the affected plugins that need updates to 
> > > > support
> > > > targetsdk=23
> > > >
> > > > But as you can see this is less important that getting the 
> > > > plugins to
> > > work
> > > > correctly with permissions :-)
> > > >
> > > >
> > > >
> > > > On Tue, Sep 1, 2015 at 12:03 AM Joe Bowser <bows...@gmail.com>
> wrote:
> > > >
> > > > > BTW: I got Contacts somewhat working with Marshmellow.  It's 
> > > > > still
> > got
> > > > the
> > > > > same crappy concurrency bugs that it always has, and I am not 
> > > > > sure
> > how
> > > to
> > > > > resolve those without re-writing the damn thing, bu

RE: going to merge PR #39 for globalization plugin ?

[Nikhil Khandelwal]

Would be great to have some help in merging pending PRs. There are lots of them 
pending. [1]

This is a good guide on this for committers: 
https://github.com/apache/cordova-coho/blob/master/docs/processing-pull-requests.md

Thanks,
Nikhil

[1] http://s.apache.org/cordovaPulls

-Original Message-
From: Shazron [mailto:shaz...@gmail.com] 
Sent: Thursday, September 10, 2015 11:06 AM
To: dev@cordova.apache.org
Subject: Re: going to merge PR #39 for globalization plugin ?

I'm too lazy as well, too much to do :/ looks like you have to do it.
Merge it no need to ask permission, dear core committer :)

On Thursday, September 10, 2015, Carlos Santana 
wrote:

> Any objections for me to merge PR #39 [1] ?
> I'm going to review it again, and merge if it looks good.
>
> Also I see that there are other 5 PRs, dating back to Aug 28, 2014 ouch !!
>
> Was thinking on giving some love to the plugin and handle the other 
> PRs also, what you guys think?
>
> Anyone knows if some of these PRs are already merged, and just open 
> can't be close with a git comment? I'm too lazy to check :-p if 
> someone can give me the answer quickly
>
> [1]: 
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fapache%2fcordova-plugin-globalization%2fpull%2f39=01%7c01%7cnikhilkh%40microsoft.com%7c4f072382eacb4d1a461108d2ba0a7b52%7c72f988bf86f141af91ab2d7cd011db47%7c1=fZTeBpO14TWnXOsWyBIRlAhLHyAGrXSUr3TOqTNYCQk%3d
>

RE: Marshmallow Update and Cordova-Android 5.0

[Nikhil Khandelwal]

It would be great to add this platform matrix to our buildbot CI. Any 
volunteers?

-Nikhil

-Original Message-
From: Karen Tran [mailto:ktop...@gmail.com] 
Sent: Monday, September 7, 2015 7:32 PM
To: dev@cordova.apache.org
Subject: Re: Marshmallow Update and Cordova-Android 5.0

I tested your camera plugin through mobilespec and the permissions are working.

On Thu, Sep 3, 2015 at 12:10 PM, Joe Bowser  wrote:

> On Thu, Sep 3, 2015 at 8:07 AM Karen Tran  wrote:
>
> > Hi Joe,
> >
> > I tested your patch and it works for the most part using 
> > mobilespec's manual test for contacts. I do see the prompt for 
> > permissions contacts,
> but
> > not explicitly to read or write contacts like you mentioned.
> >
> > I don't either, even though I'm explicitly promoting for the permission.
> Also, I found that if you prompt for READ permissions, you get both 
> READ and WRITE.
>
>
> > One thing that doesn't work is if you click "Deny" permission, the 
> > app crashes. I don't think we'd want that to happen, so we'll have 
> > to handle that case.
> >
>
> It should work now.  I forgot to return out of the method once the 
> permission is denied.
>
>
> >
> > And as for the contact autotests, they're a bit finicky now with a 
> > couple of failures.
> >
>
> Contacts has always been finicky, and needs a full re-write.  I wasn't 
> intending to fully fix this plugin (because of time), just get the 
> permissions working because it's the low hanging fruit.  Any change to 
> the flow of the tests will break the tests because of concurrency 
> issues with the Android Contacts API.
>
> I also have the Camera using the plugin, since we rely on external 
> storage for determining whether we're going to produce duplicates.
>
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithu
> b.com%2finfil00p%2fcordova-plugin-camera%2ftree%2fsmores=01%7c01%
> 7cnikhilkh%40microsoft.com%7c30099748db0849137b6b08d2b7f5b4e5%7c72f988
> bf86f141af91ab2d7cd011db47%7c1=HQYKeY5Xnkqpr0xnwsNH8wGvtNduDAl59
> FUYbH7WQHo%3d
>
>
>
> > On Tue, Sep 1, 2015 at 9:39 AM, Carlos Santana 
> > 
> > wrote:
> >
> > > Joe I understand the feeling. One part of me saying that we should 
> > > name
> > the
> > > version 4.2 since there are no API changes.
> > > But my other part says that if developer's ignore because is 4.x 
> > > stuff
> > will
> > > break in new major release of Android M (23)
> > >
> > > I would say that also agree that best option is to name is
> > > cordova-android@5
> > > , then is clear to developers that they can use targetsdk=23 and 
> > > also
> new
> > > major versions for the affected plugins that need updates to 
> > > support
> > > targetsdk=23
> > >
> > > But as you can see this is less important that getting the plugins 
> > > to
> > work
> > > correctly with permissions :-)
> > >
> > >
> > >
> > > On Tue, Sep 1, 2015 at 12:03 AM Joe Bowser  wrote:
> > >
> > > > BTW: I got Contacts somewhat working with Marshmellow.  It's 
> > > > still
> got
> > > the
> > > > same crappy concurrency bugs that it always has, and I am not 
> > > > sure
> how
> > to
> > > > resolve those without re-writing the damn thing, but the purpose 
> > > > of
> > this
> > > is
> > > > to figure out how to get permissions to work, and I have 
> > > > something
> that
> > > > works.
> > > >
> > > > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2
> > > > fgithub.com%2finfil00p%2fcordova-plugin-contacts%2ftree%2fsmores
> > > > =01%7c01%7cnikhilkh%40microsoft.com%7c30099748db0849137b6b0
> > > > 8d2b7f5b4e5%7c72f988bf86f141af91ab2d7cd011db47%7c1=c9deJEn
> > > > 9QG4vSDvqCMhBH%2f7r6RyBjitCYeMUtlXC4WE%3d
> > > >
> > > > This works with the latest smores tree of Cordova Android, and I
> tested
> > > it
> > > > on Lollipop and Marshmellow.  I'm going to move on to some of 
> > > > the
> other
> > > > plugins to get them ready for Marshmellow, but it'd be good to 
> > > > have
> > > people
> > > > look these over.
> > > >
> > > > I did find a nasty security bug with this, though.  If you 
> > > > request
> one
> > > > permission out of the permission group, you get all the permissions.
> > So,
> > > > anything that can read contacts can magically write contacts 
> > > > even if
> > you
> > > > don't request that permission explicitly.  I think this is a 
> > > > serious
> > bug,
> > > > and I'm going to dig tomorrow to see if someone already reported it.
> > > >
> > > > On Mon, Aug 31, 2015 at 11:35 AM Joe Bowser 
> wrote:
> > > >
> > > > > Hey
> > > > >
> > > > > So, I created a new topic branch of my github with the new 
> > > > > changes
> as
> > > > > suggested earlier.
> > > > >
> > > > > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f
> > > > > %2fgithub.com%2finfil00p%2fcordova-android%2ftree%2fsmores
> > > > > a=01%7c01%7cnikhilkh%40microsoft.com%7c30099748db0849137b6b08d
> > > > > 

RE: [REVIEW] CPR readonly blog post.

[Nikhil Khandelwal]

Do we even need a plugman CLI now? Monthly download counts on npm have remained 
steady at around 25K or so. [1]

I know our docs talk about a platform-centric workflow whereby there is no 
cordova CLI and a platform is used on its own, and the plugman CLI might be 
needed. It's not clear to me how popular that workflow is and something we need 
to support.

[1] http://npm-stat.com/charts.html?package=plugman===

-Nikhil

-Original Message-
From: Nikhil Khandelwal [mailto:nikhi...@microsoft.com] 
Sent: Thursday, September 3, 2015 10:21 PM
To: dev@cordova.apache.org
Subject: RE: [REVIEW] CPR readonly blog post.

This looks great. It will be good to reference our previous blog post about 
this announcement:
https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fcordova.apache.org%2fannouncements%2f2015%2f04%2f21%2fplugins-release-and-move-to-npm.html=01%7c01%7cnikhilkh%40microsoft.com%7ceed8f7f58fdb4e6ea71708d2b4e8b53d%7c72f988bf86f141af91ab2d7cd011db47%7c1=2w2%2b2FtDC0S8gUkHQ7jmui26kaoY3HTe%2fvsrY0HhX9w%3d
 - just to let devs know that this is not the first time we're talking about 
this.

-Nikhil

-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com] 
Sent: Thursday, September 3, 2015 5:50 PM
To: dev@cordova.apache.org
Subject: Re: [REVIEW] CPR readonly blog post.

Replace "read-only" , it's soo 2014
Use "immutable" sounds more hipster :-)

Other than that looks good to me, I notice you don't mentioned plugman cli. I 
think is OK to make general use to be cordova cli. 


- Carlos
Sent from my iPhone

> On Sep 3, 2015, at 8:27 PM, Shazron <shaz...@gmail.com> wrote:
>  
> Looks good. Spelling "swithed"
> 
>> On Thu, Sep 3, 2015 at 5:14 PM, Steven Gill <stevengil...@gmail.com> wrote:
>> 
>> Please review.
>> 
>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fcordova%2fapache-blog-posts%2fblob%2fmaster%2f2015-09-03-CPR-readonly.md=01%7c01%7cnikhilkh%40microsoft.com%7cdfd3d7c4de9d4bb4889b08d2b4c2bf24%7c72f988bf86f141af91ab2d7cd011db47%7c1=IDvO8xH%2fZvE5qfsebJIVW0GBI57LWpYAY71X7%2bbzs3w%3d
>> 
>> Anything else I should add?
>> 
>> -Steve
>> 

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


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


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

RE: Merges as a feature

[Nikhil Khandelwal]

I sort of agree with Raymond that is a useful functionality and is easy enough 
to do this for users - by using a 'convention'. Customizing the build system 
using hooks sounds more complicated for the developer. How does ionic & mfp 
actually achieve this? How does a developer specify specific versions of files 
that need to be included only on certain platforms.

-Nikhil

-Original Message-
From: Jesse [mailto:purplecabb...@gmail.com] 
Sent: Tuesday, September 1, 2015 3:18 PM
To: dev@cordova.apache.org
Subject: Re: Merges as a feature

Well finding it in the docs is/was.
This functionality is depended on by Visual Studio TACO so I don't think it is 
going anywhere soon.




My team is hiring!
@purplecabbage
https://na01.safelinks.protection.outlook.com/?url=risingj.com=01%7c01%7cnikhilkh%40microsoft.com%7c7f9065b097754dab6e3608d2b31b4271%7c72f988bf86f141af91ab2d7cd011db47%7c1=LaeCiYKqEmUrtyvFWibxgtMPzi52MfNI5rJHHotD0sc%3d

On Tue, Sep 1, 2015 at 3:03 PM, Raymond Camden 
wrote:

> Yeah I don't think documentation is a problem. :)
>
> On Tue, Sep 1, 2015 at 4:58 PM, Carlos Santana 
> wrote:
> > Merges doc is here:
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fcordo
> va.apache.org%2fdocs%2fen%2fedge%2fguide_cli_index.md.html%23The%2520C
> ommand-Line%2520Interface_using_merges_to_customize_each_platform
> =01%7c01%7cnikhilkh%40microsoft.com%7c7f9065b097754dab6e3608d2b31b4271
> %7c72f988bf86f141af91ab2d7cd011db47%7c1=%2f2FhMxoCI4p5BF1l22FIPv
> Wt3jA0%2fECQfsW9iIAmpbA%3d
> >
> >
> > - Carlos
> > Sent from my iPhone
> >
> >> On Sep 1, 2015, at 5:53 PM, Jesse  wrote:
> >>
> >> I would like to get rid of merges, now that you bring it up.
> >> We have far too many nuanced features that just sort of go undoc'd.
> >>
> >> I may change my mind if someone can point me at a page in the docs 
> >> that explains the full use and value of this feature because 
> >> currently it
> just
> >> sounds like technical debt.
> >>
> >>
> >> My team is hiring!
> >> @purplecabbage
> >> https://na01.safelinks.protection.outlook.com/?url=risingj.com
> >> =01%7c01%7cnikhilkh%40microsoft.com%7c7f9065b097754dab6e3608d2b31b4
> >> 271%7c72f988bf86f141af91ab2d7cd011db47%7c1=LaeCiYKqEmUrtyvFWi
> >> bxgtMPzi52MfNI5rJHHotD0sc%3d
> >>
> >> On Tue, Sep 1, 2015 at 2:38 PM, Raymond Camden 
> >>  >
> >> wrote:
> >>
> >>> Oh sorry - well - I brought it up in an issue report for Ionic.
> >>> They've got a few different ways of handling this, and I thought 
> >>> it might make sense to mention the Cordova Merges feature too. I 
> >>> was asked if it was possibly going away, hence me asking the 
> >>> Powers that Be here. (Wait, I think I'm one of those Powers...)
> >>>
> >>> On Tue, Sep 1, 2015 at 4:32 PM, Carlos Santana 
> >>> 
> >>> wrote:
>  Ok I agree for simple use case is very simple to drop files in merges.
> >>> Which is the use case for visual studio template.
> 
>  Just curious on why an open ended question?
> 
>  It will be the same as me asking "Is hooks as a Feature going away?"
> >>> With not other context.
> 
>  What prompted you to ask a the random question?
> 
>  Did someone told you that merges is going away?
> 
>  - Carlos
>  Sent from my iPhone
> 
> > On Sep 1, 2015, at 5:18 PM, Raymond Camden 
> > 
> >>> wrote:
> >
> > Ok, so now we're off my initial question and into a debate. :)
> >
> > I think you are absolutely right - there are more powerful 
> > solutions
> -
> > but that doesn't negate the ease of use of merges. The 
> > simplicity of it may be just fine for many use cases.
> >
> >
> >> On Tue, Sep 1, 2015 at 4:10 PM, Carlos Santana <
> csantan...@gmail.com>
> >>> wrote:
> >> If people wants achieve to do what merges do, I recommend hooks 
> >> or
> >>> custom build process (i.e. npm scripts, gulp, grunt, ant, perl, 
> >>> ruby,
> etc)
> >>> or running custom build from hooks.
> >>
> >> There is more flexibility and control thru hooks than merges.
> >>
> >> - Carlos
> >> Sent from my iPhone
> >>
> >>> On Sep 1, 2015, at 5:04 PM, Raymond Camden <
> raymondcam...@gmail.com>
> >>> wrote:
> >>>
> >>> K good enough for me. I don't agree with you. ;)
> >>>
>  On Tue, Sep 1, 2015 at 3:25 PM, Carlos Santana <
> csantan...@gmail.com>
> >>> wrote:
>  In my personal opinion it's not a best practice anymore to 
>  use
> >>> merges.
> 
>  The feature works today if you create a folder "merges"
> 
>  cordova create doesn't create it by default It will not go 
>  away, visual studio leverages the "merges" folder
> in
> >>> their cordova templates.
> 
>  It will not be remove or deprecated, and at the same time 
>  will not
> >>> be 

RE: [DISCUSS] Local plugin configuration

[Nikhil Khandelwal]

I like this design (we should have had this in the first place) - but am 
concerned of the breaking nature.

Do we have a specific case of a name conflict that we know of? Another way to 
do this would be to use naming conventions - similar to a namespace. The 
recommendation would be to prefix the preference name with the plugin id - 
though that makes preference names rather long and does not guarantee anything.

-Nikhil 

-Original Message-
From: Shazron [mailto:shaz...@gmail.com] 
Sent: Tuesday, September 1, 2015 4:33 PM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Local plugin configuration

>
>
> So what I'm missing from the plugin spec is the possibility to 
> describe what preferences are available/required for the plugin to 
> work.
>
>
It being under  would imply this but I think you are asking about the 
way currently things are. Yeah right now if preference is not added under the 
 a user wouldn't know about it.


> > All relevant platforms
> > will now need to support reading of these new tags, and have a way 
> > for plugins to access them. This would be a major platform version 
> > bump
> because
> > of a new API needed for plugins (which is next for cordova-osx and 
> > cordova-ios but the other platforms already have their major version 
> > bumps). We could avoid a major version bump if we could shoehorn 
> > namespacing the plugin preferences into the current settings [1].
>
> Is there already a JS API defined for plugins, that hey should expose?
> i.e we could then add the
>
> /* {object} */ Plugin.getConfiguration();
>
> to it.
>

No there is no API for this currently.



> >
> > The problem would be, if the new tags are specified in plugin.xml, 
> > and
> you
> > didn't have the newer platform installed, the plugin won't be 
> > configured properly. This could be mitigated by having the required 
> > platform version specified in an  tag, but this will exclude 
> > your plugin from
> older
> > platforms.
>
> I think the plugins need to be backward compatible, you could add a 
> fallback information, like 
> default="cordova.png" />
> 
>
> and plugman should copy over all params anyways, right?
>

They still won't be configured properly, since older platforms won't know what 
to do with these new attributes, and won't save them for plugins to access. The 
config parser is part of the platform. The plugin however, could read this 
config.xml themselves of course but we're trying to solve this in a generic way 
that is easier for plugin authors.

Also, I found an issue already filed (by me) essentially already asking for 
what you want:
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fbrowse%2fCB-6458=01%7c01%7cnikhilkh%40microsoft.com%7c358da174d2c54994660308d2b325da62%7c72f988bf86f141af91ab2d7cd011db47%7c1=jkto%2fhvkmiVg5UX9j2uzVYlSCroxjLRDahhoYwj%2fY%2b0%3d

Perhaps we could continue on that issue, I've tentatively labeled the issue for 
cordova-ios-5.0.x

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

RE: [DISCUSS] cordova-ios 4.0.0 release

[Nikhil Khandelwal]

This is great level of detail. Since there are plugin API changes - it would be 
great to make a broader post - on slack, twitter, our blog. 

Do we have a sense of how impactful are the breaking changes - say how many of 
the top 50 plugins will not compile when ios 4.0 releases? If not, I can help 
with some of this.

-Nikhil

-Original Message-
From: Shazron [mailto:shaz...@gmail.com] 
Sent: Tuesday, September 1, 2015 4:38 PM
To: dev@cordova.apache.org
Subject: [DISCUSS] cordova-ios 4.0.0 release

Gotta get the train going again, it's been too long.

The kanban board for this is at:
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fsecure%2fRapidBoard.jspa%3frapidView%3d76=01%7c01%7cnikhilkh%40microsoft.com%7c08b034c083874c2c66d508d2b3267cc1%7c72f988bf86f141af91ab2d7cd011db47%7c1=K1qHZZpDy2lSIUt4tG98j9MPVP7FRCDOp1TJ%2fpPQo9U%3d

Please help if you can by assigning an issue to yourself, and selecting the 
"Start Progress" button. This will show who is working on what in the middle 
"In Progress" column.

I've trimmed this and it includes cordova-ios platform issues, and some plugin 
issues. Priority given to platform issues of course, and issues with iOS 9. If 
there is a pressing issue that needs to go in, assign it the label 
"cordova-ios-4.0.x" but propose it to this thread first so we don't get 
de-railed, there's only so much room on the train. Similarly if you think an 
issue can get thrown off the train to cordova-ios-5.0.x, post on this thread.

Focus is on core plugin stability with the new platform, since it does have API 
changes. If downstream distribution people are on this list, this concerns your 
third-party plugins too.

The easiest way to test if it affects your plugin building:

```
cordova platform add 
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fapache%2fcordova-ios.git=01%7c01%7cnikhilkh%40microsoft.com%7c08b034c083874c2c66d508d2b3267cc1%7c72f988bf86f141af91ab2d7cd011db47%7c1=g3UNK0NRdsaPGqsxIzUMxcXN8zRLpWyVdhUKe9pLnA0%3d
cordova plugin add your-plugin-id
cordova build
```

Plugin updates and highlights:
- API changes doc:
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fapache%2fcordova-ios%2fblob%2fmaster%2fguides%2fAPI%2520changes%2520in%25204.0.md=01%7c01%7cnikhilkh%40microsoft.com%7c08b034c083874c2c66d508d2b3267cc1%7c72f988bf86f141af91ab2d7cd011db47%7c1=EPGtg%2fAbzCvZ%2f3zib2H5I9oNyvJB7%2bFSCeHJ5q1n5Dc%3d
- 3 new private core plugins to the platform:
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fapache%2fcordova-ios%2ftree%2fmaster%2fCordovaLib%2fClasses%2fPrivate%2fPlugins=01%7c01%7cnikhilkh%40microsoft.com%7c08b034c083874c2c66d508d2b3267cc1%7c72f988bf86f141af91ab2d7cd011db47%7c1=DFA1psN5aCn0GNucm9NOFRZWJRX86%2bp2RmXZA4GHkKA%3d
- Plugin localized strings and resource loading:
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fapache%2fcordova-ios%2fblob%2fmaster%2fCordovaLib%2fClasses%2fPublic%2fCDVPlugin%252BResources.h=01%7c01%7cnikhilkh%40microsoft.com%7c08b034c083874c2c66d508d2b3267cc1%7c72f988bf86f141af91ab2d7cd011db47%7c1=qGNLKonBYDHgwhSa5iPnakeBns2vfuVa42OTIMHqmCE%3d
   - Preferences helper:
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fapache%2fcordova-ios%2fblob%2fmaster%2fCordovaLib%2fClasses%2fPublic%2fNSDictionary%252BCordovaPreferences.h=01%7c01%7cnikhilkh%40microsoft.com%7c08b034c083874c2c66d508d2b3267cc1%7c72f988bf86f141af91ab2d7cd011db47%7c1=6S%2bInwG0YRdLm9niK4wZtEMks6BBYjsrzEXeOTvnuU8%3d
   - WebViews as plugins. UIWebView is a private core plugin (see above).
WKWebView as a plugin installable
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fapache%2fcordova-plugins%2ftree%2fmaster%2fwkwebview-engine=01%7c01%7cnikhilkh%40microsoft.com%7c08b034c083874c2c66d508d2b3267cc1%7c72f988bf86f141af91ab2d7cd011db47%7c1=a9Tazxtga6e9dYRMoO3z1YBTe5%2fdYDVAOnLe1yk3sik%3d

I also want to highlight this scenario which a lot of people will encounter:
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fbrowse%2fCB-9592=01%7c01%7cnikhilkh%40microsoft.com%7c08b034c083874c2c66d508d2b3267cc1%7c72f988bf86f141af91ab2d7cd011db47%7c1=S8a9hXH%2b0msUEiIcOAjH3SPOsj%2bpzcpfttKujsWTwPs%3d

I had to trim features and push it off to cordova-ios-5.0.x:
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fsecure%2fRapidBoard.jspa%3frapidView%3d86=01%7c01%7cnikhilkh%40microsoft.com%7c08b034c083874c2c66d508d2b3267cc1%7c72f988bf86f141af91ab2d7cd011db47%7c1=fMkNggbxDd6d9AjQKNqxFOcEqzuZKdUWp7V3f2pw79A%3d

Planned ship/vote date is around iOS 9 release time, which I believe is in
2 weeks or so (mid Sept 2015).

Choo choo

RE: Update: Plugins Registry warnings

[Nikhil Khandelwal]

On a related note, was our plan to do re-direction from old plugin registry ID 
to npm ID? I still get a warning and no automatic re-direction with latest 
cordova.

cordova plugin add org.apache.cordova.camera
Fetching plugin "org.apache.cordova.camera" via npm
WARNING: org.apache.cordova.camera has been renamed to cordova-plugin-camera. 
You may not be getting the latest version! We suggest you `cordova plugin rm 
org.apache.cordova.camera` and `cordova plugin add cordova-plugin-camera`.

Thanks,
Nikhil


-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Monday, August 31, 2015 4:25 PM
To: dev@cordova.apache.org
Subject: Re: Update: Plugins Registry warnings

So I have a PR ready to make the registry read-only. [1]

Unfortunately, plugman don't support outputting the errors received from the 
registry to our users. `plugman publish PLUGIN` outputs `publish fail`.

Even though I added a nice error message to the registry, users won't see it. 
Maybe other tools which consume plugins directly from the registry will be able 
to use this message.

If others have better suggestions for this problem, please share.

Any holdback on me merging this commit and deploying it?

Note: I accidentally pushed my original commit to the wrong origin (apache) so 
reverted it.

[1] 
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fapache%2fcordova-registry%2fpull%2f1=01%7c01%7cnikhilkh%40microsoft.com%7cf6adff27b1b24fc2cceb08d2b25b72cb%7c72f988bf86f141af91ab2d7cd011db47%7c1=7PRvSCOB7pl%2b5Hj3MoQAJSOjTWXXBsRluJJ04823hMI%3d

On Tue, Aug 11, 2015 at 7:14 PM, Shazron  wrote:

> "At the last hangout we discussed delaying switching the registry over 
> to read only until Aug 15thish. We should discuss what else needs to 
> happen for us to hit this."
>
> This is coming up fast. Anything we need to do before this deadline?
>
> On Thu, Jul 30, 2015 at 10:08 AM, Steven Gill 
> wrote:
>
> > So I looked into adding warnings into the registry that users who 
> > are trying to publish/adduser would get, but it won't work.
> >
> > If plugman publish is successful, plugman does nothing. If plugman
> publish
> > fails, plugman will output the error that the registry sends.
> >
> > Once we switch the registry to read-only, I'll add an error message 
> > that tells users to publish to npm and points them to the appropriate guide.
> >
> > At the last hangout we discussed delaying switching the registry 
> > over to read only until Aug 15thish. We should discuss what else 
> > needs to happen for us to hit this.
> >
> > The next tools release, plugman looses all commands related to the
> registry
> > (publish, unpublish, adduser, owner). I'll be starting that release 
> > right after iOS 3.9.0 is done releasing.
> >
> > I am going to spend time tomorrow trying to gather the emails of 
> > people
> who
> > are still publishing and send them an email asking them to move over 
> > to npm.
> >
> > -Steve
> >
>

RE: [DISCUSS] Tools Release?

[Nikhil Khandelwal]

I really just meant minor version bump instead of major. Sorry for the mix-up 
in terminology.

-Nikhil

-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com] 
Sent: Thursday, August 27, 2015 11:07 PM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Tools Release?

That was my thinking no API breakage no major bump. 

Feature added minor bump

- Carlos
Sent from my iPhone

 On Aug 28, 2015, at 1:47 AM, Steven Gill stevengil...@gmail.com wrote:
 
 It is interesting. Adding a new platform could be consideration for a 
 major or minor. The platform (OSX) is having a major jump.
 
 According to semver, a major would be making a incompatible api change 
 and a minor would be adding functionality in a backwards-compatible manner.
 
 We don't break anything by adding osx, so I'm leaning toward minor.
 
 -Steve
 
 On Thu, Aug 27, 2015 at 10:37 PM, Carlos Santana 
 csantan...@gmail.com
 wrote:
 
 +1 minor release bump not major
 
 - Carlos
 Sent from my iPhone
 
 On Aug 27, 2015, at 11:45 PM, Nikhil Khandelwal 
 nikhi...@microsoft.com
 wrote:
 
 Also, there has been a browser release that we need to pin.
 
 -Nikhil
 
 -Original Message-
 From: Nikhil Khandelwal [mailto:nikhi...@microsoft.com]
 Sent: Wednesday, August 26, 2015 6:21 PM
 To: dev@cordova.apache.org
 Subject: RE: [DISCUSS] Tools Release?
 
 +1. Not sure if it will be a patch release as it does ship new 
 +platforms
 along with it and it could be considered a major bump because of that.
 
 -Nikhil
 
 -Original Message-
 From: Jesse [mailto:purplecabb...@gmail.com]
 Sent: Wednesday, August 26, 2015 6:17 PM
 To: dev@cordova.apache.org
 Subject: Re: [DISCUSS] Tools Release?
 
 +1
 
 
 
 On Aug 26, 2015, at 6:14 PM, Carlos Santana csantan...@gmail.com
 wrote:
 
 Yep makes sense to cut a release before that PR hits master
 On Wed, Aug 26, 2015 at 9:11 PM Carlos Santana 
 csantan...@gmail.com
 wrote:
 
 +1
 On Wed, Aug 26, 2015 at 8:47 PM Steven Gill 
 stevengil...@gmail.com
 wrote:
 
 How do people feel about a patch tools release including the 
 recently released platforms (windows, browser) + early support 
 for osx + updated cordova-serve.
 
 It would be nice to get this out before we add the new platform 
 api polyfill PR which is slated to get merged end of this week.
 https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2f
 git 
 hub.com%2fapache%2fcordova-lib%2fpull%2f282data=01%7c01%7cnikhil
 kh% 
 40microsoft.com%7cd6166af76ee448279b7808d2ae7d429b%7c72f988bf86f1
 41a 
 f91ab2d7cd011db47%7c1sdata=o4lRdDOed%2fvW6ZhlIidmAsdT2OSAwsoQ0Nw
 rMI
 4nTU8%3d
 
 
 - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
 For additional commands, e-mail: dev-h...@cordova.apache.org
 
 
 
 - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
 For additional commands, e-mail: dev-h...@cordova.apache.org
 
 
 
 - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
 For additional commands, e-mail: dev-h...@cordova.apache.org
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
 For additional commands, e-mail: dev-h...@cordova.apache.org
 
 

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


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

RE: [DISCUSS] Tools Release?

[Nikhil Khandelwal]

Also, there has been a browser release that we need to pin.

-Nikhil

-Original Message-
From: Nikhil Khandelwal [mailto:nikhi...@microsoft.com] 
Sent: Wednesday, August 26, 2015 6:21 PM
To: dev@cordova.apache.org
Subject: RE: [DISCUSS] Tools Release?

+1. Not sure if it will be a patch release as it does ship new platforms along 
with it and it could be considered a major bump because of that.

-Nikhil

-Original Message-
From: Jesse [mailto:purplecabb...@gmail.com]
Sent: Wednesday, August 26, 2015 6:17 PM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Tools Release?

+1



 On Aug 26, 2015, at 6:14 PM, Carlos Santana csantan...@gmail.com wrote:
 
 Yep makes sense to cut a release before that PR hits master
 On Wed, Aug 26, 2015 at 9:11 PM Carlos Santana csantan...@gmail.com wrote:
 
 +1
 On Wed, Aug 26, 2015 at 8:47 PM Steven Gill stevengil...@gmail.com
 wrote:
 
 How do people feel about a patch tools release including the 
 recently released platforms (windows, browser) + early support for 
 osx + updated cordova-serve.
 
 It would be nice to get this out before we add the new platform api 
 polyfill PR which is slated to get merged end of this week.
 https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgit
 hub.com%2fapache%2fcordova-lib%2fpull%2f282data=01%7c01%7cnikhilkh%
 40microsoft.com%7cd6166af76ee448279b7808d2ae7d429b%7c72f988bf86f141a
 f91ab2d7cd011db47%7c1sdata=o4lRdDOed%2fvW6ZhlIidmAsdT2OSAwsoQ0NwrMI
 4nTU8%3d
 

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


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


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

RE: [DISCUSS] Tools Release?

[Nikhil Khandelwal]

+1. Not sure if it will be a patch release as it does ship new platforms along 
with it and it could be considered a major bump because of that.

-Nikhil

-Original Message-
From: Jesse [mailto:purplecabb...@gmail.com] 
Sent: Wednesday, August 26, 2015 6:17 PM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Tools Release?

+1



 On Aug 26, 2015, at 6:14 PM, Carlos Santana csantan...@gmail.com wrote:
 
 Yep makes sense to cut a release before that PR hits master
 On Wed, Aug 26, 2015 at 9:11 PM Carlos Santana csantan...@gmail.com wrote:
 
 +1
 On Wed, Aug 26, 2015 at 8:47 PM Steven Gill stevengil...@gmail.com
 wrote:
 
 How do people feel about a patch tools release including the 
 recently released platforms (windows, browser) + early support for 
 osx + updated cordova-serve.
 
 It would be nice to get this out before we add the new platform api 
 polyfill PR which is slated to get merged end of this week.
 https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgit
 hub.com%2fapache%2fcordova-lib%2fpull%2f282data=01%7c01%7cnikhilkh%
 40microsoft.com%7cd6166af76ee448279b7808d2ae7d429b%7c72f988bf86f141a
 f91ab2d7cd011db47%7c1sdata=o4lRdDOed%2fvW6ZhlIidmAsdT2OSAwsoQ0NwrMI
 4nTU8%3d
 

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


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

RE: [DISCUSS] cordova-windows release

[Nikhil Khandelwal]

+1 to filing a JIRA for this with repro steps. We should address this in the 
next release. Vldmrrr is there already a JIRA for this?

-Nikhil

-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com] 
Sent: Wednesday, August 26, 2015 10:54 AM
To: dev@cordova.apache.org; Rob Paveza rob.pav...@microsoft.com
Subject: Re: [DISCUSS] cordova-windows release

So your saying failing to build from CLI is not critical to stop the release?

I'm OK not to stop the release, but still an issue filed a JIRA for the problem 
and see if it can be fixed in a subsequent release soon.

Also to note in the blog post for the release that introduce a problem that 
building from CLI is broken but there is workaround, and that you guys are 
going to take a look to fix ASAP.


On Wed, Aug 26, 2015 at 1:06 PM vldmrrr vldm...@gmail.com wrote:

 I finally tried running mobilespec  on my system, it fails with the 
 same error when building from command line for windows10, BUT when I 
 tried building from VS IDE, it builds fine, and does pass app cert 
 kit. Same goes about my test hello app. Good enough as far as I am 
 concerned

 On 8/23/2015 1:10 AM, Rob Paveza wrote:
  I'm not sure what you're seeing.  I definitely saw that with the 
  older
 versions, but I'm not seeing that on the release version.  CB-9524 is 
 fixed, I'll update that.
 
  I just validated it at home as well.
 
  Do you have the latest version of Visual Studio and Win10 tools?  
  The
 .NET Native stuff came in really late, but this is what I get as my output:
  -
  Building project:
 F:\cordova\mobilespec\platforms\windows\CordovaApp.Windows10.jsproj
   Configuration : release
   Platform  : x64
 Starting .NET Native compilation
 C:\Windows\Microsoft.NET\Framework\v4.0.30319\Csc.exe /noconfig
 /unsafe+
 /pdb:F:\cordova\mobilespec\platforms\windows\build\windows\bld\ilc\int
 ermediate\org.apache.m
 obilespec.pdb /nostdlib+ /reference:C:\Program Files
 (x86)\MSBuild\Microsoft\.NetNative\x64\ilc\lib\Private\System.Private.CoreLib.dll
 /debug:full /out:F:\cordova\
 
 mobilespec\platforms\windows\build\windows\bld\ilc\intermediate\org.ap
 ache.mobilespec.exe /target:winexe 
 F:\cordova\mobilespec\platforms\windows\build\windows\bld\il
 c\intermediate\fake.cs
 Processing application code
  C:\Program Files
 (x86)\MSBuild\Microsoft\.NetNative\x64\ilc\IlcInternals.targets(789,5):
 warning : Your application is missing a Runtime Directives (rd.xml) file.
 Runt
  ime Directives are used to describe the dynamic behavior of your
 application and control the .NET Native optimizer. It is recommended 
 to have at least one rd.xml file
  in your project.
 [F:\cordova\mobilespec\platforms\windows\CordovaApp.Windows10.jsproj]
 Computing application closure and generating interop code
 Compiling interop code
 Generating serialization code
 Cleaning up unreferenced code
 Running native compilers
 Generating fixups for native code
 Compilation successful.
 
 CordovaApp.Windows10 -
 F:\cordova\mobilespec\platforms\windows\AppPackages\CordovaApp.Windows
 10_0.0.1.0_x64_Test\CordovaApp.Windows10_0.0.1.0_x64.appx
BUILD OUTPUT:
 F:\cordova\mobilespec\platforms\windows\AppPackages\CordovaApp.Windows
 10_0.0.1.0_x64_Test\CordovaApp.Windows10_0.0.1.0_x64.appx
 
  Deploying windows10 package to device:
 
 F:\cordova\mobilespec\platforms\windows\AppPackages\CordovaApp.Windows
 10_0.0.1.0_x64_Test\CordovaApp.Windows10_0.0.1.0_x64.appx
  Attempt to uninstall previous application version...
  Attempt to install application...
  Found package:
 F:\cordova\mobilespec\platforms\windows\AppPackages\CordovaApp.Windows
 10_0.0.1.0_x64_Test\CordovaApp.Windows10_0.0.1.0_x64.appx
 
  Installing app...
  Found dependency package(s):
 
 F:\cordova\mobilespec\platforms\windows\AppPackages\CordovaApp.Windows
 10_0.0.1.0_x64_Test\Dependencies\x86\Microsoft.NET.Native.Runtime.1.1.
 appx
 
 F:\cordova\mobilespec\platforms\windows\AppPackages\CordovaApp.Windows
 10_0.0.1.0_x64_Test\Dependencies\x86\Microsoft.VCLibs.x86.14.00.appx
 
 F:\cordova\mobilespec\platforms\windows\AppPackages\CordovaApp.Windows
 10_0.0.1.0_x64_Test\Dependencies\x64\Microsoft.NET.Native.Runtime.1.1.
 appx
 
 F:\cordova\mobilespec\platforms\windows\AppPackages\CordovaApp.Windows
 10_0.0.1.0_x64_Test\Dependencies\x64\Microsoft.VCLibs.x64.14.00.appx
 
  Success: Your app was successfully installed.
  Starting application...
  ActivateApplication:
 org.apache.mobilespec_h35559jr9hy9m!org.apache.mobilespec
  -
  Mobilespec contains the globalization plugin as well and I also 
  created
 a new app to validate (I'm on a different computer too than the one 
 than I authored the release from).  WACK passed on all of these.
 
  It just looks to me like you're running into a problem with the .NET
 Native compiler as it's installed on your system.  If you want I can 
 try to get someone to work with you to figure out what's going on.
 
  -Rob