RE: [Vote] 3.7.1 WP8 Release

[Parashuram Narasimhan (MS OPEN TECH)]

+1

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Friday, December 19, 2014 11:40 AM
To: dev@cordova.apache.org
Subject: Re: [Vote] 3.7.1 WP8 Release

+1

Verified archive

On Thu, Dec 18, 2014 at 4:44 AM, Sergey Grebnov (Akvelon) < 
v-seg...@microsoft.com> wrote:
>
> Please review and vote on this 3.7.1 WP8 Release.
>
> Release issue: https://issues.apache.org/jira/browse/CB-8179
>
> Repos ready to be released have been published to dist/dev:
> https://dist.apache.org/repos/dist/dev/cordova/CB-8179
>
> The package was published from its corresponding git tag: fb6796796b
>
> Upon a successful vote I will upload the archive to dist/, publish it 
> to NPM, and post the corresponding blog post.
>
> Voting guidelines:
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting
> .md
>
> Voting will go on for a minimum of 48 hours.
>
> I vote +1:
> * Ran coho audit-license-headers over the relevant repos
> * Ran coho check-license to ensure all dependencies and 
> subdependencies have Apache-compatible licenses
> * Performed manual tests to ensure platform could be successfully 
> built and run
>
> Thx!
> Sergey
>
> -
> 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] Cordova-WP8 Release

[Parashuram Narasimhan (MS OPEN TECH)]

Hi,

We discovered that certain core plugins are affected, as described in this bug 
- https://issues.apache.org/jira/browse/CB-8139
It would be great if we would add this pull request 
(https://github.com/apache/cordova-wp8/pull/68) and do a release of the WP8 
platform. Are there other features that we would like to add to the release?

RE: [DISCUSS] Cordova-Ubuntu Release

[Parashuram Narasimhan (MS OPEN TECH)]

Are you also planning to do a CLI release with this? If you are, could we do a 
wp8 release in the CLI too? 

-Original Message-
From: Maxim Ermilov [mailto:maxim.ermi...@canonical.com] 
Sent: Monday, December 15, 2014 5:46 AM
To: dev@cordova.apache.org
Subject: [DISCUSS] Cordova-Ubuntu Release

Does anyone have any reason to delay a cordova-ubuntu platform release?
Any outstanding patches to land?

If not, I will start the release tomorrow.

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

RE: Apache license in "cordova create"

[Parashuram Narasimhan (MS OPEN TECH)]

Maybe we could ask legal-disc...@apache.org about this issue? They should be 
able to give us a definitive answer about the alternatives. 

From: Brian LeRoux
Sent: ‎Wednesday‎, ‎December‎ ‎10‎, ‎2014 ‎12‎:‎46‎ ‎PM
To: dev@cordova.apache.org

guess so yea, great first patch Martin ;)

On Wed, Dec 10, 2014 at 12:32 PM, Andrew Grieve 
wrote:

> Could we just strip the license as a part of the create script?
>
> On Wed, Dec 10, 2014 at 2:30 PM, Brian LeRoux  wrote:
>
> > recent discussions elsewhere indicate (to me) that while the ASL (apache
> > software license) is compatible with other licenses but the ASF (apache
> > software foundation) doesn't want to conflate our source with other ones
> > (reasonable imo)
> >
> >
> > On Wed, Dec 10, 2014 at 11:21 AM, Josh Soref 
> > wrote:
> >
> > > In theory, shouldn't we be able to put that file under an MIT/BSD
> license
> > > to make people happier?
> > >
> > > Getting sample content to be usable by others is a pain, and something
> > > that is one of the last steps people work on.
> > >
> > > I think Mozilla moved its tests to MIT to address this.
> > >
> > > I have no idea what Apache's policy is.
> > >
> > > Unfortunately, I can't find any good examples of this…
> > >
> > >
> >
> https://github.com/eclipsesource/raspberry-pi-examples/blob/master/com.ecli
> > >
> >
> psesource.iot.photosensor-example/src/com/eclipsesource/iot/photosensor/exa
> > > mple/Main.java
> > >
> > > Has an Eclipse license on a sample, which is probably just as bad.
> > >
> > >
> >
> http://hg.netbeans.org/main/file/23e994b27837/apisupport.crudsample/crud-sa
> > > mple-application/CustomerDBAccess/src/demo/Customer.java
> > >
> > > Has GPL/CDDL. GPL is clearly useless. I'm not sure CDDL is more helpful
> > > than Apache.
> > >
> > >
> > >
> >
> http://www.contactandcoil.com/software/a-very-fast-tutorial-on-open-source-
> > > licenses/
> > >
> > >
> >
> http://mail-archives.apache.org/mod_mbox/cayenne-dev/200710.mbox/%3C62FEC22
> > > 5-fe92-476b-84c1-69869b179...@objectstyle.org%3E
> > >
> > > http://apache.org/legal/3party.html#category-a
> > >
> > >
> >
> http://opendata.stackexchange.com/questions/245/cc-by-vs-mit-or-bsd-license
> > > s-regarding-re-use
> > >
> > >
> > > https://wiki.creativecommons.org/CC0_FAQ
> > >
> > >
> > > I think we should probably get permission and relicense those files as
> > > CC-0.
> > >
> > > CC-0 isn't in the list that Apache has whitelisted, but I think we
> should
> > > be able to convince apache that this is the right license for these
> files
> > > (and similar template files to be used to generate content that a
> > consumer
> > > is supposed to be able to do w/ however they please).
> > >
> > > On 12/10/14, 2:02 PM, "Brian LeRoux"  wrote:
> > >
> > > >no mistake, but it is a requirement for us to distribute code at
> apache.
> > > >you are free to remove and relicense as you wish.
> > > >
> > > >On Wed, Dec 10, 2014 at 9:49 AM, Martin Sidaway 
> > > >wrote:
> > > >
> > > >> I'm a bit puzzled by the Apache license notice present in the
> > following
> > > >> files after doing "cordova create":
> > > >>
> > > >> www/index.html
> > > >> www/js/index.js
> > > >> www/css/index.css
> > > >>
> > > >> The trouble is that if I begin my project by extending those files,
> it
> > > >> seems like the Apache license covers my changes as well as the
> > original
> > > >> template. It also seems like I am saying that my changes are
> "licensed
> > > >>to
> > > >> the Apache Software Foundation under one or more contributor license
> > > >> agreements". And it doesn't seem like the Apache license would allow
> > me
> > > >>to
> > > >> remove those notices.
> > > >>
> > > >> So am I right in thinking that if I want to develop software that I
> > > >>might
> > > >> not intend to be Apache-licensed and/or licensed to ASF, I have to
> > > >>delete
> > > >> these 3 files and start from scratch?
> > > >>
> > > >> This sort of thing seems a little inappropriate in a template.
> > Basically
> > > >> what it means is that I have to (1) work out what the template does
> > and
> > > >> which parts I actually need to begin a project, (2) rewrite those
> > parts
> > > >>by
> > > >> hand (basic html document structure, meta/viewport tag, etc.) taking
> > > >>care
> > > >> not to resort to copy/paste, (3) gradually realise that the aspects
> of
> > > >>my
> > > >> app that behave inconveniently on certain platforms correspond to
> > > >>things I
> > > >> chose not to copy over from the template.
> > > >>
> > > >> Is there any other way to approach this? Is it a mistake?
> > > >>
> > > >> Thanks.
> > > >>
> > >
> > >
> >
>

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

RE: Buildbot for Cordova on Apache Infra - Update

[Parashuram Narasimhan (MS OPEN TECH)]

Awesome - Thanks Marcel. Once the master is ready, we will start setting up the 
slaves. 

-Original Message-
From: Marcel Kinard [mailto:cmarc...@gmail.com] 
Sent: Friday, December 5, 2014 1:42 PM
To: dev@cordova.apache.org
Subject: Re: Buildbot for Cordova on Apache Infra - Update

The IBM team here would be willing to set up a slave with some of our devices. 
We have a collection of Android, iOS, BB10, WP8. Looking forward to 
instructions on slave setup ;-)

On Dec 5, 2014, at 12:20 PM, Parashuram Narasimhan (MS OPEN TECH) 
 wrote:

> It would be great if we could have other platforms also run using Apache 
> Infra. Blackberry, Tizen, FirefoxOS, Amazon - any takers for this? We would 
> be happy to help. 
> 
> -Original Message-
> From: Steven Gill [mailto:stevengil...@gmail.com] 
> Sent: Wednesday, December 3, 2014 12:23 PM
> To: dev@cordova.apache.org
> Subject: Re: Buildbot for Cordova on Apache Infra - Update
> 
> This is amazing news!
> 
> Adobe will definitely setup some slaves and try to get our device wall going 
> again.
> 
> It would be great if other companies jumped on board with a few slaves for 
> their devices to get some love from medic.
> 
> Setting up a slave instructions would also be very helpful! :)
> 


-
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: Buildbot for Cordova on Apache Infra - Update

[Parashuram Narasimhan (MS OPEN TECH)]

It would be great if we could have other platforms also run using Apache Infra. 
Blackberry, Tizen, FirefoxOS, Amazon - any takers for this? We would be happy 
to help. 

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Wednesday, December 3, 2014 12:23 PM
To: dev@cordova.apache.org
Subject: Re: Buildbot for Cordova on Apache Infra - Update

This is amazing news!

Adobe will definitely setup some slaves and try to get our device wall going 
again.

It would be great if other companies jumped on board with a few slaves for 
their devices to get some love from medic.

Setting up a slave instructions would also be very helpful! :)

On Mon, Nov 17, 2014 at 3:03 PM, Parashuram Narasimhan (MS OPEN TECH) < 
panar...@microsoft.com> wrote:

> Wanted to update the mailing list on the progress for Buildbot and 
> Medic on Apache infrastructure and how to run them on the nightlies.
>
> Here is the long conversation as a ticket -
> https://issues.apache.org/jira/browse/INFRA-8588
>
> Basically, the Cordova configuration will be merged with the 
> configuration that also includes other projects. This can be setup so 
> that Medic can be run on the nightlies also. The next step would be 
> setting up slaves. We also have an option of contributing our own slaves to 
> the Apache master.
>
> Microsoft Open Tech is planning on contributing the following 
> configurations for slaves
>
>
> -  Windows 8 Build on Windows OS
>
> -  Windows 8.1 build on Windows OS
>
> -  Windows Phone 8 build on Windows OS
>
> -  Windows Phone 8.1 build on Windows OS
>
> -  Android build on Windows OS.
>
> Since there are many more platforms, can other in the community help 
> with expanding this test matrix (like adding iOS machine, adding 
> Blackberry/FxOS platforms)? P.S: We have never run medic on other 
> platforms that can be built using Windows, so we could help with those 
> too, but would need help from the community.
>
>
>

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

RE: [VOTE] Plugins Release Dec 2, 2014

[Parashuram Narasimhan (MS OPEN TECH)]

+1
Verified archives via `coho verify-archive`
*   Verified tags manually
*   Checked plugins can be added via `cordova add plugin`
*   Checked plugins loaded correctly to mobilespec app
*   Did smoke testing of mobilespec app (ran autotests)
*   Verified Release Notes.


-Original Message-
From: Ian Clelland [mailto:iclell...@google.com] 
Sent: Wednesday, December 3, 2014 7:54 AM
To: dev@cordova.apache.org
Subject: Re: [VOTE] Plugins Release Dec 2, 2014

+1

* Verified archive contents against public repos at the matching hashes
* Verified signatures of release packages
* Ran mobile spec on Android (5.0, 4.4.4) and iOS (6.0, 7.0.6 and 8.0.2)

On Tue Dec 02 2014 at 7:18:35 PM Steven Gill  wrote:

> Please review and vote on the release of this plugins release.
>
> Release issue: https://issues.apache.org/jira/browse/CB-8110
>
> The plugins have been published to
> dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-8110/
>
> The packages were published from their corresponding git tags:
> cordova-plugin-battery-status: 0.2.12 (ec59ef11a5)
> cordova-plugin-camera: 0.3.4 (2045e0a644)
> cordova-plugin-console: 0.2.12 (9e57b0d5c3)
> cordova-plugin-contacts: 0.2.15 (1347f12868)
> cordova-plugin-device: 0.2.13 (a0e4edceb1)
> cordova-plugin-device-motion: 0.2.11 (110b27671f)
> cordova-plugin-device-orientation: 0.3.10 (eef90c5659)
> cordova-plugin-dialogs: 0.2.11 (d7e34c28b7)
> cordova-plugin-file: 1.3.2 (d2c00a155b)
> cordova-plugin-file-transfer: 0.4.8 (04e114e055)
> cordova-plugin-geolocation: 0.3.11 (0db6fd9952)
> cordova-plugin-globalization: 0.3.3 (65db106599)
> cordova-plugin-inappbrowser: 0.5.4 (b9653af691)
> cordova-plugin-media: 0.2.15 (b8088cd6c8)
> cordova-plugin-media-capture: 0.3.5 (9f8d409aa0)
> cordova-plugin-network-information: 0.2.14 (17a38609fb)
> cordova-plugin-splashscreen: 0.3.5 (67e8b9f01d)
> cordova-plugin-statusbar: 0.1.9 (e445123e4c)
> cordova-plugin-vibration: 0.3.12 (57c92693fe)
>
> Upon a successful vote I will upload the archives to dist/, upload 
> them to the Plugins Registry, and post the corresponding blog post.
>
> Voting guidelines:
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting
> .md
>
> Voting will go on for a minimum of 48 hours.
>
> I vote +1:
> * Ran coho audit-license-headers over the relevant repos
> * Ran coho check-license to ensure all dependencies and 
> subdependencies have Apache-compatible licenses
> * Ran mobile spec on my android. It passed
>

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

Code coverage report for Cordova-js, cordova-cli and cordova-lib

[Parashuram Narasimhan (MS OPEN TECH)]

Hi,

As we are working on the various Medic/Build-bot items, we thought that it 
would be an interesting exercise to look at the `npm tests` that are available 
for cordova-lib, cordova-cli and cordova-js. I could not attach the full report 
(attachments are stripped off), but here is the summary. 

Does the community think that adding code coverage using Istanbul to the unit 
tests would be useful? 


|   | Statements| Branches  | Functions 
| Lines |
|-  |-- |-  
|   |-- |
| cordova-js| 73.71% (760 / 1031)   | 60.93% (287 / 471)| 69.74% (136 / 
195)| 73.78% (757 / 1026)   |
| cordova-lib   | 67.81% (3489 / 5145)  | 56.9% (1229 / 2160)   | 65.62% (586 / 
893)| 68.09% (3438 / 5049)  |
| cordova-cli   | 65.77% (98 / 149) | 54.21% (58 / 107) | 64.29% (9 / 
14)   | 66.22% (98 / 148) |

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

RE: plugins supported on cordova-browser platform?

[Parashuram Narasimhan (MS OPEN TECH)]

I think each of these plugins also have a JIRA ticket. Sergey, do you have a 
query filter that shows all the open JIRA tickets for cordova-browser plugins ? 
 

-Original Message-
From: Sergey Shakhnazarov (Akvelon) [mailto:v-ses...@microsoft.com] 
Sent: Monday, December 1, 2014 8:49 AM
To: dev@cordova.apache.org
Subject: RE: plugins supported on cordova-browser platform?

Hello Carlos,

I'm interested in Browser support as well, here is a table showing Browser 
platform compatibility to Cordova core plugins:
Plugin  Support status  Details
cordova-plugin-camera   Supported   destinationType: 
Camera.DestinationType.DATA_URL is supported (base64 encoded data is returned)
cordova-plugin-device   Supported   
cordova-plugin-device-motionSupported   Returns random 
values
cordova-plugin-device-orientation   Supported   Returns random 
values
cordova-plugin-network-information  Supported   WiFi connection 
type returned if there is any connection; `offline` and `online` Events are not 
implemented
cordova-plugin-console  Supported   W3C API is not 
completed, basic functions are supported
cordova-plugin-battery-status   Not supported   Implemented an 
adapter:  [2]
cordova-plugin-contacts Not supported   
cordova-plugin-dialogs  Not supported   Adapter to 
browser' functions can be made
cordova-plugin-file Not supported
cordova-plugin-file-transferNot supported
cordova-plugin-geolocation  Supported   Works out of 
the box as the API meets W3C Geolocation API
cordova-plugin-globalizationNot supported
cordova-plugin-inappbrowser Partially supported  
cordova-plugin-mediaNot supported
cordova-plugin-media-captureNot supported
cordova-plugin-splashscreen Not supported
cordova-plugin-statusbarNot supported
cordova-plugin-vibrationSupported   JIRA item with 
some comments: [3] 

Info on some of the plugins supported can be found in this article [4].

[2]:
https://github.com/MSOpenTech/cordova-plugin-battery-status/commits/CB-7953  

[3]:
https://issues.apache.org/jira/browse/CB-7966

[4]:
http://www.raymondcamden.com/2014/9/24/Browser-as-a-platform-for-your-PhoneGapCordova-apps
 

Please let me know if you have any questions or considerations.

Best regards,
Sergey Shakhnazarov.

-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com] 
Sent: Monday, December 1, 2014 6:03 PM
To: dev@cordova.apache.org
Subject: plugins supported on cordova-browser platform?

How do I get a glance view of what core plugins are supported on browser 
platform?

I want to see which ones are supported and which ones are left to be implement.

It will be nice if this could be a dynamic table view in plugin registry.
http://plugins.cordova.io/#/search?id=org.apache.cordova.&platforms=browser,ios,android

let me know if this is a good feature for the registry, and can open a JIRA 
feature to track for the future.

What about adding browser platform to the docs [1].
My instinct says no, 1. not a super supported platform yet, 2. don't know how 
well we keep this list up to date.
If I say yes, I would put a remark (* in experimental support) for the browser 
column.

[1]:
http://cordova.apache.org/docs/en/4.0.0/guide_support_index.md.html#Platform%20Support

let me know what you think.
B�CB��[��X��ܚX�KK[XZ[
�]�][��X��ܚX�P�ܙݘK�\X�K�ܙ�B��܈Y][ۘ[��[X[��K[XZ[
�]�Z[�ܙݘK�\X�K�ܙ�B

RE: Measuring Perf of Cordova apps (Android/iOS)

[Parashuram Narasimhan (MS OPEN TECH)]

Yes please :) 

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Tuesday, November 18, 2014 10:54 AM
To: dev@cordova.apache.org
Subject: Re: Measuring Perf of Cordova apps (Android/iOS)

Sure!

Want me to post it?

-Steve

On Mon, Nov 17, 2014 at 11:32 AM, Parashuram Narasimhan (MS OPEN TECH) < 
panar...@microsoft.com> wrote:

> Hey,
>
> Wanted to ping on this. Now that the tools release blog post is 
> published, can we publish this post too ?
>
> -Original Message-
> From: Parashuram Narasimhan (MS OPEN TECH) 
> [mailto:panar...@microsoft.com]
> Sent: Friday, November 7, 2014 2:35 PM
> To: dev@cordova.apache.org
> Subject: RE: Measuring Perf of Cordova apps (Android/iOS)
>
> Thanks for merging it. I did not want to mess up the release blog 
> posts we are doing now - hence the date, but would defer to your 
> better judgment on when to publish.
>
> -Original Message-
> From: Steven Gill [mailto:stevengil...@gmail.com]
> Sent: Friday, November 7, 2014 2:22 PM
> To: dev@cordova.apache.org
> Subject: Re: Measuring Perf of Cordova apps (Android/iOS)
>
> Looks good to me. I merged it into apache-blog-posts repo.
>
>
> https://github.com/cordova/apache-blog-posts/blob/master/2014-11-12-co
> rdova-perf.md
>
> It still needs to be published to the site. Looks like you are aiming 
> to publish it on Wednesday, November 12th (based on the date in the file 
> name).
>
> -Steve
>
> On Fri, Nov 7, 2014 at 8:18 AM, Parashuram Narasimhan (MS OPEN TECH) < 
> panar...@microsoft.com> wrote:
>
> > Thanks Josh for reviewing it. I have fixed the issues.
> >
> > On 11/7/14, 2:55 AM, "Josh Soref"  wrote:
> >
> > >‎You can benefit from a spelling (you have capitalized the second 
> > >letter of one long word) and grammar checker (there's a 
> > >parenthetical where you want "and", not "or")
> > >
> > >Otherwise, it seems pretty neat.
> > >‎
> > >Sent from my BlackBerry 10 smartphone.
> > >
> > >?B 
> > >KK
> > >KKCB
> > >? ?[  X  ܚX K??K[XZ[? ??] ][  X  ܚX P? ܙ?ݘK \?X ?K ܙ B  ܈?Y??]?[ۘ[??
> > > [X[  ? ??K[XZ[? ??] Z?[??? ܙ?ݘK \?X ?K ܙ B
> >
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>

Buildbot for Cordova on Apache Infra - Update

[Parashuram Narasimhan (MS OPEN TECH)]

Wanted to update the mailing list on the progress for Buildbot and Medic on 
Apache infrastructure and how to run them on the nightlies.

Here is the long conversation as a ticket - 
https://issues.apache.org/jira/browse/INFRA-8588

Basically, the Cordova configuration will be merged with the configuration that 
also includes other projects. This can be setup so that Medic can be run on the 
nightlies also. The next step would be setting up slaves. We also have an 
option of contributing our own slaves to the Apache master.

Microsoft Open Tech is planning on contributing the following configurations 
for slaves


-  Windows 8 Build on Windows OS

-  Windows 8.1 build on Windows OS

-  Windows Phone 8 build on Windows OS

-  Windows Phone 8.1 build on Windows OS

-  Android build on Windows OS.

Since there are many more platforms, can other in the community help with 
expanding this test matrix (like adding iOS machine, adding Blackberry/FxOS 
platforms)? P.S: We have never run medic on other platforms that can be built 
using Windows, so we could help with those too, but would need help from the 
community.

RE: Measuring Perf of Cordova apps (Android/iOS)

[Parashuram Narasimhan (MS OPEN TECH)]

Hey,

Wanted to ping on this. Now that the tools release blog post is published, can 
we publish this post too ? 

-Original Message-
From: Parashuram Narasimhan (MS OPEN TECH) [mailto:panar...@microsoft.com] 
Sent: Friday, November 7, 2014 2:35 PM
To: dev@cordova.apache.org
Subject: RE: Measuring Perf of Cordova apps (Android/iOS)

Thanks for merging it. I did not want to mess up the release blog posts we are 
doing now - hence the date, but would defer to your better judgment on when to 
publish. 

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com]
Sent: Friday, November 7, 2014 2:22 PM
To: dev@cordova.apache.org
Subject: Re: Measuring Perf of Cordova apps (Android/iOS)

Looks good to me. I merged it into apache-blog-posts repo.

https://github.com/cordova/apache-blog-posts/blob/master/2014-11-12-cordova-perf.md

It still needs to be published to the site. Looks like you are aiming to 
publish it on Wednesday, November 12th (based on the date in the file name).

-Steve

On Fri, Nov 7, 2014 at 8:18 AM, Parashuram Narasimhan (MS OPEN TECH) < 
panar...@microsoft.com> wrote:

> Thanks Josh for reviewing it. I have fixed the issues.
>
> On 11/7/14, 2:55 AM, "Josh Soref"  wrote:
>
> >‎You can benefit from a spelling (you have capitalized the second 
> >letter of one long word) and grammar checker (there's a parenthetical 
> >where you want "and", not "or")
> >
> >Otherwise, it seems pretty neat.
> >‎
> >Sent from my BlackBerry 10 smartphone.
> >
> >?B KK
> >KKCB
> >? ?[  X  ܚX K??K[XZ[? ??] ][  X  ܚX P? ܙ?ݘK \?X ?K ܙ B  ܈?Y??]?[ۘ[?? 
> > [X[  ? ??K[XZ[? ??] Z?[??? ܙ?ݘK \?X ?K ܙ B
>
>

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

RE: [VOTE] Tools Release, take 3

[Parashuram Narasimhan (MS OPEN TECH)]

Voting +1

•   Verified signatures and hashes via ‘coho verify-archive’. Pass
•   Manually verified tags. Pass
•   Installed Cordova from archives. Pass 
•   Installed/uninstalled Cordova with npm via ‘npm install cordova@rc’. 
Pass
•   Verified ability to update Cordova from older version Pass
•   Verified ability to create Cordova app with windows and wp8 platforms 
(--usenpm / --usegit flags)
•   Built app for different archs (x86, x64, arm, anycpu). Pass
•   Ran app with target keys and vers

-Original Message-
From: Josh Soref [mailto:jso...@blackberry.com] 
Sent: Thursday, November 13, 2014 7:25 AM
To: dev@cordova.apache.org
Subject: Re: [VOTE] Tools Release, take 3

Ray Camden wrote:
> To update your tools:
>
> npm install -g cordova
> npm install -g plugman
>
> To be clear, a "regular" user doesn't need to update plugman, right?

I think there is a workflow where a regular user uses `plugman` directly (I 
think it's probably one where you aren't using cordova, but instead use 
cordova-{platform}/bin/create and friends).

Otherwise, if you only use `cordova` directly, then the plugman it uses would 
be updated automatically by updating cordova, and you'd be fine.

Afaiu, there are three workflows:
1. Plugin author — uses plugman directly 2. Single-platform writer — 
potentially uses plugman directly 3. Multiplatform writer — uses cordova (and 
everything else is used
indirectly)

The instructions would probably benefit from "if you have foo installed, use X 
to update it".

B CB  [  
X  ܚX KK[XZ[
 ] ][  X  ܚX P ܙݘK \X K ܙ B  ܈Y][ۘ[  [X[  K[XZ[
 ] Z[ ܙݘK \X K ܙ B

RE: [Vote] 3.7.1 Windows Release

[Parashuram Narasimhan (MS OPEN TECH)]

Thanks a lot Steve for this. I think this looks good. 

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Tuesday, November 11, 2014 7:49 PM
To: dev@cordova.apache.org
Subject: Re: [Vote] 3.7.1 Windows Release

I made some style updates and published it.
http://cordova.apache.org/news/2014/11/11/windows-cert.html. If we need to make 
more changes, we can still do that. I will announce this on twitter now.

-Steve

On Tue, Nov 11, 2014 at 7:07 PM, Parashuram Narasimhan (MS OPEN TECH) < 
panar...@microsoft.com> wrote:

> Thanks a lot Steve for helping on this. I have updated the blog post 
> according to the comment, and checked that it works.
>
> -Original Message-
> From: Steven Gill [mailto:stevengil...@gmail.com]
> Sent: Tuesday, November 11, 2014 6:52 PM
> To: dev@cordova.apache.org
> Subject: Re: [Vote] 3.7.1 Windows Release
>
> Yup! See it now. I left some comments. I'll push the blog once it is ready!
>
> -Steve
>
> On Tue, Nov 11, 2014 at 6:46 PM, Parashuram Narasimhan (MS OPEN TECH) 
> < panar...@microsoft.com> wrote:
>
> > This one - https://github.com/cordova/apache-blog-posts/pull/21 ?
> >
> > -Original Message-
> > From: Steven Gill [mailto:stevengil...@gmail.com]
> > Sent: Tuesday, November 11, 2014 6:45 PM
> > To: dev@cordova.apache.org
> > Subject: Re: [Vote] 3.7.1 Windows Release
> >
> > Hey Parashuram,
> >
> > I don't see the PR for it
> >
> > On Tue, Nov 11, 2014 at 6:42 PM, Parashuram Narasimhan (MS OPEN 
> > TECH) < panar...@microsoft.com> wrote:
> >
> > > I could help, but I don’t have the rights to the blog repo, or a 
> > > way to publish it :(
> > >
> > > -Original Message-
> > > From: Jesse [mailto:purplecabb...@gmail.com]
> > > Sent: Tuesday, November 11, 2014 6:34 PM
> > > To: dev@cordova.apache.org
> > > Subject: Re: [Vote] 3.7.1 Windows Release
> > >
> > > I'll look into how to do that.
> > >
> > > FYI, users can also patch older cordova-windows projects with this
> > plugin:
> > >
> > > $ cordova plugin add com.risingj.patchtempcert
> > >
> > > @purplecabbage
> > > risingj.com
> > >
> > > On Tue, Nov 11, 2014 at 6:09 PM, Parashuram Narasimhan (MS OPEN
> > > TECH) < panar...@microsoft.com> wrote:
> > >
> > > > Thanks a lot Jesse and Sergey for the quick turn around. Can e 
> > > > also publish the Cordova blog post? I have sent a pull request.
> > > > 
> > > > From: Jesse<mailto:purplecabb...@gmail.com>
> > > > Sent: 11/11/2014 5:43 PM
> > > > To: dev@cordova.apache.org<mailto:dev@cordova.apache.org>
> > > > Subject: Re: [Vote] 3.7.1 Windows Release
> > > >
> > > > Done, and Done'r. Thanks for your quick work Sergey!
> > > >
> > > > https://www.npmjs.org/package/cordova-windows
> > > >
> > > > @purplecabbage
> > > > risingj.com
> > > >
> > > > On Tue, Nov 11, 2014 at 5:26 PM, Sergey Grebnov (Akvelon) < 
> > > > v-seg...@microsoft.com> wrote:
> > > >
> > > > > Jesse, could you please publish cordova-windows-3.7.1.tgz to npm?
> > > > >
> > > > > Can someone also grant me with w/ write access to
> > npm/cordova-windows?
> > > > >
> > > > > My id: sgrebnov
> > > > >
> > > > > Thx!
> > > > > Sergey
> > > > > -Original Message-
> > > > > From: Sergey Grebnov (Akvelon) [mailto:v-seg...@microsoft.com]
> > > > > Sent: Tuesday, November 11, 2014 5:18 PM
> > > > > To: dev@cordova.apache.org
> > > > > Subject: RE: [Vote] 3.7.1 Windows Release
> > > > >
> > > > > The vote has now closed. The results are:
> > > > >
> > > > > Positive Binding Votes: 3
> > > > >
> > > > > Parashuram Narasimhan
> > > > > Jesse MacFadyen
> > > > > Sergey Grebnov
> > > > > Negative Binding Votes: 0
> > > > >
> > > > > The vote has passed.
> > > > >
> > > > > -Original Message-
> > > > > From: Jesse [mailto:purplecabb...@gmail.com]
> > > > > Sent: Tuesday, November 11, 2014 5:05 PM
> > > > > To: dev@cordova.apache.org
> > > > > Subject: Re: [Vote] 3.7.1 Windows R

RE: [Vote] 3.7.1 Windows Release

[Parashuram Narasimhan (MS OPEN TECH)]

Thanks a lot Steve for helping on this. I have updated the blog post according 
to the comment, and checked that it works. 

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Tuesday, November 11, 2014 6:52 PM
To: dev@cordova.apache.org
Subject: Re: [Vote] 3.7.1 Windows Release

Yup! See it now. I left some comments. I'll push the blog once it is ready!

-Steve

On Tue, Nov 11, 2014 at 6:46 PM, Parashuram Narasimhan (MS OPEN TECH) < 
panar...@microsoft.com> wrote:

> This one - https://github.com/cordova/apache-blog-posts/pull/21 ?
>
> -Original Message-
> From: Steven Gill [mailto:stevengil...@gmail.com]
> Sent: Tuesday, November 11, 2014 6:45 PM
> To: dev@cordova.apache.org
> Subject: Re: [Vote] 3.7.1 Windows Release
>
> Hey Parashuram,
>
> I don't see the PR for it
>
> On Tue, Nov 11, 2014 at 6:42 PM, Parashuram Narasimhan (MS OPEN TECH) 
> < panar...@microsoft.com> wrote:
>
> > I could help, but I don’t have the rights to the blog repo, or a way 
> > to publish it :(
> >
> > -Original Message-
> > From: Jesse [mailto:purplecabb...@gmail.com]
> > Sent: Tuesday, November 11, 2014 6:34 PM
> > To: dev@cordova.apache.org
> > Subject: Re: [Vote] 3.7.1 Windows Release
> >
> > I'll look into how to do that.
> >
> > FYI, users can also patch older cordova-windows projects with this
> plugin:
> >
> > $ cordova plugin add com.risingj.patchtempcert
> >
> > @purplecabbage
> > risingj.com
> >
> > On Tue, Nov 11, 2014 at 6:09 PM, Parashuram Narasimhan (MS OPEN 
> > TECH) < panar...@microsoft.com> wrote:
> >
> > > Thanks a lot Jesse and Sergey for the quick turn around. Can e 
> > > also publish the Cordova blog post? I have sent a pull request.
> > > 
> > > From: Jesse<mailto:purplecabb...@gmail.com>
> > > Sent: 11/11/2014 5:43 PM
> > > To: dev@cordova.apache.org<mailto:dev@cordova.apache.org>
> > > Subject: Re: [Vote] 3.7.1 Windows Release
> > >
> > > Done, and Done'r. Thanks for your quick work Sergey!
> > >
> > > https://www.npmjs.org/package/cordova-windows
> > >
> > > @purplecabbage
> > > risingj.com
> > >
> > > On Tue, Nov 11, 2014 at 5:26 PM, Sergey Grebnov (Akvelon) < 
> > > v-seg...@microsoft.com> wrote:
> > >
> > > > Jesse, could you please publish cordova-windows-3.7.1.tgz to npm?
> > > >
> > > > Can someone also grant me with w/ write access to
> npm/cordova-windows?
> > > >
> > > > My id: sgrebnov
> > > >
> > > > Thx!
> > > > Sergey
> > > > -Original Message-
> > > > From: Sergey Grebnov (Akvelon) [mailto:v-seg...@microsoft.com]
> > > > Sent: Tuesday, November 11, 2014 5:18 PM
> > > > To: dev@cordova.apache.org
> > > > Subject: RE: [Vote] 3.7.1 Windows Release
> > > >
> > > > The vote has now closed. The results are:
> > > >
> > > > Positive Binding Votes: 3
> > > >
> > > > Parashuram Narasimhan
> > > > Jesse MacFadyen
> > > > Sergey Grebnov
> > > > Negative Binding Votes: 0
> > > >
> > > > The vote has passed.
> > > >
> > > > -Original Message-
> > > > From: Jesse [mailto:purplecabb...@gmail.com]
> > > > Sent: Tuesday, November 11, 2014 5:05 PM
> > > > To: dev@cordova.apache.org
> > > > Subject: Re: [Vote] 3.7.1 Windows Release
> > > >
> > > > I vote +1:
> > > > * Ran coho verify-archive
> > > > * created and ran a project
> > > >
> > > > @purplecabbage
> > > > risingj.com
> > > >
> > > > On Tue, Nov 11, 2014 at 4:52 PM, Jesse 
> > wrote:
> > > >
> > > > > okay, I went through the whole process just now too.
> > > > > I see your key is published to cordova-dist, the rest is 
> > > > > optional
> ...
> > > > > so don't let it hold you back
> > > > >
> > > > >
> > > > > @purplecabbage
> > > > > risingj.com
> > > > >
> > > > > On Tue, Nov 11, 2014 at 4:43 PM, Sergey Grebnov (Akvelon) < 
> > > > > v-seg...@microsoft.com> wrote:
> > > > >
> > > > >> Working on this, stuck on the following command, trying to 
> > > > >>

RE: [Vote] 3.7.1 Windows Release

[Parashuram Narasimhan (MS OPEN TECH)]

This one - https://github.com/cordova/apache-blog-posts/pull/21 ? 

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Tuesday, November 11, 2014 6:45 PM
To: dev@cordova.apache.org
Subject: Re: [Vote] 3.7.1 Windows Release

Hey Parashuram,

I don't see the PR for it

On Tue, Nov 11, 2014 at 6:42 PM, Parashuram Narasimhan (MS OPEN TECH) < 
panar...@microsoft.com> wrote:

> I could help, but I don’t have the rights to the blog repo, or a way 
> to publish it :(
>
> -Original Message-
> From: Jesse [mailto:purplecabb...@gmail.com]
> Sent: Tuesday, November 11, 2014 6:34 PM
> To: dev@cordova.apache.org
> Subject: Re: [Vote] 3.7.1 Windows Release
>
> I'll look into how to do that.
>
> FYI, users can also patch older cordova-windows projects with this plugin:
>
> $ cordova plugin add com.risingj.patchtempcert
>
> @purplecabbage
> risingj.com
>
> On Tue, Nov 11, 2014 at 6:09 PM, Parashuram Narasimhan (MS OPEN TECH) 
> < panar...@microsoft.com> wrote:
>
> > Thanks a lot Jesse and Sergey for the quick turn around. Can e also 
> > publish the Cordova blog post? I have sent a pull request.
> > 
> > From: Jesse<mailto:purplecabb...@gmail.com>
> > Sent: 11/11/2014 5:43 PM
> > To: dev@cordova.apache.org<mailto:dev@cordova.apache.org>
> > Subject: Re: [Vote] 3.7.1 Windows Release
> >
> > Done, and Done'r. Thanks for your quick work Sergey!
> >
> > https://www.npmjs.org/package/cordova-windows
> >
> > @purplecabbage
> > risingj.com
> >
> > On Tue, Nov 11, 2014 at 5:26 PM, Sergey Grebnov (Akvelon) < 
> > v-seg...@microsoft.com> wrote:
> >
> > > Jesse, could you please publish cordova-windows-3.7.1.tgz to npm?
> > >
> > > Can someone also grant me with w/ write access to  npm/cordova-windows?
> > >
> > > My id: sgrebnov
> > >
> > > Thx!
> > > Sergey
> > > -Original Message-
> > > From: Sergey Grebnov (Akvelon) [mailto:v-seg...@microsoft.com]
> > > Sent: Tuesday, November 11, 2014 5:18 PM
> > > To: dev@cordova.apache.org
> > > Subject: RE: [Vote] 3.7.1 Windows Release
> > >
> > > The vote has now closed. The results are:
> > >
> > > Positive Binding Votes: 3
> > >
> > > Parashuram Narasimhan
> > > Jesse MacFadyen
> > > Sergey Grebnov
> > > Negative Binding Votes: 0
> > >
> > > The vote has passed.
> > >
> > > -Original Message-
> > > From: Jesse [mailto:purplecabb...@gmail.com]
> > > Sent: Tuesday, November 11, 2014 5:05 PM
> > > To: dev@cordova.apache.org
> > > Subject: Re: [Vote] 3.7.1 Windows Release
> > >
> > > I vote +1:
> > > * Ran coho verify-archive
> > > * created and ran a project
> > >
> > > @purplecabbage
> > > risingj.com
> > >
> > > On Tue, Nov 11, 2014 at 4:52 PM, Jesse 
> wrote:
> > >
> > > > okay, I went through the whole process just now too.
> > > > I see your key is published to cordova-dist, the rest is optional ...
> > > > so don't let it hold you back
> > > >
> > > >
> > > > @purplecabbage
> > > > risingj.com
> > > >
> > > > On Tue, Nov 11, 2014 at 4:43 PM, Sergey Grebnov (Akvelon) < 
> > > > v-seg...@microsoft.com> wrote:
> > > >
> > > >> Working on this, stuck on the following command, trying to 
> > > >> figure out what is wrong
> > > >>
> > > >> λ gpg --keyserver keys.gnupg.net --send-keys E954EC3C
> > > >> gpg: sending key E954EC3C to hkp server keys.gnupg.net
> > > >> gpg: system error while calling external program: No error
> > > >> gpg: WARNING: unable to remove tempfile (out)
> > > >> `C:\Users\Sergei\AppData\Local\Temp\gpg-B55F2B\tempout.txt': No 
> > > >> such file or directory
> > > >> gpg: no handler for keyserver scheme `hkp'
> > > >> gpg: keyserver send failed: keyserver error
> > > >>
> > > >> Thx!
> > > >> Sergey
> > > >> -Original Message-
> > > >> From: Jesse [mailto:purplecabb...@gmail.com]
> > > >> Sent: Tuesday, November 11, 2014 3:46 PM
> > > >> To: dev@cordova.apache.org
> > > >> Subject: Re: [Vote] 3.7.1 Windows Release
> > > >>
> > > >> Sergey, you

RE: [Vote] 3.7.1 Windows Release

[Parashuram Narasimhan (MS OPEN TECH)]

I could help, but I don’t have the rights to the blog repo, or a way to publish 
it :( 

-Original Message-
From: Jesse [mailto:purplecabb...@gmail.com] 
Sent: Tuesday, November 11, 2014 6:34 PM
To: dev@cordova.apache.org
Subject: Re: [Vote] 3.7.1 Windows Release

I'll look into how to do that.

FYI, users can also patch older cordova-windows projects with this plugin:

$ cordova plugin add com.risingj.patchtempcert

@purplecabbage
risingj.com

On Tue, Nov 11, 2014 at 6:09 PM, Parashuram Narasimhan (MS OPEN TECH) < 
panar...@microsoft.com> wrote:

> Thanks a lot Jesse and Sergey for the quick turn around. Can e also 
> publish the Cordova blog post? I have sent a pull request.
> 
> From: Jesse<mailto:purplecabb...@gmail.com>
> Sent: ‎11/‎11/‎2014 5:43 PM
> To: dev@cordova.apache.org<mailto:dev@cordova.apache.org>
> Subject: Re: [Vote] 3.7.1 Windows Release
>
> Done, and Done'r. Thanks for your quick work Sergey!
>
> https://www.npmjs.org/package/cordova-windows
>
> @purplecabbage
> risingj.com
>
> On Tue, Nov 11, 2014 at 5:26 PM, Sergey Grebnov (Akvelon) < 
> v-seg...@microsoft.com> wrote:
>
> > Jesse, could you please publish cordova-windows-3.7.1.tgz to npm?
> >
> > Can someone also grant me with w/ write access to  npm/cordova-windows?
> >
> > My id: sgrebnov
> >
> > Thx!
> > Sergey
> > -Original Message-
> > From: Sergey Grebnov (Akvelon) [mailto:v-seg...@microsoft.com]
> > Sent: Tuesday, November 11, 2014 5:18 PM
> > To: dev@cordova.apache.org
> > Subject: RE: [Vote] 3.7.1 Windows Release
> >
> > The vote has now closed. The results are:
> >
> > Positive Binding Votes: 3
> >
> > Parashuram Narasimhan
> > Jesse MacFadyen
> > Sergey Grebnov
> > Negative Binding Votes: 0
> >
> > The vote has passed.
> >
> > -Original Message-
> > From: Jesse [mailto:purplecabb...@gmail.com]
> > Sent: Tuesday, November 11, 2014 5:05 PM
> > To: dev@cordova.apache.org
> > Subject: Re: [Vote] 3.7.1 Windows Release
> >
> > I vote +1:
> > * Ran coho verify-archive
> > * created and ran a project
> >
> > @purplecabbage
> > risingj.com
> >
> > On Tue, Nov 11, 2014 at 4:52 PM, Jesse  wrote:
> >
> > > okay, I went through the whole process just now too.
> > > I see your key is published to cordova-dist, the rest is optional ...
> > > so don't let it hold you back
> > >
> > >
> > > @purplecabbage
> > > risingj.com
> > >
> > > On Tue, Nov 11, 2014 at 4:43 PM, Sergey Grebnov (Akvelon) < 
> > > v-seg...@microsoft.com> wrote:
> > >
> > >> Working on this, stuck on the following command, trying to figure 
> > >> out what is wrong
> > >>
> > >> λ gpg --keyserver keys.gnupg.net --send-keys E954EC3C
> > >> gpg: sending key E954EC3C to hkp server keys.gnupg.net
> > >> gpg: system error while calling external program: No error
> > >> gpg: WARNING: unable to remove tempfile (out)
> > >> `C:\Users\Sergei\AppData\Local\Temp\gpg-B55F2B\tempout.txt': No 
> > >> such file or directory
> > >> gpg: no handler for keyserver scheme `hkp'
> > >> gpg: keyserver send failed: keyserver error
> > >>
> > >> Thx!
> > >> Sergey
> > >> -Original Message-
> > >> From: Jesse [mailto:purplecabb...@gmail.com]
> > >> Sent: Tuesday, November 11, 2014 3:46 PM
> > >> To: dev@cordova.apache.org
> > >> Subject: Re: [Vote] 3.7.1 Windows Release
> > >>
> > >> Sergey, you need to publish your keys. We cannot verify-archive
> > otherwise.
> > >> Instructions here:
> > >> https://github.com/apache/cordova-coho/blob/master/docs/setting-u
> > >> p-gp
> > >> g.md
> > >>
> > >> And yes, this should be a 72 minute voting window
> > >>
> > >>
> > >>
> > >> @purplecabbage
> > >> risingj.com
> > >>
> > >> On Tue, Nov 11, 2014 at 2:51 PM, Parashuram Narasimhan (MS OPEN 
> > >> TECH) < panar...@microsoft.com> wrote:
> > >>
> > >> > +1. Checked the certificate issue works fine. Since this is a 
> > >> > +critical
> > >> > release, I would suggest that we don't want for the 48 hours. 
> > >> > Note that the 48hours in only recommended and can be relaxed if 
> > >> > t

RE: [Vote] 3.7.1 Windows Release

[Parashuram Narasimhan (MS OPEN TECH)]

Thanks a lot Jesse and Sergey for the quick turn around. Can e also publish the 
Cordova blog post? I have sent a pull request.

From: Jesse<mailto:purplecabb...@gmail.com>
Sent: ‎11/‎11/‎2014 5:43 PM
To: dev@cordova.apache.org<mailto:dev@cordova.apache.org>
Subject: Re: [Vote] 3.7.1 Windows Release

Done, and Done'r. Thanks for your quick work Sergey!

https://www.npmjs.org/package/cordova-windows

@purplecabbage
risingj.com

On Tue, Nov 11, 2014 at 5:26 PM, Sergey Grebnov (Akvelon) <
v-seg...@microsoft.com> wrote:

> Jesse, could you please publish cordova-windows-3.7.1.tgz to npm?
>
> Can someone also grant me with w/ write access to  npm/cordova-windows?
>
> My id: sgrebnov
>
> Thx!
> Sergey
> -Original Message-
> From: Sergey Grebnov (Akvelon) [mailto:v-seg...@microsoft.com]
> Sent: Tuesday, November 11, 2014 5:18 PM
> To: dev@cordova.apache.org
> Subject: RE: [Vote] 3.7.1 Windows Release
>
> The vote has now closed. The results are:
>
> Positive Binding Votes: 3
>
> Parashuram Narasimhan
> Jesse MacFadyen
> Sergey Grebnov
> Negative Binding Votes: 0
>
> The vote has passed.
>
> -Original Message-
> From: Jesse [mailto:purplecabb...@gmail.com]
> Sent: Tuesday, November 11, 2014 5:05 PM
> To: dev@cordova.apache.org
> Subject: Re: [Vote] 3.7.1 Windows Release
>
> I vote +1:
> * Ran coho verify-archive
> * created and ran a project
>
> @purplecabbage
> risingj.com
>
> On Tue, Nov 11, 2014 at 4:52 PM, Jesse  wrote:
>
> > okay, I went through the whole process just now too.
> > I see your key is published to cordova-dist, the rest is optional ...
> > so don't let it hold you back
> >
> >
> > @purplecabbage
> > risingj.com
> >
> > On Tue, Nov 11, 2014 at 4:43 PM, Sergey Grebnov (Akvelon) <
> > v-seg...@microsoft.com> wrote:
> >
> >> Working on this, stuck on the following command, trying to figure out
> >> what is wrong
> >>
> >> λ gpg --keyserver keys.gnupg.net --send-keys E954EC3C
> >> gpg: sending key E954EC3C to hkp server keys.gnupg.net
> >> gpg: system error while calling external program: No error
> >> gpg: WARNING: unable to remove tempfile (out)
> >> `C:\Users\Sergei\AppData\Local\Temp\gpg-B55F2B\tempout.txt': No such
> >> file or directory
> >> gpg: no handler for keyserver scheme `hkp'
> >> gpg: keyserver send failed: keyserver error
> >>
> >> Thx!
> >> Sergey
> >> -Original Message-
> >> From: Jesse [mailto:purplecabb...@gmail.com]
> >> Sent: Tuesday, November 11, 2014 3:46 PM
> >> To: dev@cordova.apache.org
> >> Subject: Re: [Vote] 3.7.1 Windows Release
> >>
> >> Sergey, you need to publish your keys. We cannot verify-archive
> otherwise.
> >> Instructions here:
> >> https://github.com/apache/cordova-coho/blob/master/docs/setting-up-gp
> >> g.md
> >>
> >> And yes, this should be a 72 minute voting window
> >>
> >>
> >>
> >> @purplecabbage
> >> risingj.com
> >>
> >> On Tue, Nov 11, 2014 at 2:51 PM, Parashuram Narasimhan (MS OPEN TECH)
> >> < panar...@microsoft.com> wrote:
> >>
> >> > +1. Checked the certificate issue works fine. Since this is a
> >> > +critical
> >> > release, I would suggest that we don't want for the 48 hours. Note
> >> > that the 48hours in only recommended and can be relaxed if the
> >> > community feels that a release needs to happen sooner.
> >> >
> >> > -Original Message-
> >> > From: Sergey Grebnov (Akvelon) [mailto:v-seg...@microsoft.com]
> >> > Sent: Tuesday, November 11, 2014 2:48 PM
> >> > To: dev@cordova.apache.org
> >> > Subject: [Vote] 3.7.1 Windows Release
> >> >
> >> > Please review and vote on this 3.7.1 Windows Release.
> >> >
> >> > Release issue: https://issues.apache.org/jira/browse/CB-8004
> >> >
> >> > Repos ready to be released have been published to dist/dev:
> >> > https://dist.apache.org/repos/dist/dev/cordova/CB-8004
> >> >
> >> > The package was published from its corresponding git tag:
> >> > 3.7.1 (d62def2432)
> >> >
> >> > Upon a successful vote I will upload the archive to dist/, publish
> >> > it to NPM, and post the corresponding blog post.
> >> >
> >> > Voting guidelines:
> >> > https://github.com/apache/cordova-coho/blob/master/docs/release-vot
> >> > ing
> >> > .md
> >> >
> >> > I vote +1:
> >> > * Ran coho verify-archive
> >> > * Performed platform functional testing
> >> >
> >> > Thx!
> >> > Sergey
> >> >
> >> >
> >> > ---
> >> > -- 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: [Vote] 3.7.1 Windows Release

[Parashuram Narasimhan (MS OPEN TECH)]

+1. Checked the certificate issue works fine. Since this is a critical release, 
I would suggest that we don't want for the 48 hours. Note that the 48hours in 
only recommended and can be relaxed if the community feels that a release needs 
to happen sooner. 

-Original Message-
From: Sergey Grebnov (Akvelon) [mailto:v-seg...@microsoft.com] 
Sent: Tuesday, November 11, 2014 2:48 PM
To: dev@cordova.apache.org
Subject: [Vote] 3.7.1 Windows Release

Please review and vote on this 3.7.1 Windows Release.

Release issue: https://issues.apache.org/jira/browse/CB-8004

Repos ready to be released have been published to dist/dev:
https://dist.apache.org/repos/dist/dev/cordova/CB-8004

The package was published from its corresponding git tag:
3.7.1 (d62def2432)

Upon a successful vote I will upload the archive to dist/, publish it to NPM, 
and post the corresponding blog post.

Voting guidelines: 
https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md

I vote +1:
* Ran coho verify-archive
* Performed platform functional testing

Thx!
Sergey


-
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: [Urgent] Windows platform build issue due to expired certificate

[Parashuram Narasimhan (MS OPEN TECH)]

Thanks Jesse. 
Here is a draft of the blog post that could go out to ensure that users do not 
have this issue - 
https://github.com/MSOpenTech/apache-blog-posts/blob/master/2014-11-11-windows-cert.md
 

So, should we start an official vote, and publish this to npm?  

-Original Message-
From: Jesse [mailto:purplecabb...@gmail.com] 
Sent: Tuesday, November 11, 2014 1:54 PM
To: dev@cordova.apache.org
Subject: Re: [Urgent] Windows platform build issue due to expired certificate

Done:
https://git-wip-us.apache.org/repos/asf?p=cordova-windows.git;a=commit;h=d62def2432680e81c98225e25f4abeeba6939df2

@purplecabbage
risingj.com

On Tue, Nov 11, 2014 at 1:36 PM, Sergey Grebnov (Akvelon) < 
v-seg...@microsoft.com> wrote:

> Jesse, please commit the updated certificate and tag the branch, I'll 
> be able to assist with the release process.
>
> -Sergey
> -Original Message-
> From: Jesse [mailto:purplecabb...@gmail.com]
> Sent: Tuesday, November 11, 2014 1:32 PM
> To: dev@cordova.apache.org
> Subject: Re: [Urgent] Windows platform build issue due to expired 
> certificate
>
> Okay, I don't see his commit though.
> https://git-wip-us.apache.org/repos/asf?p=cordova-windows.git;a=summar
> y https://github.com/apache/cordova-windows/tree/master/template
>
> Should I commit my updated .pfx file?
>
> @purplecabbage
> risingj.com
>
> On Tue, Nov 11, 2014 at 1:20 PM, Parashuram Narasimhan (MS OPEN TECH) 
> < panar...@microsoft.com> wrote:
>
> > Sergey is working on tagging and getting a release candidate out.
> >
> > -Original Message-
> > From: Jesse [mailto:purplecabb...@gmail.com]
> > Sent: Tuesday, November 11, 2014 1:19 PM
> > To: dev@cordova.apache.org
> > Subject: Re: [Urgent] Windows platform build issue due to expired 
> > certificate
> >
> > 1. yes, lets aim for a vote + release asap 2. yes
> >
> > Mark, this applies to 'windows' only, wp8@3.7.1 is still okay
> >
> > @purplecabbage
> > risingj.com
> >
> > On Tue, Nov 11, 2014 at 1:10 PM, Mark Koudritsky 
> > wrote:
> >
> > > If this will be windows and wp 3.7.1, I'll update the tools 
> > > release candidates tomorrow.
> > >
> > > On Tue, Nov 11, 2014 at 3:48 PM, Parashuram Narasimhan (MS OPEN
> > > TECH) < panar...@microsoft.com> wrote:
> > >
> > > > As a result of this certificate expiry, Cordova-windows for all 
> > > > users is currently broken. Cordova windows that were building 
> > > > fine yesterday are broken now. I am hoping to get this fixed as 
> > > > soon as possible, and can I suggest the following
> > > >
> > > > 1. Make a quick Windows Platform release. We don't have to wait 
> > > > for the usual voting time since this is a critical fix. I am 
> > > > hoping we can get
> > > this
> > > > in today
> > > > 2. A blog post on the Apache Cordova blog detailing how existing 
> > > > users
> > > can
> > > > update to the new version (using --usegit).
> > > >
> > > > The pull request for this has been merged - 
> > > > https://github.com/apache/cordova-windows/pull/12. We will start 
> > > > tagging so that we can start a vote on this.
> > > >
> > > >
> > > >
> > > > -Original Message-
> > > > From: Parashuram Narasimhan (MS OPEN TECH) [mailto:
> > > panar...@microsoft.com]
> > > > Sent: Tuesday, November 11, 2014 11:26 AM
> > > > To: dev@cordova.apache.org
> > > > Subject: RE: Windows platform build issue due to expired 
> > > > certificate
> > > >
> > > > This breaks all Cordova for Windows platforms. I think we should 
> > > > fix this and do a Windows platform release immediately. Given 
> > > > that tools is also
> > > not
> > > > out yet, can we make this into the tools release too?
> > > > Also, how does this impact older Cordova CLI versions ? We may 
> > > > need a fix for them too, right ?
> > > >
> > > > -Original Message-
> > > > From: Sergey Grebnov (Akvelon) [mailto:v-seg...@microsoft.com]
> > > > Sent: Tuesday, November 11, 2014 10:57 AM
> > > > To: dev@cordova.apache.org
> > > > Subject: Windows platform build issue due to expired certificate
> > > >
> > > > Confirm this issue, looks very critical.
> > > >
> > > > Thx!
> > > > Sergey
> > > > -Original Message

RE: [Urgent] Windows platform build issue due to expired certificate

[Parashuram Narasimhan (MS OPEN TECH)]

Sergey is working on tagging and getting a release candidate out. 

-Original Message-
From: Jesse [mailto:purplecabb...@gmail.com] 
Sent: Tuesday, November 11, 2014 1:19 PM
To: dev@cordova.apache.org
Subject: Re: [Urgent] Windows platform build issue due to expired certificate

1. yes, lets aim for a vote + release asap 2. yes

Mark, this applies to 'windows' only, wp8@3.7.1 is still okay

@purplecabbage
risingj.com

On Tue, Nov 11, 2014 at 1:10 PM, Mark Koudritsky  wrote:

> If this will be windows and wp 3.7.1, I'll update the tools release 
> candidates tomorrow.
>
> On Tue, Nov 11, 2014 at 3:48 PM, Parashuram Narasimhan (MS OPEN TECH) 
> < panar...@microsoft.com> wrote:
>
> > As a result of this certificate expiry, Cordova-windows for all 
> > users is currently broken. Cordova windows that were building fine 
> > yesterday are broken now. I am hoping to get this fixed as soon as 
> > possible, and can I suggest the following
> >
> > 1. Make a quick Windows Platform release. We don't have to wait for 
> > the usual voting time since this is a critical fix. I am hoping we 
> > can get
> this
> > in today
> > 2. A blog post on the Apache Cordova blog detailing how existing 
> > users
> can
> > update to the new version (using --usegit).
> >
> > The pull request for this has been merged - 
> > https://github.com/apache/cordova-windows/pull/12. We will start 
> > tagging so that we can start a vote on this.
> >
> >
> >
> > -Original Message-
> > From: Parashuram Narasimhan (MS OPEN TECH) [mailto:
> panar...@microsoft.com]
> > Sent: Tuesday, November 11, 2014 11:26 AM
> > To: dev@cordova.apache.org
> > Subject: RE: Windows platform build issue due to expired certificate
> >
> > This breaks all Cordova for Windows platforms. I think we should fix 
> > this and do a Windows platform release immediately. Given that tools 
> > is also
> not
> > out yet, can we make this into the tools release too?
> > Also, how does this impact older Cordova CLI versions ? We may need 
> > a fix for them too, right ?
> >
> > -Original Message-
> > From: Sergey Grebnov (Akvelon) [mailto:v-seg...@microsoft.com]
> > Sent: Tuesday, November 11, 2014 10:57 AM
> > To: dev@cordova.apache.org
> > Subject: Windows platform build issue due to expired certificate
> >
> > Confirm this issue, looks very critical.
> >
> > Thx!
> > Sergey
> > -Original Message-
> > From: dougestey [mailto:g...@git.apache.org]
> > Sent: Tuesday, November 11, 2014 10:22 AM
> > To: dev@cordova.apache.org
> > Subject: [GitHub] cordova-windows pull request: CB-5323 Windows8 
> > build fails due to ...
> >
> > Github user dougestey commented on the pull request:
> >
> >
> > https://github.com/apache/cordova-windows/pull/12#issuecomment-62592
> > 066
> >
> > So it's 11.11.2014, and this just happened to me again.
> >
> >
> > ---
> > If your project is set up for it, you can reply to this email and 
> > have your reply appear on GitHub as well. If your project does not 
> > have this feature enabled and wishes so, or if the feature is 
> > enabled but not working, please contact infrastructure at 
> > infrastruct...@apache.org or file a JIRA ticket with INFRA.
> > ---
> >
> > 
> > - 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: [Urgent] Windows platform build issue due to expired certificate

[Parashuram Narasimhan (MS OPEN TECH)]

As a result of this certificate expiry, Cordova-windows for all users is 
currently broken. Cordova windows that were building fine yesterday are broken 
now. I am hoping to get this fixed as soon as possible, and can I suggest the 
following

1. Make a quick Windows Platform release. We don't have to wait for the usual 
voting time since this is a critical fix. I am hoping we can get this in today 
2. A blog post on the Apache Cordova blog detailing how existing users can 
update to the new version (using --usegit). 

The pull request for this has been merged - 
https://github.com/apache/cordova-windows/pull/12. We will start tagging so 
that we can start a vote on this. 



-Original Message-
From: Parashuram Narasimhan (MS OPEN TECH) [mailto:panar...@microsoft.com] 
Sent: Tuesday, November 11, 2014 11:26 AM
To: dev@cordova.apache.org
Subject: RE: Windows platform build issue due to expired certificate

This breaks all Cordova for Windows platforms. I think we should fix this and 
do a Windows platform release immediately. Given that tools is also not out 
yet, can we make this into the tools release too? 
Also, how does this impact older Cordova CLI versions ? We may need a fix for 
them too, right ? 

-Original Message-
From: Sergey Grebnov (Akvelon) [mailto:v-seg...@microsoft.com] 
Sent: Tuesday, November 11, 2014 10:57 AM
To: dev@cordova.apache.org
Subject: Windows platform build issue due to expired certificate

Confirm this issue, looks very critical. 

Thx!
Sergey
-Original Message-
From: dougestey [mailto:g...@git.apache.org] 
Sent: Tuesday, November 11, 2014 10:22 AM
To: dev@cordova.apache.org
Subject: [GitHub] cordova-windows pull request: CB-5323 Windows8 build fails 
due to ...

Github user dougestey commented on the pull request:

https://github.com/apache/cordova-windows/pull/12#issuecomment-62592066
  
So it's 11.11.2014, and this just happened to me again.


---
If your project is set up for it, you can reply to this email and have your 
reply appear on GitHub as well. If your project does not have this feature 
enabled and wishes so, or if the feature is enabled but not working, please 
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with 
INFRA.
---

-
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: Windows platform build issue due to expired certificate

[Parashuram Narasimhan (MS OPEN TECH)]

This breaks all Cordova for Windows platforms. I think we should fix this and 
do a Windows platform release immediately. Given that tools is also not out 
yet, can we make this into the tools release too? 
Also, how does this impact older Cordova CLI versions ? We may need a fix for 
them too, right ? 

-Original Message-
From: Sergey Grebnov (Akvelon) [mailto:v-seg...@microsoft.com] 
Sent: Tuesday, November 11, 2014 10:57 AM
To: dev@cordova.apache.org
Subject: Windows platform build issue due to expired certificate

Confirm this issue, looks very critical. 

Thx!
Sergey
-Original Message-
From: dougestey [mailto:g...@git.apache.org] 
Sent: Tuesday, November 11, 2014 10:22 AM
To: dev@cordova.apache.org
Subject: [GitHub] cordova-windows pull request: CB-5323 Windows8 build fails 
due to ...

Github user dougestey commented on the pull request:

https://github.com/apache/cordova-windows/pull/12#issuecomment-62592066
  
So it's 11.11.2014, and this just happened to me again.


---
If your project is set up for it, you can reply to this email and have your 
reply appear on GitHub as well. If your project does not have this feature 
enabled and wishes so, or if the feature is enabled but not working, please 
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with 
INFRA.
---

-
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: Measuring Perf of Cordova apps (Android/iOS)

[Parashuram Narasimhan (MS OPEN TECH)]

Thanks for merging it. I did not want to mess up the release blog posts we are 
doing now - hence the date, but would defer to your better judgment on when to 
publish. 

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Friday, November 7, 2014 2:22 PM
To: dev@cordova.apache.org
Subject: Re: Measuring Perf of Cordova apps (Android/iOS)

Looks good to me. I merged it into apache-blog-posts repo.

https://github.com/cordova/apache-blog-posts/blob/master/2014-11-12-cordova-perf.md

It still needs to be published to the site. Looks like you are aiming to 
publish it on Wednesday, November 12th (based on the date in the file name).

-Steve

On Fri, Nov 7, 2014 at 8:18 AM, Parashuram Narasimhan (MS OPEN TECH) < 
panar...@microsoft.com> wrote:

> Thanks Josh for reviewing it. I have fixed the issues.
>
> On 11/7/14, 2:55 AM, "Josh Soref"  wrote:
>
> >‎You can benefit from a spelling (you have capitalized the second 
> >letter of one long word) and grammar checker (there's a parenthetical 
> >where you want "and", not "or")
> >
> >Otherwise, it seems pretty neat.
> >‎
> >Sent from my BlackBerry 10 smartphone.
> >
> >?B KK
> >KKCB  
> >? ?[  X  ܚX K??K[XZ[? ??] ][  X  ܚX P? ܙ?ݘK \?X ?K ܙ B  ܈?Y??]?[ۘ[?? 
> > [X[  ? ??K[XZ[? ??] Z?[??? ܙ?ݘK \?X ?K ܙ B
>
>

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

Re: Measuring Perf of Cordova apps (Android/iOS)

[Parashuram Narasimhan (MS OPEN TECH)]

Thanks Josh for reviewing it. I have fixed the issues.

On 11/7/14, 2:55 AM, "Josh Soref"  wrote:

>‎You can benefit from a spelling (you have capitalized the second letter
>of one long word) and grammar checker (there's a parenthetical where you
>want "and", not "or")
>
>Otherwise, it seems pretty neat.
>‎
>Sent from my BlackBerry 10 smartphone.
>
>?B�CB�
>?�?[��X��ܚX�K??K[XZ[?�??]�][��X��ܚX�P?�ܙ?ݘK�\?X�?K�ܙ�B��܈?Y??]?[ۘ[??��[X[�
>?�??K[XZ[?�??]�Z?[???�ܙ?ݘK�\?X�?K�ܙ�B

RE: Running browser platform in Linux

[Parashuram Narasimhan (MS OPEN TECH)]

Sorry for not being clear. I was saying that we should not open the file:// URL 
in a specific browser. We should ideally spin up a webserver and open the 
default browser on the system

Why a server ? Because 
- file:// and http:// have differences in quota and permissions for many APIs 
like IndexedDB or WebSQL
- Cordova apps on mobile can make cross-domain AJAX requests. You cannot do 
that in the browser due to same-origin restriction. However, CORS can help, but 
is restricted due to file://
- Cookies and protocol relative paths may get messed up. 

Why default browser? Default browser would just mean opening the HTML file. 
- I may not have Chrome installed
- Chrome may not be installed at that location
- Issues like Linux that you described. 
- Integration of cordova-browsers in IDEs and Ripple-as-a-platform may be hard. 
 


-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Thursday, November 6, 2014 1:55 PM
To: dev@cordova.apache.org
Subject: Re: Running browser platform in Linux

Victor, feel free to send a PR so is uses config.xml content src instead of 
www/index.html.

Also send the PR for your patches to run script.


On Thu, Nov 6, 2014 at 1:17 PM, Victor Sosa  wrote:

> Not sure I'm following you, Parashuram, can you explain a little more, 
> please?
>
> One more I noticed is that in the run script of the browser platform, 
> it is directly pointing to "www/*index.html*", why is index.html 
> hardcoded there instead of reading config.xml?
>
> I patched my run script to use this google-chrome command and I'm 
> happy to share it. Also will try to patch the index.html reference in 
> the script to open the browser.
>
> 2014-11-06 14:50 GMT-06:00 Parashuram Narasimhan (MS OPEN TECH) <
> panar...@microsoft.com>:
>
> > I don't this we should launch Chrome this way. How about using 
> > something like browser-launcher, or even karma-chrome-launcher 
> > instead? Also, why
> not
> > just "open" the HTML page?
>

Chrome needs to be launched with flags for some of the plugins to work (camera 
I believe). That is why you can't just open it.


> >
> > -Original Message-
> > From: Victor Sosa [mailto:sosah.vic...@gmail.com]
> > Sent: Thursday, November 6, 2014 12:45 PM
> > To: dev@cordova.apache.org
> > Subject: Running browser platform in Linux
> >
> > Hello all.
> >
> > I've been playing a little bit with the Browse platform and the 
> > first thing I notice is that when running the application using 
> > "cordova run browser"
> > it handles the cases of when using Windows and Darwin (MacOS) but no
> Linux
> > (I'm on Ubuntu 14.04). Is there any particular reason of why it is 
> > not handled?
> >
> >
> >
> https://github.com/apache/cordova-browser/blob/master/bin/templates/pr
> oject/cordova/run
> >
> > Moreover, I have Chrome installed in my machine, but it doesn't 
> > respond
> to
> > the typical "chrome" command because I get an error in the standard 
> > output[1], so I have to use "google-chrome" command to launch it. 
> > Does anyone something about this? I downloaded the DEB package 
> > directly from Google Chrome.
> >
> > Appreciate your help
> >
> > [1]
> > * Error*chrome: error while loading shared libraries: libudev.so.0:
> cannot
> > open shared object file: No such file or directory
> >
> >
> > --
> > Victor Adrian Sosa Herrera
> > IBM Software Engineer
> > Guadalajara, Jalisco
> >
>
>
>
> --
> Victor Adrian Sosa Herrera
> IBM Software Engineer
> Guadalajara, Jalisco
>

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

RE: Running browser platform in Linux

[Parashuram Narasimhan (MS OPEN TECH)]

I don’t this we should launch Chrome this way. How about using something like 
browser-launcher, or even karma-chrome-launcher instead? Also, why not just 
"open" the HTML page? 

-Original Message-
From: Victor Sosa [mailto:sosah.vic...@gmail.com] 
Sent: Thursday, November 6, 2014 12:45 PM
To: dev@cordova.apache.org
Subject: Running browser platform in Linux

Hello all.

I've been playing a little bit with the Browse platform and the first thing I 
notice is that when running the application using "cordova run browser"
it handles the cases of when using Windows and Darwin (MacOS) but no Linux (I'm 
on Ubuntu 14.04). Is there any particular reason of why it is not handled?

https://github.com/apache/cordova-browser/blob/master/bin/templates/project/cordova/run

Moreover, I have Chrome installed in my machine, but it doesn't respond to the 
typical "chrome" command because I get an error in the standard output[1], so I 
have to use "google-chrome" command to launch it. Does anyone something about 
this? I downloaded the DEB package directly from Google Chrome.

Appreciate your help

[1]
* Error*chrome: error while loading shared libraries: libudev.so.0: cannot open 
shared object file: No such file or directory


--
Victor Adrian Sosa Herrera
IBM Software Engineer
Guadalajara, Jalisco

RE: FW: Adding Windows tests to ci.cordova.io

[Parashuram Narasimhan (MS OPEN TECH)]

I have never opened an INFRA ticket before. Can someone please help with 
opening an Apache INFRA ticket where we could get a VM ? My team could do built 
bot setup on master on that machine, and we could then pool our resources to 
add slaves. I also read that there are others who run medic, so it would be 
good to have more folks/companies contributing machines to run these tests. 

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Wednesday, November 5, 2014 11:37 AM
To: dev@cordova.apache.org
Cc: Max Woghiren
Subject: RE: FW: Adding Windows tests to ci.cordova.io

+1 for testing nightlys and moving to apache infra
On Nov 5, 2014 11:33 AM, "Parashuram Narasimhan (MS OPEN TECH)" < 
panar...@microsoft.com> wrote:

> A quick question - does it make sense to move the main build bot 
> master to an Apache Infrastructure? We could then have slaves be 
> independent developers, or by folks who already run medic (like google and 
> msopentech).
> This was the sort of federated model we were looking at.
>
> MSOpenTech's medic slaves are based on Azure VMs and can be connected 
> from an external master. Not sure if the same can work for Google's slaves 
> too.
>
> I am hoping that if we have such an infrastructure, we could run Medic 
> with our nightlies, giving us more confidence. We could get to an 
> ideal state where our tests are green, and a red in medic really means 
> that stuff is broken.
>
> -Original Message-
> From: Sergey Grebnov (Akvelon) [mailto:v-seg...@microsoft.com]
> Sent: Wednesday, November 5, 2014 10:46 AM
> To: Max Woghiren; dev@cordova.apache.org
> Subject: RE: FW: Adding Windows tests to ci.cordova.io
>
> Hi,
>
> I'm going to make a step forward in this direction by adding required 
> changes to Medic and additional improvements today (see below). Please 
> let me know if anyone has some additional ideas, want to discuss/collaborate.
>
> 1. Merged Windows/Unix sample config files so that we have single 
> config for buildbot master which will support all type of  slaves/tests.
> 2. Make Android test to run on both Windows and Unix.
> 3. Rely on mobile-spec to create test app (currently Medic just 
> duplicates those steps) 4. Add required fixes so that platform tests 
> run correctly (currently broken)
>
> -Sergey
> -Original Message-
> From: mmo...@google.com [mailto:mmo...@google.com] On Behalf Of Michal 
> Mocny
> Sent: Wednesday, October 8, 2014 7:05 AM
> To: Parashuram Narasimhan (MS OPEN TECH)
> Cc: Michal Mocny; Max Woghiren; dev@cordova.apache.org
> Subject: Re: FW: Adding Windows tests to ci.cordova.io
>
> I think Federating was the option last discussed, but I'm not actually 
> in-the-know about how the details.
>
> -Michal
>
> On Tue, Oct 7, 2014 at 9:54 PM, Parashuram Narasimhan (MS OPEN TECH) < 
> panar...@microsoft.com> wrote:
>
> >  I will not be at PGDay, but Kirk (from MSOpenTech) can cover this.
> > Does it make sense to move this to Apache infrastructure? Should we 
> > also look at a model where more people can simply set up machines 
> > and we could federate the results back to the main server ?
> >
> >
> >
> > -  FirefoxOS, Amazon FireOS, Ubuntu folks and other platforms -
> > what is your take on this ?
> >
> >
> >
> > *From:* mmo...@google.com [mailto:mmo...@google.com] *On Behalf Of 
> > *Michal Mocny
> > *Sent:* Tuesday, October 7, 2014 6:06 PM
> > *To:* Parashuram Narasimhan (MS OPEN TECH); Max Woghiren
> > *Cc:* dev@cordova.apache.org
> > *Subject:* Re: FW: Adding Windows tests to ci.cordova.io
> >
> >
> >
> > David from our team historically took care of most of it, but has 
> > moved on to other projects.
> >
> >
> >
> > Max would like to pick up where David left it, and has started to 
> > make some improvements, but its not really as actively maintained as it was.
> > Max and I will be at PGDay -- would love to discuss more sustainable 
> > maintenance of CI there, and how best to share effort with other teams.
> >
> >
> >
> > -Michal
> >
> >
> >
> > On Tue, Oct 7, 2014 at 5:18 PM, Parashuram Narasimhan (MS OPEN TECH) 
> > < panar...@microsoft.com> wrote:
> >
> > Adding back to dev list - Jesse's reply was
> >
> > +1
> > I would very much like to see this work integrated in the CI. Who is 
> > looking after the CI?
> >
> >
> > From: Jesse [mailto:purplecabb...@gmail.com]
> > Sent: Tuesday, October 7, 2014 2:17 PM
> > To: Parashuram Narasimhan (MS OPEN TECH)
> > Subject: Re: Adding Windows tests

RE: Adding ability to add any platform on any OS

[Parashuram Narasimhan (MS OPEN TECH)]

Could we postpone the check-reqs script to prepare instead on when adding it? 
This way, all platforms can at least be added on all OSes.  One benefit I see 
of adding iOS on windows for example would be the ability to use remote build 
agents that just push the source code to a remote machine or a VM. 

-Original Message-
From: Marcel Kinard [mailto:cmarc...@gmail.com] 
Sent: Thursday, October 23, 2014 1:29 PM
To: dev@cordova.apache.org
Subject: Re: Adding ability to add any platform on any OS

Edna will tackle converting the iOS create script from bash to node.js.

On Oct 21, 2014, at 8:55 PM, Carlos Santana  wrote:

> We can start by small wins by making CLI a bit smarter, if the user do 
> "cordova build" the cordova project might have multiple platforms and 
> some of them it can't compile, the same for "cordova run", printing a 
> message and skipping the step would be a good improvement.
> 
> for "cordova create", I agree with Andrew ios should be easy to write 
> in nodejs and be able to run the create command in a non OSX.


-
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 Nightly Builds

[Parashuram Narasimhan (MS OPEN TECH)]

Can we also run Medic on these nightlies ? My team could volunteer to do that 
work, if you guys think it is useful. 

-Original Message-
From: agri...@google.com [mailto:agri...@google.com] On Behalf Of Andrew Grieve
Sent: Monday, November 3, 2014 7:58 PM
To: dev
Subject: Re: Cordova Nightly Builds

so long as we unpublish old ones, I believe the list of versions shouldn't grow 
indefinitely.

On Mon, Nov 3, 2014 at 4:42 PM, Marcel Kinard  wrote:

> Nice!
>
> Doing an "npm info cordova" will yield a nightly-increasing number of 
> entries in the 'version' key?
>
> These would not be artifacts that we could vote on, correct?
>
> On Oct 30, 2014, at 1:16 AM, Steven Gill  wrote:
>
> > I have been doing some work on releasing nightlys recently.
> >
> > Please review PR [1] and comment on the issue [2].
> >
> > [1] https://github.com/apache/cordova-coho/pull/58
> > [2] https://issues.apache.org/jira/browse/CB-7904
>
>
> -
> 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: FW: Adding Windows tests to ci.cordova.io

[Parashuram Narasimhan (MS OPEN TECH)]

A quick question - does it make sense to move the main build bot master to an 
Apache Infrastructure? We could then have slaves be independent developers, or 
by folks who already run medic (like google and msopentech). This was the sort 
of federated model we were looking at. 

MSOpenTech's medic slaves are based on Azure VMs and can be connected from an 
external master. Not sure if the same can work for Google's slaves too.

I am hoping that if we have such an infrastructure, we could run Medic with our 
nightlies, giving us more confidence. We could get to an ideal state where our 
tests are green, and a red in medic really means that stuff is broken. 

-Original Message-
From: Sergey Grebnov (Akvelon) [mailto:v-seg...@microsoft.com] 
Sent: Wednesday, November 5, 2014 10:46 AM
To: Max Woghiren; dev@cordova.apache.org
Subject: RE: FW: Adding Windows tests to ci.cordova.io

Hi, 

I'm going to make a step forward in this direction by adding required changes 
to Medic and additional improvements today (see below). Please let me know if 
anyone has some additional ideas, want to discuss/collaborate. 

1. Merged Windows/Unix sample config files so that we have single config for 
buildbot master which will support all type of  slaves/tests. 
2. Make Android test to run on both Windows and Unix.
3. Rely on mobile-spec to create test app (currently Medic just duplicates 
those steps) 4. Add required fixes so that platform tests run correctly 
(currently broken)

-Sergey
-Original Message-
From: mmo...@google.com [mailto:mmo...@google.com] On Behalf Of Michal Mocny
Sent: Wednesday, October 8, 2014 7:05 AM
To: Parashuram Narasimhan (MS OPEN TECH)
Cc: Michal Mocny; Max Woghiren; dev@cordova.apache.org
Subject: Re: FW: Adding Windows tests to ci.cordova.io

I think Federating was the option last discussed, but I'm not actually 
in-the-know about how the details.

-Michal

On Tue, Oct 7, 2014 at 9:54 PM, Parashuram Narasimhan (MS OPEN TECH) < 
panar...@microsoft.com> wrote:

>  I will not be at PGDay, but Kirk (from MSOpenTech) can cover this. 
> Does it make sense to move this to Apache infrastructure? Should we 
> also look at a model where more people can simply set up machines and 
> we could federate the results back to the main server ?
>
>
>
> -  FirefoxOS, Amazon FireOS, Ubuntu folks and other platforms –
> what is your take on this ?
>
>
>
> *From:* mmo...@google.com [mailto:mmo...@google.com] *On Behalf Of 
> *Michal Mocny
> *Sent:* Tuesday, October 7, 2014 6:06 PM
> *To:* Parashuram Narasimhan (MS OPEN TECH); Max Woghiren
> *Cc:* dev@cordova.apache.org
> *Subject:* Re: FW: Adding Windows tests to ci.cordova.io
>
>
>
> David from our team historically took care of most of it, but has 
> moved on to other projects.
>
>
>
> Max would like to pick up where David left it, and has started to make 
> some improvements, but its not really as actively maintained as it was.
> Max and I will be at PGDay -- would love to discuss more sustainable 
> maintenance of CI there, and how best to share effort with other teams.
>
>
>
> -Michal
>
>
>
> On Tue, Oct 7, 2014 at 5:18 PM, Parashuram Narasimhan (MS OPEN TECH) < 
> panar...@microsoft.com> wrote:
>
> Adding back to dev list – Jesse’s reply was
>
> +1
> I would very much like to see this work integrated in the CI. Who is 
> looking after the CI?
>
>
> From: Jesse [mailto:purplecabb...@gmail.com]
> Sent: Tuesday, October 7, 2014 2:17 PM
> To: Parashuram Narasimhan (MS OPEN TECH)
> Subject: Re: Adding Windows tests to ci.cordova.io
>
>
> @purplecabbage
> risingj.com<http://risingj.com>
>
> On Tue, Oct 7, 2014 at 11:17 AM, Parashuram Narasimhan (MS OPEN TECH) 
> < panar...@microsoft.com<mailto:panar...@microsoft.com>> wrote:
> Hi,
>
> Wanted to ping on this thread. What would be the best way to get 
> Windows support in the official ci.cordova.org<http://ci.cordova.org> ?
>
> -Original Message-
> From: Maria Bukharina [mailto:maria.bukhar...@akvelon.com maria.bukhar...@akvelon.com>]
> Sent: Friday, October 3, 2014 5:51 AM
> To: dev@cordova.apache.org<mailto:dev@cordova.apache.org>
> Subject: Adding Windows tests to ci.cordova.io<http://ci.cordova.io>
>
> Hi all,
>
> I'm working on improvements of medic tests for Windows platform. We 
> had prepared pull request about supporting of Windows Universal Apps 
> https://github.com/apache/cordova-medic/pull/16. Seemed that adding 
> Windows tests to http://ci.cordova.io/ is stuck. Could we please 
> discuss it again.
>
> By the way is medic autotests are still best practice for testing cordova?
> Seems http://ci.cordova.io/ is broken for a long time. I've found out 
> that

RE: cordova-browser plugin polyfills -- which projects already have work in this space?

[Parashuram Narasimhan (MS OPEN TECH)]

We have started working on porting some of the plugins to the browser platform. 
I think we should add JIRA work items for each, and assign to ourselves, if we 
are starting to work on a plugin to ensure that we don't have 2 folks working 
on the same plugin :) 

-Original Message-
From: Suraj Pindoria [mailto:suraj.pindo...@yahoo.com.INVALID] 
Sent: Wednesday, November 5, 2014 10:07 AM
To: dev@cordova.apache.org
Subject: Re: cordova-browser plugin polyfills -- which projects already have 
work in this space?

Just an FYI that geolocation does work in the browser.  I tested this over the 
summer and all the major browsers already have support for it.

Suraj.

> On Nov 5, 2014, at 9:35 AM, Ray Camden  wrote:
> 
> Hmpth - let me look into that post lunch.
> 
> On 11/5/14, 10:53 AM, "Michal Mocny"  wrote:
> 
>> Cool!  But I can't find how to do this with "browse all plugins".  
>> Appears to be a filter option on search results but cannot search for 
>> * or . -- and the filter doesn't persist nor alter url for 
>> linkability.
>> 
>> -Michal
>> 
>> On Wed, Nov 5, 2014 at 11:46 AM, Ray Camden  wrote:
>> 
>>> As just an FYI, plugins.cordova.io can now filter to plugins that 
>>> support browser as a platform. This could be used to figure out what 
>>> plugins have added support.
>>> 
>>> 
>>> 
>>> On 11/5/14, 9:57 AM, "Michal Mocny"  wrote:
>>> 
 The process for implementing a browser polyfill (I'm new to this, 
 may
>>> be
 missing steps), appears to be just like any other platform whose 
 implementations are in js (like firefoxos, windows).  Here is the 
 implementation for device plugin for example:
>>> 
>>> 
>>> 
>>> - 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: Summarizing thoughts on cordova-browser vs Ripple

[Parashuram Narasimhan (MS OPEN TECH)]

MSOpenTech is currently working on porting our ripple-platform prototype - 
https://github.com/MSOpenTech/cordova-ripple to work on top of cordova-browser. 
The question on how each plugin exposes a UI to provide mock data is still up 
for discussion, but Intel has a lot of context on that area. 

-Original Message-
From: Kirupa Chinnathambi [mailto:kiru...@microsoft.com] 
Sent: Wednesday, November 5, 2014 11:04 AM
To: dev@cordova.apache.org
Subject: RE: Summarizing thoughts on cordova-browser vs Ripple

+1 to what you’ve both stated.

Cordova-browser shouldn't be responsible for providing mock data, UI, or any 
additional functionality for simulating a plug-in. It’s primary goal is to (as 
you both mention) be responsible for getting apps to run in the browser. 
Simulating plug-in behavior would be external to that in some form or fashion.

Cheers,
Kirupa

-Original Message-
From: mikeywbro...@gmail.com [mailto:mikeywbro...@gmail.com] On Behalf Of 
Michael Brooks
Sent: Wednesday, November 5, 2014 9:22 AM
To: dev@cordova.apache.org
Subject: Re: Summarizing thoughts on cordova-browser vs Ripple

>
> In my view, ripple should be built on top of the browser platform 
> work, and ideally also decouple the UI from the plugin 
> instrumentation, but thats up to the folks running that effort.




> With all this in mind, I think the cordova-browser effort should 
> proceed with current direction, but keep in mind that more advanced 
> plugin instrumentation doesn't belong there.


This echo's my views on the Browser Platform and Ripple as well.

Ideally, the Browser Platform is a production deployment environment for the 
web, while Ripple is debugging instrumentation that runs on the Browser 
Platform.

On Wed, Nov 5, 2014 at 8:04 AM, Michal Mocny  wrote:

> We debated a bit about browser vs ripple at phonegap day (especially 
> Intel folks who have done lots of work here), and the my personal 
> tldr; is that there is in fact a home for both.
>
> Basically, browser-platform is for getting apps running in a browser
> (duh) with as much working functionality as possible.  Its supposed to 
> simplify the 'if cordova then dialog else alert' problem, so you can 
> build even more of your app with just local development.  Seemingly 
> this could be used to make targeting both web and app even easier.
>
> Ripple is for instrumenting/debugging apps by manipulating plugins.  
> Its about having a UI that reaches into geolocation or camera and 
> controls what the plugin returns to the app.  Its about re-running the 
> same device events over and over for tracking application logic changes.
>
> Some of the work ripple has done traditionally can now in fact just be 
> done via browser DevTools, but their are still some cases where custom 
> hooks into plugins are the best way to provide a good local 
> "simulator".  (Chrome DevTools at least now provide mobile emulation, unsure 
> about others).
>
> In my view, ripple should be built on top of the browser platform 
> work, and ideally also decouple the UI from the plugin 
> instrumentation, but thats up to the folks running that effort.
>
> With all this in mind, I think the cordova-browser effort should 
> proceed with current direction, but keep in mind that more advanced 
> plugin instrumentation doesn't belong there.
>
> -Michal
>

RE: [Vote] 3.7.0 Windows & Windows Phone Release

[Parashuram Narasimhan (MS OPEN TECH)]

We now have the required number of votes. Can we consider this vote also 
closed? 

-Original Message-
From: Staci Cooper [mailto:staci@gmail.com] 
Sent: Monday, November 3, 2014 12:26 PM
To: dev@cordova.apache.org
Subject: Re: [Vote] 3.7.0 Windows & Windows Phone Release

+1
* Verified license headers via coho audit-license-headers
* Verified ability to create, build, and run cordova app with windows and 
wp8 platforms
* Ran automated tests on win8.1 and 8.0 machines, and also on wp8.1 and
wp8.0 devices. Found no regressions


On Mon, Nov 3, 2014 at 11:02 AM, Sergey Grebnov (Akvelon) < 
v-seg...@microsoft.com> wrote:

> I vote +1
> *  Verified signatures via "coho verify-archive"
> *  Verified tags manually
> *  Verified license headers via "coho audit-license-headers"
> *  Checked package files and version
> *  Verified ability to create Cordova app with windows and wp8 
> platforms
> *  Tested building and running app with --phone, --win flags 
> (successfully build and run)
> *  Verified app can be built for different archs (x86, x64, 
> arm,
> anycpu)
> *  Verified app can be deployed on devices
> *  Validated resultant packages using Windows App Cert Kit ( 
> all packages passed except CordovaApp.Phone_0.0.1.0_x86_debug_Test and
> CordovaApp.Phone_0.0.1.0_x64_debug_Test)
> *  Checked release notes
>
> Thx!
> Sergey
> -Original Message-
> From: Parashuram Narasimhan (MS OPEN TECH) 
> [mailto:panar...@microsoft.com]
> Sent: Saturday, November 1, 2014 9:11 AM
> To: dev@cordova.apache.org
> Subject: RE: [Vote] 3.7.0 Windows & Windows Phone Release
>
> +1
> Verified Archives, ran manual tests.
>
> -Original Message-
> From: Steven Gill [mailto:stevengil...@gmail.com]
> Sent: Friday, October 31, 2014 7:18 PM
> To: dev@cordova.apache.org
> Subject: [Vote] 3.7.0 Windows & Windows Phone Release
>
> Please review and vote on this 3.7.0 Windows & Windows Phone Release.
>
> Release issue: https://issues.apache.org/jira/browse/CB-7923
>
> Repos ready to be released have been published to
> dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-7923
>
> The package was published from its corresponding git tag:
> cordova-windows: 3.7.0 (6d9a19b0db)
> cordova-wp8: 3.7.0 (279215372e)
>
> Upon a successful vote I will upload the archive to dist/, publish it 
> to NPM, and post the corresponding blog post.
>
> Voting guidelines:
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting
> .md
>
> Voting will go on for a minimum of 48 hours.
>
> I vote +1:
> * Ran coho audit-license-headers over the relevant repos
> * Ran coho check-license to ensure all dependencies and 
> subdependencies have Apache-compatible licenses
>
> -
> 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: [Vote] 3.7.0 Windows & Windows Phone Release

[Parashuram Narasimhan (MS OPEN TECH)]

+1 
Verified Archives, ran manual tests. 

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Friday, October 31, 2014 7:18 PM
To: dev@cordova.apache.org
Subject: [Vote] 3.7.0 Windows & Windows Phone Release

Please review and vote on this 3.7.0 Windows & Windows Phone Release.

Release issue: https://issues.apache.org/jira/browse/CB-7923

Repos ready to be released have been published to
dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-7923

The package was published from its corresponding git tag:
cordova-windows: 3.7.0 (6d9a19b0db)
cordova-wp8: 3.7.0 (279215372e)

Upon a successful vote I will upload the archive to dist/, publish it to NPM, 
and post the corresponding blog post.

Voting guidelines:
https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md

Voting will go on for a minimum of 48 hours.

I vote +1:
* Ran coho audit-license-headers over the relevant repos
* Ran coho check-license to ensure all dependencies and subdependencies have 
Apache-compatible licenses

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

RE: [DISCUSS] Windows Release

[Parashuram Narasimhan (MS OPEN TECH)]

Thanks :) 

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Thursday, October 30, 2014 1:53 PM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Windows Release

Sure, why not!

On Thu, Oct 30, 2014 at 1:06 PM, Parashuram Narasimhan (MS OPEN TECH) < 
panar...@microsoft.com> wrote:

> This looks good. I am waiting for Sergey to confirm. Can we also do a 
> Wp8 release please ? We had a critical bug fix for this.
>
> -Original Message-
> From: Steven Gill [mailto:stevengil...@gmail.com]
> Sent: Thursday, October 30, 2014 11:48 AM
> To: dev@cordova.apache.org
> Subject: [DISCUSS] Windows Release
>
> Waiting for any PRs?
>
> Can we move forward. Want me to do it or do we have some windows 
> maintainers who want to give it a shot?
>
> Essentially follow the steps at
>
> https://github.com/apache/cordova-coho/blob/master/docs/platforms-rele
> ase-process.md
> .
> Skip the steps about updating cli & lib since we are doing a tools 
> release post platform releases.
>
> Should be a simple process.
>
> -
> 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

[Parashuram Narasimhan (MS OPEN TECH)]

Can we also look at this pull request please ? It fixes a bug with dependency 
plugins - 
CB-7846 Fix plugin deletion when dependency plugin does not exist #110
https://github.com/apache/cordova-lib/pull/110


-Original Message-
From: Shazron [mailto:shaz...@gmail.com] 
Sent: Thursday, October 30, 2014 8:53 AM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Tools Release

I'll get that tested and merged in later today as well as get the iOS platform 
ready for vote.

On Thursday, October 30, 2014, Mark Koudritsky  wrote:

> On Wed, Oct 29, 2014 at 6:40 PM, Shazron  >
> wrote:
>
> > Mark, this patch is important for us to get pulled in:
> > https://github.com/apache/cordova-lib/pull/116
> >
> >
> The patch looks good to me. I haven't branched yet, just merge it in 
> if everything else is ok with it.
>
>
>
> > On Wed, Oct 29, 2014 at 3:27 PM, Steven Gill  >
> > wrote:
> >
> > > Okay, so lets get windows + ios platforms released and then follow 
> > > that
> > up
> > > with a tools release
> >
>
> Agreed, waiting for ios & windows release. (doing some prep work for 
> now)
>

RE: [DISCUSS] Windows Release

[Parashuram Narasimhan (MS OPEN TECH)]

This looks good. I am waiting for Sergey to confirm. Can we also do a Wp8 
release please ? We had a critical bug fix for this. 

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Thursday, October 30, 2014 11:48 AM
To: dev@cordova.apache.org
Subject: [DISCUSS] Windows Release

Waiting for any PRs?

Can we move forward. Want me to do it or do we have some windows maintainers 
who want to give it a shot?

Essentially follow the steps at
https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md.
Skip the steps about updating cli & lib since we are doing a tools release post 
platform releases.

Should be a simple process.

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

RE: [DISCUSS] Tools Release

[Parashuram Narasimhan (MS OPEN TECH)]

+1 to a tools release. We also have some bugs fixes for the Windows platform, 
so we may use this as an opportunity to increase the pinned windows platform 
version. 

-Original Message-
From: Mark Koudritsky [mailto:kam...@google.com] 
Sent: Wednesday, October 29, 2014 2:20 PM
To: dev@cordova.apache.org
Subject: [DISCUSS] Tools Release

I would like to start a tools release.
Any outstanding patches to land? Thoughts?

 - Mark

RE: Adding ability to add any platform on any OS

[Parashuram Narasimhan (MS OPEN TECH)]

What about saving and restoring platforms?  Cordova platforms will not be 
checked in, but we could do a cordova platform save. When I now do a cordova 
platform restore on my Mac machine, will is try to restore the Windows platform 
also and fail ? 

-Original Message-
From: Josh Soref [mailto:jso...@blackberry.com] 
Sent: Friday, October 17, 2014 2:15 PM
To: Jesse; dev@cordova.apache.org
Subject: Re: Adding ability to add any platform on any OS

cordova serve could still benefit from it...

Although I haven't looked into it too much. ‎ Sent from my BlackBerry 10 
smartphone.


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

RE: [Vote] Tools Release

[Parashuram Narasimhan (MS OPEN TECH)]

+1.

Verified signatures, hashes and tags manually. 

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Wednesday, October 15, 2014 2:32 PM
To: dev@cordova.apache.org
Subject: Re: [Vote] Tools Release

Need one more vote!

On Mon, Oct 13, 2014 at 10:07 AM, Sergey Grebnov (Akvelon) < 
v-seg...@microsoft.com> wrote:

> I vote +1:
> *   Verified signatures and hashes via 'coho verify-archive'
> *   Verified tags manually
> *   Extracted archives, ensured everything install without errors
> *   Ensured license headers are present everywhere via 'coho
> audit-license-headers'
> *   Ensured all dependencies and subdependencies have
> Apache-compatible licenses via 'coho check-license'
> *   Ensured Cordova app can be created and platforms can be added
> using '--usegit' key
> *   Ensured app launching and building  okay
>
> Thx!
> Sergey
> -Original Message-
> From: Steven Gill [mailto:stevengil...@gmail.com]
> Sent: Saturday, October 11, 2014 2:50 AM
> To: dev@cordova.apache.org
> Subject: [Vote] Tools Release
>
> Please review and vote on this Tools Release.
>
> Release issue: https://issues.apache.org/jira/browse/CB-7661
>
> Tools have been published to
> dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-7661/
>
> The packages were published from their corresponding git tags:
>
> cordova-js: 3.7.1 (f5046c9665)
> cordova-lib: 4.0.0 (f5db3d13d5)
> cordova-plugman: 0.22.12 (203706aac1)
> cordova-cli: 4.0.0 (0fb8fbb189)
>
>
> Upon a successful vote I will upload the archives to dist/, publish 
> them to NPM under the latest tag, and post the corresponding blog post.
>
> Voting guidelines:
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting
> .md
>
> Voting will go on for a minimum of 48 hours.
>
> I vote +1:
> * Ran coho audit-license-headers over the relevant repos
> * Ran coho check-license to ensure all dependencies and 
> subdependencies have Apache-compatible licenses
> * Ensured continuous build was green when repos were tagged
>
> -
> 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: Measuring Perf of Cordova apps (Android/iOS)

[Parashuram Narasimhan (MS OPEN TECH)]

@Michal - I tested the WkWebView using a simple iOS App and loaded a webpage on 
it - not Cordova yet and that was the reason I did not publish the results. 
Can't wait for WkWebView to be in Cordova and then see how much of an 
improvement we could get :) 

For the metrics, the idea was not to compare iOS vs Android, but rather compare 
2 deploys of the same app. This idea is, a developer runs the tests per commit 
(in a continuous integration system) and can see which commit slowed down the 
app. This way, they could also figure out the CSS or JS event handlers they 
added during that commit. The graphs would look something like 
http://nparashuram.com/perfslides/perfjankie - you can see how the 3rd commit 
on that graph is bad since I added an onScroll event handler.

@Andrew - I would love to do a blog post. Should I write it on my blog and 
refer to it in the official Cordova blog, or can this be in the official 
cordova blog? Note that I developed this tool independently and is not an 
official Cordova release, but if the folks in the community feel that this 
could be interesting to any Cordova developer and makes sense to put in the 
official Cordova blog, I would love to write a quick tutorial. 

-Original Message-
From: agri...@google.com [mailto:agri...@google.com] On Behalf Of Andrew Grieve
Sent: Tuesday, October 14, 2014 11:48 AM
To: dev
Subject: Re: Measuring Perf of Cordova apps (Android/iOS)

Super Cool. This would definitely be useful to add to a continuous build 
system. Certainly would make a good referral blog post if you want to have a 
stab at it :)

On Tue, Oct 14, 2014 at 2:28 PM, Michal Mocny  wrote:

> Very cool Parashuram.
>
> How did you test WkWebView?  non-cordova?
>
> Also, the results have different labels on iOS/Android, which I assume 
> means you are just reporting what the tools report.  Would you 
> consider mapping the values which have direct parallels to the same 
> labels so we can do more direct comparisons?
>
> -Michal
>
> On Mon, Oct 13, 2014 at 2:47 PM, Parashuram 
> wrote:
>
> > Over the weekend, I created a tool to measure the rendering and 
> > network performance for Cordova apps, and I thought of sharing it on 
> > the list. I
> am
> > able to pick up numbers from iOS and Android (4.4).
> >
> > Here is a demo video - https://www.youtube.com/watch?v=TG_eTe_H-s4
> > More details on how to run it on your cordova app : [link <
> >
> http://blog.nparashuram.com/2014/10/measuring-rendering-performance-me
> trics.html
> > >
> > ]
> > Browser-perf : http://npmjs.org/package/browser-perf
> >
> > Would love to hear feedback from the community on this. Initial 
> > tests
> with
> > WkWebview and UIWebView show some good numbers.
> >
> > Since a lot of people worry about perf of hybrid apps, I am hoping 
> > that this tool would give them a way to look at hard numbers and see 
> > that
> hybrid
> > apps can be as smooth as native apps.
> >
> > Parashuram
> > http://nparashuram.com
> >
>

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

Re: [VOTE] Plugins Release Oct 3, 2014

[Parashuram Narasimhan (MS OPEN TECH)]

+1

Verified Signatures, tags and functionality.

On 10/10/14, 3:50 PM, "Steven Gill"  wrote:

>We need one more vote to publish
>
>On Mon, Oct 6, 2014 at 8:18 PM, Sergey Grebnov (Akvelon) <
>v-seg...@microsoft.com> wrote:
>
>> I vote +1
>> *   Verified signatures and hashes
>> *   Verified tags
>> *   Checked plugin functionality with mobilespec app for windows and
>> wp8 platforms
>> *   Checked release notes
>>
>> Thx!
>> Sergey
>> -Original Message-
>> From: Steven Gill [mailto:stevengil...@gmail.com]
>> Sent: Saturday, October 4, 2014 4:22 AM
>> To: dev@cordova.apache.org
>> Subject: [VOTE] Plugins Release Oct 3, 2014
>>
>> Please review and vote on the release of this plugins release.
>>
>> Release issue: https://issues.apache.org/jira/browse/CB-7699
>>
>> The plugins have been published to
>> dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-7699/
>>
>> The packages were published from their corresponding git tags:
>> cordova-plugin-camera: 0.3.3 (021743f20e)
>> cordova-plugin-contacts: 0.2.14 (a9df3c4fa0)
>> cordova-plugin-file-transfer: 0.4.7 (d0d8698af1)
>> cordova-plugin-globalization: 0.3.2 (6485890999)
>> cordova-plugin-inappbrowser: 0.5.2 (8ce6b497fa)
>> cordova-plugin-media: 0.2.14 (35ab3af539)
>> cordova-plugin-media-capture: 0.3.4 (852a053993)
>> cordova-plugin-network-information: 0.2.13 (056c6dddaf)
>> cordova-plugin-splashscreen: 0.3.4 (b46cdca795)
>>
>> Upon a successful vote I will upload the archives to dist/, upload them
>>to
>> the Plugins Registry, and post the corresponding blog post.
>>
>> Voting guidelines:
>> 
>>https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
>>
>> Voting will go on for a minimum of 48 hours.
>>
>> I vote +1:
>> * Ran coho audit-license-headers over the relevant repos
>> * Used `license-checker` to ensure all dependencies have
>>Apache-compatible
>> licenses
>>
>> -
>> 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: Independent platform release summary

[Parashuram Narasimhan (MS OPEN TECH)]

4.0 is also good. Should we tag and start a vote for that ?
Sorry for asking about vote again, but I want to ensure that the issues
that Sergey fixed in the CLI/Lib are impacting some folks and I hope this
release could help them fast.

On 10/10/14, 10:17 AM, "Victor Sosa"  wrote:

>lol... I like that :P
>
>2014-10-10 12:09 GMT-05:00 Joe Bowser :
>
>> On Oct 10, 2014 10:05 AM, "Brian LeRoux"  wrote:
>> >
>> > OR we move to named releases externally.
>> >
>> > Cordova MX === 4.0
>>
>> Cordova Mexico?
>>
>> > On Oct 10, 2014 10:03 AM, "Michal Mocny"  wrote:
>> >
>> > > 4 was also discussed as fine, and in isolation would have been our
>> choice
>> > > for sure -- but we worried that with the impending "cordova-4.0"
>> releases,
>> > > it would confuse users and not mark a clear departure from cadver.
>> > >
>> > > The more I think about it though, the less important I think that
>>worry
>> > > is.  Maybe 4.0 is fine.
>> > >
>> > > (Apologies to Steve, who just wants to get this over with)
>> > >
>> > > On Fri, Oct 10, 2014 at 12:48 PM, Brian LeRoux  wrote:
>> > >
>> > > > As is 4.
>> > > >
>> > > > This is more of an outreach, marketing, blogging, tweeting, etc
>> problem.
>> > > > Versions are for issue tracking not marketing. (Tho semver and our
>> > > > respective $BIGCO's confuse that to their and our continued
>>strife.)
>> > > >
>> > > > (All IMO of course, happy to follow the wisdom of the crowd on
>>this
>> one.)
>> > > > On Oct 10, 2014 9:29 AM, "Michal Mocny" 
>>wrote:
>> > > >
>> > > > > 5 is also fine.
>> > > > >
>> > > > > On Fri, Oct 10, 2014 at 12:17 PM, Brian LeRoux 
>>wrote:
>> > > > >
>> > > > > > I am against it. Its not going to achieve the goal of
>>alleviating
>> > > > > > confusion. People see the CLI as the version not the
>>platforms.
>> I'd
>> > > > > rather
>> > > > > > we went to 5 if anything.
>> > > > > > On Oct 9, 2014 3:56 PM, "Parashuram Narasimhan (MS OPEN
>>TECH)" <
>> > > > > > panar...@microsoft.com> wrote:
>> > > > > >
>> > > > > > > I meant tag and start the vote for the next release :)
>> > > > > > >
>> > > > > > > On 10/9/14, 3:01 PM, "Chuck Lantz" 
>> wrote:
>> > > > > > >
>> > > > > > > >+1
>> > > > > > > >
>> > > > > > > >-Chuck
>> > > > > > > >
>> > > > > > > >-Original Message-
>> > > > > > > >From: Jesse [mailto:purplecabb...@gmail.com]
>> > > > > > > >Sent: Thursday, October 9, 2014 2:55 PM
>> > > > > > > >To: dev@cordova.apache.org
>> > > > > > > >Subject: Re: Independent platform release summary
>> > > > > > > >
>> > > > > > > >+1 to not voting ;) , it implies we will wait 72 hours
>>before
>> > > moving
>> > > > > on.
>> > > > > > > >
>> > > > > > > >How about if anyone is completely against 10.0.0 they
>>voice it
>> > > here,
>> > > > > in
>> > > > > > > >the next couple hours, otherwise we move forward.
>> > > > > > > >
>> > > > > > > >@purplecabbage
>> > > > > > > >risingj.com
>> > > > > > > >
>> > > > > > > >On Thu, Oct 9, 2014 at 2:52 PM, Steven Gill <
>> > > stevengil...@gmail.com
>> > > > >
>> > > > > > > >wrote:
>> > > > > > > >
>> > > > > > > >> I don't think a vote is necessary. I'd hate to see us
>>resort
>> to
>> > > > > voting
>> > > > > > > >> to solve problems. Voting should be a last resort if
>> consensus
>> > > is
>> > > > > > > >> split. I don't see that in this scenario.
>> > > >

Re: Independent platform release summary

[Parashuram Narasimhan (MS OPEN TECH)]

I meant tag and start the vote for the next release :)

On 10/9/14, 3:01 PM, "Chuck Lantz"  wrote:

>+1
>
>-Chuck
>
>-Original Message-
>From: Jesse [mailto:purplecabb...@gmail.com]
>Sent: Thursday, October 9, 2014 2:55 PM
>To: dev@cordova.apache.org
>Subject: Re: Independent platform release summary
>
>+1 to not voting ;) , it implies we will wait 72 hours before moving on.
>
>How about if anyone is completely against 10.0.0 they voice it here, in
>the next couple hours, otherwise we move forward.
>
>@purplecabbage
>risingj.com
>
>On Thu, Oct 9, 2014 at 2:52 PM, Steven Gill 
>wrote:
>
>> I don't think a vote is necessary. I'd hate to see us resort to voting
>> to solve problems. Voting should be a last resort if consensus is
>> split. I don't see that in this scenario.
>>
>> I propose we bumb the version up to 10.0.0.
>>
>> On Thu, Oct 9, 2014 at 2:45 PM, Parashuram Narasimhan (MS OPEN TECH) <
>> panar...@microsoft.com> wrote:
>>
>> > Lets start with a vote for 10.0.0 ? And if someone feels strongly
>> > about calling it something the vote could be cancelled !!
>> >
>> > On 10/9/14, 2:41 PM, "Chuck Lantz"  wrote:
>> >
>> > >Yeah agreed - Vladimir squashed the bug and what was at once point
>> > >to be called 3.7.0 has been mainly waiting on a version number.
>> > >Personally I am fine with 10.0.0 or 5.0.0 - Either send the message
>> > >that platform versions are divorced from the CLI from a versioning
>> > >perspective (though behavior is still predictable).  Leo - I think
>> > >at least out of the gate devs will likely focus on the CLI version
>> > >as primary.  Basically today, the cadence version of the CLI is
>> > >what people talk about.  Heck, Cordova
>> > >3.4.1 was 3.4.0 for all platforms but iOS.  The main message is
>> > >that
>> when
>> > >you platform add android, you may see an npm pull for
>> > >cordova-android@4.3.2 and that is expected.  It's just formalizing
>> > >the message and allows independent platform rev'ing.
>> > >
>> > >-Chuck
>> > >
>> > >-Original Message-
>> > >From: Steven Gill [mailto:stevengil...@gmail.com]
>> > >Sent: Thursday, October 9, 2014 2:13 PM
>> > >To: dev@cordova.apache.org
>> > >Cc: Michal Mocny; Marcel Kinard
>> > >Subject: Re: Independent platform release summary
>> > >
>> > >I think vladimir fixed the bug. We just need to release now.
>> > >
>> > >Only thing holding back the release now is consensus on the version
>> > >of the cli. It seemed like most people were leaning toward 10.0.0.
>> > >Should I move forward with that? I would just have to branch + pin
>> > >deps
>> > >
>> > >Leo the documentation version dropdown box would be tied to cli
>>version.
>> > >It still makes sense to copy over platform documentation into
>> > >platform repos and maybe copy it into docs during generation time.
>> > >
>> > >As for plugin pinning, plugins have more to do with platforms. I
>> wouldn't
>> > >say they aren't tied to the cli at all. I understand your point
>>though.
>> > >So far, we haven't had any plugins that won't work with previous
>> versions
>> > >(As far as I know). We should really fix the engine stuff for
>> > >plugins so we can keep track of what platforms they work for. I'd
>> > >like us to give warnings to users to update their plugins if newer
>>versions are out.
>> > >Cordova info should also dump what versions of plugins you have
>> installed
>> > >if it doesn't already. In combination with cordova --save & cordova
>> > >--restore, we should be able to recommend a workflow that is easily
>> > >reproducible on any machine.
>> > >
>> > >On Thu, Oct 9, 2014 at 1:44 PM, Chuck Lantz 
>> wrote:
>> > >
>> > >> Okay - so - there's a pretty nasty CLI blocker bug right now.
>> > >> Plugins with dependencies don't install (this affects all
>> > >> platforms).  In my opinion, we need to get a CLI release out
>> > >> really soon.  Are we closed on this topic, or do we need to look
>> > >> at doing the old process to get this out the door while we are
>>still talking?
>> > >>
>> > >

Re: Independent platform release summary

[Parashuram Narasimhan (MS OPEN TECH)]

Lets start with a vote for 10.0.0 ? And if someone feels strongly about
calling it something the vote could be cancelled !!

On 10/9/14, 2:41 PM, "Chuck Lantz"  wrote:

>Yeah agreed - Vladimir squashed the bug and what was at once point to be
>called 3.7.0 has been mainly waiting on a version number.  Personally I
>am fine with 10.0.0 or 5.0.0 - Either send the message that platform
>versions are divorced from the CLI from a versioning perspective (though
>behavior is still predictable).  Leo - I think at least out of the gate
>devs will likely focus on the CLI version as primary.  Basically today,
>the cadence version of the CLI is what people talk about.  Heck, Cordova
>3.4.1 was 3.4.0 for all platforms but iOS.  The main message is that when
>you platform add android, you may see an npm pull for
>cordova-android@4.3.2 and that is expected.  It's just formalizing the
>message and allows independent platform rev'ing.
>
>-Chuck
>
>-Original Message-
>From: Steven Gill [mailto:stevengil...@gmail.com]
>Sent: Thursday, October 9, 2014 2:13 PM
>To: dev@cordova.apache.org
>Cc: Michal Mocny; Marcel Kinard
>Subject: Re: Independent platform release summary
>
>I think vladimir fixed the bug. We just need to release now.
>
>Only thing holding back the release now is consensus on the version of
>the cli. It seemed like most people were leaning toward 10.0.0. Should I
>move forward with that? I would just have to branch + pin deps
>
>Leo the documentation version dropdown box would be tied to cli version.
>It still makes sense to copy over platform documentation into platform
>repos and maybe copy it into docs during generation time.
>
>As for plugin pinning, plugins have more to do with platforms. I wouldn't
>say they aren't tied to the cli at all. I understand your point though.
>So far, we haven't had any plugins that won't work with previous versions
>(As far as I know). We should really fix the engine stuff for plugins so
>we can keep track of what platforms they work for. I'd like us to give
>warnings to users to update their plugins if newer versions are out.
>Cordova info should also dump what versions of plugins you have installed
>if it doesn't already. In combination with cordova --save & cordova
>--restore, we should be able to recommend a workflow that is easily
>reproducible on any machine.
>
>On Thu, Oct 9, 2014 at 1:44 PM, Chuck Lantz  wrote:
>
>> Okay - so - there's a pretty nasty CLI blocker bug right now.  Plugins
>> with dependencies don't install (this affects all platforms).  In my
>> opinion, we need to get a CLI release out really soon.  Are we closed
>> on this topic, or do we need to look at doing the old process to get
>> this out the door while we are still talking?
>>
>> There are also a series of other bugs in the currently tagged "3.6.4"
>> platforms for Android, Windows, and Windows Phone 8.  These can be
>> handled independently, but the CLI bug can't.
>>
>> https://issues.apache.org/jira/browse/CB-7670
>>
>> -Chuck
>>
>> -Original Message-
>> From: Treggiari, Leo [mailto:leo.treggi...@intel.com]
>> Sent: Thursday, October 9, 2014 12:23 PM
>> To: Michal Mocny
>> Cc: Marcel Kinard; dev
>> Subject: RE: Independent platform release summary
>>
>> I'll have to admit that this seems a bit weird.  That is, independent
>> versions of the CLI and platforms, with a "Cordova release" named
>> "something" - e.g. a date?
>>
>> Imagine a user wants to know whether the new whitelist entry in
>> config.xml is supported in the versions of CLI and platforms that they
>> have - assuming they understand the distinction between the CLI and
>> platforms to begin with.  They use some command to list the versions
>> of the "things" (CLI and
>> platforms) they have installed.  They go to the individual
>> documentation of the "things" and try to figure it out.
>>
>> The way the Cordova documentation works today is nice with the combo
>> box where I can select a Cordova version - 3.6.0, 3.5.0, ...  What
>> would the combo box contain in the new versioning scheme and how many
>> entries would there be?  Are the answers "dates" and "lots of dates"?
>> Or would there be no Cordova version documentation other than an
>> explanation of how to get the list of "things" you currently have and
>> where to find the documentation on them.
>>
>> To "pin" or not to "pin.
>>
>> Note that, to me, the pinning choice defines what happens when I use
>> "cordova {plugin | platform} add foo" with no specific version
>>specified.
>>
>> I've understood, so far at least, that plugins are not pinned (an add
>> always fetches something) and platforms are pinned to a CLI version
>> (an add tells the CLI that I will be using that platform (already
>> installed) for this project).  Everything I have read which includes 1
>> book and the on-line project documentation, suggest that, even if not
>> stating it explicitly.  E.g. plugins talk about "fetching" and
>> platforms don't.  There is a way to fetch a specific version o

RE: FW: Adding Windows tests to ci.cordova.io

[Parashuram Narasimhan (MS OPEN TECH)]

I will not be at PGDay, but Kirk (from MSOpenTech) can cover this. Does it make 
sense to move this to Apache infrastructure? Should we also look at a model 
where more people can simply set up machines and we could federate the results 
back to the main server ?


-  FirefoxOS, Amazon FireOS, Ubuntu folks and other platforms – what is 
your take on this ?

From: mmo...@google.com [mailto:mmo...@google.com] On Behalf Of Michal Mocny
Sent: Tuesday, October 7, 2014 6:06 PM
To: Parashuram Narasimhan (MS OPEN TECH); Max Woghiren
Cc: dev@cordova.apache.org
Subject: Re: FW: Adding Windows tests to ci.cordova.io

David from our team historically took care of most of it, but has moved on to 
other projects.

Max would like to pick up where David left it, and has started to make some 
improvements, but its not really as actively maintained as it was.  Max and I 
will be at PGDay -- would love to discuss more sustainable maintenance of CI 
there, and how best to share effort with other teams.

-Michal

On Tue, Oct 7, 2014 at 5:18 PM, Parashuram Narasimhan (MS OPEN TECH) 
mailto:panar...@microsoft.com>> wrote:
Adding back to dev list – Jesse’s reply was

+1
I would very much like to see this work integrated in the CI. Who is looking 
after the CI?


From: Jesse [mailto:purplecabb...@gmail.com<mailto:purplecabb...@gmail.com>]
Sent: Tuesday, October 7, 2014 2:17 PM
To: Parashuram Narasimhan (MS OPEN TECH)
Subject: Re: Adding Windows tests to ci.cordova.io<http://ci.cordova.io>


@purplecabbage
risingj.com<http://risingj.com><http://risingj.com>

On Tue, Oct 7, 2014 at 11:17 AM, Parashuram Narasimhan (MS OPEN TECH) 
mailto:panar...@microsoft.com><mailto:panar...@microsoft.com<mailto:panar...@microsoft.com>>>
 wrote:
Hi,

Wanted to ping on this thread. What would be the best way to get Windows 
support in the official 
ci.cordova.org<http://ci.cordova.org><http://ci.cordova.org> ?

-Original Message-
From: Maria Bukharina 
[mailto:maria.bukhar...@akvelon.com<mailto:maria.bukhar...@akvelon.com><mailto:maria.bukhar...@akvelon.com<mailto:maria.bukhar...@akvelon.com>>]
Sent: Friday, October 3, 2014 5:51 AM
To: 
dev@cordova.apache.org<mailto:dev@cordova.apache.org><mailto:dev@cordova.apache.org<mailto:dev@cordova.apache.org>>
Subject: Adding Windows tests to 
ci.cordova.io<http://ci.cordova.io><http://ci.cordova.io>

Hi all,

I'm working on improvements of medic tests for Windows platform. We had 
prepared pull request about supporting of Windows Universal Apps 
https://github.com/apache/cordova-medic/pull/16. Seemed that adding Windows 
tests to http://ci.cordova.io/ is stuck. Could we please discuss it again.

By the way is medic autotests are still best practice for testing cordova? 
Seems http://ci.cordova.io/ is broken for a long time. I've found out that last 
successful build of Android_Master was at Sep 23 20:15.

Thanks,
Maria

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

FW: Adding Windows tests to ci.cordova.io

[Parashuram Narasimhan (MS OPEN TECH)]

Adding back to dev list – Jesse’s reply was

+1
I would very much like to see this work integrated in the CI. Who is looking 
after the CI?


From: Jesse [mailto:purplecabb...@gmail.com]
Sent: Tuesday, October 7, 2014 2:17 PM
To: Parashuram Narasimhan (MS OPEN TECH)
Subject: Re: Adding Windows tests to ci.cordova.io


@purplecabbage
risingj.com<http://risingj.com>

On Tue, Oct 7, 2014 at 11:17 AM, Parashuram Narasimhan (MS OPEN TECH) 
mailto:panar...@microsoft.com>> wrote:
Hi,

Wanted to ping on this thread. What would be the best way to get Windows 
support in the official ci.cordova.org<http://ci.cordova.org> ?

-Original Message-
From: Maria Bukharina 
[mailto:maria.bukhar...@akvelon.com<mailto:maria.bukhar...@akvelon.com>]
Sent: Friday, October 3, 2014 5:51 AM
To: dev@cordova.apache.org<mailto:dev@cordova.apache.org>
Subject: Adding Windows tests to ci.cordova.io<http://ci.cordova.io>

Hi all,

I'm working on improvements of medic tests for Windows platform. We had 
prepared pull request about supporting of Windows Universal Apps 
https://github.com/apache/cordova-medic/pull/16. Seemed that adding Windows 
tests to http://ci.cordova.io/ is stuck. Could we please discuss it again.

By the way is medic autotests are still best practice for testing cordova? 
Seems http://ci.cordova.io/ is broken for a long time. I've found out that last 
successful build of Android_Master was at Sep 23 20:15.

Thanks,
Maria

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

RE: Adding Windows tests to ci.cordova.io

[Parashuram Narasimhan (MS OPEN TECH)]

Hi,

Wanted to ping on this thread. What would be the best way to get Windows 
support in the official ci.cordova.org ? 

-Original Message-
From: Maria Bukharina [mailto:maria.bukhar...@akvelon.com] 
Sent: Friday, October 3, 2014 5:51 AM
To: dev@cordova.apache.org
Subject: Adding Windows tests to ci.cordova.io

Hi all,

I'm working on improvements of medic tests for Windows platform. We had 
prepared pull request about supporting of Windows Universal Apps 
https://github.com/apache/cordova-medic/pull/16. Seemed that adding Windows 
tests to http://ci.cordova.io/ is stuck. Could we please discuss it again.

By the way is medic autotests are still best practice for testing cordova? 
Seems http://ci.cordova.io/ is broken for a long time. I've found out that last 
successful build of Android_Master was at Sep 23 20:15.

Thanks,
Maria


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

RE: Independent platform release summary

[Parashuram Narasimhan (MS OPEN TECH)]

Thanks Michael for the document, discussing it would be much easier. 

Do you think we should change the proposal sections to also list the pros/cons 
of each approach? This way, we would also capture various concerns raised in 
this thread. 

-Original Message-
From: mmo...@google.com [mailto:mmo...@google.com] On Behalf Of Michal Mocny
Sent: Tuesday, October 7, 2014 8:52 AM
To: Michal Mocny
Cc: Joe Bowser; dev
Subject: Re: Independent platform release summary

Created a doc to summarize.  Trying to keep it concise and free of 
opinions/conclusions, only context & goals.

https://docs.google.com/document/d/1VqAVo2AA5vZ7LRmq_9jJ6oa7Nyr2OrjLCfEkBhO-X8U/edit?usp=sharing

On Tue, Oct 7, 2014 at 11:02 AM, Michal Mocny  wrote:

> +dev list again :P
>
> The timezone in the doodle is EST but there is a switcher to set your 
> own (surprised it didn't do that).
>
> On Tue, Oct 7, 2014 at 11:01 AM, Joe Bowser  wrote:
>
>> What timezone is this meant for?
>>
>> On Tue, Oct 7, 2014 at 7:59 AM, Michal Mocny  wrote:
>>
>>> Here is a doodle for those interested -- but if this timeline is too 
>>> hasty we can figure out a future date: 
>>> http://doodle.com/a2nd8n3z8dm4ffbx.
>>> I'm
>>> rather busy for two weeks starting next week (as are many of us in 
>>> prep for sh dev conf & pgday) so really hope we can do this this 
>>> week.
>>>
>>> I'll put together a doc outlining some goals/non-goals and the 
>>> current proposals and we can discuss the tradeoffs and brainstorm options.
>>>
>>> -Michal
>>>
>>> On Tue, Oct 7, 2014 at 8:41 AM, Josh Soref 
>>> wrote:
>>>
>>> >
>>> >
>>> > ‎
>>> > > (d) CLI versions completely independent of platforms, just like
>>> plugins.
>>> > > - In this case, we need to implement platform->cli version
>>> requirements
>>> > > (node peerDependancies?)
>>> > > - Basically means we play down CLI version entirely, users are 
>>> > > just expected to stay up to date with CLI always. Platform 
>>> > > versions are
>>> all
>>> > > that matters. I don't think this is too different than what we 
>>> > > have
>>> > today.
>>> >
>>> > I personally like (d) most. ‎
>>> >
>>> > Say we start at 5.0.0 for cli.
>>> > * When a platform updates, we can go to 5.0.1.
>>> >
>>> > * When cli adds a new feature, we can go to 5.1.0.
>>> >
>>> > * When the cli removes a feature/ platform , we can go to 6.0.0.
>>> >
>>> > Mostly, that should take us for 5.0.1000. Or occasionally to 
>>> > 5.2.5000,
>>> and
>>> > rarely to 6.0.5.
>>> >
>>> > Say a platform is at 3.7.0.
>>> > * When a platform makes changes, it goes from 3.7.1.
>>> >
>>> > * When a platform adds a feature, it can go to 3.8.0.
>>> >
>>> > * When a platform drops support for a platform / configuration, it
>>> goes to
>>> > 4.0.0.
>>>
>>
>>
>

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

RE: List replies

[Parashuram Narasimhan (MS OPEN TECH)]

Same issue with outlook client. 

-Original Message-
From: purplecabbage [mailto:purplecabb...@gmail.com] 
Sent: Monday, October 6, 2014 9:05 PM
To: Cordova Dev
Subject: List replies

Anyone know what changed with replies to the list?  They now seem to go 
directly to the poster, and you now must reply-all. This is a strange behavior 
change and I can't tell if it's gmail or dev@cordova.apache.org

Sent from my iPhone
-
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: Build signed archives using CLI

[Parashuram Narasimhan (MS OPEN TECH)]

How about a "cordova package" command, that would be for packaging the app for 
the store? Note that different platforms may have different requirements for 
certs, signing etc. So it may make sense to promote this to a different command 
and let each command take care of packaging the app for the store. This command 
will also mean that developers don’t have to go over to the native projects 
when they finally want to publish their apps to the store.  

-Original Message-
From: Josh Soref [mailto:jso...@blackberry.com] 
Sent: Monday, October 6, 2014 12:46 PM
To: dev
Subject: Re: Build signed archives using CLI

if you do:
Cordova build --release,
The blackberry10 platform will generate a signed image...

On 10/6/14, 3:18 PM, "Andrew Grieve"  wrote:

>AFAIK, I don't think there's any technical roadblocks. Just need a 
>proposal for how it should look, and then a patch & docs to add it!
>
>For Android's hot-off-the-press gradle support, you can set an 
>environment variable that points to a .properties file for signing 
>builds. This shows one way to go about it, but I'm not in love with the 
>.properties idea.
>
>On Mon, Oct 6, 2014 at 2:48 PM, Victor Sosa 
>wrote:
>
>> Hi community.
>>
>> Been looking at this topic and wondering why the build command does 
>>not  create signed archives.  Digging a little bit found a lot of 
>>differences in  the platforms to create these archives.
>>
>> For instance, in Android you need to
>> 1. Export your APK in release mode (--release flag) 2. Sign your APK 
>> (you already need a RSA key)
>>
>> In iOS, you need to:
>> 1. Export your APP using --device flag (--release seems to export for  
>>emulator only)  2. Either use XCode (UI-based) and sign the archive or 
>>use xcrun (headless
>> process)
>>
>> Besides these differences, what is preventing Cordova from providing 
>> a generic one-way to build these signed, ready-to-publish archives?
>>
>> Perhaps I'm missing something here...?  I really appreciate your 
>>insights  on this topic
>>
>> Thanks!
>>
>> --
>> Victor Adrian Sosa Herrera
>> IBM Software Engineer
>> Guadalajara, Jalisco
>>


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

RE: [VOTE] Tools Release

[Parashuram Narasimhan (MS OPEN TECH)]

Should we simply cherry pick that comment out and go ahead with the release? 
The existing latest release (3.6.4) has a bunch of bugs in the Windows platform 
that need to be fixed. 

-Original Message-
From: iclell...@google.com [mailto:iclell...@google.com] On Behalf Of Ian 
Clelland
Sent: Monday, October 6, 2014 7:57 AM
To: Steven Gill
Cc: Shazron; dev@cordova.apache.org
Subject: Re: [VOTE] Tools Release

FYI, I just opened CB-7718 as a blocking issue against CordovaLib. I haven't 
tracked down the cause (except that it's somewhere in the CB-6481
code) but if we were to re-open the vote, I'd have to -1 it.

On Fri, Oct 3, 2014 at 7:39 PM, Steven Gill  wrote:

> Okay, taking this discussion back into "independent platform release 
> summary" thread
>
> On Fri, Oct 3, 2014 at 4:21 PM, Shazron  wrote:
>
> > Did we have consensus on 4.0 though? I would think a bigger version 
> > would increase separation - and that's what I sensed consensus on. 
> > After a few releases, the cordova platforms will already be at 4.0, 
> > and we're at
> square
> > one.
> >
> > On Fri, Oct 3, 2014 at 2:38 PM, Steven Gill 
> > wrote:
> >
> >> I am going to close this vote and redo it with CLI + Lib versioning 
> >> set
> to
> >> 4.0.0
> >>
> >> On Thu, Oct 2, 2014 at 7:37 AM, Steven Gill 
> >> 
> >> wrote:
> >>
> >> > I must have forgot to run svn up. I'll do it soon when I get to 
> >> > my computer.
> >> >
> >> >
> >> > On Thursday, October 2, 2014, Sergey Grebnov (Akvelon) < 
> >> > v-seg...@microsoft.com> wrote:
> >> >
> >> >> I don't see Tools packages on
> >> >> https://dist.apache.org/repos/dist/dev/cordova/CB-7661/
> >> >> Am I looking to wrong location?
> >> >>
> >> >> Thx!
> >> >> Sergey
> >> >> -Original Message-
> >> >> From: Steven Gill [mailto:stevengil...@gmail.com]
> >> >> Sent: Thursday, October 2, 2014 3:14 AM
> >> >> To: dev@cordova.apache.org
> >> >> Subject: [VOTE] Tools Release
> >> >>
> >> >> Please review and vote on this Tools Release.
> >> >>
> >> >> Release issue: https://issues.apache.org/jira/browse/CB-7661
> >> >>
> >> >> Both tools have been published to 
> >> >> dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-7661/
> >> >>
> >> >> The packages were published from their corresponding git tags:
> >> >>
> >> >> cordova-js: 3.7.0 (d84626637e)
> >> >> cordova-lib: 3.7.0 (329275484b)
> >> >> cordova-plugman: 0.22.11 (6ac534395a)
> >> >> cordova-cli: 3.7.0 (88e0c3ac00)
> >> >>
> >> >> You can test the cli by running npm install -g cordova@rc
> >> >>
> >> >> To test Android, Browser, Windows, WP, use --usegit flag when 
> >> >> adding
> >> them
> >> >> to your project.
> >> >> ex. cordova platform add android --usegit
> >> >>
> >> >>
> >> >> As you can see, in this release I have made the cli semver compliant.
> >> >> The version is now 3.7.0.
> >> >> I have also made cordova-lib's version 3.7.0 to sync up the two. 
> >> >> If
> you
> >> >> have any issues with this, lets discuss.
> >> >>
> >> >>
> >> >> Upon a successful vote I will upload the archives to dist/, 
> >> >> publish
> >> them
> >> >> to NPM, and post the corresponding blog post.
> >> >>
> >> >> Voting guidelines:
> >> >>
> >>
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting
> .md
> >> >>
> >> >> Voting will go on for a minimum of 48 hours.
> >> >>
> >> >> I vote +1:
> >> >> * Ran coho audit-license-headers over the relevant repos
> >> >> * Used `license-checker` to ensure all dependencies have 
> >> >> Apache-compatible licenses
> >> >>
> >> >
> >>
> >
> >
>

RE: Independent platform release summary

[Parashuram Narasimhan (MS OPEN TECH)]

Would jumping to 4.x mean we have to re-tag restart the vote process? 
Traditionally, Cordova has had major version bump close to Phonegap day - If we 
continue this to be 3.7.0, will we have another release close to Phonegap day, 
calling that 4.0 ? 

-Original Message-
From: brian.ler...@gmail.com [mailto:brian.ler...@gmail.com] On Behalf Of Brian 
LeRoux
Sent: Thursday, October 2, 2014 12:58 PM
To: Steven Gill
Cc: Shazron; dev@cordova.apache.org
Subject: Re: Independent platform release summary

I'm down with jumping to 4.x but not convinced a jump to 5.x would actually 
spur more understanding. (Also thanks for tackling this Steve.)

On Thu, Oct 2, 2014 at 9:00 PM, Steven Gill  wrote:

> I'm not opposed to a big version jump. It would draw attention to the 
> fact that we are changing our versioning & releasing process. How do 
> others feel?
>
> -Steve
>
> On Thu, Oct 2, 2014 at 11:45 AM, Shazron  wrote:
>
> > Thanks Steve for writing that up.
> > I can definitely see the confusion in messaging, especially at the 
> > start of this new process.
> >
> > So for "2) CLI + Lib version" I am proposing a radical idea (à la 
> > Windows
> > 10) where we jump to a new version totally separate from the current 
> > 3.x series to further detach the association of the CLI version with 
> > platform versions. Version 5.x? Not sure how sem-ver kosher it is.
> >
> > I already have one scenario. I sent out pull requests for docs and 
> > the
> CLI
> > for the new iPhone 6 icons and splash screens. These will be in the 
> > next iOS platform release 3.7.0, and if another platform didn't take 
> > 3.8.0 already, most likely CLI 3.8.0.
> >
> > This would mean the docs would be at 3.8.0, CLI at 3.8.0 but 
> > cordova-ios will be at 3.7.0. This is how the messaging will look 
> > like if I were to write a blog post:
> > "To get cordova-cli support for iPhone 6 splash screens and icons, 
> > please update to cordova-cli 3.8.0, which will grab the 3.7.0 
> > version of cordova-ios where this feature is implemented. Check out 
> > the 3.8.0 cordova-docs for usage". A bit clunky.
> >
> >
> >
> >
> >
> > On Thu, Oct 2, 2014 at 11:28 AM, Steven Gill 
> > 
> > wrote:
> >
> >> Hey All,
> >>
> >> I wanted to give summary of where I believe this process is going 
> >> and answer any questions you all might have. None of this is set in 
> >> stone,
> so
> >> please provide feedback so we can iron this out.
> >>
> >> 1) Platforms can now release independently
> >>
> >> If iOS wants to release 3.7.0, it doesn't have to wait for other
> platforms
> >> to be ready to release. Just run through
> >>
> >>
> https://github.com/apache/cordova-coho/blob/master/docs/platforms-rele
> ase-process.md
> >> and do a tools release.
> >>
> >> 2) CLI + Lib version will rise very quickly.
> >>
> >> Right now, CLI is about to be released at version 3.7.0. No 
> >> platforms
> are
> >> currently at version 3.7.0. Say iOS wants to release 3.7.0 next 
> >> week,
> they
> >> could do that, update the CLI to version 3.8.0. I suggest a 
> >> platform
> being
> >> released would cause the CLI to do a minor release 
> >> (MAJOR.MINOR.PATCH -> 3.8.0). But this is obviously open to discussion.
> >>
> >> 3) Docs
> >>
> >> Docs version will now be tied to CLI. If we do a major or minor 
> >> release
> of
> >> the CLI, docs should be regenerated to match the version of the 
> >> CLI. Say iOS 3.7.0 requires the newest version of the CLI, we can 
> >> make note of
> that
> >> in docs + blog post. Maybe we list the platform versions associated 
> >> to
> CLI
> >> somewhere in the docs?
> >>
> >> 4) Helping users debug
> >>
> >> Cordova.version & cordova.platformVersion will both return the 
> >> version
> of
> >> the platform, not the cli. Users can easily tell you what version 
> >> of cordova-platform they are using by doing this. Generated 
> >> cordova.js
> files
> >> in projects will also have this information at the top of the file 
> >> along with commit hash.
> >>
> >> 5) Messaging
> >>
> >> We need to be clear about this in our messaging to users. This is a
> change
> >> from how we have been doing things and I foresee some confusion at 
> >> the beginning. Moving platforms over to package.json eventually 
> >> will help users see that platforms are independent, but we need to 
> >> do more now to help users adapt to this change.
> >>
> >> They need to know to expect the CLI version to jump quickly, and to 
> >> know that platform versions != cordova-cli version.
> >>
> >> Blog posts can list platforms cli was tested with, similarly to how 
> >> we list what plugin versions the cli was tested with when 
> >> releasing. (see the bottom of 
> >> http://cordova.apache.org/announcements/2014/09/22/cordova-361.html 
> >> for an
> >> example)
> >>
> >> Hopefully I didn't leave out anything major. Feedback please!
> >>
> >
> >
>

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
F

3.6.0 and version of Git

[Parashuram Narasimhan (MS OPEN TECH)]

Folks from the VS team discovered an interesting bug and I wanted to understand 
if this is something that we would like to fix in Cordova

Tl;Dr; - Cordova 3.6.0 version only seems to support Git 1.9.0. Git 1.8.3 seems 
to have issues. Should we simply document this and leave it, or should we try 
to add support for git 1.8.3 also?

Details

Here is the error you will see when trying to install a plugin from a git URI 
with 1.8.3:

C:\>cordova plugin add https://github.com/a
pache/cordova-plugin-camera.git
Fetching plugin "https://github.com/apache/cordova-plugin-camera.git"; via git cl
one
Error: Command failed: fatal: could not create work tree dir 'C:\User\Ap
pData\Local\Temp\plugman\git\1412264624317'.: No such file or directory

at ChildProcess.exithandler (child_process.js:637:15)
at ChildProcess.EventEmitter.emit (events.js:98:17)
at maybeClose (child_process.js:743:16)
at Socket. (child_process.js:956:11)
at Socket.EventEmitter.emit (events.js:95:17)
at Pipe.close (net.js:465:12)

RE: [VOTE] 3.6.4 Windows Release

[Parashuram Narasimhan (MS OPEN TECH)]

Should that not be a part of the plugin release? This is a vote for the 
platform release - does the fix impact the platform too ? 

-Original Message-
From: Maxime LUCE [mailto:max...@touchify.co] 
Sent: Thursday, October 2, 2014 3:34 AM
To: dev@cordova.apache.org
Subject: RE: [VOTE] 3.6.4 Windows Release

-

There is a bug fix for big file write on Windows 8 and Windows platforms in 
cordova-plugin-file !
It could be a good idea to review and merge this fix !

Cordialement.


Maxime LUCE
Touchify, CEO

+33 6 28 60 72 34 | skype: maximeluce
max...@touchify.co | http://touchify.co


-Message d'origine-
De : Parashuram Narasimhan (MS OPEN TECH) [mailto:panar...@microsoft.com] 
Envoyé : mercredi 1 octobre 2014 19:47 À : dev@cordova.apache.org Objet : RE: 
[VOTE] 3.6.4 Windows Release

Sorry, I meant leaving it as is works. Since this will be published in the blog 
post, we don't have to restart the vote.   

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com]
Sent: Wednesday, October 1, 2014 10:20 AM
To: dev@cordova.apache.org
Subject: Re: [VOTE] 3.6.4 Windows Release

So you want me to move releasenotes in 3.6.x branch and restart the votes?
Just clarifying

On Wed, Oct 1, 2014 at 10:13 AM, Parashuram Narasimhan (MS OPEN TECH) < 
panar...@microsoft.com> wrote:

> I think moving RELEASENotes works good. +1 on the vote.
>
> -Original Message-
> From: Steven Gill [mailto:stevengil...@gmail.com]
> Sent: Wednesday, October 1, 2014 10:06 AM
> To: dev@cordova.apache.org
> Subject: Re: [VOTE] 3.6.4 Windows Release
>
> Windows and WP8 will be missing release notes because we are using npm 
> pack to package and the packaged directory is a subdirectory in the repo.
> RELEASENOTES.md is in the root.
>
> This is the last release where the package directory is a sub directory.
> Master for both those repos have moved all files to the root 
> (including package.json). Future releases will include RELEASENOTES.md.
>
> We could move RELEASENOTES.md into the sub directory on the 3.6.x 
> branch for both repos and retag. I don't think it is necessary since 
> the notes will be posted in the blog post, but if people feel strongly 
> about including it, I will go ahead and do it.
>
>
>
> On Wed, Oct 1, 2014 at 9:56 AM, Sergey Grebnov (Akvelon) < 
> v-seg...@microsoft.com> wrote:
>
> > I vote +1
> > *   Checked package files - there is missing RELEASENOTES.md file
> > *   Ran coho verify-archive over the relevant repo
> > *   Verified ability to create and run Cordova app with windows
> > platform
> > *   Tested building and running app with --phone, --win, --archs
> flags
> > (successfully build and run)
> > *   Validated created apps via Cert Kit
> > *   Verified supporting of --target key
> > *   Run medic tests
> >
> > Missing RELEASENOTES file is not a critical bag, so I still vote +1.
> >
> > Thx!
> > Sergey
> >
> > -Original Message-
> > From: Steven Gill [mailto:stevengil...@gmail.com]
> > Sent: Wednesday, October 1, 2014 2:05 AM
> > To: dev@cordova.apache.org
> > Subject: [VOTE] 3.6.4 Windows Release
> >
> > Please review and vote on this 3.6.4 Windows Release.
> >
> > Release issue: https://issues.apache.org/jira/browse/CB-7661
> >
> > Repos ready to be released have been published to
> > dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-7661
> >
> > The package was published from its corresponding git tag:
> > cordova-windows: 3.6.4 (b940eca6fe)
> >
> > Upon a successful vote I will upload the archive to dist/, publish 
> > it to NPM, and post the corresponding blog post.
> > Voting guidelines:
> > https://github.com/apache/cordova-coho/blob/master/docs/release-voti
> > ng .md Voting will go on for a minimum of 48 hours.
> >
> > I vote +1:
> > * Ran coho audit-license-headers over the relevant repos
> > * Used `license-checker` to ensure all dependencies have 
> > Apache-compatible licenses
> >
>

RE: [VOTE] 3.6.4 Windows Release

[Parashuram Narasimhan (MS OPEN TECH)]

Sorry, I meant leaving it as is works. Since this will be published in the blog 
post, we don't have to restart the vote.   

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Wednesday, October 1, 2014 10:20 AM
To: dev@cordova.apache.org
Subject: Re: [VOTE] 3.6.4 Windows Release

So you want me to move releasenotes in 3.6.x branch and restart the votes?
Just clarifying

On Wed, Oct 1, 2014 at 10:13 AM, Parashuram Narasimhan (MS OPEN TECH) < 
panar...@microsoft.com> wrote:

> I think moving RELEASENotes works good. +1 on the vote.
>
> -Original Message-
> From: Steven Gill [mailto:stevengil...@gmail.com]
> Sent: Wednesday, October 1, 2014 10:06 AM
> To: dev@cordova.apache.org
> Subject: Re: [VOTE] 3.6.4 Windows Release
>
> Windows and WP8 will be missing release notes because we are using npm 
> pack to package and the packaged directory is a subdirectory in the repo.
> RELEASENOTES.md is in the root.
>
> This is the last release where the package directory is a sub directory.
> Master for both those repos have moved all files to the root 
> (including package.json). Future releases will include RELEASENOTES.md.
>
> We could move RELEASENOTES.md into the sub directory on the 3.6.x 
> branch for both repos and retag. I don't think it is necessary since 
> the notes will be posted in the blog post, but if people feel strongly 
> about including it, I will go ahead and do it.
>
>
>
> On Wed, Oct 1, 2014 at 9:56 AM, Sergey Grebnov (Akvelon) < 
> v-seg...@microsoft.com> wrote:
>
> > I vote +1
> > *   Checked package files - there is missing RELEASENOTES.md file
> > *   Ran coho verify-archive over the relevant repo
> > *   Verified ability to create and run Cordova app with windows
> > platform
> > *   Tested building and running app with --phone, --win, --archs
> flags
> > (successfully build and run)
> > *   Validated created apps via Cert Kit
> > *   Verified supporting of --target key
> > *   Run medic tests
> >
> > Missing RELEASENOTES file is not a critical bag, so I still vote +1.
> >
> > Thx!
> > Sergey
> >
> > -Original Message-
> > From: Steven Gill [mailto:stevengil...@gmail.com]
> > Sent: Wednesday, October 1, 2014 2:05 AM
> > To: dev@cordova.apache.org
> > Subject: [VOTE] 3.6.4 Windows Release
> >
> > Please review and vote on this 3.6.4 Windows Release.
> >
> > Release issue: https://issues.apache.org/jira/browse/CB-7661
> >
> > Repos ready to be released have been published to
> > dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-7661
> >
> > The package was published from its corresponding git tag:
> > cordova-windows: 3.6.4 (b940eca6fe)
> >
> > Upon a successful vote I will upload the archive to dist/, publish 
> > it to NPM, and post the corresponding blog post.
> > Voting guidelines:
> > https://github.com/apache/cordova-coho/blob/master/docs/release-voti
> > ng .md Voting will go on for a minimum of 48 hours.
> >
> > I vote +1:
> > * Ran coho audit-license-headers over the relevant repos
> > * Used `license-checker` to ensure all dependencies have 
> > Apache-compatible licenses
> >
>

RE: [VOTE] 3.6.4 Windows Release

[Parashuram Narasimhan (MS OPEN TECH)]

I think moving RELEASENotes works good. +1 on the vote. 

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Wednesday, October 1, 2014 10:06 AM
To: dev@cordova.apache.org
Subject: Re: [VOTE] 3.6.4 Windows Release

Windows and WP8 will be missing release notes because we are using npm pack to 
package and the packaged directory is a subdirectory in the repo.
RELEASENOTES.md is in the root.

This is the last release where the package directory is a sub directory.
Master for both those repos have moved all files to the root (including 
package.json). Future releases will include RELEASENOTES.md.

We could move RELEASENOTES.md into the sub directory on the 3.6.x branch for 
both repos and retag. I don't think it is necessary since the notes will be 
posted in the blog post, but if people feel strongly about including it, I will 
go ahead and do it.



On Wed, Oct 1, 2014 at 9:56 AM, Sergey Grebnov (Akvelon) < 
v-seg...@microsoft.com> wrote:

> I vote +1
> *   Checked package files - there is missing RELEASENOTES.md file
> *   Ran coho verify-archive over the relevant repo
> *   Verified ability to create and run Cordova app with windows
> platform
> *   Tested building and running app with --phone, --win, --archs flags
> (successfully build and run)
> *   Validated created apps via Cert Kit
> *   Verified supporting of --target key
> *   Run medic tests
>
> Missing RELEASENOTES file is not a critical bag, so I still vote +1.
>
> Thx!
> Sergey
>
> -Original Message-
> From: Steven Gill [mailto:stevengil...@gmail.com]
> Sent: Wednesday, October 1, 2014 2:05 AM
> To: dev@cordova.apache.org
> Subject: [VOTE] 3.6.4 Windows Release
>
> Please review and vote on this 3.6.4 Windows Release.
>
> Release issue: https://issues.apache.org/jira/browse/CB-7661
>
> Repos ready to be released have been published to
> dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-7661
>
> The package was published from its corresponding git tag:
> cordova-windows: 3.6.4 (b940eca6fe)
>
> Upon a successful vote I will upload the archive to dist/, publish it 
> to NPM, and post the corresponding blog post.
> Voting guidelines:
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting
> .md Voting will go on for a minimum of 48 hours.
>
> I vote +1:
> * Ran coho audit-license-headers over the relevant repos
> * Used `license-checker` to ensure all dependencies have 
> Apache-compatible licenses
>

Re: Next Cordova Release

[Parashuram Narasimhan (MS OPEN TECH)]

Awesome, thanks steve. Please do let us know if there is anything we can
help you with. 

On 9/29/14, 11:03 AM, "Steven Gill"  wrote:

>Alright lets do this!
>
>Releasing:
>Cordova-Android 3.6.4
>Cordova-Windows 3.6.4
>Cordova-WP8 3.6.4
>Cordova-Browser 3.6.0
>
>Cordova-Lib 0.21.14
>Cordova-JS 3.7.0
>Cordova-Plugman 0.22.11
>Cordova-CLI 3.7.0
>I think it is a good time to drop the cadVer-SemVer versioning for the
>CLI.
>Lets just make it SemVer but start from 3.7.0
>
>1) Release issue:
> - coho create-release-bug is supposed to be used for cadence releases. It
>won't make sense when we aren't release every platform. We will have to
>create the release issue manually. This is what we have been doing for
>tools releases for a while now.
>
>2) Platform version files should be bumped using coho. Coho also goes in
>and changes the version script output for many of the platforms (all
>except
>windows ones last I saw)
>
>3) I like this idea. I personally think we should test it thoroughly
>before
>we push it live though. Not sure what problems might arise. If people feel
>confident with releasing this change and have tested it, I won't stand in
>the way of it being released.
>
>I recently merged in my Indy platform release work. I want to take this
>release to go through the process and fix any problems that come up. You
>can see the doc at
>https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-
>process.md.
>Sergey, I can work with you on this or, if you don't mind, I can take over
>from here.
>
>-Steve
>
>
>On Mon, Sep 29, 2014 at 2:45 AM, Sergey Grebnov (Akvelon) <
>v-seg...@microsoft.com> wrote:
>
>> Hi, here are release branches:
>>
>> https://github.com/apache/cordova-cli/tree/rb_3.6.4-0.21.14
>> https://github.com/apache/cordova-lib/tree/rb_0.21.14
>>
>> https://github.com/apache/cordova-android/tree/3.6.x
>> https://github.com/apache/cordova-windows/tree/3.6.x
>> https://github.com/apache/cordova-wp8/tree/3.6.x
>>
>> I've not updated versions and added tags due to the following
>> questions/issues:
>>
>> 1. I wanted to create release issue to use while updating version files
>> but it is not possible since we don't have 3.6.4 version in JIRA. Could
>> someone create it?
>> λ coho create-release-bug --version=3.6.4
>>Cannot find version ID number in JIRA related to "root" version
>>string:
>> 3.6.4
>>
>> 2. Is it ok to bump platform version files manually? - I see we mixed
>>coho
>> and manual edits during 3.6.3 release.
>>
>> 3. What do you think if we change depending platform versions in
>> platforms.js [1] to 3.6 (or 3.6.x) instead of 3.6.3/4?  This way we
>>will be
>> able to release 3.6.4 for ios, bb, other platforms w/o TOOLS release.
>>Same
>> if we want to release 3.6.5 version of some platform later.
>> * npm cache logic used in LIB seems to correctly handle this
>>case
>> and download updated platform version when it is available on npm
>> * for --usegit option we can have 3.6 tag along with 3.6.3 and
>> 3.6.4  so this will work as well
>>
>> [1]
>> 
>>https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova
>>/platforms.js
>>
>> Thx!
>> Sergey
>>
>> -Original Message-
>> From: Jesse [mailto:purplecabb...@gmail.com]
>> Sent: Saturday, September 27, 2014 2:20 AM
>> To: dev@cordova.apache.org
>> Subject: Re: Next Cordova Release
>>
>> Yes, 3.6.x branch and tag it when it is ready.
>> then they can also be cherry-picked into master, or you could commit
>>them
>> into master, and cherry-pick them into the 3.6.x branch ...
>>
>> @purplecabbage
>> risingj.com
>>
>> On Fri, Sep 26, 2014 at 9:08 AM, Marcel Kinard 
>>wrote:
>>
>> > I'd suggest pushing the commits on to the end of the 3.6.x branch, and
>> > then tag it 3.6.4.
>> >
>> > On Sep 26, 2014, at 11:58 AM, Sergey Grebnov (Akvelon) <
>> > v-seg...@microsoft.com> wrote:
>> >
>> > > Hi, I’ve created the following repos for 3.6.4 release and going to
>> > > push
>> > them to apache. Should I use 3.6.x branch and create a new 3.6.4 tag
>> > or
>> > 3.6.4 branch?
>> >
>> >
>>

Re: Removed Windows7 which is now in its own branch

[Parashuram Narasimhan (MS OPEN TECH)]

Are you looking at this Windows 7 code ?

https://github.com/apache/cordova-windows/tree/Win32 ?

From: Ming Zhu mailto:zhu.m...@icloud.com>>
Reply-To: "dev@cordova.apache.org" 
mailto:dev@cordova.apache.org>>
Date: Monday, September 29, 2014 at 10:30 AM
To: "dev@cordova.apache.org" 
mailto:dev@cordova.apache.org>>
Subject: Removed Windows7 which is now in its own branch

Hi Guys,

In the latest release note, it was written

  *   Removed Windows7 which is now in its own branch

I suppose this means Windows7 (for laptop/desktop) not for WP7, right?
Does anyone know where I can find this branch?


br,
Michael

Next Cordova Release

[Parashuram Narasimhan (MS OPEN TECH)]

Marcel, thank you for driving the Cordova tools release - 3.6.3.

There are a few bugs that we discovered in this release that we would like to 
fix. These are not major to require a full major version bump, but regressions 
that should be fixed. The bugs we would like to get into a release are


1.   Windows and Wp8 platform

a.   --target flag is not supported in the Windows platforms. Given the new 
support for Windows 8, Windows 8.1 and Windows Phone 8.1 this is important as 
it lets users choose a way to run the app on specific emulators

2.   Android

a.   The --nobuild flag for run seems to be broken now.

b.  If possible we would also like to get the patch for Cordova activity 
name so that Unicode characters can be used for Android apps.

   i.  Does 
this change also need to be made in Amazon FireOS? Archana, should we send in a 
pull request for that ?

3.   Tools

a.   The community has agreed on the hooks implementation and this is done 
now.

Will the next release be 4.0, and when is it planned for? If it is a month 
away, can we cherry pick these changes into 3.6.3 and make a 3.6.4 release 
before that ? Are there other bug fixes that people want to go in a next 
release.

We can volunteer to do the next release (with consultation from Marcel if 
possible, since he is now knows the release process).

RE: [DISCUSS] shrinkwrap

[Parashuram Narasimhan (MS OPEN TECH)]

Also a quick question. Will we be withholding the 3.6.* release till we resolve 
this discussion? 

-Original Message-
From: mikeywbro...@gmail.com [mailto:mikeywbro...@gmail.com] On Behalf Of 
Michael Brooks
Sent: Thursday, September 18, 2014 12:18 PM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] shrinkwrap

Personally, I've never got into shrinkwrap. In my opinion, it's another barrier 
to contribution and another place for mistakes to be made.

I prefer on the old-school "shrinkwrap" approach, which is explicitly 
specifying each dependency version:
https://github.com/phonegap/phonegap-cli/blob/master/package.json#L29-L40

Discrete and explicit commits mark where and when dependencies are upgraded:
https://github.com/phonegap/phonegap-cli/commit/e6d68e47a3a5cf4e9e6308467a6ae7716f6c5f9d

It's clean. It's simple. It's an `npm install` away.

With that said, shrinkwrap can be useful when our projects are using a fork of 
a dependency that hasn't accepted our patch. Do we have that use case in 
Cordova?

In general, I lean the approach that is simpler, less error prone, and 
encourages new contributors.

Thanks for starting this discussion Marcel!
Michael

On Thu, Sep 18, 2014 at 11:55 AM, Mark Koudritsky  wrote:

> >
> >
> > Mark,
> >   I want to understand better your statement "resulted in a great 
> > deal of confusion for contributors". Can you give more details about that.
>
>
> One simple case I had myself was when debugging a suspected problem 
> with one of dependencies and wasting several hours to only discover 
> that the dependency version setting in package.json was ignored due to 
> presence of npm-shrinkwrap. It's stupid simple, but since shrinkwrap 
> is not a very common tool, people are not aware of it, or just forget that 
> it's there.
> While for us it's the center of this discussion, the average cordova 
> contributor is likely to not even remember what the decision was about 
> which repos should contain it when etc.
>

RE: cordova push plugin release

[Parashuram Narasimhan (MS OPEN TECH)]

Hi Erik, 

Where is this push plugin available ? 

-Original Message-
From: Erik Jan de Wit [mailto:ede...@redhat.com] 
Sent: Tuesday, September 16, 2014 5:44 AM
To: dev@cordova.apache.org
Subject: Re: cordova push plugin release

Ultimate goal is to enable swift as a language to create plugins with

On 16 Sep,2014, at 11:41 , Erik Jan de Wit  wrote:

> Hi all,
> 
> After testing we are happy to announce that the 1.0.1 version of the cordova 
> push plugin has been released. Thanks to everyone for testing and making this 
> release happen. The reason for this point release was an error in the android 
> dependencies of the plugin making it unusable.
> 
> Happy coding,
>   Erik Jan

RE: [DISCUSS] shrinkwrap

[Parashuram Narasimhan (MS OPEN TECH)]

If we do have shrinkwrap in git at all times, who would be responsible for 
updating not only the versions of our dependencies, but also the dependencies 
of these dependencies? 

Why should cordova-lib and cordova-plugman not have shrinkwraps? Not all tools 
use cordova-cli as a way to build cordova apps. There were also discussions 
about using cordova-lib being the public API to build apps. If that is the 
case, judging by our shrinkwrap philosophy, we need that file on all repos that 
we say are public API. 

-Original Message-
From: Mark Koudritsky [mailto:kam...@google.com] 
Sent: Thursday, September 18, 2014 7:21 AM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] shrinkwrap

>
> I suggest that:
> - The shrinkwrap exist in git at all times, not just during the 
> release process.
>
-1 for that. Having shrinkwrap at all times will result in postponed discovery 
of incompatibilities with newer versions (which are usually trickier than 
shrinkwrap problems) until you nuke node_modules during release. From my 
experience for repos that had it, it also resulted in a great deal of confusion 
for contributors.

- At the beginning of a new dev/test cycle in a project that has a
> shrinkwrap, developers should not only "git pull", but should also "rm 
> -r node_modules ; npm install".
>
+1, no need to use shrinkwrap in cordova-lib, only cordova-cli and
cordova-plugman (they don't depend on each other now, both contain executables 
calling into cordova-lib).

RE: [DISCUSS] continuous build and release process

[Parashuram Narasimhan (MS OPEN TECH)]

About the release branches, is the idea that we continue to push stuff on 
master and then create a new 3.7.0 branch when we would like to release 3.7.0? 
I am guessing that this would be for platforms and the tools. How would this 
look when the platforms start getting released independently (we don’t have to 
answer that now, but I guess we will look at it when platforms do get released 
independently). 

In addition to release branches, should we also ensure that feature branches 
are strictly followed - i.e. master is always stable? 
I am guessing that these release branches will live on forever and in case of 
security patches, we would go back and apply them to the each branch? 

About buildbot, we also run our tests on buildbot. Is there a way to buildbot 
master to be hosted by Apache infra, and all of us federate machines and test 
results to build bot? I am guessing that 1 person cannot run tests for all 
platforms, so it makes sense to have a way to let multiple people contribute 
platform specific slaves/device walls where these tests are run. 

-Original Message-
From: Mark Koudritsky [mailto:kam...@google.com] 
Sent: Thursday, September 18, 2014 7:51 AM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] continuous build and release process

+1 for release branches, reverting version bumps feels really awkward
+1 for more continuous integration. And just to make sure more people 
+are
aware of it, there is this buildbot running some CI 
http://108.170.217.131:8010/waterfall

A half baked idea for a more automated release process:
Talking only about the tools releases for now as I don't have experience with 
releasing the other parts.
The idea is to have it scripted in two stages with all the human input 
concentrated between the two stages. The first stage would automatically 
collect some info and write out a "release config file" with values that need 
to be decided upon by humans. The release manager then edits that file (maybe 
even gets it reviewed/approved by others). Then the second automated stage 
would use that config file to prepare artifacts ready for voting.
Coho already does much of that, but with the current release process [1] human 
inputs are spread between many points along the way which prevents more 
automation.

[1]
https://github.com/apache/cordova-coho/blob/master/docs/tools-release-process.md
​

RE: [Vote] 3.6.1 Cadence Release 3rd attempt

[Parashuram Narasimhan (MS OPEN TECH)]

I looked at the voting process and it seems to say that the 72 hour window is a 
recommendation. Given that we have all verified the code multiple times and the 
community agrees that this is only a version bump, can we close the vote if we 
have 3 +1 votes ? 

>From the policy - 

Release policy describes the voting process as:
"Votes on whether a package is ready to be released use majority approval -- 
i.e., at least three PMC members must vote affirmatively for release, and there 
must be more positive than negative votes. Releases may not be vetoed. Before 
voting +1 PMC members are required to download the signed source code package, 
compile it as provided, and test the resulting executable on their own 
platform, along with also verifying that the package meets the requirements of 
the ASF policy on releases." http://apache.org/dev/release.html


Majority Approval is defined as:
"Refers to a vote (sense 1) which has completed with at least three binding +1 
votes and more +1 votes than -1 votes. ( I.e. , a simple majority with a 
minimum quorum of three positive votes.) Note that in votes requiring majority 
approval a -1 vote is simply a vote against, not a veto. Compare Consensus 
Approval. See also the description of the voting process." 
http://www.apache.org/foundation/glossary.html#MajorityApproval

The voting process includes: "Votes should generally be permitted to run for at 
least 72 hours to provide an opportunity for all concerned persons to 
participate regardless of their geographic locations." 
http://www.apache.org/foundation/voting.html


-Original Message-
From: Marcel Kinard [mailto:cmarc...@gmail.com] 
Sent: Monday, September 15, 2014 11:32 AM
To: dev@cordova.apache.org
Subject: Re: [Vote] 3.6.1 Cadence Release 3rd attempt

Yes, it started Friday afternoon: 
http://callback-dev.markmail.org/thread/dugazo5xrfvnqw32

Note that it is not a new attempt at 3.6.1, instead it is a version bump to 
3.6.3 due to npm registry requirements.

I was about to poke the thread, since the 72 hour mark will be reached this 
afternoon. So yes, please test and vote! The more the merrier (at least up 
through 3 ;-)

On Sep 15, 2014, at 2:28 PM, Parashuram Narasimhan (MS OPEN TECH) 
 wrote:

> Wanted to check if the vote for 3.6.3 started? We wanted to start running our 
> tests for the vote.  

RE: [Vote] 3.6.1 Cadence Release 3rd attempt

[Parashuram Narasimhan (MS OPEN TECH)]

Never mind - found the thread. Given that this is re-packaging, do we still 
have to wait for the 72 hour window?  

-Original Message-
From: Parashuram Narasimhan (MS OPEN TECH) [mailto:panar...@microsoft.com] 
Sent: Monday, September 15, 2014 11:28 AM
To: dev@cordova.apache.org
Subject: RE: [Vote] 3.6.1 Cadence Release 3rd attempt

Hi,

Wanted to check if the vote for 3.6.3 started? We wanted to start running our 
tests for the vote.  

-Original Message-
From: Shazron [mailto:shaz...@gmail.com]
Sent: Friday, September 12, 2014 11:19 AM
To: dev@cordova.apache.org
Subject: Re: [Vote] 3.6.1 Cadence Release 3rd attempt

+1 for Andrew's idea, makes sense.

On Fri, Sep 12, 2014 at 11:06 AM, Marcel Kinard  wrote:

>
> On Sep 12, 2014, at 1:26 PM, Andrew Grieve  wrote:
>
> > We might in the future consider pinning CLI to download 3.6.x so 
> > that it will automatically pick up point releases for times like this.
> > Don't think the logic's i there now for that though.
>
> We don't frequently do point releases, but I still like that idea. I 
> created https://issues.apache.org/jira/browse/CB-7537 to capture this 
> idea. Thanks!

RE: [Vote] 3.6.1 Cadence Release 3rd attempt

[Parashuram Narasimhan (MS OPEN TECH)]

Hi,

Wanted to check if the vote for 3.6.3 started? We wanted to start running our 
tests for the vote.  

-Original Message-
From: Shazron [mailto:shaz...@gmail.com] 
Sent: Friday, September 12, 2014 11:19 AM
To: dev@cordova.apache.org
Subject: Re: [Vote] 3.6.1 Cadence Release 3rd attempt

+1 for Andrew's idea, makes sense.

On Fri, Sep 12, 2014 at 11:06 AM, Marcel Kinard  wrote:

>
> On Sep 12, 2014, at 1:26 PM, Andrew Grieve  wrote:
>
> > We might in the future consider pinning CLI to download 3.6.x so 
> > that it will automatically pick up point releases for times like this.
> > Don't think the logic's i there now for that though.
>
> We don't frequently do point releases, but I still like that idea. I 
> created https://issues.apache.org/jira/browse/CB-7537 to capture this 
> idea. Thanks!

RE: New project vs.

[Parashuram Narasimhan (MS OPEN TECH)]

To standardize, could we not need a param name, and set the Main class name in 
Android to something static always - say CordovaApp? The only problem would be 
in debugging where the activity name would be same. 

-Original Message-
From: Josh Soref [mailto:jso...@blackberry.com] 
Sent: Friday, September 12, 2014 12:02 PM
To: dev@cordova.apache.org
Subject: Re: New project  vs. 

I thought the initial plan was to just standardize on a safe name, and worry 
about the other variation later...

On 9/12/14, 2:59 PM, "Vladimir Kotikov (Akvelon)" 
wrote:

>Bumping this again.
>
>Can anyone pls. review following PRs:
>https://github.com/apache/cordova-cli/pull/192
>https://github.com/apache/cordova-lib/pull/84
>https://github.com/apache/cordova-android/pull/118
>
>This is an implementation for CB-7231 “Provide more control over 
>CordovaProjectName vs CordovaAppName” [1] These changes adds a new 
>option for cli and Android tooling  - --projectname that allow to user 
>to specify main class name, different from application name. This is 
>necessary when application name contains non-ASCII characters since ADK 
>tools can't properly handle this situation.
>
>Implementation is for Android only, since we don't see any problems 
>with other platforms.
>
>I think we need to decide should it be a core option that can be 
>defined via CLI command or in config.xml or just an android optio/preference.
>And if it is a core, do we need it for all platforms, or for android only?
>
>-
>Best regards, Vladimir
>
>
>-Original Message-
>From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com]
>Sent: Friday, September 5, 2014 5:24 PM
>To: dev@cordova.apache.org
>Subject: RE: New project  vs. 
>
>Hi all!
>
>I’ve started working on implementation for CB-7231 “Provide more 
>control over CordovaProjectName vs CordovaAppName” [1].
>
>Draft implementation for android is ready, you can review it here:
>https://github.com/apache/cordova-cli/pull/192
>https://github.com/apache/cordova-lib/pull/84
>https://github.com/apache/cordova-android/pull/118
>
>1.General changes in cli/lib
>  * ProjectName can be specified via --projectname option for cli 
>create command;
>  * It's written to config.xml into  element.
>Another option - store Project name into  element's attribute 
>- AppName
>
>2. Android part of implementation:
>  * ProjectName can be specified for bin/create script via 
>--projectname option;
>  * If specified, used for main activity/class name replacement;
>
>3. Android_parser in cli
>  * update_from_config() method handles   element in 
>config.xml during prepare step and renames main class and changes 
>activity name in manifest according to  value.
>  * in case of  element removal main class and activity 
>name are remains unchanged from last rename.
>
>For discussion:
>1. Currently I use  element to store ProjectName at 
>config.xml? Another possible option - use  
>approach, like Carlos proposed.
>2. Currently if ProjectName becomes undefined ( element is
>removed) main class file and activity are not being renamed back to app 
>name.
>
>Thoughts?
>
>And just a PS. Could anyone pls. give me permissions at JIRA so I can 
>assign issues to myself?
>
>[1] https://issues.apache.org/jira/browse/CB-7231
>
>---
>Best regards, Vladimir

RE: [Vote] 3.6.0 Cadence Release

[Parashuram Narasimhan (MS OPEN TECH)]

Sergey should be able to help, but he is in a different time zone. Do we know a 
list of things remaining ? 

-Original Message-
From: Marcel Kinard [mailto:cmarc...@gmail.com] 
Sent: Wednesday, September 3, 2014 2:16 PM
To: dev@cordova.apache.org
Subject: Re: [Vote] 3.6.0 Cadence Release

Could Sergey or Staci help out? If your time runs out, what specifically is 
left?

On Sep 3, 2014, at 1:42 PM, Jesse  wrote:

> I believe so, I am working through this today.  I am also in the 
> process of moving from Canada to the US, so I may not be able to do 
> much past mid-late afternoon.
> 
> On Wed, Sep 3, 2014 at 10:20 AM, Marcel Kinard  wrote:
> 
>> So the last thing holding back a new vote thread is a new rc for wp8 
>> and windows which depends on CB-7455?

RE: [Vote] 3.6.0 Cadence Release

[Parashuram Narasimhan (MS OPEN TECH)]

Agree with Jesse. If you still want to test it, I tried doing it with a private 
npm registry, and changed my npm to pick up from that registry. I did not see a 
lot of value added though. I did this when I was playing with the idea of using 
npm to use plugins.  

-Original Message-
From: Jesse [mailto:purplecabb...@gmail.com] 
Sent: Tuesday, September 2, 2014 10:21 AM
To: dev@cordova.apache.org
Subject: Re: [Vote] 3.6.0 Cadence Release

We cannot post to npm without the vote passing. There is a bunch of crazy 
overhead tag bs we could do, but then we would not be voting on the final 
released binaries.

Just test with --usegit



@purplecabbage
risingj.com


On Tue, Sep 2, 2014 at 6:47 AM, Carlos Santana  wrote:

> I see cordova cli rc on npm, I want to test it using npm but I get errors.
> Maybe cordova-lib should be also posted to npm but not make it latest 
> until we release.
>
> I get this errors:
>
> $ npm install cordova@rc
>
> npm ERR! Error: version not found: cordova-lib@0.21.8
>
>
> On Tue, Sep 2, 2014 at 9:29 AM, Bryan Higgins 
> wrote:
>
> > +1
> >
> > - Verified signatures and hashes for cordova-blackberry
> > - Verified sha1 match tag 3.6.0
> > - Ran mobile spec on various BB10 devices and OS versions
> >
> > Steve - I added you as an owner for cordova-blackberry10 on npm. The 
> > cordova-blackberry package should probably be unpublished.
> >
> >
> > On Tue, Sep 2, 2014 at 1:15 AM, Archana Naik 
> > 
> > wrote:
> >
> > > vote +1
> > > Verified amazon-fireos bundle, signatures and hashes.
> > >
> > > When are we planning to publish it to npm?
> > >
> > >
> > > On Mon, Sep 1, 2014 at 2:40 PM, Sergey Grebnov (Akvelon) < 
> > > v-seg...@microsoft.com> wrote:
> > >
> > > > I vote +1:
> > > > * Verified signatures and hashes for cordova-cli, cordova-lib, 
> > > > cordova-plugman, cordova-windows, cordova-wp8
> > > > * Verified sha1s match tags for cordova-cli, cordova-lib,
> > > cordova-plugman,
> > > > cordova-windows, cordova-wp8
> > > > * Run Medic tests for Windows and Windows Phone 8
> > > > * Tested Android build on Windows
> > > > * Tested Windows platform manually
> > > > building and running app with VS2012 (msbuild 
> > > > 4.0)/VS2013(msbuild
> > > 12.0)
> > > > -win and -phone switches
> > > > support of target platform settings (config.xml)
> > > > support of custom icons and splash screen images
> > > >
> > > > Thx!
> > > > Sergey
> > > > -Original Message-
> > > > From: Steven Gill [mailto:stevengil...@gmail.com]
> > > > Sent: Saturday, August 30, 2014 5:35 AM
> > > > To: dev@cordova.apache.org
> > > > Subject: [Vote] 3.6.0 Cadence Release
> > > >
> > > > Please review and vote on this 3.6.0 Cadence Release.
> > > >
> > > > Release issue: https://issues.apache.org/jira/browse/CB-7383
> > > >
> > > > Repos ready to be released have been published to
> > > > dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-7383
> > > >
> > > > The packages were published from their corresponding git tags:
> > > > cordova-android: 3.6.0 (014327c59a)
> > > > cordova-ios: 3.6.0 (3a92b2dbf0)
> > > > cordova-blackberry: 3.6.0 (ed435bfc9e)
> > > > cordova-windows: 3.6.0 (cdb292f4a3)
> > > > cordova-wp8: 3.6.0 (a879f5258b)
> > > > cordova-firefoxos: 3.6.0 (9ab176f855)
> > > >
> > > > cordova-ubuntu: 3.6.0 (bff472e4c2)
> > > > cordova-amazon-fireos: 3.6.0 (4e94c6d198)
> > > > cordova-js: 3.6.0 (906b34c0a4)
> > > > cordova-mobile-spec: 3.6.0 (27053f7dd8)
> > > > cordova-app-hello-world: 3.6.0 (65a2171a19)
> > > >
> > > > cordova-cli: 3.6.0-0.2.8 (01cb09f2d1)
> > > > cordova-lib: 0.21.8 (14670ec9b5)
> > > > cordova-plugman: 0.22.5 (29488fce7e)
> > > >
> > > >
> > > > Upon a successful vote I will upload the archives to dist/, 
> > > > publish
> > them
> > > > to NPM, and post the corresponding blog post.
> > > >
> > > > Voting guidelines:
> > > >
> > >
> >
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting
> .md
> > > >
> > > > Voting will go on for a minimum of 72 hours.
> > > >
> > > > I vote +1:
> > > > * Ran coho audit-license-headers over the relevant repos
> > > > * Used `license-checker` to ensure all dependencies have
> > > Apache-compatible
> > > > licenses
> > > > * Ensured continuous build was green when repos were tagged
> > > >
> > >
> >
>
>
>
> --
> Carlos Santana
> 
>

RE: GPU Profile tracing in Cordova Apps

[Parashuram Narasimhan (MS OPEN TECH)]

I was able to get the traces from a real Kindle Fire device, and also get 
benchmarks. I installed a Chromium shell, and ran the commands, that are an 
equivalent of 

adb shell am broadcast -a org.chromium.chrome.testshell.GPU_PROFILER_START. 

This was using a Chrome shell, and I was wondering what the equivalent of it 
would be in case of Cordova Android apps. Would the name be any different? 


-Original Message-
From: Archana Naik [mailto:naik.arch...@gmail.com] 
Sent: Tuesday, August 26, 2014 8:30 AM
To: dev@cordova.apache.org
Subject: Re: GPU Profile tracing in Cordova Apps

Hi, Parashuram

Which device did you try to run your profiling on? Difference between Android 
chromium and Amazon Chromium could be underneath chromium version.
KK based android is based on v30. Amazon started with v25 and is now upto
v34 on some devices. Also, amazon' s port has some of the HTML5 features like 
WebGL enabled and many more optimizations done for Fire OS based devices.
Let me know if you have any specific questions?

Archana


On Mon, Aug 25, 2014 at 2:47 PM, Parashuram Narasimhan (MS OPEN TECH) < 
panar...@microsoft.com> wrote:

> However, since that functionality is based on Chromium (and even works 
> on chrome), I am guessing that it should be possible in Cordova webviews.
>
> -Original Message-
> From: Joe Bowser [mailto:bows...@gmail.com]
> Sent: Monday, August 25, 2014 2:22 PM
> To: dev
> Subject: Re: GPU Profile tracing in Cordova Apps
>
> Amazon's Chromium is different than Android Chromium.  I don't know 
> exactly how they're different, but I wouldn't expect GPU profiling to 
> work the same way.
>
>
> On Mon, Aug 25, 2014 at 2:18 PM, Parashuram 
> wrote:
>
> > Hi,
> >
> > I am working on a performance framework (
> > http://github.com/axemclion/browser-perf) and was looking at ways to 
> > start the GPU profile on Cordova Android apps.
> >
> > To read about:tracing information for Chrome, I can do
> >
> > $ adb shell am broadcast -a com.android.chrome.GPU_ PROFILER_START 
> > -e categories "benchmark" -e continuous ""
> >
> > ​In case of Amazon's ​port of Chromium, I use
> >
> > $ adb shell am broadcast -a
> > com.android.org.chromium.action.PROFILE_START.<
> > package.name>
> >
> > ​However, for Cordova Webview apps, the following does not seem to 
> > work ​
> >
> > $ ​adb shell am broadcast -a
> > io.cordova.hellocordova.GPU_PROFILER_START
> >
> > Am I missing something obvious, or is the webview implemented
> differently?
> > I am starting to look at the source but was hoping that the experts 
> > on this list could point me to the right direction.
> > ​
> >
> >
> > Parashuram
> > http://nparashuram.com
> >
>

RE: [Discuss] 3.6.0 Release

[Parashuram Narasimhan (MS OPEN TECH)]

Do any of these known issues block the release? Can we start the vote today as 
Steve wanted despite these issues? 

-Original Message-
From: Marcel Kinard [mailto:cmarc...@gmail.com] 
Sent: Friday, August 29, 2014 9:10 AM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release

So to consolidate the list of known issues that should be addressed before 
cutting an RC:

* CB-7375 Investigate breaking changes at file plugin
* Android manual plugin tests not run yet
* CB-7410 lots of breakages of the Android native tests
* CB-7416 Windows+plugins. source-file is not correctly processed

Any omissions or extras?

On Aug 27, 2014, at 2:19 PM, Sergey Grebnov (Akvelon)  
wrote:

> Found out another Windows issue. Jesse could you pls take a look? Otherwise 
> I'll investigate it my tomorrow morning.
> 
> CB-7416 - Windows+plugins. source-file is not correctly processed
> 
> Thx!
> Sergey

RE: [Discuss] 3.6.0 Release

[Parashuram Narasimhan (MS OPEN TECH)]

Given that both the blockers are now closed, will we be starting a vote thread 
next? 

-Original Message-
From: Bryan Higgins [mailto:br...@bryanhiggins.net] 
Sent: Tuesday, August 26, 2014 1:05 PM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release

BB10 should be good to go now.

I published cordova-blackberry10 as a package [1]. We had already updated the 
name in package.json due to the strict name checking in CLI, so this had to be 
done anyway.

Adding all packages to bundledDependencies works around the 'npm install'
problem [2].

[1] https://www.npmjs.org/package/cordova-blackberry10

[2]
https://git-wip-us.apache.org/repos/asf?p=cordova-blackberry.git;a=commit;h=8f9248654791f820490919a876d06bba591f6f6c




On Tue, Aug 26, 2014 at 3:23 PM, Parashuram Narasimhan (MS OPEN TECH) < 
panar...@microsoft.com> wrote:

> We found a few issues with Windows Phone 8.1 (whitelist does not allow
> HTTP) that Sergey discussed and is fixing.
>
> -Original Message-
> From: Marcel Kinard [mailto:cmarc...@gmail.com]
> Sent: Tuesday, August 26, 2014 11:54 AM
> To: dev@cordova.apache.org
> Subject: Re: [Discuss] 3.6.0 Release
>
> I'm running mobile-spec (plugins + non-plugins + automatic + manual +
> platforms) with master on Android and finding a few failing tests, but 
> they are getting fixed. With an impending 3.6.0 release soon, I would 
> assume many others are doing the same. But perhaps that's not a good 
> assumption.
>
> On Aug 8, 2014, at 2:11 PM, Steven Gill  wrote:
>
> > How does everyone feel about me starting the release process next 
> > Tuesday, August 12, 2014?
> >
> > Will your platform be ready?
>
>

RE: [Discuss] 3.6.0 Release

[Parashuram Narasimhan (MS OPEN TECH)]

We found a few issues with Windows Phone 8.1 (whitelist does not allow HTTP) 
that Sergey discussed and is fixing. 

-Original Message-
From: Marcel Kinard [mailto:cmarc...@gmail.com] 
Sent: Tuesday, August 26, 2014 11:54 AM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release

I'm running mobile-spec (plugins + non-plugins + automatic + manual + 
platforms) with master on Android and finding a few failing tests, but they are 
getting fixed. With an impending 3.6.0 release soon, I would assume many others 
are doing the same. But perhaps that's not a good assumption.

On Aug 8, 2014, at 2:11 PM, Steven Gill  wrote:

> How does everyone feel about me starting the release process next 
> Tuesday, August 12, 2014?
> 
> Will your platform be ready?

RE: [Discuss] 3.6.0 Release

[Parashuram Narasimhan (MS OPEN TECH)]

In the issue, @kamrik suggested a possible quick fix. Can we do that so that 
releasing 3.6.0 is not blocked ?

-Original Message-
From: Josh Soref [mailto:jso...@blackberry.com] 
Sent: Wednesday, August 20, 2014 10:56 PM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release

Parashuram Narasimhan wrote:
> Wanted to ping about the 3.6.0 thread.
> Are all the open issues taken care of?

No, the nice thing about issues is that you can check and see. 

> Is there something we can help on? 
...

https://github.com/apache/cordova-lib/pull/75

‎

RE: Directory Structure - CLI directory config proposal

[Parashuram Narasimhan (MS OPEN TECH)]

It is the latter. The idea is that there is a default directory structure that 
shall be defined by Cordova CLI, and the IDE can modify it, call tasks like 
prepare or compile directly from cordova-lib. The IDE could do clever things 
like copy only modified files, use symlinks, etc. From the hangouts discussion, 
it was agree that cordova-lib would expose APIs that shall be used by build 
systems, IDEs and the CLI. We need to finalize on that API.

I could volunteer to take the first stab at that API that cordova-lib suggests. 
Does that sound good ?

-Original Message-
From: Treggiari, Leo [mailto:leo.treggi...@intel.com] 
Sent: Thursday, August 21, 2014 6:45 AM
To: dev@cordova.apache.org
Subject: RE: Directory Structure - CLI directory config proposal

Is the flexible directory structure being proposed so that the CLI can 
"conform" to a directory structure defined by the IDE, or so that a user can 
define the directory structure and both the CLI and the IDE use it?  I'm an IDE 
developer, but I don't have a lot a sympathy for the former.  The latter is 
useful.  I don't understand why an IDE should think IT defines the directory 
structure, just like the CLI did prior to this proposal.

Leo

-Original Message-
From: Parashuram Narasimhan (MS OPEN TECH) [mailto:panar...@microsoft.com] 
Sent: Wednesday, August 20, 2014 10:17 PM
To: dev@cordova.apache.org
Subject: RE: Directory Structure - CLI directory config proposal

Should the platform/plugin save/restore take care of the ability to restore 
platforms? That way, though the platforms folder is discernable, we do not have 
to necessarily delete it. The goal of able to re-create a project solely based 
on the checked-in information still stays. 

The user may choose to check in the user specific config if the entire team 
decides to use that as a project structure. They would not check the 
user-config in cases where individual users use different IDEs. 

-Original Message-
From: Marcel Kinard [mailto:cmarc...@gmail.com] 
Sent: Tuesday, August 19, 2014 12:50 PM
To: dev@cordova.apache.org
Subject: Re: Directory Structure - CLI directory config proposal

I don't want to dramatically increase the scope of this thread, but I'm 
wondering if this is the opportunity to get the platforms dir to be 100% 
generated and discardable between app builds. The goal being that then there is 
a clean line of what devs should check into SCM and what is in their .gitignore 
file.

It also feels like there should be a slight difference between user-specific 
config that doesn't go into a team SCM (my copy of cordova-android is in 
/home/marcelk/customized), and project-specific config that does go into a team 
SCM (the layout of this meta config that describes where the project dirs are).

And yes, it should be 100% compatible with today's directory structure.

RE: GPU Profile tracing in Cordova Apps

[Parashuram Narasimhan (MS OPEN TECH)]

However, since that functionality is based on Chromium (and even works on 
chrome), I am guessing that it should be possible in Cordova webviews. 

-Original Message-
From: Joe Bowser [mailto:bows...@gmail.com] 
Sent: Monday, August 25, 2014 2:22 PM
To: dev
Subject: Re: GPU Profile tracing in Cordova Apps

Amazon's Chromium is different than Android Chromium.  I don't know exactly how 
they're different, but I wouldn't expect GPU profiling to work the same way.


On Mon, Aug 25, 2014 at 2:18 PM, Parashuram  wrote:

> Hi,
>
> I am working on a performance framework (
> http://github.com/axemclion/browser-perf) and was looking at ways to 
> start the GPU profile on Cordova Android apps.
>
> To read about:tracing information for Chrome, I can do
>
> $ adb shell am broadcast -a com.android.chrome.GPU_ PROFILER_START -e 
> categories "benchmark" -e continuous ""
>
> ​In case of Amazon's ​port of Chromium, I use
>
> $ adb shell am broadcast -a 
> com.android.org.chromium.action.PROFILE_START.<
> package.name>
>
> ​However, for Cordova Webview apps, the following does not seem to 
> work ​
>
> $ ​adb shell am broadcast -a 
> io.cordova.hellocordova.GPU_PROFILER_START
>
> Am I missing something obvious, or is the webview implemented differently?
> I am starting to look at the source but was hoping that the experts on 
> this list could point me to the right direction.
> ​
>
>
> Parashuram
> http://nparashuram.com
>

RE: continuous integration woze

[Parashuram Narasimhan (MS OPEN TECH)]

If some of the tests are too strict, should we move it to be triggered on a 
different branch? For example, fails come only on master, while they show up as 
"warning" for other branches and we build --force incase of other branches?  

-Original Message-
From: Josh Soref [mailto:jso...@blackberry.com] 
Sent: Wednesday, August 20, 2014 8:00 AM
To: dev@cordova.apache.org
Subject: Re: continuous integration woze



On 8/20/14, 10:50 AM, "Mark Koudritsky"  wrote:

>AFAIK Travis only supplies a binary pass/fail status, so there is no 
>such thing as a warning.
>A Travis check for pull request doesn't mark the entire build on master 
>as failed, only that pull request. So there is no need to panic and 
>"drop everything and fix the build", instead just "fix the build" by 
>updating the pull request :)

Fwiw, I thought that I had pushed an update to the pull request, but apparently 
my `git commit —amend` was missing a `-a`, and thus my `git push -f` didn't do 
anything useful.


>That said, I would be glad if Travis was commenting on pull request 
>with a line or two rather than just setting the binary pass/fail 
>status. This would also be a great feature for using multiple CI 
>services like we do with Travis and AppVeyor. Anybody knows if Travis 
>can be configured to leave comments under pull requests?

I would much prefer this, because as is, I have at least 4 "outputs" from
travis+appveyor,
and yet if you look at the pull request, you'll only see one.

RE: Directory Structure - CLI directory config proposal

[Parashuram Narasimhan (MS OPEN TECH)]

Should the platform/plugin save/restore take care of the ability to restore 
platforms? That way, though the platforms folder is discernable, we do not have 
to necessarily delete it. The goal of able to re-create a project solely based 
on the checked-in information still stays. 

The user may choose to check in the user specific config if the entire team 
decides to use that as a project structure. They would not check the 
user-config in cases where individual users use different IDEs. 

-Original Message-
From: Marcel Kinard [mailto:cmarc...@gmail.com] 
Sent: Tuesday, August 19, 2014 12:50 PM
To: dev@cordova.apache.org
Subject: Re: Directory Structure - CLI directory config proposal

I don't want to dramatically increase the scope of this thread, but I'm 
wondering if this is the opportunity to get the platforms dir to be 100% 
generated and discardable between app builds. The goal being that then there is 
a clean line of what devs should check into SCM and what is in their .gitignore 
file.

It also feels like there should be a slight difference between user-specific 
config that doesn't go into a team SCM (my copy of cordova-android is in 
/home/marcelk/customized), and project-specific config that does go into a team 
SCM (the layout of this meta config that describes where the project dirs are).

And yes, it should be 100% compatible with today's directory structure.

RE: [Discuss] 3.6.0 Release

[Parashuram Narasimhan (MS OPEN TECH)]

Wanted to ping about the 3.6.0 thread. Are all the open issues taken care of? 
Is there something we can help on?   

-Original Message-
From: Josh Soref [mailto:jso...@blackberry.com] 
Sent: Tuesday, August 19, 2014 1:11 PM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release

Mark Koudritsky wrote:
>npm info cordova-blackberry10---  404
>npm info cordova-blackberry--- OK
>
>cli is looking for blackberry10 as npm name but it's blckberry.
>I think the altplatform: 'blackberry'  in platforms.js can solve this.

Nope, that's for the internal directory name, not the external package name.

https://github.com/apache/cordova-lib/pull/75


Would address this, except that the 3.5 package doesn't include its 
dependencies… so the pull request includes code to handle that too.

RE: Adding Windows tests to http://ci.cordova.io/

[Parashuram Narasimhan (MS OPEN TECH)]

Sounds good, Sergey can probably restart this thread after you return. In the 
meantime, did others on this mailing list try out setting up medic on Windows? 
The hope is that this script makes is super simple and anyone should be able to 
contribute test results back. 

-Original Message-
From: m...@google.com [mailto:m...@google.com] On Behalf Of Max Woghiren
Sent: Thursday, August 14, 2014 1:42 PM
To: dev
Cc: Maria Bukharina (Akvelon); Artem Antonets (Akvelon)
Subject: Re: Adding Windows tests to http://ci.cordova.io/

Welcome, Maria and Anton—looking forward to working with you. :)

The scripts will certainly be handy, and I am on board with the idea of adding 
Windows tests to ci.cordova.io.

However, starting tomorrow, I'm away until Tuesday, August 26th, so the timing 
is unfortunate.  I won't be able to review the PR or work on getting Windows on 
Cordova CI until then.


On Thu, Aug 14, 2014 at 12:23 PM, Sergey Grebnov (Akvelon) < 
v-seg...@microsoft.com> wrote:

> Hi,  I want to introduce our new test team members Maria and Anton who 
> has recently joined our team and made a couple of Medic improvements.
>
> #1 They created special scripts to automate Medic set-up [1]. Using 
> these scripts you can set up local Medic instance including OSX or 
> Windows master and required slave instances (currently supports windows 
> slaves only).
> #2 Various fixes and documentation improvements. PR is available here 
> [2]
> #3 Set up local Medic instance[3] to track platforms healthiness on 
> Windows (currently supports of Android, WP8  and Windows Universal Apps).
>
> Taking into account that OSX master can now support Windows slaves I 
> wonder if we can include windows tests support to 
> http://ci.cordova.io/ so that we finally have single place for all 
> supported platforms tests results. As per David notes and Medic repo 
> activities it looks like that Max Woghiren is one of the owners of 
> this area , isn't it? Max, what do you think about this idea and what 
> help we can provide from our side (including hosting of Windows slaves)?
>
> [1] https://github.com/MSOpenTech/medic-bootstrap
> [2] https://github.com/apache/cordova-medic/pull/16
> [3] http://msot-master.cloudapp.net:8010/
>
> Thx!
> Sergey
>

RE: Directory Structure - CLI directory config proposal

[Parashuram Narasimhan (MS OPEN TECH)]

I think the idea of this feature is to have ZERO impact on existing workflows. 
This would be a very useful feature for IDEs who may do additional things like 
caching platforms, providing customized versions of platforms, etc. The 
implementation we have follows that philosophy. Brian, Jesse, it would be great 
if you could look at our implementation and let me know if your concerns are 
addressed. 

-Original Message-
From: brian.ler...@gmail.com [mailto:brian.ler...@gmail.com] On Behalf Of Brian 
LeRoux
Sent: Monday, August 11, 2014 11:06 AM
To: dev@cordova.apache.org
Subject: Re: Directory Structure - CLI directory config proposal

I can see the value but have found configurable path look ups tend to be very 
fragile. (The more config the more variable paths create more opportunities for 
weird side effects.) I echo the sentiment that we need to be 100% certain this 
feature does not break existing (default) workflow.


On Mon, Aug 11, 2014 at 10:44 AM, Jesse  wrote:

> I see zero value in this feature, so I will simply ask that we please 
> don't break any expectations that already exist.
> If this can be achieved without altering the current workflow then I 
> will keep quiet.
>
>
> @purplecabbage
> risingj.com
>
>
> On Mon, Aug 11, 2014 at 10:13 AM, Carlos Santana 
> 
> wrote:
>
> > Yep I agree with using .cordova/config.json for this directory config.
> and
> > it would be in 3.x should not wait for 4.x
> >
> >
> >
> > On Mon, Aug 11, 2014 at 1:07 PM, Michal Mocny 
> wrote:
> >
> > > Lets not add a new public config file until we have many long 
> > > talks to figure out all the requirements for a future CLI.  
> > > Perhaps PGDay US
> will
> > be
> > > a good opportunity to get together in person and hash out some ideas?
> > >
> > > And since I don't think we should block work like what is being
> discussed
> > > here, we should continue to use the .cordova/config.json.  We can
> migrate
> > > those features to a public config file without issue.
> > >
> > > -Michal
> > >
> > >
> > > On Mon, Aug 11, 2014 at 12:49 PM, Carlos Santana 
> > >  >
> > > wrote:
> > >
> > > > I like what Mark suggested of not passing json string in the 
> > > > command
> > > line,
> > > > and better to pass a json file.
> > > > Why are we talking about 4.0 release? This can be landed on 3.x
> unless
> > > I'm
> > > > missing something very obvious.
> > > >
> > > > I would also would like to propose that we expose the hidden
> > config.json
> > > as
> > > > a plublic file on the root of the project like cordova.json 
> > > > (easy to
> > > find,
> > > > easy to edit, easy to understand what's going on).
> > > > Allowing the www template come with a default cordova.json with
> default
> > > > values, and allow downstream distributions like IBM :-), to have 
> > > > a different template for "cordova create 
> > > > --copy-from=ibmtemplate/)
> with a
> > > > different cordova.json
> > > > Also cordova.json can serve as a way to identity a cordova 
> > > > project
> root
> > > > directory by high level IDE/Tools maybe this change of 
> > > > cordova.json is a big enough for a 4.x
> > > >
> > > >
> > > >
> > > > On Mon, Aug 11, 2014 at 11:27 AM, Parashuram Narasimhan (MS OPEN
> TECH)
> > <
> > > > panar...@microsoft.com> wrote:
> > > >
> > > > > Should we go ahead and create a branch in the main project so 
> > > > > that
> > you
> > > > can
> > > > > also add your ideas to it? We could target this feature for a 
> > > > > 4.0
> > > > release.
> > > > >
> > > > > -Original Message-
> > > > > From: Mark Koudritsky [mailto:kam...@google.com]
> > > > > Sent: Monday, August 11, 2014 7:56 AM
> > > > > To: dev@cordova.apache.org
> > > > > Subject: Re: Directory Structure - CLI directory config 
> > > > > proposal
> > > > >
> > > > > I like the way it looks now, but I would argue that we need to 
> > > > > take
> > it
> > > > > another step further and make it a CordovaProject class that 
> > > > > should
> > > only
> > > > be
> > > > > instantiated once and contain all the 

RE: cordova plugin save

[Parashuram Narasimhan (MS OPEN TECH)]

How about storing all this information in a project's package.json  ? 

If all Cordova CLI projects were simply NodeJS projects and Cordova was the 
builder, like Grunt or Gulp  (Thinking about it, Cordova actually is a builder)
Plugins are runtime dependencies and will be in the dependencies section of the 
project's package.json. Platforms are required only for the build time and they 
would be in devDependencies. This way, we can also install semver'ed plugins, 
and plugins themselves can be published to npmjs.org. 

Additionally, people could even build native code using node-gyp, and all 
post-plugin hooks to build C/C++ based plugins would work. 

This may be a deviation from the current config.xml, but does this sound like 
something we would like to target for the future? 

-Original Message-
From: mmo...@google.com [mailto:mmo...@google.com] On Behalf Of Michal Mocny
Sent: Monday, August 18, 2014 5:53 AM
To: Treggiari, Leo
Cc: Michal Mocny; dev
Subject: Re: cordova plugin save

On Fri, Aug 15, 2014 at 10:29 PM, Treggiari, Leo 
wrote:

>  I have a few follow-on questions / comments:
>
>
>
> > Run-time Platform-specific config:
>
> >  - Automatically created on prepare from a combination of initial
> application template and many project properties
>
> >  - Currently, this is the cordova "platform" config.xml, but also 
> > the
> various platform metadata files like AndroidManifest.xml and App.plist 
> etc
>
>
>
> So, part of the job of config.xml is to hold other application 
> definition metadata.  In particular, one set of properties is used 
> during preparation to generate the platform specific manifest files.  
> Is this set of config.xml properties ever used directly by a platform 
> at installation or loading, or is it just used during preparation?
>

Yes it is used at runtime.  Platforms/plugins can query s at 
runtime for all sorts of settings (simple things like colors, or complex things 
like how to cloud backup, where files should live)


>
> > Build-time Platform-generic App config:
>
> >   - Settings *every* developer would agree with.
>
> >   - Goes into VC, required to build the project.
>
> >   - Currently, this is /config.xml
>
>
>
> However, the fact that Cordova CLI does not store the list of 
> platforms and plugins in config.xml, makes it quite incomplete.
>

Yes.

>
>
> Project config:
>
>   - Settings local to a given developers machine / project instance.
>
>   - Currently, this is /.cordova/config.json
>
>   - Can also have a global version that applies to all projects, but 
> the content is the same as per-project, conceptually the same.
>
>  - and ~/.cordova/config.json
>
>   - [I've been calling "Project config" the "Workspace config".  I 
> think both terms are overloaded and confusing.  Perhaps we should just 
> call it the "Local config"?]
>
>
>
> Sounds good.
>
>
>
> > I think the point of this thread was to figure out if the list of
> platform/plugins to restore from should go.  With the above 
> descriptions, here are my 2c:
>
>
>
> I’m still at a higher level question which is why save/restore at all?  
> It seems like it would be better if the ‘plugin/platform add/remove’ 
> commands maintained their lists in config.xml.  There’s no need for a 
> ‘save’ command then.  ‘restore’ could be interesting if it can’t be 
> done automatically – i.e. if Cordova CLI knows the list of plugins 
> from config.xml, then it could automatically  fetch them if they are 
> missing from the plugins directory.
>

Gorkems answer is spot on.  We agree, we just don't have it *yet*.  Waiting on 
PR's to address some of the issues raised in recent reviews.

>
>
> As an IDE developer, my overall goal would be to make it such that 
> Cordova CLI and an IDE could be used seamlessly on the same application.  E.g.
> support a user who likes to use both at different times, and teams 
> where some users want to use the CLI and other users want to use an IDE.
>

>
> Leo
>
>
>
> *From:* mmo...@google.com [mailto:mmo...@google.com] *On Behalf Of 
> *Michal Mocny
> *Sent:* Thursday, August 14, 2014 5:53 AM
> *To:* dev
> *Cc:* Treggiari, Leo
>
> *Subject:* Re: cordova plugin save
>
>
>
> Summarizing / simplifying since this thread has run away:
>
>
>
> Run-time Platform-specific config:
>
>   - Automatically created on prepare from a combination of initial 
> application template and many project properties
>
>   - Currently, this is the cordova "platform" config.xml, but also the 
> various platform metadata files like AndroidManifest.xml and App.plist 
> etc
>
>
>
> Build-time Platform-generic App config:
>
>   - Settings *every* developer would agree with.
>
>   - Goes into VC, required to build the project.
>
>   - Currently, this is /config.xml
>
>
>
> Project config:
>
>   - Settings local to a given developers machine / project instance.
>
>   - Currently, this is /.cordova/config.json
>
>   - Can also have a global version that applies to all projects, but 
> the content is the 

RE: [Discuss] 3.6.0 Release

[Parashuram Narasimhan (MS OPEN TECH)]

The command line switches have been finalized for 3.6.0. Once that is merged, 
we should be good to release 3.6.0 from windows perspective. 

-Original Message-
From: iclell...@google.com [mailto:iclell...@google.com] On Behalf Of Ian 
Clelland
Sent: Tuesday, August 12, 2014 1:00 PM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release

I think that A) is likely the feasible solution for 3.6.0.

B) seems like a 4.0-scope project (but an interesting one; I hadn't considered 
it working in that direction) We'd probably spend a while debating the 
particulars -- I don't know if changing the CSP syntax is a good idea, or if 
we'd want an X-Navigation-Policy header of our own to play with -- but I think 
that a drastic change of direction like that would require a major version 
update if it's in core.

The other alternative I see (which goes back to the thread that Andrew
linked) is to pull 1, 2, and 3 out of the core, and have plugins for all of it.

What changes would we need to make to the plugin architecture to make that 
happen?



On Tue, Aug 12, 2014 at 3:16 PM, Andrew Grieve  wrote:

> A malicious XSS that navigates the page would probably opt to not 
> include cordova.js :P.
>
> So - I see there being three kinds of things to have whitelists for:
> 1) Top-level navigations,
> 2) intents (on supported platforms)
> 3) resources / CSP-related requests.
>
> According to CSP docs here:
>
> https://developer.mozilla.org/en-US/docs/Web/Security/CSP/CSP_policy_d
> irectives
> You cannot use CSP to control 1).
>
> Right now the whitelist tries to cover 1) and 3), but I think from 
> this
> thread: http://markmail.org/thread/hbr5tlopbbl4pnl3
> That we agreed to change it to cover only 1), Although this 
> conversation will likely be more all-encompassing.
>
> Options for specifying 1), 2), 3):
> A) Keep all three separate, with 1) and 2) in config.xml, and 3) in a 
>  added by the user
> B) Augment the CSP syntax with support for 1) and 2) (as Parashuram 
> suggested), and have cordova.js extract 1) and 2) out of the , 
> which is added by the user. Make the whitelists empty until cordova.js 
> does the extraction.
> C) Have them all specified in config.xml, and have Cordova somehow 
> enforce
> 3) on page load.
>
> Another factor: What is put in config.xml is open to be modified by 
> plugins (for better or for worse). Might be useful, but I'm not sure 
> of a concrete use-case (maybe Camera plugin would need this?)
>
> As Ian pointed out, C) isn't really feasible on Android in all cases, 
> but I'm torn between A) and B).
>
>
>
> On Tue, Aug 12, 2014 at 11:59 AM, Michal Mocny 
> wrote:
>
> > Any page navigations have to include cordova.js, right?  What about 
> > injecting the meta tag before deviceready?
> >
> >
> > On Tue, Aug 12, 2014 at 11:54 AM, Ian Clelland 
> > 
> > wrote:
> >
> > > I love the idea of using CSP for this, especially because it 
> > > handles
> > things
> > > that our whitelist intercept code can't, like  tags and
> > WebSockets.
> > >
> > > The problem that I've found with it is that we can only enforce it 
> > > for single-page apps. We can inject our own CSP headers into the
> > application's
> > > start page very easily, but if the user can leave that page and 
> > > load another, then the headers will no longer apply. The WebView 
> > > interface
> > won't
> > > let use add headers to subsequent pages, so it's up to the 
> > > developer to include them in a  tag instead. (and malicious 
> > > attackers, of
> > course,
> > > won't)
> > >
> > > For now, I would encourage devs to include that  tag on 
> > > *all* of
> > the
> > > pages in their apps, but we can't do it automatically.
> > >
> > > If it turns out that we can, then I'd be on board with including 
> > > that
> in
> > > the 4.0 branch. It's a much better way to do it. Then we'd only 
> > > need
> the
> > > second whitelist for launching intents, I think.
> > >
> > > Ian
> > >
> > >
> > > On Tue, Aug 12, 2014 at 11:48 AM, Parashuram Narasimhan (MS OPEN 
> > > TECH)
> <
> > > panar...@microsoft.com> wrote:
> > >
> > > > Had a quick question on the whitelists. I remember that there 
> > > > was
> talk
> > of
> > > > using CSP to fix this issue. A CSP file may not be backward
> compatible,
> > > but
> > > > could potentially just give us one list in

RE: Time to Update the Who's Who!

[Parashuram Narasimhan (MS OPEN TECH)]

Username: axemclion

-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com] 
Sent: Friday, August 15, 2014 9:55 AM
To: dev@cordova.apache.org
Subject: Re: Time to Update the Who's Who!

What's your username when you login?


On Fri, Aug 15, 2014 at 12:25 PM, Parashuram Narasimhan (MS OPEN TECH) < 
panar...@microsoft.com> wrote:

> I tried editing this page, but it says that this page is immutable. Do 
> I need more rights than that of a committer?
>
> -Original Message-
> From: Carlos Santana [mailto:csantan...@gmail.com]
> Sent: Friday, August 15, 2014 6:55 AM
> To: dev@cordova.apache.org
> Subject: Re: Time to Update the Who's Who!
>
> Michal at least the IBM team maintains our section :-p
>
> Could one of you for each company at least update with the names of 
> the people that you are aware of for your section in the page?
>
> That could be a good first pass.
>
>
>
> On Thu, Aug 14, 2014 at 6:05 PM, Jesse  wrote:
>
> > Wow, Shaz!
> > I am #12, #21, #30, #49
> >
> > I think this email alone should be enough to get everyone who isn't 
> > listed at https://wiki.apache.org/cordova/who to add themselves 
> > and/or
> company.
> >
> > @purplecabbage
> > risingj.com
> >
> >
> > On Thu, Aug 14, 2014 at 2:50 PM, Shazron  wrote:
> >
> > > There's a "Who Sent it?" list here 
> > > http://callback-dev.markmail.org/search/?q=
> > > that shows #of emails sent by a person in the list.
> > >
> > > On Thu, Aug 14, 2014 at 2:47 PM, Michal Mocny 
> > > 
> > wrote:
> > > > I think thats the best we've got, but agree that its not really
> > > maintained
> > > > by anyone.
> > > >
> > > > Perhaps crawling this list to see email frequency would work too?
> > > >
> > > >
> > > > On Thu, Aug 14, 2014 at 5:39 PM, Lisa Seacat DeLuca <
> > ldel...@us.ibm.com>
> > > > wrote:
> > > >
> > > >> I noticed that our who's who page is a little out of date:
> > > >> https://wiki.apache.org/cordova/who
> > > >>
> > > >> For example, Microsoft isn't even listed.  Is there a better 
> > > >> way of figuring out which companies and how many committers 
> > > >> from each company
> > > are
> > > >> participating?  Trying to put together some stats for my 
> > > >> management
> > and
> > > I
> > > >> know they'd find that interesting.
> > > >>
> > > >>
> > > >> Lisa
> > > >>
> > > >>
> > > >> Lisa Seacat DeLuca
> > > >> Mobile Engineer | t: +415.787.4589 | *ldel...@apache.org* 
> > > >>  | | *ldel...@us.ibm.com* 
> > > >>  |
> > > >> *lisaseacat.com* <http://www.lisaseacat.com/> | [image: follow 
> > > >> @LisaSeacat on twitter] <http://www.twitter.com/LisaSeacat>|
> [image:
> > > >> follow Lisa Seacat DeLuca on linkedin] 
> > > >> <http://www.linkedin.com/in/lisaseacat>
> > >
> >
>
>
>
> --
> Carlos Santana
> 
>



--
Carlos Santana

RE: Time to Update the Who's Who!

[Parashuram Narasimhan (MS OPEN TECH)]

I tried editing this page, but it says that this page is immutable. Do I need 
more rights than that of a committer? 

-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com] 
Sent: Friday, August 15, 2014 6:55 AM
To: dev@cordova.apache.org
Subject: Re: Time to Update the Who's Who!

Michal at least the IBM team maintains our section :-p

Could one of you for each company at least update with the names of the people 
that you are aware of for your section in the page?

That could be a good first pass.



On Thu, Aug 14, 2014 at 6:05 PM, Jesse  wrote:

> Wow, Shaz!
> I am #12, #21, #30, #49
>
> I think this email alone should be enough to get everyone who isn't 
> listed at https://wiki.apache.org/cordova/who to add themselves and/or 
> company.
>
> @purplecabbage
> risingj.com
>
>
> On Thu, Aug 14, 2014 at 2:50 PM, Shazron  wrote:
>
> > There's a "Who Sent it?" list here
> > http://callback-dev.markmail.org/search/?q=
> > that shows #of emails sent by a person in the list.
> >
> > On Thu, Aug 14, 2014 at 2:47 PM, Michal Mocny 
> wrote:
> > > I think thats the best we've got, but agree that its not really
> > maintained
> > > by anyone.
> > >
> > > Perhaps crawling this list to see email frequency would work too?
> > >
> > >
> > > On Thu, Aug 14, 2014 at 5:39 PM, Lisa Seacat DeLuca <
> ldel...@us.ibm.com>
> > > wrote:
> > >
> > >> I noticed that our who's who page is a little out of date:
> > >> https://wiki.apache.org/cordova/who
> > >>
> > >> For example, Microsoft isn't even listed.  Is there a better way 
> > >> of figuring out which companies and how many committers from each 
> > >> company
> > are
> > >> participating?  Trying to put together some stats for my 
> > >> management
> and
> > I
> > >> know they'd find that interesting.
> > >>
> > >>
> > >> Lisa
> > >>
> > >>
> > >> Lisa Seacat DeLuca
> > >> Mobile Engineer | t: +415.787.4589 | *ldel...@apache.org* 
> > >>  | | *ldel...@us.ibm.com* 
> > >>  |
> > >> *lisaseacat.com*  | [image: follow 
> > >> @LisaSeacat on twitter] | [image:
> > >> follow Lisa Seacat DeLuca on linkedin] 
> > >> 
> >
>



--
Carlos Santana

RE: Adding Windows tests to http://ci.cordova.io/

[Parashuram Narasimhan (MS OPEN TECH)]

It would also be great if others could try out the script to setup their own 
instances of Medic. The hope is to make medic setup so simple that anyone can 
set up the machine and report the test results back to couchdb. 

-Original Message-
From: Sergey Grebnov (Akvelon) [mailto:v-seg...@microsoft.com] 
Sent: Thursday, August 14, 2014 9:23 AM
To: dev@cordova.apache.org
Cc: Maria Bukharina (Akvelon); Artem Antonets (Akvelon)
Subject: Adding Windows tests to http://ci.cordova.io/

Hi,  I want to introduce our new test team members Maria and Anton who has 
recently joined our team and made a couple of Medic improvements.

#1 They created special scripts to automate Medic set-up [1]. Using these 
scripts you can set up local Medic instance including OSX or Windows master and 
required slave instances (currently supports windows slaves only).
#2 Various fixes and documentation improvements. PR is available here [2]
#3 Set up local Medic instance[3] to track platforms healthiness on Windows 
(currently supports of Android, WP8  and Windows Universal Apps).

Taking into account that OSX master can now support Windows slaves I wonder if 
we can include windows tests support to http://ci.cordova.io/ so that we 
finally have single place for all supported platforms tests results. As per 
David notes and Medic repo activities it looks like that Max Woghiren is one of 
the owners of this area , isn't it? Max, what do you think about this idea and 
what help we can provide from our side (including hosting of Windows slaves)?

[1] https://github.com/MSOpenTech/medic-bootstrap
[2] https://github.com/apache/cordova-medic/pull/16
[3] http://msot-master.cloudapp.net:8010/

Thx!
Sergey

RE: Feedback on "cordova plugin save" & friends

[Parashuram Narasimhan (MS OPEN TECH)]

Given that we are looking at decoupling engine and platform releases, there 
should be ways to specify them separately, right ? In this case, I am assuming 
it is basically version of cordova-cli/cordova-lib and the platform, assuming 
that cordova-cli can work with older platform versions. 

-Original Message-
From: Gorkem Ercan [mailto:gorkem.er...@gmail.com] 
Sent: Tuesday, August 12, 2014 3:59 PM
To: Chuck Lantz
Cc: dev@cordova.apache.org
Subject: Re: Feedback on "cordova plugin save" & friends

On Tue, Aug 12, 2014 at 08:40:25PM +, Chuck Lantz wrote:
> +1
> 
> That same pattern could be applied to platforms actually with an additional 
> version attribute:
> 
> 
>   ... things like icons, splaschreens, and maybe even packaging details 
> go here ...
> 
> 
> We could also follow a similar model if we wanted to say what top 
> level cordova version was used to create the project by using the 
> engine element from plugin.xml
> 
> 

Already had a PR [1] for saving and restoring platforms, that is MIA. Is there 
a specific reason why you want engines stated expilicitly, wouldn't platforms 
be sufficient.

[1] https://github.com/apache/cordova-lib/pull/18


> 
> -Chuck
> 
> -Original Message-
> From: mmo...@google.com [mailto:mmo...@google.com] On Behalf Of Michal 
> Mocny
> Sent: Tuesday, August 12, 2014 1:34 PM
> To: dev
> Cc: Gorkem Ercan
> Subject: Re: Feedback on "cordova plugin save" & friends
> 
>  is nice, but why not just  as plugin.xml already uses?
>  config.xml and plugin.xml share lots of tags already, why fork here?
> 
> -Michal
> 
> 
> On Tue, Aug 12, 2014 at 4:06 PM, Andrew Grieve  wrote:
> 
> > Played around with it and it's pretty clear to me that the ability 
> > to record your plugins & platforms in config.xml is a big step up.
> >
> > I do have some specific comments about the current design though:
> >
> > - Right now the plugin save saves all plugins to config.xml rather 
> > than just explicitly-installed plugins.
> >   - For the shrinkwrap use-case, you actually do want to record 
> > dependent plugins and their versions though, so it's still important for 
> > this case.
> > - Plugin restore doesn't work for locally installed plugins. e.g. 
> > try it with mobilespec. It won't remember to look in the right spot for 
> > plugins.
> > - Really don't like that  is used, since that could be 
> > confused by the tools with the runtime config.xml's  tag.
> > Instead, I think the syntax PGBuild uses would be better (minus the
> > gap:) http://docs.build.phonegap.com/en_US/configuring_plugins.md.html
> >   - Note there's a PR for adding  (CB-7142)
> >
> > When I was playing with it, I found that I wished that is would just 
> > run every time I added a plugin, rather than having to run the 
> > command explicitly afterwards. Maybe we could add an environment 
> > variable that will enable it while we're still experimenting? Then, 
> > too, we could make platform / plugin restore a part of `prepare`.
> >
> > Don't have the intention of picking up work on this in the near 
> > term, but wanted to at least share the feedback since I did play around 
> > with it.
> >

RE: Chrome-axiom

[Parashuram Narasimhan (MS OPEN TECH)]

http://goto ? The URL does not seem to resolve. Is there an external URL ? 

-Original Message-
From: Andrew Grieve [mailto:agri...@google.com] 
Sent: Tuesday, August 12, 2014 8:49 AM
To: dev
Subject: Chrome-axiom

New mailinglist that it may be worth joining.

"Chrome Axiom is the Chrome Developer Tooling platform. We're building the well 
lit path for web developers to succeed."

http://goto/chrome-axiom

RE: [Discuss] 3.6.0 Release

[Parashuram Narasimhan (MS OPEN TECH)]

Had a quick question on the whitelists. I remember that there was talk of using 
CSP to fix this issue. A CSP file may not be backward compatible, but could 
potentially just give us one list instead of 2 whitelists. The CSP file may be 
like the following

Content-Security-Policy: 
script-src 'self', foo.com, bar.com 
img-src cdn.com 
intent-src mail, sms

Note the new intent-src directive, that is basically used to launch external 
programs. Do you think this could be something we can look at, for 4.0 ? I am 
not sure if our whitelist xml file maps to a W3C spec, but CSP seems more like 
a standard. This is breaking, and 4.0 may be the right time to do it ? 

-Original Message-
From: iclell...@google.com [mailto:iclell...@google.com] On Behalf Of Ian 
Clelland
Sent: Tuesday, August 12, 2014 8:30 AM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release

I've created CB-7291 for the whitelist issue, and I've ported the code from 
June to the new-style configuration architecture and committed it to a named 
CB-7291 branch on cordova-android.

If anyone has any thoughts/opinions on the syntax or the proposal itself, or on 
what the defaults should be for new and upgrading applications, please chime in 
on the issue.



On Mon, Aug 11, 2014 at 11:26 AM, Parashuram Narasimhan (MS OPEN TECH) < 
panar...@microsoft.com> wrote:

> I think we should also finalize on the platform switches so that we 
> all agree on a pattern (even if it is different across platforms). 
> This way, we can release 3.6.0 with a set of switches, and ensure that 
> it is backward compatible.
>
>
> -Original Message-
> From: iclell...@google.com [mailto:iclell...@google.com] On Behalf Of 
> Ian Clelland
> Sent: Monday, August 11, 2014 8:00 AM
> To: dev@cordova.apache.org
> Subject: Re: [Discuss] 3.6.0 Release
>
> I'll see about committing that today; I've had to reorganize it quite 
> a bit after the Big Config Refactor.
>
> Joe, I'm pretty certain that your code is still in master, but 
> definitely add those tests to make sure, and to make sure we don't regress.
>
> Ian
>
>
> On Mon, Aug 11, 2014 at 10:52 AM, Marcel Kinard 
> wrote:
>
> > I agree with Joe.
> >
> > On Aug 11, 2014, at 10:02 AM, Joe Bowser  wrote:
> >
> > > Let's not release until the new whitelist is figured out.  That 
> > > feature
> > is
> > > too important.
> >
>

RE: Directory Structure - CLI directory config proposal

[Parashuram Narasimhan (MS OPEN TECH)]

Should we go ahead and create a branch in the main project so that you can also 
add your ideas to it? We could target this feature for a 4.0 release. 

-Original Message-
From: Mark Koudritsky [mailto:kam...@google.com] 
Sent: Monday, August 11, 2014 7:56 AM
To: dev@cordova.apache.org
Subject: Re: Directory Structure - CLI directory config proposal

I like the way it looks now, but I would argue that we need to take it another 
step further and make it a CordovaProject class that should only be 
instantiated once and contain all the info of ProjectMeta + most of the info 
passed around in the ad-hoc opts objects.

I'm somewhat against passing JSON strings as command line parameters. Would 
prefer to expose this to the command line via something along the lines of 
--config-mixin=some_file.json and as part of the JS API via something like 
cordova.create(, config_mixin).

All this said, I like the change the way it is right now.



On Sun, Aug 10, 2014 at 12:39 PM, Sergey Grebnov (Akvelon) < 
v-seg...@microsoft.com> wrote:

> Hi guys, sharing implementation prototype for this feature[1] . please 
> let me know what do you think.
>
> Highlights:
> 1. Introduced project settings class (ProjectMeta) which wraps 
> config.json and exposes project setting info including folders 
> locations (now passed to cordova methods instead of config.json) 2. 
> Support of the following cordova folders and their default values (no 
> changes here)
> ProjectMeta.defaultWwwPath = 'www';
> ProjectMeta.defaultPlatformsPath = 'platforms';
> ProjectMeta.defaultHooksPath = 'hooks';
> ProjectMeta.defaultMergesPath = 'merges';
> ProjectMeta.defaultPluginsPath = 'plugins';
>
> 3. Non-default folders structure could be passed during 'cordova create ..'
> cordova create hello io.cordova.hellocordova HelloCordova "{
> ""id"": ""io.cordova.hellocordova"", ""name"": ""HelloCordova"",
>  ""wwwPath"": ""."", ""platformsPath"": 
> ""cordova_components/platforms"",
>  ""pluginsPath"": ""cordova_components/plugins"", ""hooksPath"":
> ""cordova_components/hooks"",  ""mergesPath"":
> ""cordova_components/merges""  }"
>
> 4. More details and examples could be found here [2] 5. Source code 
> could be found here: [3], [4]
>
> [1] https://issues.apache.org/jira/browse/CB-7205
> [2] https://gist.github.com/daserge/aee3d3503c93accf3f0a
> [3]
> https://github.com/MSOpenTech/cordova-lib/tree/configurable-directorie
> s/
> [4]
> https://github.com/MSOpenTech/cordova-cli/tree/configurable-directorie
> s/
>
> Thx!
> Sergey
> From: Lisa Seacat DeLuca [mailto:ldel...@us.ibm.com]
> Sent: Thursday, July 10, 2014 11:50 AM
> To: dev@cordova.apache.org
> Subject: Re: Directory Structure - CLI directory config proposal
>
> I didn't have anything in mind as far as where the settings could be 
> made available.  I was more broaching the subject to see if it's 
> possible or if there would be a lot of code rewrite to make it work.  
> I'm not as familiar with how the CLI works or how the code decides to 
> place certain files in certain locations on build and creation.  So 
> defaulting to the rest of you for that expertise.  IBM would like to 
> see this happen from a product standpoint.
>
>
> Lisa
> @LisaSeacat
>
>
>
> Gorkem Ercan ---07/08/2014 03:36:54 PM---On Tue, Jul 08, 2014 at 
> 09:02:03AM -0400, Michal Mocny wrote: > Lets see what Lisa had in 
> mind, but
>
> From: Gorkem Ercan 
> To: dev@cordova.apache.org
> Date: 07/08/2014 03:36 PM
> Subject: Re: Directory Structure - CLI directory config proposal 
> ____
>
>
>
>
> On Tue, Jul 08, 2014 at 09:02:03AM -0400, Michal Mocny wrote:
> > Lets see what Lisa had in mind, but I always assumed it fit into 
> > .cordova/config.json.
> >
>
> Do you consider the contents of .cordova/config.json to be shared 
> among developers of a project.
>
>
> >
> > On Tue, Jul 8, 2014 at 8:46 AM, Andrew Grieve 
> wrote:
> >
> > > Wondering what this will look like. config.xml settings?
> > > .cordova/config.json? A new config file?
> > >
> > >
> > > On Mon, Jul 7, 2014 at 2:43 PM, Parashuram Narasimhan (MS OPEN 
> > > TECH) < panar...@microsoft.com> wrote:
> > >
> > > > +1 to this proposal. If we are able to agree on a 

RE: [Discuss] 3.6.0 Release

[Parashuram Narasimhan (MS OPEN TECH)]

I think we should also finalize on the platform switches so that we all agree 
on a pattern (even if it is different across platforms). This way, we can 
release 3.6.0 with a set of switches, and ensure that it is backward 
compatible. 


-Original Message-
From: iclell...@google.com [mailto:iclell...@google.com] On Behalf Of Ian 
Clelland
Sent: Monday, August 11, 2014 8:00 AM
To: dev@cordova.apache.org
Subject: Re: [Discuss] 3.6.0 Release

I'll see about committing that today; I've had to reorganize it quite a bit 
after the Big Config Refactor.

Joe, I'm pretty certain that your code is still in master, but definitely add 
those tests to make sure, and to make sure we don't regress.

Ian


On Mon, Aug 11, 2014 at 10:52 AM, Marcel Kinard  wrote:

> I agree with Joe.
>
> On Aug 11, 2014, at 10:02 AM, Joe Bowser  wrote:
>
> > Let's not release until the new whitelist is figured out.  That 
> > feature
> is
> > too important.
>

RE: platform switches for Windows Universal Apps

[Parashuram Narasimhan (MS OPEN TECH)]

It would be great if we have a unified format across all platforms. It would be 
great if these options can also be specified in config.xml - that would also 
help IDEs. 

-Original Message-
From: Jesse [mailto:purplecabb...@gmail.com] 
Sent: Thursday, August 7, 2014 3:32 PM
To: dev@cordova.apache.org
Subject: Re: platform switches for Windows Universal Apps

cordova run ios --retina --64bit --family ipad

cordova run android --target=X

We need to clean this up I think ...



@purplecabbage
risingj.com


On Thu, Aug 7, 2014 at 2:58 PM, Parashuram Narasimhan (MS OPEN TECH) < 
panar...@microsoft.com> wrote:

> I think we should also ensure use reuse concepts that already exist in 
> other platforms. How are phone vs tablet options specified for Android 
> and iOS on the command line? How do we plan to do it in the future ?
>
> -Original Message-
> From: Sergey Grebnov (Akvelon) [mailto:v-seg...@microsoft.com]
> Sent: Thursday, August 7, 2014 5:25 AM
> To: dev@cordova.apache.org
> Subject: platform switches for Windows Universal Apps
>
> New Windows platform template supports standard Windows apps as well 
> as Windows Phone 8.1 apps. As a developer I need an option to specify 
> which target I should run when doing 'cordova run/emulate' (run phone 
> version on the device/emulator or run windows store app).
>
> Current draft implementation uses '-store' and '-phone' switches but 
> we should discuss final names for them. Here are a few alternatives.  
> Thoughts?
>
> --tablet
> --handset or --phone
> or --targetDevice="tablet, handset" <- similar to how we define target 
> chip architecture
>
> Thx!
> Sergey
>

RE: platform switches for Windows Universal Apps

[Parashuram Narasimhan (MS OPEN TECH)]

I think we should also ensure use reuse concepts that already exist in other 
platforms. How are phone vs tablet options specified for Android and iOS on the 
command line? How do we plan to do it in the future ?

-Original Message-
From: Sergey Grebnov (Akvelon) [mailto:v-seg...@microsoft.com] 
Sent: Thursday, August 7, 2014 5:25 AM
To: dev@cordova.apache.org
Subject: platform switches for Windows Universal Apps

New Windows platform template supports standard Windows apps as well as Windows 
Phone 8.1 apps. As a developer I need an option to specify which target I 
should run when doing 'cordova run/emulate' (run phone version on the 
device/emulator or run windows store app).

Current draft implementation uses '-store' and '-phone' switches but we should 
discuss final names for them. Here are a few alternatives.  Thoughts?

--tablet
--handset or --phone
or --targetDevice="tablet, handset" <- similar to how we define target chip 
architecture

Thx!
Sergey

RE: Windows Phone Camera bug vote

[Parashuram Narasimhan (MS OPEN TECH)]

I have also forwarded this bug to my friends in Windows Phone team :) 

-Original Message-
From: Marcel Kinard [mailto:cmarc...@gmail.com] 
Sent: Wednesday, August 6, 2014 2:13 PM
To: dev@cordova.apache.org
Subject: Re: Windows Phone Camera bug vote

Done.

On Aug 6, 2014, at 2:59 PM, Jesse  wrote:

> Please go here:
> http://wpdev.uservoice.com/forums/110705-dev-platform/suggestions/3744
> 086-cameracapturetask
> 
> and vote so that MS will fix a bug that forces all images taken by the 
> camera to be copied to CameraRoll.
> 
> Your vote counts! Use 3 of em!
> 
> 
> Cheers,
>  Jesse
> 
> @purplecabbage
> risingj.com

RE: Proposal: remove platform versions from platfroms.js

[Parashuram Narasimhan (MS OPEN TECH)]

I would not be able to join the Friday hangout, but here are my main concerns -

I agree that it would be best to always give the users the latest version of 
the platform and keeping it independent of the CLI. However, given that Cordova 
now also caters to enterprise users, backwards compatibility and reproducible 
dev environment. 
The question would be - what should be the default behavior? When a new user 
downloads the CLI and then creates a project, we could download the latest 
versions, but will they always be saved in the config.xml so that they can be 
restored? Does it not make more sense to semver them to ensure that breaking 
changes do not impact users who do not want to upgrade their projects? Asking 
users to change config.xml if they need to preserve platforms every time may 
not be a good default.  

Does this change also mean  that every release of the Cordova CLI will be 
tested against multiple versions of the platforms? 

In case of Visual Studio, a version of CLI is bundled with the tools and the 
user cannot choose any other version. This simplifies issues with support and 
is a guarantee that the specific version of the CLI works with a specific 
version of VS tools. Visual Studio and Cordova have different release timings 
and would it always be possible to guarantee that a newer version of the CLI 
works with an older version of the VS tools? 

-Original Message-
From: Jesse [mailto:purplecabb...@gmail.com] 
Sent: Wednesday, July 23, 2014 10:47 AM
To: dev@cordova.apache.org
Subject: Re: Proposal: remove platform versions from platfroms.js

Yeah, let's discuss the full impact on Friday.

@purplecabbage
risingj.com


On Wed, Jul 23, 2014 at 7:36 AM, Michal Mocny  wrote:

> This sounds like a great topic for hangout Friday.  Glad to have a 
> concrete proposal / some counter arguments to discuss.
>
>
> On Wed, Jul 23, 2014 at 10:22 AM, Mark Koudritsky 
> wrote:
>
> > >
> > > Currently WebWorks ships specific versions of things.
> > > If we had shipped unpinned versions of stuff, then eventually we 
> > > would have created projects which our UI wouldn't have recognized 
> > > as valid (because, they e.g. Didn't have a ".cordova", or a 
> > > "hooks", or a
> "merges"
> > > or whichever things we had been using to determine if a project 
> > > was
> > valid).
> > >
> >
> > As long as you continue to ship a version of cordova-backberry 
> > bundled
> with
> > WebWorks, it won't be affected by the change I propose. CLI will use 
> > that bundled version just like it does now using the settings in 
> > .cordova/config.json. We do the same thing with cca.
> >
> > If in the future you decide to stop bundling cordova-blackberry with 
> > WebWorks and switch to the npm published versions, I see several 
> > good
> ways
> > for doing that, but in any case, you will probably want to expose 
> > the version (or range of versions) to use as a user editable setting.
> >
>

RE: Proposal: remove platform versions from platfroms.js

[Parashuram Narasimhan (MS OPEN TECH)]

I was thinking platforms are devDependencies and plugins are dependencies :) 

In a way, that’s how the bundling works - plugins are packaged with the app, 
while platforms are only needed during development !!

-Original Message-
From: Anis KADRI [mailto:anis.ka...@gmail.com] 
Sent: Wednesday, July 23, 2014 10:54 AM
To: dev@cordova.apache.org
Subject: Re: Proposal: remove platform versions from platfroms.js

+1 for package.json for platforms. plugins might a bit trickier but 
+still
doable, we could get rid of plugins/ but we somehow need to keep track of them 
in node_modules/ (maybe use one of the 10 config files we have).
Platforms in package.json should cause no problems though, add/remove 
platforms, pin/unpin versions if required.


On Wed, Jul 23, 2014 at 7:36 AM, Michal Mocny  wrote:

> This sounds like a great topic for hangout Friday.  Glad to have a 
> concrete proposal / some counter arguments to discuss.
>
>
> On Wed, Jul 23, 2014 at 10:22 AM, Mark Koudritsky 
> wrote:
>
> > >
> > > Currently WebWorks ships specific versions of things.
> > > If we had shipped unpinned versions of stuff, then eventually we 
> > > would have created projects which our UI wouldn't have recognized 
> > > as valid (because, they e.g. Didn't have a ".cordova", or a 
> > > "hooks", or a
> "merges"
> > > or whichever things we had been using to determine if a project 
> > > was
> > valid).
> > >
> >
> > As long as you continue to ship a version of cordova-backberry 
> > bundled
> with
> > WebWorks, it won't be affected by the change I propose. CLI will use 
> > that bundled version just like it does now using the settings in 
> > .cordova/config.json. We do the same thing with cca.
> >
> > If in the future you decide to stop bundling cordova-blackberry with 
> > WebWorks and switch to the npm published versions, I see several 
> > good
> ways
> > for doing that, but in any case, you will probably want to expose 
> > the version (or range of versions) to use as a user editable setting.
> >
>

RE: [Discuss] The Future of Ripple as a Top Level ASF Project

[Parashuram Narasimhan (MS OPEN TECH)]

Hi Gorkem,

We have produced a couple of prototypes to show how Ripple can be used as a 
platform. We have been able to delegate most of the plugin specific 
functionality to the plugin itself, that includes a  tag in 
its plugin.xml. 
We are definitely interested in supporting Ripple and do not have a preference 
about it becoming a Cordova sub project, or staying a top level project. 

Would love to hear your feedback on this prototype, and any suggestions that 
you may have on taking this forward. 

-Original Message-
From: Gorkem Ercan [mailto:gorkem.er...@gmail.com] 
Sent: Friday, July 18, 2014 9:06 AM
To: dev@cordova.apache.org
Subject: Re: [Discuss] The Future of Ripple as a Top Level ASF Project

Did this discussion concluded? What was the conclusion?

I would like to see Ripple to have a healthy future and if having it as a 
sub-project on Cordova ensures it, I would like to help with that.
I think we can have one or two people from Red Hat assisting on the maintenance 
of Ripple. This probably is not enough for a top-level project but may be 
enough to continue as a sub-project.

Also, I know there are tools (folks from MSFT, I am looking at you) that use 
ripple, they may also be ultimately interested on the well being of the project.
--
Gorkem




On Tue, Apr 22, 2014 at 10:30 AM, Brent Lintner 
wrote:

> Hey All,
>
> Since becoming an incubator project (being donated graciously by 
> BlackBerry), Ripple has seen positive contributions.
>
> However, it is also apparent that the community does not seem large 
> enough to sustain a project like this as a top level project (let 
> alone an individual PMC).
>
> Three of the original contributors/creators of Ripple are now fully 
> involved in a new technology startup in an unrelated field and 
> therefore we no longer have the resources to support Ripple in ASF. 
> Also, BlackBerry has given no resources to help since donating Ripple 
> to the ASF (this might be due to a change in their internal priorities).
>
> Given this, I would like to propose:
>
> 1. We find more community members willing to lead committership of the 
> project, and see how that goes.
>
> 2. We also consider the eventuality of folding Ripple into another ASF 
> project, if possible. If so, it would seem Cordova is a candidate for 
> this, especially given the project being one of Ripple's main focus and 
> support.
> If the community votes for this, we should involve the Cordova 
> community to gage their interests as well (I've CC'd their mailing list in 
> this email).
>
> 3. If the above does not work out, I would then suggest we consider 
> the most unfortunate (put perhaps prudent) eventuality, which is to "fail"
> Ripple as an incubator project. "fail" is this case, not being negative.
>
> And, if it does fail incubation- what does ASF normally do with the 
> project?
>
> Does it get donated back to the original party? Does it get moved to 
> an open source project outside of ASF (under a different license)?
>
> Any insight would be appreciated!
>
> --
> Brent Lintner
>

RE: Proposal: remove platform versions from platfroms.js

[Parashuram Narasimhan (MS OPEN TECH)]

Always downloading the latest will also be a problem for Visual Studio that 
uses Cordova as the IDE. 

We would need a way where if 2 developers checkout the project and use a 
specific version of Cordova (CLI), they should have the same version of 
platform too. Given that the version of the platforms is not picked up from any 
place in the project and is explicitly specified only in the CLI, this would be 
hard. 

If a user does not check in the platform versions, how will be they able to 
recreate the platforms again ? 

A random idea - how about we treat Cordova projects like a NodeJs project. 
Cordova is much like a "build system" (think Grunt). There is a package.json 
(another config file, sign :( ) that specifies the version of platforms and 
plugins that this Cordova platform needs. This would be like how Grunt version 
is specified in package.json. The Cordova-cli would be like Grunt-cli. This 
way, plugin and platforms can simply be installed using npm and are treated 
just like packages to "build" an app. 

-Original Message-
From: Josh Soref [mailto:jso...@blackberry.com] 
Sent: Tuesday, July 22, 2014 3:06 PM
To: dev@cordova.apache.org
Subject: Re: Proposal: remove platform versions from platfroms.js

Mark Koudritsky wrote:
>As the next step in decoupling platform releases I would like to remove 
>the hard-coded version in platform.js and let the CLI to download the 
>latest platform version available on npm by default.

As long as the file will continue to support pinned versions…

I'm not quite sure where I stand on this as a default behavior.

Currently WebWorks ships specific versions of things.
If we had shipped unpinned versions of stuff, then eventually we would have 
created projects which our UI wouldn't have recognized as valid (because, they 
e.g. Didn't have a ".cordova", or a "hooks", or a "merges"
or whichever things we had been using to determine if a project was valid).

The second version of the problem is that I'd sort of like to be able to 
/think/ about letting webworks users get newer versions of cordova-blackberry 
w/o necessarily having to install a new "webworks".
(This is sort of the opposite of the previous one)

The third, is that I might want to have distinct version series for webworks 
based things and cordova based things (I'm not really sure on this point).

One approach is to rely on api versioning so instead of platform = 3.5 ->
3.6 -> 3.7, we could have platform = 3.5:3.5 -> 3.5:3.6, where the major number 
is a cli version. That would in theory let me offer different versions of the 
platform to a cli w/o giving it a version that will just break it.

>- It will hit the network for every "platform add" that has no version 
>explicitly specified. In most cases the reply from npm will be an "HTTP
>304
>- Not Modified".
> - We'll have to add in some sort of check that the version of CLI that 
>you have works with the platform. E.g. current tools might not work 
>with cordova-5.0. In than case we can display an error that instructs 
>the user to either upgrade CLI or specify the platform version 
>explicitly.

Not a big fan of this "specify explicitly" nor "command line", webworks is 
often used w/ a GUI (well, we ship one, I'm not sure how often it's used…).

WebWorks also ships its own version of cordova-blackberry, which isn't 
precisely the same as the version that's in the registry. I'm not sure I'd want 
to have to hit the network for this. At the very least, I'd like information 
about how to cache our version into the cache so at least something is present.