Draft blog post for transitioning off cordova-plugin-file-transfer

https://github.com/apache/cordova-docs/pull/746 Comments, reviews, questions, ideas, whatever are welcome! Appreciate any feedback folks have. Cheers, Fil - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For

Re: [DISCUSS][DOCS] Revert a change

he ASF repo, sorry. :( > > Kindly, > Dmitry > >> On Sep 13, 2017, at 1:08 PM, Filip Maj <maj@gmail.com> wrote: >> >> We have an issue posted to make docs publishing automatic: >> https://issues.apache.org/jira/browse/CB-13162 >> >> Not to der

Re: [DISCUSS][DOCS] Revert a change

We have an issue posted to make docs publishing automatic: https://issues.apache.org/jira/browse/CB-13162 Not to derail the topic, but there is a longer wishlist in that issue, and I do think achieving the goals in that issue would require reworking the docs repository quite a bit. We can discuss

Re: [DISCUSS] cordova-ios 4.1.1 Release

g/jira/secure/RapidBoard.jspa?rapidView=173 >>> >>> On Tue, Aug 22, 2017 at 11:47 AM, Shazron <shaz...@gmail.com> wrote: >>> >>>> I'll get that in as the lone issue on the board. >>>> I'm also thinking this should be 4.5.0 instead of 4.

Re: [GITHUB MOVE] Bulk move of all repos

Should we delete/remove/archive any of those before moving them over? We have repos like app harness, medic, and others that are not contributed to nor used anymore. On Tue, Aug 29, 2017 at 10:13 PM, Steven Gill wrote: > We can deal with jira issues -> github issues

Re: [DISCUSS] cordova-ios 4.1.1 Release

CB-12830 [1] is something that I think we should sneak in to the release, time permitting. [1] https://issues.apache.org/jira/browse/CB-12830 On Sat, Aug 12, 2017 at 4:05 AM, Shazron wrote: >  I do! yes 4.4.1 > > On Aug 11, 2017 at 5:40 PM, julio cesar sanchez

Re: [GitHub] shazron closed pull request #329: CB-13112 - should not create a new file reference on each "cordova prepare"

Well, it's a PR-specific one (open/close PR actions send an email). We asked for commits to not be sent to dev, not for PR activity to not be sent to dev. On Thu, Aug 10, 2017 at 1:48 PM, Steven Gill wrote: > This email shouldn't be coming to the mailing list right? > >

Re: git commits being sent to dev

Looks like it's no longer spamming. HooraY! On Wed, Aug 9, 2017 at 10:44 AM, Steven Gill wrote: > it should be changed to comm...@cordova.apache.org now. Lets see > > On Tue, Aug 8, 2017 at 4:01 PM, Steven Gill wrote: > >>

Re: [CORE PLUGINS][DISCUSS] Roadmap 2017

sion/tasks in there. [1] https://issues.apache.org/jira/browse/CB-12719 [2] https://github.com/GoogleChrome/dialog-polyfill On Fri, Jul 28, 2017 at 12:57 PM, Filip Maj <maj@gmail.com> wrote: > Small update on this topic: > > - still need to clarify next steps on some of the INTEG

Re: [DISCUSS] Moving JIRA issues to Github

;>> yourself, which comes with its own challenges). But Github has an API, >>> I am pretty sure someone already wrote something that combines issues >>> of several repos into one interface to look at, then links to the >>> individual issues (If not, it wouldn't be too

Re: [DISCUSS] Moving JIRA issues to Github

uld end up in GitHub, at which point we'd triage them within > GitHub. > > Is there going to be a default repository to hold them before they're > triaged and organized? > > On a slightly different note, I'm looking forward to the new PR process. It > always felt a li

Re: cordova 8 proposal

Thanks for kicking this off. Lotsa good stuff in there, but lots to sort through. Recommend everyone take a look! On Wed, Aug 2, 2017 at 4:51 PM, Steven Gill wrote: > Let me know what you think! > https://github.com/cordova/cordova-discuss/pull/72

Re: [GITHUB MOVE] Phase 1 Complete, next steps

at some point should we migrate / create a cordova-discuss repo [1] to the apache org? [1] https://github.com/cordova/cordova-discuss On Wed, Aug 2, 2017 at 12:42 PM, Shazron wrote: > Phase 1 complete: > https://issues.apache.org/jira/browse/INFRA-14347 > > We need to: > >

Re: [DISCUSS] Moving JIRA issues to Github

nic-cli/issues/2386 > > As the original poster of the issue and each reply is @-mentioned they > are notified about the "new" issue and can continue participating. > Replying users also can just include the @username in their new > replies again to make sure people get no

Re: [DISCUSS] Moving JIRA issues to Github

I think the ease of use of GitHub issues overcomes potential problems about cross-referencing issues. Worth noting on this topic that GitHub already provides good support for referencing pull requests from issues across repos / orgs. The benefit of having issues and PRs in one place, to me, is a

Re: [GITHUB MOVE] Phase 1 Complete, next steps

This makes me so happy :) On Wed, Aug 2, 2017 at 12:42 PM, Shazron wrote: > Phase 1 complete: > https://issues.apache.org/jira/browse/INFRA-14347 > > We need to: > > 1. Update some of our tools, mainly Coho, to point directly to Github, > since the git-wip-us.a.o repo is now

Re: [CORE PLUGINS][DISCUSS] Roadmap 2017

On Tue, Jul 25, 2017 at 9:59 AM, Kerri Shotts <kerrisho...@gmail.com> wrote: > Just wanted to say “THANKS!” for the work you’ve done on this! :-) It’s much > appreciated! > > ~ Kerri > >> On Jul 22, 2017, at 14:43, Filip Ma

Re: [DISCUSS] Accepting new apps into the App Showcase

https://issues.apache.org/jira/browse/CB-13126 On Thu, Jul 27, 2017 at 1:52 PM, Steven Gill <stevengil...@gmail.com> wrote: > File it! > > On Thu, Jul 27, 2017 at 1:42 PM, Filip Maj <maj@gmail.com> wrote: > >> Is that concensus? Time to file an issue? I love :kni

Re: [DISCUSS] Accepting new apps into the App Showcase

> > > @purplecabbage >> > > > risingj.com >> > > > >> > > > On Tue, Jul 25, 2017 at 12:43 PM, julio cesar sanchez < >> > > > jcesarmob...@gmail.com> wrote: >> > > > >> > > > > I liked Kerri's id

Re: WebRTC (getUserMedia) in cordova-ios on iOS11

IIRC, it's not uncommon for the webview to lag behind Mobile Safari. On Wed, Jul 26, 2017 at 11:47 PM, Toplak Daniel wrote: > He devs, > > Does anyone played with WebRTC on iOS? > > I get a test running only in Safari with iOS 11 Beta 4, but not in a cordova > app. > Both

Re: Incompatible plugin should reject the build

OMG late to this thread but yes, this should fail and freakout. My assumption is the same as the person who reported CB-12122 is: any dependent plugins that fail constraint checking would bubble the failure up the dependency chain. Unfortunately, the behaviour is not _super_ explicit in the docs

Re: [DISCUSS] Accepting new apps into the App Showcase

I'm of the opinion that we, the cordova devs are already sinking under the amount of incoming PRs and TODOs just with maintaining the tooling, platforms, plugins, and docs. I think it would be better to turf it and let downstream projects do that stuff if they wish. I think PhoneGap has one, so

Re: Highlighting top issues w/ JIRA boards and labels

both labels. > > = > ISSUES: > 1. Right now the 'ios-next' board is just named that, 'ios-next'. It is not > clearly visible what the next planned version is. I'm not sure how to > effectively communicate this in JIRA with the Kanban board interface. This > information sho

Re: [CORE PLUGINS][DISCUSS] Roadmap 2017

gt;> >> To fix this, we can rename the classes, but then it will just be a native >> side fix. For JavaScript, we want the integrated plugin's native code to >> prevail (thus it's JavaScript not to be clobbered), not the older version >> of the plugin -- we can discus

Re: [CORE PLUGINS][DISCUSS] Roadmap 2017

nt the integrated plugin's native code to > prevail (thus it's JavaScript not to be clobbered), not the older version > of the plugin -- we can discuss this more at length in the issue. > > > > On Sat, Jul 22, 2017 at 12:43 PM, Filip Maj <maj@gmail.com> wrote: > >&g

Re: [CORE PLUGINS][DISCUSS] Roadmap 2017

ues.apache.org/jira/browse/CB-12708 [2] https://issues.apache.org/jira/browse/CB-12709 [3] https://issues.apache.org/jira/browse/CB-13045 [4] https://issues.apache.org/jira/browse/CB-13046 [5] https://issues.apache.org/jira/browse/CB-13052 [6] https://issues.apache.org/jira/browse/CB-12903 [7] http://

Highlighting top issues w/ JIRA boards and labels

Hi everyone, Over the past little while, I've been trying to wrap my head around what open issues exist within Cordova, which ones are top priority + how we can identify the most pressing issues, and how to bubble those up to the top for PMC members and contributor/committers. With some of the

Re: cordova-lib proposal on test directory reorganization

I'm planning on merging this in later today if there are no more comments. So far only positive ones! On Mon, Jun 26, 2017 at 7:45 AM, Filip Maj <maj@gmail.com> wrote: > Still looking for a bit more feedback, please take a look if you have > time! Thanks Anis for your feedback

Re: cordova-lib proposal on test directory reorganization

at 5:41 PM, Filip Maj <maj@gmail.com> wrote: > Proposal up in PR form here: https://github.com/apache/cordova-lib/pull/568 > > tl;dr consolidating `spec-cordova/` and `spec-plugman` directories > into one, setting up to for one-unit-test-spec.js per source-module.js > file.

Re: Cloudapp CI is down, builds moving to Travis

ttery-status plugin: > https://github.com/apache/cordova-plugin-battery-status/pull/55 > > Now I'm working to propagate it through other plugin repositories. Soon we'll > have plugin PRs covered again! > > -Original Message- > From: Filip Maj [mailto:maj@gmail.com] >

cordova-lib proposal on test directory reorganization

Proposal up in PR form here: https://github.com/apache/cordova-lib/pull/568 tl;dr consolidating `spec-cordova/` and `spec-plugman` directories into one, setting up to for one-unit-test-spec.js per source-module.js file. Looking for eyes and feedback! If you have any, please drop comments in the

Re: Cloudapp CI is down, builds moving to Travis

you have > any insight on that, I'd be glad to hear it. > > -----Original Message- > From: Filip Maj [mailto:maj@gmail.com] > Sent: Wednesday, June 21, 2017 4:33 PM > To: dev@cordova.apache.org > Subject: Re: Cloudapp CI is down, builds moving to Travis > > Any JIRA i

Re: Cloudapp CI is down, builds moving to Travis

Any JIRA issues we should look at to track progress? Alex, what can we do to assist? seems like a lot of work - let us know! On Wed, Jun 21, 2017 at 5:39 AM, wrote: > Our Plugins testing CI (Jenkins) is officially dead now. > We're migrating all the jobs to Travis and

Re: Hello

Welcome Georgios! Nice to e-meet you, I'm Fil. Thanks for reaching out about where and how to contribute - we really appreciate it. The easyfix stuff Julio pointed to is a great place to start and get your bearings on how the issue tracker works, and hopefully you can start there to figure out

Re: [DRAFT] Apache Cordova Board Report - June 2017

Just one nit: "have request Gitbox access" --> "have requested Gitbox access" LGTM otherwise! On Sun, Jun 18, 2017 at 3:40 PM, wrote: > LGTM. > > Sent from my phone. > > ___ > Kerri Shotts > photoKandy Studios, LLC > > On the Web:

Re: [Android] Let's drop support for Jellybean

17 at 12:10 PM Simon MacDonald <simon.macdon...@gmail.com> > wrote: > > I would happily drop support for anything less than API level 19 in the > next cordova-android major release. > > > Simon Mac Donald > http://simonmacdonald.com > > On Sun, Feb 26, 2017 at 10

Re: [CORE PLUGINS][DISCUSS] Roadmap 2017

Great job, awesome to see progress on this. 6 plugins to sunset, 5 to integrate! Huge progress. On Thu, Jun 8, 2017 at 7:09 PM, Shazron wrote: > Deadline has passed for: > https://issues.apache.org/jira/browse/CB-12708 > > I believe I captured consensus in the issues as best I

Re: [NOTICE] Intent on moving to Github

can help, will be glad >> >> --Carlos >> >> >> On Tue, Jun 6, 2017 at 6:30 PM Steven Gill <stevengil...@gmail.com> wrote: >> >> > Yay! Hope ASF allows us to finally do this! >> > >> > On Tue, Jun 6, 2017 at 3:28 PM, Filip Maj <maj

Re: move common, fetch and serve to their own repo

Friendly reminder that we will have to update the CI scripts to handle this now. I believe we are mid-transition away from cloudapp Jenkins to Travis/AppVeyor now (ping Alex Sorokin). On Tue, Jun 6, 2017 at 1:03 AM, Steven Gill wrote: > I've started moving cordova-common,

Re: [NOTICE] Intent on moving to Github

My one comment is OMG YISS! On Mon, Jun 5, 2017 at 6:41 PM, Shazron wrote: > The Apache Cordova Project Management Committee (PMC) has consensus that we > should move primary development of Apache Cordova to Github, from Apache's > servers (role would be reversed, Apache would

Re: [VOTE] Coho Release

I vote +1 * Ran coho audit-license-headers over the coho repo * Ran coho check-license to ensure all coho source has Apache-compatible licenses * Ensured continuous build was green when repos were tagged On Thu, May 11, 2017 at 10:36 AM, Shazron wrote: > Please review and

[ANNOUNCE] Cordova-Android 6.2.3 released

Tweet: https://twitter.com/apachecordova/status/860551489902657536 Blog: http://cordova.apache.org/announcements/2017/05/04/android-release.html - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional

Re: [VOTE] 6.2.3 Android release

The vote has now closed. The results are: Positive Binding Votes: 3 Filip Maj Joe Bowser Shazron Abdullah The vote has passed. On Thu, May 4, 2017 at 3:56 PM, Shazron <shaz...@gmail.com> wrote: > I vote +1: > * Ran coho audit-license-headers over the relevant repos > * Ran coh

[ANNOUNCE] May 2017 Plugins Release is out

ze tweet: https://twitter.com/apachecordova/status/859866885914894336 ze blog: http://cordova.apache.org/news/2017/05/01/plugins-release.html - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands,

[VOTE] 6.2.3 Android release

Please review and vote on this 6.2.3 Android Release by replying to this email (and keep discussion on the DISCUSS thread - am piggy-backing on the 6.2.2 release DISCUSS thread) Release issue: https://issues.apache.org/jira/browse/CB-12746 The archive has been published to dist/dev:

Re: [DISCUSS] cordova-android@6.2.2 release

, Apr 28, 2017 at 11:48 AM, Steven Gill <stevengil...@gmail.com> wrote: > Done. > https://github.com/stevengill/cordova-docs/commit/03b67269efe58ebd1cf12042ec9616bd1d05ea25 > > On Fri, Apr 28, 2017 at 11:40 AM, Filip Maj <maj@gmail.com> wrote: > >> I would put mor

[BLOG POST][DRAFT] May 2017 Plugins Release

Please review! https://github.com/apache/cordova-docs/pull/701 - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [VOTE] Plugins Release, April 28 2017

The vote has now closed. The results are: Positive Binding Votes: 3 Filip Maj Shazron Abdullah Jesse MacFadyen The vote has passed. On Mon, May 1, 2017 at 4:02 PM, Jesse <purplecabb...@gmail.com> wrote: > I vote +1: > *Ran coho verify-archives against all .tgz dists > * All

Re: [DISCUSS] cordova-android@6.2.2 release

I would put more emphasis on upgrading for users of the latest Android SDK tools. Older cordova-android versions cannot and will not work with the latest SDK tools, so it's really important. On Fri, Apr 28, 2017 at 11:20 AM, Steven Gill wrote: > Blog Post: >

Re: [DISCUSS] Plugins Release

, and just spec.27) On Thu, Apr 27, 2017 at 1:30 PM, Filip Maj <maj@gmail.com> wrote: > Alright, the plugins release issue is here: > https://issues.apache.org/jira/browse/CB-12736 > > For the plugins that warranted releases, I've got the RCs for them up > on dist-dev: ht

[VOTE] Plugins Release, April 28 2017

Please review and vote on the release of this plugins release by replying to this email (and keep discussion on the DISCUSS thread). Release issue: https://issues.apache.org/jira/browse/CB-12736 The plugins have been published to dist/dev: https://dist.apache.org/repos/dist/dev/cordova/CB-12736/

Re: [DISCUSS] Plugins Release

, Steven Gill <stevengil...@gmail.com> wrote: > do it! > > On Wed, Apr 26, 2017 at 12:51 PM, Filip Maj <maj@gmail.com> wrote: > >> We did some work this week and got a bunch of community PRs merged in >> to many plugin repos. >> >> Anyone have any r

[DISCUSS] Plugins Release

We did some work this week and got a bunch of community PRs merged in to many plugin repos. Anyone have any reasons to not do a release? Anything outstanding anyone wants to get merged in before moving ahead with a plugins release? Any other comments on the topic? Cheers, Fil Maj

Re: [CORE PLUGINS] Expansion of features needs to be discussed in dev@

I know some of the plugins (all of them?) call out at the top of the docs that they are based on standards. I think we should be more dilligent in referencing those specs when discussing/weighing changes to the APIs. It would be a lot easier to maintain a stance such as "this does not follow the

Re: cordova can't see android targets

Hi Oleg, This is an issue caused by Google changing the Android SDK tooling in version 26. If you use the latest cordova-android, it should be compatible with the new tools. Unfortunately, support for the new tools is unreleased at this time so you will need to use the latest cordova-android

Re: Proof of Concept: Android Studio Project Structure

Dropping ANT support now seems like a good idea. This overall sounds good to me. One question I have is how would this affect users that have only the command-line tools installed, and not a full Android studio setup? Does this approach preclude those users from leveraging Cordova? I'm not sure

Re: [DISCUSS] Cordova@7 Release

Any specific things worth manually testing out above and beyond what our CI does? On Fri, Apr 21, 2017 at 6:56 PM, Shazron wrote: > Yes! > I'll get on https://issues.apache.org/jira/browse/CB-12655 for the release > (its on the board) > > On Fri, Apr 21, 2017 at 4:49 PM, Jesse

Re: [DISCUSS] cordova-common@2.0.2 release

none here On Fri, Apr 14, 2017 at 7:41 PM, Shazron wrote: > I will start the vote tonight if there are no objections. > > Changes: > Anything Mar 10 2017 and newer - > https://github.com/apache/cordova-lib/commits/master/cordova-common > > This release is needed because it is

Re: [NIGHTLY BUILDS] Missing

yay! that seemed to have fixed it! On Tue, Mar 21, 2017 at 10:51 PM, Filip Maj <maj@gmail.com> wrote: > Just added apachebuilds as owner to both cordova-android and cordova-ios. > > On Tue, Mar 21, 2017 at 8:10 PM, Darryl Pogue <dvpdin...@gmail.com> wrote: >> Hey V

Re: [NIGHTLY BUILDS] Missing

ish nightlies (user apachebuilds, >> https://www.npmjs.com/~apachebuilds) are now incorrect, at least I’m not >> able to login to NPM with these credentials. >> >> I have updated the job to run on proper set of nodes, but until we get new >> credentials (or at l

Re: [DISCUSS] Cordova-Android 6.2.0 Release

I am all for a new release, to get compatibiltiy with the latest SDK tooling out ASAP. No objections here. On Mon, Mar 20, 2017 at 12:36 PM, Joe Bowser wrote: > Hey > > Does anyone have any reason to delay Cordova-Android 6.2.0? I want to get a > release out to address the

Re: [VOTE] plugin release : cordova-plugin-screen-orientation (attempt 2)

I vote +1: - Verified plugin tag 2.0.0 (6bda75f2b7) works w/ latest cordova-android, and orientationchange event, lock and unlock functionality works as expected on an Android emulator running Android 7.1. - Verified plugin tag 2.0.0 (6bda75f2b7) works w/ latest cordova-ios, and orientationchange

[DISCUSS] Remove cordova-android's `android_sdk_version` script

I recently issued a pull request to update the cordova-android CLI scripts to work with Android SDK Tools 25.3.1 [1]. As part of the discussion in there, it came up that, in particular cases where one's environment was not set up with proper environment variables, running

Re: [DRAFT][REPORT] Cordova - March 2017

+1 On Mon, Mar 13, 2017 at 9:30 PM, wrote: > +1 > > Sent from my phone. > > ___ > Kerri Shotts > >> On Mar 13, 2017, at 19:43, Shazron wrote: >> >> I will send this out later tonight/early tomorrow if there are no

[ANNOUNCEMENT] cordova-common@2.0.1 released

cordova-common@2.0.1 is in cordova-dist and npm. Rejoice! - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [VOTE] cordova-common 2.0.1 Release

The vote has now closed. The results are: Positive Binding Votes: 3 Filip Maj Alexander Sorokin Steven Gill The vote has passed. On Fri, Mar 10, 2017 at 3:41 AM, <alsoro...@apache.org> wrote: > I vote +1. > > * Ran coho verify-archive > * Verified tag > * Verified version

[VOTE] cordova-common 2.0.1 Release

Please review and vote on this cordova-common release by replying to this email (and keep discussion on the DISCUSS thread) Release issue: https://issues.apache.org/jira/browse/CB-12558 cordova-common 2.0.1 has been published to dist/dev: https://dist.apache.org/repos/dist/dev/cordova/CB-12558

[DISCUSS] cordova-common patch bump + release

I'd like to do just a patch version bump + release of cordova-common. I recently updated the process `spawn` helper [1], which I need to help with the Android SDK Tools 25.3.1 update that broke cordova-android's CLI build scripts [2]. Does anyone have any reason to delay such a release? Any

Re: [DISCUSS] Mothballing cordova-blackberry

Simon Mac Donald > http://simonmacdonald.com > > On Fri, Mar 3, 2017 at 4:02 PM, Filip Maj <maj@gmail.com> wrote: > >> +9001 >> >> On Fri, Mar 3, 2017 at 12:59 PM, Jesse <purplecabb...@gmail.com> wrote: >> > +1000 >> > >> >

Re: [DISCUSS] Mothballing cordova-blackberry

+9001 On Fri, Mar 3, 2017 at 12:59 PM, Jesse wrote: > +1000 > > > @purplecabbage > risingj.com > > On Fri, Mar 3, 2017 at 12:58 PM, Shazron wrote: > >> Effectively the project repo is dead, but let's make it official. >> >> Blackberry has only one

Re: [Android] Let's drop support for Jellybean

As much as I personally would like to do so, I wonder what the reaction among consumers of cordova would be. On Sun, Feb 26, 2017 at 1:39 AM, Jesse wrote: > +1 > Our CI tests only test as far back as 4.4, so maybe I thought we were > already there. > > > > > >

Re: [Discuss] plugins release

I've worked through the contacts plugin PRs, and either closed them, pinged the authors for rebases/updates/more info, or pinged platform maintainers for some extra eyes on ones I am unsure about. Current state of plugin PRs: cordova-plugin-inappbrowser --> Last week: 30, Today: 38 - it's

Re: [NIGHTLY BUILDS] Missing

I recall Alex saying he enabled parallel builds on cloudapp within the last week, sounds like it might be relevant. We'll need our MSFT friends and cloudapp admins to rescue us in this situation! On Tue, Feb 14, 2017 at 4:12 PM, Shazron wrote: > I believe they don't run

Re: Temporary turbulence on the CI

Holy cow! This is so awesome Alex, awesome job! I've started watching the issue, perhaps we can make that test server more stable so we can more effectively leverage Sauce for the testing. On Thu, Feb 9, 2017 at 5:52 AM, wrote: > I think I've stabilized the builds now.

Re: CB-11602: (android) Adds onRestart event support

+1 ! On Wed, Jan 25, 2017 at 11:35 AM, Kerri Shotts wrote: > +1 to moving splash screen into platforms. > > > ~ Kerri > >> On Jan 25, 2017, at 01:09, Simon MacDonald wrote: >> >> I would be happy to see Splash Screen go back to the platforms as

Re: Platform Version support/coverage

; Going to add the iOS 10 builds this week. Will keep you informed. > > -Original Message- > From: Filip Maj [mailto:maj@gmail.com] > Sent: Friday, January 6, 2017 2:19 AM > To: dev@cordova.apache.org > Subject: Re: Platform Version support/coverage > > Thanks Shaz. If we w

Re: Platform Version support/coverage

ep you informed. > > -Original Message----- > From: Filip Maj [mailto:maj@gmail.com] > Sent: Friday, January 6, 2017 2:19 AM > To: dev@cordova.apache.org > Subject: Re: Platform Version support/coverage > > Thanks Shaz. If we want to make that happen, then I think that Alex wil

Re: Platform Version support/coverage

va-ios@4.4.0 we would increase the minimum > deployment target to iOS 9 (previously discussed in a thread in this list). > > On Thu, Jan 5, 2017 at 1:01 PM, Filip Maj <maj@gmail.com> wrote: > >> Hi! >> >> TL;DR: what OS versions should we be running our test

Platform Version support/coverage

Hi! TL;DR: what OS versions should we be running our tests on? What versions should we be testing against in our CI? Recently, I received an email from Sauce Labs, letting me know that support for test runs on Android 4.3 and below has officially ended. This reminded me that our current Android

Re: plugins and engines

om> >> > > wrote: >> > > >> > > > I think we should start testing plugins with cordova-android 4.1.1 as >> > is >> > > > the lower required by Google to publish on Google play. If some >> plugin >> > > > doesn't

Re: [Vote] 6.1.1 Android Release

I vote +1: - nightly CI builds for cordova-android have two failures, but they are both "connection broken" ones. (cc @alsorokin). otherwise looks good. I attribute this to a CI server hiccup: *

Re: plugins and engines

Sounds like a good idea, but how to go about doing it? We probably can't easily, for example, rule out older versions of iOS without someone testing with an old Xcode version. On Tue, Jan 3, 2017 at 5:15 PM, Shazron wrote: > Related:

Re: [VOTE] Plugins Release (Dec 12th 2016)

I vote +1: - successfully created android and ios projects with the plugins - ran through the manual tests for both plugins on Android 5.1 and iOS 9.3 emusims. On Thu, Dec 15, 2016 at 2:13 AM, wrote: > I vote +1 > > * Verified signatures and hashes > * Verified tags > *

Re: [DISCUSS] Plugins Release Dec 12th, 2016

+1 On Wed, Dec 14, 2016 at 12:19 PM, julio cesar sanchez wrote: > +1 > > 2016-12-14 20:01 GMT+01:00 Shazron : > >> Two plugins that were omitted from the last released are planned for this >> one: >> 1) Updates in cordova-plugin-battery-status that we

Re: [DRAFT] [REPORT] Cordova - December 2016

LGTM On Tue, Dec 13, 2016 at 5:11 PM, Shazron wrote: > I will send this out later tonight/early tomorrow if there are no comments: > > https://github.com/cordova/apache-board-reports/blob/master/2016/2016-12.md

Re: [DISCUSS] EOL cordova-medic

On Mon, Dec 12, 2016 at 1:46 PM, Jesse wrote: > What would be the added responsibilities for cordova-paramedic? Good question. As far as I can tell, I believe paramedic would need to additionally house the helper JSON files containing configuration that one passes into

[DISCUSS] EOL cordova-medic

Dearest cordova devs, I'd like to discuss the possibility of killing off the cordova-medic repo. Kinda funny, as I landed the first commit in that repo over 4 years ago. I recently sent some updates in a pull request to medic [1], updating some appium stuff, and after some discussion with Alex,

Re: [BLOG POST] Dec 07 2016 Plugins Release

+1 On Mon, Dec 12, 2016 at 11:19 AM, Kerri Shotts wrote: > +1 > > ~ Kerri > >> On Dec 11, 2016, at 17:17, Shazron wrote: >> >> https://github.com/apache/cordova-docs/pull/667 >> >> +1 it, etc >> >> Pending npm package publish. >

Re: [VOTE] Plugins Release

I vote +1: - created a cordova-android 6.1.0-based mobile-spec project, installed relevant tags of plugins, ran autotests, poked around manual tests, things seem fine. - created a cordova-ios 4.3.1-based mobile-spec project, installed relevant tags of plugins, ran autotests, poked around manual

Re: An idea for manually testing plugins

://cordova-ci.cloudapp.net:8080/view/Pull%20requests/job/cordova-plugin-contacts-pr/lastSuccessfulBuild/PLATFORM=ios/consoleText [4] https://saucelabs.com/beta/tests/b014505bd8894ff58b383471bdaf4759 On Wed, Dec 7, 2016 at 6:14 AM, Filip Maj <maj@gmail.com> wrote: > I am planning o

Re: An idea for manually testing plugins

armob...@gmail.com> > wrote: > >> +1 to appium >> >> >> >> 2016-12-05 23:33 GMT+01:00 Filip Maj <maj@gmail.com>: >> >> >> >> > Hi, it's me again! >> >> > >> >> > How I'd like to contribute to Cor

Re: Access to Jenkins instance, questions about CI

is only us who can bring the slave back online > if something bad happens. > > Thanks, > Alexander Sorokin > > -Original Message- > From: Filip Maj [mailto:maj@gmail.com] > Sent: Tuesday, December 6, 2016 1:32 AM > To: dev@cordova.apache.org > Subject: A

An idea for manually testing plugins

Hi, it's me again! How I'd like to contribute to Cordova is to help automate the stuff that saves committers having to take the manual time to do themselves. I think a good first goal would be to help automate as much of platform release testing as possible [1]. The autotests seem to be handled

Access to Jenkins instance, questions about CI

Dearest Cordova devs, I would like to get admin-level access to the cloudapp jenkins instance: http://cordova-ci.cloudapp.net:8080/ Who can grant me this karma? I wanted to check out how the various jobs are configured, what triggers them and what the triggered code looks like. I also wanted

Re: [Vote] 4.3.1 iOS Release

I vote +1 I ran the following tests against an iOS 10.1 iPhone 7 plus simulator 1. mobilespec autotests - i get the two media failures that seem to be expected (at least per Kerri’s vote) - i get file.spec.147 failure every time w/ code:1 NOT_FOUND_ERR. manual file tests all pass fine, though. -

Re: [Vote] 4.3.1 iOS Release

The release notes in coho [1] note to check npm outdated dependencies. When I run that against commit 0c201c42344f63c7590c4190ba2285fa199300bb, I get: ~/src/cordova-ios on master via ⬢ v6.9.1 ➔ npm outdated --depth=0 Package Current Wanted Latest Location nodeunit0.8.8 0.8.8 0.10.2

Re: Hello again!

gt; On Mon, Nov 28, 2016 at 11:50 AM, Simon MacDonald <simon.macdon...@gmail.com >> wrote: > >> Never heard of this guy. >> Simon Mac Donald >> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsimonm >> acdonald.com=02%7C01%7Cv-alsoro%40microso

Hello again!

Hi everyone! Just wanted to (re)introduce myself after a 3 year or so hiatus :) I used to be an active member of the group between 2011 and 2013 when I was on the Adobe PhoneGap team. I took a 3 year detour focusing on mobile testing infrastructure at Sauce Labs, but recently rejoined the Adobe

Re: Running file-transfer tests against local server

Ideally we'd get Apache infra to fix up the VM, and we could build some bandwidth caps into it and better monitoring into the instance to get some more visibility into the situation should it go off the rails again. In the mean time, we should look at alternatives. I'll look into hosting an

Re: [DISCUSS] Split cordova-lib modules into their own repos

+1 On Tue, Nov 22, 2016 at 9:33 PM, Darryl Pogue wrote: > On 22 November 2016 at 17:30, Steven Gill wrote: >> I propose to split these modules into their own git repos. Thoughts? > > A giant +1 from me! > > I routinely run into cases where

  1   2   3   4   5   6   7   8   9   10   >