+1. We should change ci.cordova.io to point to the new Jenkins server location
for periodic build.
-Nikhil
-Original Message-
From: Shazron [mailto:shaz...@gmail.com]
Sent: Thursday, June 23, 2016 11:18 AM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Buildbot deprecation
Thank
This is awesome, Shaz! Love it!
-Nikhil
-Original Message-
From: Shazron [mailto:shaz...@gmail.com]
Sent: Monday, June 13, 2016 1:51 PM
To: dev@cordova.apache.org
Subject: Re: Apache Cordova Project Global Status Page
-Original Message-
From: Nikhil Khandelwal [mailto:nikhi...@microsoft.com]
Sent: Tuesday, May 31, 2016 1:35 PM
To: dev@cordova.apache.org
Subject: RE: [DISCUSS] Cordova-Android 5.2.0 Release
Support for incremental prepare (PR #295) has been merged. We should be ready
for a release
Support for incremental prepare (PR #295) has been merged. We should be ready
for a release.
-Nikhil
-Original Message-
From: Joe Bowser [mailto:bows...@gmail.com]
Sent: Thursday, May 26, 2016 2:52 PM
To: dev
Subject: Re: [DISCUSS] Cordova-Android 5.2.0 Release
31, 2016 8:22 AM
To: dev <dev@cordova.apache.org>
Subject: Re: Proposal: Change Android Project Directory Structure to Android
Studio style
On Fri, May 27, 2016 at 12:22 PM, Nikhil Khandelwal <nikhi...@microsoft.com>
wrote:
> As I see it, a change to the directory structure wi
As I see it, a change to the directory structure will break almost every
Android plugin currently out there.
There are atleast 20K references [1] on github where people use depend on the
current directory structure for android: "res/xml/config.xml".
Taking the example of a config.xml
I agree this qualifies for a minor version bump. I feel like these are the
inner workings of the clean command and not a very explicit contract that we
know anyone depends on.
-Nikhil
-Original Message-
From: Jason Ginchereau [mailto:jason...@microsoft.com]
Sent: Friday, May 27, 2016
+1. It will be great to get this PR merged now that cordova-common has been
released: https://github.com/apache/cordova-android/pull/295/files
-Nikhil
-Original Message-
From: Simon MacDonald [mailto:simon.macdon...@gmail.com]
Sent: Wednesday, May 25, 2016 10:38 AM
To:
The only known issue with Node v6 and Cordova is: CB-11200. The bug breaks
uninstallation of plugins with custom frameworks for iOS platform, such as
Facebook plugin.
This JIRA has been resolved in corodva-ios master. We'll need a release of
cordova-ios and a tools release pinning that
I wanted to bring this to the dev list's attention:
https://github.com/cordova/cordova-discuss/issues/39.
The idea is to have an LTS version of cordova. It might be a good idea to
re-visit & document our release cadence as well.
-Nikhil
We'll need a cordova-ios release to make that happen. However, cordova-ios has
a recent regression that needs to be fixed before we make a release:
https://github.com/apache/cordova-ios/commit/cab0baa0f7c4d789171b0147da41a85471660c85
-Nikhil
-Original Message-
From: Carlos Santana
+1. This feels like a "core" capability.
-Nikhil
-Original Message-
From: Suraj Pindoria [mailto:suraj.pindo...@yahoo.com.INVALID]
Sent: Wednesday, May 11, 2016 9:08 AM
To: dev@cordova.apache.org
Subject: Re: proposal for new core plugin to control screen orientation
+1
I have been
amp; npm run config && npm test
:-)
On Thu, Feb 18, 2016 at 4:40 PM Nikhil Khandelwal <nikhi...@microsoft.com>
wrote:
> I think for plugins, platform name should be required as part of title
> of the PR and commit message in addition to JIRA number.
>
> Checklist:
+1. Let's do that!
-Nikhil
-Original Message-
From: Kerri Shotts [mailto:kerrisho...@gmail.com]
Sent: Friday, May 6, 2016 7:58 AM
To: dev@cordova.apache.org; dev@cordova.apache.org
Subject: Re: [Android] Ending support for Ice Cream Sandwich?
+1
~Kerri
I want to call attention to this proposal. Please help review this and provide
feedback. It adds the critical ability to run tests using paramedic on every PR.
-Nikhil
-Original Message-
From: Sarangan Rajamanickam [mailto:saraj...@microsoft.com]
Sent: Wednesday, April 27, 2016 5:01 PM
I’m hearing two purposes of a user list:
- Key announcements
- Self-help for users
I’m not totally convinced that slack + stack overflow are not sufficient for
finding resources & common answers for cordova issues. Creating another channel
will just fragment the community.
FWIW, our blog got
Oh great! I have not taken a close look at the implementation itself. Perhaps
you already had some of this in mind.
As for the syntax for changing attributes, I would recommend something like
this:
Also, we should always prioritize config.xml edits over plugin.xml (giving the
end developer
As far as I am aware, no one from Microsoft Cordova team will be able to make
it.
+1 for a google hangout.
-Nikhil
-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com]
Sent: Friday, April 15, 2016 2:47 PM
To: dev@cordova.apache.org
Subject: Re: Apache Con NA May 11-13
Yes, I noticed these updates too. I plan to reach out to Eddy to see if we can
consolidate fixes into one github repo here[1]. We're fixing Windows
implementation in that repo.
[1]: https://github.com/phonegap/phonegap-plugin-barcodescanner
-Nikhil
-Original Message-
From: julio cesar
This seems useful.
I'm guessing publishing the AAR requires us to establish a release process for
it? Are you planning to document the guidelines for releasing, signing,
building & versioning of this? Do you propose - every time cordova-android is
released we well release AAR as well? Or this
There are some docs here:
1.
http://cordova.apache.org/docs/en/latest/guide/hybrid/plugins/index.html#publishing-plugins
2.
http://cordova.apache.org/docs/en/latest/guide/hybrid/plugins/index.html#integrating-with-plugin-search
-Nikhil
-Original Message-
From: Brad Reynolds
I noticed there is an issue with ios-deploy/cordova-ios & Xcode 7.3. This seems
fairly high priority: CB-10962.
If the fix/workaround happens to be in cordova-ios - we might have to do
another release or add it to this release.
-Nikhil
-Original Message-
From: Shazron
;
>> On Mar 10, 2016, at 8:22 PM, Nikhil Khandelwal <nikhi...@microsoft.com>
>> wrote:
>>
>> Our cordova-cli readme has become super long & not been maintained over the
>> years. It repeats a lot of content from the docs. I have simplified i
Our cordova-cli readme has become super long & not been maintained over the
years. It repeats a lot of content from the docs. I have simplified it
significantly by linking to relevant getting started, filing issues,
contribution etc. sections that are part of our website. This should help
This is a regression in Node 5.7.0 that they fixed as part of Node 5.7.1:
https://issues.apache.org/jira/browse/CB-10675
https://github.com/nodejs/node/blob/v5.7.1/CHANGELOG.md
Move to Node 5.7.1
-Nikhil
-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com]
Sent:
In Visual Studio, we have a feature similar to "merges" to allow users to
override content of platform folder. We use hooks to copy the contents of the
folder to the platforms directory. Other than that VS does consider platforms/
directory a build artifact and often ends up deleting it on
+1 for trying "Edit on Github" - anything that _may_ increase contributions to
the docs is welcome. :)
-Nikhil
-Original Message-
From: Shazron [mailto:shaz...@gmail.com]
Sent: Tuesday, March 8, 2016 10:26 AM
To: dev@cordova.apache.org
Subject: Re: Edit to Edit on Github for Docs
I'm
What's our deprecation policy? Should we log a deprecation message before
remove this support. What alternatives do Cordova developers have - are there
other plugins which provide the equivalent functionality - perhaps with a
better API - as opposed to polling events every 1% battery drop.
Thanks, Jesse!
-Nikhil
-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com]
Sent: Friday, March 4, 2016 1:58 PM
To: dev@cordova.apache.org
Subject: Re: DISCUSS cordova-paramedic
+1 Jesse for the contribution
On Fri, Mar 4, 2016 at 4:01 PM Jesse
I agree - this is for testing purposes only - no VOTE required.
-Nikhil
On 3/4/16, 11:08 AM, "Steven Gill" wrote:
>The real question is do we vote on it before posting to npm.
>
>Since it isn't for general release distribution, but just for testing, I
>would say you
Welcome! Looking forward to your contributions!
-Nikhil
-Original Message-
From: So, Byoungro [mailto:byoungro...@intel.com]
Sent: Wednesday, March 2, 2016 8:16 PM
To: dev@cordova.apache.org
Subject: Re: Personal Introduction: Jerroyd Moore
Welcome on board, Jerroyd.
Byoungro So
SSG /
Yes, I don't see a reason to disable this.
-Nikhil
-Original Message-
From: dharmendra sharma [mailto:dharam.accent...@gmail.com]
Sent: Tuesday, March 1, 2016 5:31 AM
To: dev@cordova.apache.org
Subject: Re: cordova-cli Travis CI
I suggest we should keep Travis CI. That will enhance the
I think pinning plugins in the CLI is causing a bunch of confusion (see
CB-10677) as cordova plugin add might not get you the latest released plugin.
This is a change in behavior - perhaps - we should log when the plugin is
different from the latest released version. Also, there is an issue
Since this is a bug we encountered previously as well - should we block on it?
Also, looks like it will not be a patch release and we may need an accompanying
tools release. Is that correct?
-Nikhil
-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com]
Sent: Wednesday,
These commands look great - it will be good to add them to release process docs
if they are not already there.
-Nikhil
-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com]
Sent: Wednesday, February 24, 2016 10:03 AM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS]
I think you have to invoke cordova build with the CALL command to ensure it
does not cause your script to exit.
call cordova build
-Nikhil
-Original Message-
From: So, Byoungro [mailto:byoungro...@intel.com]
Sent: Wednesday, February 24, 2016 12:19 PM
To: dev@cordova.apache.org
Where are we with releases here? Can we still do a patch release (not requiring
a TOOLS update)?
Looks like there is also this JIRA:
https://issues.apache.org/jira/browse/CB-10493 which is causing iOS apps to be
rejected.
Thanks,
Nikhil
-Original Message-
From: Carlos Santana
I think for plugins, platform name should be required as part of title of the
PR and commit message in addition to JIRA number.
Checklist:
[ ] Tests that were added or run for a new feature/regressions
[ ] Does the new feature broadly apply to multiple platforms?
We probably need to make it
When we were building cordova plugin search, we had ideas to have a page
dedicated to listing plugins under meaningful categories. However, we could not
do that unless plugins had the correct keywords. I want to piggyback on this
call for plugins to add the correct keywords.
How about these
ifications
Analytics
Security
Cloud :-) just kidding
On Mon, Feb 8, 2016 at 12:50 PM Nikhil Khandelwal <nikhi...@microsoft.com>
wrote:
> When we were building cordova plugin search, we had ideas to have a
> page dedicated to listing plugins under meaningful categories.
>
Looks like we might need another plugins release. I have been triaging JIRAs
after the latest set of releases and these look like high priority enough to
get a release out for them. There are number of regressions/bug fixes that we
want to get released. These changes are simple and probably
I like the idea. However, currently plugins are being identified with
"ecosystem:cordova" keyword. We might have to maintain that for all plugins
that do not switch to these new keyword below.
For "tool" there is at least one example of a tool which currently shows up in
plugin search:
com> wrote:
> +1
>
> On Thu, Jan 21, 2016 at 1:38 PM, Nikhil Khandelwal
> <nikhi...@microsoft.com
> >
> wrote:
>
> > Should we version our docs on every major version (instead of minor
> > version) of cordova CLI that comes out? Should the next version of
&g
Rob,
I appreciate your enthusiasm. Cordova docs need a lot of improvement. We did a
survey in October and 70% of negative comments focused on problems with our
docs.
Committers at Microsoft are pushing hard to improve the Cordova docs - but we
need a lot of help from the community. We are
+1 for 6-month deprecation (or even earlier) for platforms where we have
already released a platform with Platform API. Duplicated code can be a real
maintenance problem here.
For other platforms that we have not released a platform API implementation and
do not plan to e.g. WP8, WebOS, Ubuntu
I'm curious what caused the regression? Why do we not have tests for this
important scenario?
-Nikhil
-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com]
Sent: Monday, January 25, 2016 1:19 AM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] inAppBrowser plugin
KADRI <anis.ka...@gmail.com> wrote:
> YES YES YES! Please cordova_plugins.js is killing me.
>
> On Wed, Jan 20, 2016 at 4:10 PM Nikhil Khandelwal
> <nikhi...@microsoft.com>
> wrote:
>
>> Where are we with --browserify support? From what I can see, most or
Should we version our docs on every major version (instead of minor version) of
cordova CLI that comes out? Should the next version of the docs be "6.x"?
Honestly, not much changes every minor release and maintaining multiple copies
has quite a few downsides w.r.t. SEO (referring to older
workflow behind a --no-browserify flag.
I'll plan to write a blog post and put it up for review week after PGDAY.
On Thu, Jan 21, 2016 at 1:19 PM, Nikhil Khandelwal <nikhi...@microsoft.com>
wrote:
> Great! Looks like we just need to update the help text then. I sent a
> PR for this: https:
Where are we with --browserify support? From what I can see, most or all the
work has been completed:
https://issues.apache.org/jira/browse/CB-8801
Should it move out of experimental now?[1]
It will help to document it and perhaps blog about its benefits as opposed to
the current default
ility.
> > I
> also
> > don't want to delay a release for people not using Crosswalk.
> >
> > Do we know of any other plugins that use the NDK? If there aren't
> > any,
> I'm
> > more agreeable to adding the file since it won't break others.
> &
If this is a regression in behavior and CrossWalk will not work out of the box
- we should consider fixing it. Sounds like it is a simple fix. Is there a JIRA
for this?
Overall, we shouldn't require/expect Cordova JS developers to modify gradle
files.
-Nikhil
-Original Message-
From:
We had a good discussion about this offline with Joe, Simon, Steve, Jesse,
Parashu and Jason. We came to the following agreement:
This is a temporary fix to the plugins which we need to take to ensure Cordova
5.x tools behavior of using the edge plugins does not break for our users. We
will
I don’t think there was a design reason. As Bill mentions in CB-10201 - for
some odd reason gradlew from the android SDK directory (the source of the file)
does not have the execute permissions. It makes sense for us to set the
permissions either after copying or before invoking it. We do this
Sorry for being late to respond. It will be great if we can publish the plugins
release on npm at the same time as the tools release which pins android 5.0.
Not publishing at the same time will break a very simple use case that Alex
described below.
-Nikhil
On 11/20/15, 12:43 PM, "Steven
>>>
>>> Held up currently with
>>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fiss
>>> ue
>>> s.apache.org%2fjira%2fbrowse%2fCB-9872=01%7c01%7cTBARHAM%40064d
>>> .m
>>> gd.microsoft.com%7cc4dbc8e54ea148e81f6b
It seems to be caused by this commit:
https://github.com/apache/cordova-plugin-device-motion/commit/90ef274ea8cae2a5639d148b769f7718f33b7134
-Nikhil
-Original Message-
From: Dmitry Blotsky [mailto:dblot...@microsoft.com]
Sent: Tuesday, October 27, 2015 9:24 PM
To:
Steve,
Did you mean you will shut this down?
https://github.com/cordova/apache-blog-posts
And not https://github.com/apache/cordova-docs
-Nikhil
-Original Message-
From: Shazron [mailto:shaz...@gmail.com]
Sent: Wednesday, October 28, 2015 6:53 PM
To: dev@cordova.apache.org
Subject:
:12 AM, Nikhil Khandelwal <nikhi...@microsoft.com>
wrote:
> I am fine with all these recommendations. The key is to be consistent.
> I have documented this and more details here:
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithu
> b.com%2fapache%2fcordova-
unless anyone has concerns.
-Steve
On Fri, Oct 23, 2015 at 12:57 PM, Nikhil Khandelwal <nikhi...@microsoft.com>
wrote:
> +1 - I'm hoping we'll release iOS as well before the next CLI release.
>
> -Nikhil
>
> -Original Message-
> From: Carlos Santana [mailto:csan
+1 - I'm hoping we'll release iOS as well before the next CLI release.
-Nikhil
-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com]
Sent: Friday, October 23, 2015 12:48 PM
To: dev@cordova.apache.org
Subject: [DISCUSS] Tools Release
I think we should release a version
/?url=http%3a%2f%2fhi.im%2fsimonmacdonald=01%7c01%7cnikhilkh%40microsoft.com%7caf6077fb55224d7b1d2c08d2db1508fe%7c72f988bf86f141af91ab2d7cd011db47%7c1=50aLt1e0sp9z4TrrSBiMnAaBdSj1RrUuIEcnPaHGD1U%3d
On Wed, Oct 21, 2015 at 6:13 PM, Nikhil Khandelwal <nikhi...@microsoft.com>
wrote:
> Th
unFhyA0X7IzCXRdEG4bxmbZT0rgu0%3d
My plan is to send pull requests to some plugins with the common issues, so
people can see how to update.
On Tue, Oct 20, 2015 at 9:45 PM, Nikhil Khandelwal <nikhi...@microsoft.com>
wrote:
> Where are we with this release?
>
> Alexander Sor
impact the 5.0 release of Android?
On Tue, Oct 20, 2015 at 6:07 PM, Nikhil Khandelwal <nikhi...@microsoft.com>
wrote:
> It got checked in earlier this morning.
>
> -Nikhil
>
> -Original Message-
> From: Joe Bowser [mailto:bows...@gmail.com]
> Sent: Tuesday, Octobe
erflow.com/search?q=%22XCODE+7%22+%5Bcordova%5D
-Original Message-----
From: Nikhil Khandelwal [mailto:nikhi...@microsoft.com]
Sent: Wednesday, October 21, 2015 7:09 AM
To: dev@cordova.apache.org
Subject: RE: [DISCUSS] cordova-ios 4.0.0 release
What are good tasks to be poached on cordo
Thanks, Joe for the summary of the impact later.
-1. IMO - a naming change is no worth the effort and future breakage.
-Nikhil
-Original Message-
From: Joe Bowser [mailto:bows...@gmail.com]
Sent: Wednesday, October 21, 2015 11:06 AM
To: dev
Subject: Re:
I am fine with all these recommendations. The key is to be consistent. I have
documented this and more details here:
https://github.com/apache/cordova-coho/pull/97
Let's continue discussion on the PR or this thread. I don't want the process to
be heavy-weight - though my goal is to address few
this get you what you want? Why does it absolutely need to be
> > in
> npm registry?
> >
> > I really don't think will be a good idea to publish two npm packages
> "cordova-lib" and "cordova-common"
> >
> > Sorry if I'm being a pain in the
ndroid?
On Tue, Oct 20, 2015 at 2:32 PM, Parashuram N <panar...@microsoft.com>
wrote:
> +1 - YES please. Requiring cordoba-common for my
> react-native-cordova-plugin adapter was a nightmare !!
>
>
>
>
> On 10/20/15, 2:23 PM, "Nikhil Khandelwal" <nikhi...@micro
Where are we with this release?
Alexander Sorokin did some analysis on plugin build failures because of this
ios-4.0-dev and there are quite a few.
This spreadsheet summarizes the build failures with the build log in a comment:
Thanks Joe!
Most of the changes look good. I did leave a comment on the design of the
CordovaPlugin base class - I don’t want to block progress on that. Feel free to
merge it - but let's see if we can rationalize why we are adding the base class
methods - it seems only for the Geoloc plugin -
I think there are two aspects of the CI. I think Dmitry is handling the
BuildBOT CI update to support android-23.
Travis CI need android 23 which is causing Joe's change to fail in PR state:
https://travis-ci.org/apache/cordova-android/builds/83964922
Joe you need to update Travis, as
If we look at GA for survey vs GA for website, there is a huge difference in
the demographics. For example, there are almost no survey impressions from
India, while India contributes the largest % of website users of any country.
I'm all for using other channels to promote the survey, however,
I am in favor of keeping it running without making any updates. There is fairly
high % of users using cordova cli version < cordova 5 (~25% based on survey
responses). Since our survey is not yet broadly publicized, but only using
twitter, this number is likely higher.
We should look at
t 2, 2015 at 1:38 PM, Homer, Tony <tony.ho...@intel.com> wrote:
>>
>>> I think this would be a great way to spur discussion about shared
>> concerns.
>>> It would be great if we could identify some opportunities to make
>>> changes that would be beneficia
Thanks for all the input! Here's the final public facing URL:
https://apachecordovabot.typeform.com/to/BCc5co.
It will be great to get some of this data before the F2F meeting. Let's all
tweet about it, post it on slack etc.
In couple of days we can see if we can want to make more tweaks to
Sorry for not responding earlier. I like where this is going. I have a bunch of
comments on the PRs.
I have some confusion around how CordovaPlugin has a protected field
'permissions' and what a derived CordovaPlugin is supposed to do with it. None
of our core plugins seem to use it.
Thanks,
Wohoo! Let's do it!
-Nikhil
-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com]
Sent: Friday, October 2, 2015 6:06 PM
To: dev@cordova.apache.org
Subject: Re: Deploying New Cordova Website
But I wanted to +1
Launched !!
- Carlos
Sent from my iPhone
> On Oct 2, 2015,
I'm up for a hangout on this subject. I do think e-mail is making it hard to
communicate this. I am with Carlos - we should not have warnings that cannot be
resolved for unreleased platform versions. This is particularly, a problem for
a new web developer to Cordova who does not understand the
is problem later with plugins, guaranteed, we
> should
> >> >>> not try to hide this problem for our own convenience.
> >> >>>
> >> >>> Let's say we took out this engine requirement, and they
> >> >>> installed
> the
>
1. cordova create test
2. cordova platform add ios
WARNING: Applications for platform ios can not be built on this OS - win32.
Adding ios project...
iOS project created with cordova-ios@3.9.1
Discovered plugin "cordova-plugin-whitelist" in config.xml. Installing to the
project
ist%2fblob%2fmaster%2fREADME.md=01%7c01%7cnikhilkh%40microsoft.com%7cd638675115ae4fa7be2d08d2c92c9d89%7c72f988bf86f141af91ab2d7cd011db47%7c1=iO9NDS0BgD53OVEDyxGv0zNW5SKXLVK0loo8ZAEmfOM%3d
On Tue, Sep 29, 2015 at 5:08 PM, Nikhil Khandelwal <nikhi...@microsoft.com>
wrote:
> 1. cordov
lve. The resolution is to ignore it. It's
> supposed to warn you, as it is working as expected.
>
> On Tue, Sep 29, 2015 at 5:19 PM, Nikhil Khandelwal
> <nikhi...@microsoft.com> wrote:
>> I understand the warning w.r.t. plugins and android 5.0 as we will release
>> android 5.
I'm fine with merging cordova-android to master. For the plugins, that have
marshmallow changes if we merge now we cannot release them till cordova-android
& the corresponding tools release happens. On the other side, if we do not
merge them CI will be broken.
It makes sense to merge it all if
+1 to major version rev. for plugins. It also is a signal these plugins will
not work with any previous version of cordova.
For reviewing changes, can you submit a PR perhaps from your topic branch to
apache/cordova-android 5.x-dev branch? It's hard to review and comment on
branch diffs - PRs
View
marked as deprecated completely disappears, not something we should make a
habit of using often. If we open the door for this, we'll get reflection
creeping elsewhere, like the Plugins API.
Just say no to reflection.
On Tue, Sep 22, 2015, 5:57 PM Nikhil Khandelwal <nikhi...@micros
il.com]
Sent: Monday, September 21, 2015 6:32 PM
To: dev@cordova.apache.org
Subject: Re: [Android] 5.0.x release branch?
On Mon, Sep 21, 2015 at 5:43 PM Nikhil Khandelwal <nikhi...@microsoft.com>
wrote:
> Can you explain why latest plugins will not be compatible with older
> versions
Can you explain why latest plugins will not be compatible with older versions
of Cordova? Can this be avoided by any means? When you mean they would not be
compatible - will it result in a build or runtime failure?
For marshmallow, what is the guidance that we need to issue to the larger
,
Nikhil
-Original Message-
From: Joe Bowser [mailto:bows...@gmail.com]
Sent: Wednesday, September 9, 2015 8:28 AM
To: dev@cordova.apache.org
Subject: Re: Marshmallow Update and Cordova-Android 5.0
Android is already there, isn't it?
On Tue, Sep 8, 2015, 9:16 PM Nikhil Khandelwal <ni
Would be great to have some help in merging pending PRs. There are lots of them
pending. [1]
This is a good guide on this for committers:
https://github.com/apache/cordova-coho/blob/master/docs/processing-pull-requests.md
Thanks,
Nikhil
[1] http://s.apache.org/cordovaPulls
-Original
It would be great to add this platform matrix to our buildbot CI. Any
volunteers?
-Nikhil
-Original Message-
From: Karen Tran [mailto:ktop...@gmail.com]
Sent: Monday, September 7, 2015 7:32 PM
To: dev@cordova.apache.org
Subject: Re: Marshmallow Update and Cordova-Android 5.0
I tested
how popular that workflow is and something we need
to support.
[1] http://npm-stat.com/charts.html?package=plugman===
-Nikhil
-Original Message-
From: Nikhil Khandelwal [mailto:nikhi...@microsoft.com]
Sent: Thursday, September 3, 2015 10:21 PM
To: dev@cordova.apache.org
Subject: RE
I sort of agree with Raymond that is a useful functionality and is easy enough
to do this for users - by using a 'convention'. Customizing the build system
using hooks sounds more complicated for the developer. How does ionic & mfp
actually achieve this? How does a developer specify specific
I like this design (we should have had this in the first place) - but am
concerned of the breaking nature.
Do we have a specific case of a name conflict that we know of? Another way to
do this would be to use naming conventions - similar to a namespace. The
recommendation would be to prefix
This is great level of detail. Since there are plugin API changes - it would be
great to make a broader post - on slack, twitter, our blog.
Do we have a sense of how impactful are the breaking changes - say how many of
the top 50 plugins will not compile when ios 4.0 releases? If not, I can
On a related note, was our plan to do re-direction from old plugin registry ID
to npm ID? I still get a warning and no automatic re-direction with latest
cordova.
cordova plugin add org.apache.cordova.camera
Fetching plugin "org.apache.cordova.camera" via npm
WARNING: org.apache.cordova.camera
csantan...@gmail.com
wrote:
+1 minor release bump not major
- Carlos
Sent from my iPhone
On Aug 27, 2015, at 11:45 PM, Nikhil Khandelwal
nikhi...@microsoft.com
wrote:
Also, there has been a browser release that we need to pin.
-Nikhil
-Original Message-
From: Nikhil
Also, there has been a browser release that we need to pin.
-Nikhil
-Original Message-
From: Nikhil Khandelwal [mailto:nikhi...@microsoft.com]
Sent: Wednesday, August 26, 2015 6:21 PM
To: dev@cordova.apache.org
Subject: RE: [DISCUSS] Tools Release?
+1. Not sure if it will be a patch
+1. Not sure if it will be a patch release as it does ship new platforms along
with it and it could be considered a major bump because of that.
-Nikhil
-Original Message-
From: Jesse [mailto:purplecabb...@gmail.com]
Sent: Wednesday, August 26, 2015 6:17 PM
To: dev@cordova.apache.org
+1 to filing a JIRA for this with repro steps. We should address this in the
next release. Vldmrrr is there already a JIRA for this?
-Nikhil
-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com]
Sent: Wednesday, August 26, 2015 10:54 AM
To: dev@cordova.apache.org; Rob
1 - 100 of 225 matches
Mail list logo