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 additio
(
>
> Kindly,
> Dmitry
>
>> On Sep 13, 2017, at 1:08 PM, Filip Maj wrote:
>>
>> 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
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
Tue, Aug 22, 2017 at 11:47 AM, Shazron 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.4.1 because there is
>>>> a new feature in there.
>>>>
>>>>
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 migration once all repos are
>
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
> wrote:
>
>
> You probably mean
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?
>
> On Thu, Aug 10, 2017 at 1:
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:
>
>> https://issues.apache.org/jira/browse/INFRA-14823
>>
>> On Tue, Aug 8, 20
ision/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 wrote:
> Small update on this topic:
>
> - still need to clarify next steps on some of the INTEGRATE plugins
> - I
s 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 much work to create
>>> something like that) (
gt; up?
>> They would 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.
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
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:
>
> 1. Update some of our
onic-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 noti
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 b
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 gone.
> 2. Update our
form-tests
On Tue, Jul 25, 2017 at 9:59 AM, Kerri Shotts 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 Maj wrote:
>> ...
>
https://issues.apache.org/jira/browse/CB-13126
On Thu, Jul 27, 2017 at 1:52 PM, Steven Gill wrote:
> File it!
>
> On Thu, Jul 27, 2017 at 1:42 PM, Filip Maj wrote:
>
>> Is that concensus? Time to file an issue? I love :knife:'ing code
>>
>> On Tue, Jul 2
Tue, Jul 25, 2017 at 12:43 PM, julio cesar sanchez <
>> > > > jcesarmob...@gmail.com> wrote:
>> > > >
>> > > > > I liked Kerri's idea about only posting open source apps. I think
>> > users
>> > > > can
>> > > &g
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 WKWebView and UIWebView
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 [1
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 do
abel.
> Your issue should not have 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 J
, 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 discuss this more at leng
t 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 wrote:
>
>> I just want
s/highfives welcome.
Cheers,
Fil
[1] https://issues.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://
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 ot
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 wrote:
> Still looking for a bit more feedback, please take a look if you have
> time! Thanks Anis for your feedback :)
>
> Don'
2017 at 5:41 PM, Filip Maj 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.
>
> Looking for
tatus 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
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 P
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 issues we s
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 AppVeyor, but for the time
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 h
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: http://www.photokandy.com/
>
>
12:10 PM Simon MacDonald
> 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:56 AM, Filip Maj wrote:
>
>>
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 could. If there was
m, and no longer write to git-wip
>>
>> other projects that moved over like traffic server, went ahead and migrated
>> all the JIRA Issues to Github Issues, a topic for another thread :-)
>>
>> let me know how I can help, will be glad
>>
>> --Carlos
>>
>
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, cordova-fetch and cordov
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 then be the mirror
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 vote on this Tools Rele
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 commands,
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 wrote:
> I vote +1:
> * Ran coho audit-license-headers over the relevant repos
> * Ran coho check-license to ensure
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, e-
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: https://dist.
, Apr 28, 2017 at 11:48 AM, Steven Gill wrote:
> Done.
> https://github.com/stevengill/cordova-docs/commit/03b67269efe58ebd1cf12042ec9616bd1d05ea25
>
> On Fri, Apr 28, 2017 at 11:40 AM, Filip Maj wrote:
>
>> I would put more emphasis on upgrading for users of the latest Androi
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
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 wrote:
> I vote +1:
> *Ran coho verify-archives against all .tgz dists
> * All relevant repos are gree
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:
> https://github.com/stevengill/cordova-
, and just spec.27)
On Thu, Apr 27, 2017 at 1:30 PM, Filip Maj 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: https://dist.apach
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/
27, 2017 at 9:18 AM, Steven Gill wrote:
> do it!
>
> On Wed, Apr 26, 2017 at 12:51 PM, Filip Maj wrote:
>
>> 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 ou
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
---
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 s
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 from
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 th
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 wrote:
>
>> Let's
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 blocking CB-8980 and
yay! that seemed to have fixed it!
On Tue, Mar 21, 2017 at 10:51 PM, Filip Maj wrote:
> Just added apachebuilds as owner to both cordova-android and cordova-ios.
>
> On Tue, Mar 21, 2017 at 8:10 PM, Darryl Pogue wrote:
>> Hey Vladimir,
>>
>> I noticed we were getting
.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 least valid token) weāre blocked on this.
>>
>>
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 problems people are hav
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
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
`./bin/android_sdk_version
+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 comments:
>>
>> https://github.com/cordova/apache
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
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, wrote:
> I vote +1.
>
> * Ran coho verify-archive
> * Verified tag
> * Verified version
> * Ability to create bla
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
T
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 outsta
nmacdonald.com
>
> On Fri, Mar 3, 2017 at 4:02 PM, Filip Maj wrote:
>
>> +9001
>>
>> On Fri, Mar 3, 2017 at 12:59 PM, Jesse wrote:
>> > +1000
>> >
>> >
>> > @purplecabbage
>> > risingj.com
>> >
>> > On F
+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 new product (and the only one they will sell I
>
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.
>
>
>
>
>
> @purplecabbage
> risingj.com
>
> On
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 growing
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 anymore. The last one was
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. Each node now has 2 execut
+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 well.
>>
>> Simon Mac Donald
>> http://simonmacdona
ek. 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 want to make that happen,
gt;
> -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 will need
> to
d 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 wrote:
>
>> Hi!
>>
>> TL;DR: what OS versions should we be running our tests on? What
>> versions should we be testin
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 C
a-plugin-compat fix the compile problems on Android 4.1.1, or is
>> > this
>> > > a thing where you just bump the API level?)
>> > >
>> > > On Wed, Jan 4, 2017 at 8:21 AM, julio cesar sanchez <
>> > > jcesarmob...@gmail.com>
>>
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:
*
http://cordova-ci.cloudapp.net:8080/view/Periodic%20builds/job/cordova-periodic-build/PLATFORM=and
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: https://issues.apache.org/jira/browse/CB-6582
> (almost 3 years
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
> * Verified that plugins c
+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 discussed (--browserify
>> fixes for Windows)
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
-
To unsubscribe,
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 paramedic - basically repla
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, h
+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.
>
--
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 t
er/appium-tests
[3]
http://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 wrote:
> I am planning o
only released less than 60 days ago.
> >
> > Perhaps a PoC project should be done for picking the appropriate
> > technology?
> >
> > We are midway through a similar PoC at my place of work, I could
> volunteer
> > some time.
> >
> > On Tue, Dec
um
>>
>>
>>
>> 2016-12-05 23:33 GMT+01:00 Filip Maj :
>>
>>
>>
>> > Hi, it's me again!
>>
>> >
>>
>> > How I'd like to contribute to Cordova is to help automate the stuff
>>
>> >
f them and it 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
>
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 re
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 to
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.
-
Sounds good. Thanks for pointing it out!
On Dec 1, 2016 1:47 PM, "Shazron" wrote:
> Hi Fil,
> This is the DISCUSS thread. The issue you brought up has been answered by
> Steve -- it's up to the discretion of the person that releases to update
> any dependencies to the latest.
>
> Ideally updatin
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 co
ngj.com
>
> On Mon, Nov 28, 2016 at 11:50 AM, Simon MacDonald > wrote:
>
>> Never heard of this guy.
>> Simon Mac Donald
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsimonm
>> acdonald.com&data=02%7C01%7Cv-alsoro%40microsoft.com%7Cdcdee27
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 P
1 - 100 of 1392 matches
Mail list logo
