GitHub user kurli opened a pull request:
https://github.com/apache/cordova-android/pull/102
[CB-6898] Fix black screen issue when app start up
Set appView invisible only when 'LoadingDialog' is enabled.
BUG=https://issues.apache.org/jira/browse/CB-6898
You can merge this
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-medic/pull/9
CB-6899 Cordova-lib link step fails on Windows slave
Replaces ln -s command, which is not workin on windows slaves, with
inline node script.
Fix for
Hi, all!
I've signed the ICLA and I've updated the PRs for the CLI and for
plugman, so now they are against cordova-lib.
https://github.com/apache/cordova-lib/pull/16
https://github.com/apache/cordova-lib/pull/17
Could someone please review them?
TIA for your help,
Gabriel
It seems that the tag points to a commit which is not present in any of the
branches. I guess that the correct commit which should be tagged is:
https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-inappbrowser.git;a=commit;h=992306bbc58f3ba9dc0f4dbcde1b084db5ba8169
-Original
Github user zalun closed the pull request at:
https://github.com/apache/cordova-plugin-device-motion/pull/13
---
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
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-medic/pull/10
CB-6889 Edit json step in master.cfg fails on Windows
When running medic on windows (either the client and server or just a
client), the Edit json step specified in master.cfg fails.
The code which is being voted on, though, isn't represented by that commit.
There are significant differences. (They appear to be all confined to
Firefox OS)
The way to reproduce the original tagged commit is to cherry-pick commit
992306b (CB-6877 Updated version and RELEASENOTES.md for release
Cordova and w3c teams~
Last week Dom (from w3c) and myself met to chat about aligning the Cordova
and w3c specs. We felt the best starting point was looking at the
vibration spec as it shouldn't change... i.e. is pretty stable. I put
together a Google Doc identifying the 4 areas that will
I guess I'd have +1 the inappbrowser, although no idea if that counts
as I'm the author of most fixes for ffo in this plugin
Dnia Mon Jun 9 15:03:45 2014 Ian Clelland pisze:
The code which is being voted on, though, isn't represented by that commit.
There are significant differences. (They
Assuming we will be doing the Hangout tomorrow, I created a draft agenda and
notes placeholder as a Google Doc, and it is linked from the wiki:
https://wiki.apache.org/cordova/Google%20Hangout%20Discussion%20Notes
Is the previously-scheduled time of 4pm EDT good? I think that maps to 8am for
Sounds great, thanks for the agenda.
Note, there are already some beefy items on the list and we always run
short on time -- so before adding more please triple consider if items are
important and cannot just be discussed on the lists.
-Michal
On Mon, Jun 9, 2014 at 10:55 AM, Marcel Kinard
I'm sorry, I don't understand neither see the benefit or value added to
this...
What's the objective of this change?
Are the node_modules platforms going to be usable by separately outside of
Cordova in NodeJS? i.e. Can I use cordova-android to do an android app in
NodeJS using the NPM module?
Shane,
I've communicated the limitations of what I expect to be approved to the
internal MS team, but clearly it needs to be you that gives approval or
otherwise.
What I communicated internally (to MS) is that an appropriate use, such as
the one you suggest, would likely be OK. I also suggested
I'm working on fix mobile spec automated tests, specifically on those which
involves the File plugin. In the test # 67 of that test suite, I've found
out that the problem is not that the directory is not moved, the problem is
that after this line is executed:
Hmmm. Definitely something wrong with inappbrowser tag. I just deleted it
and retagged it.
I will upload the new inappbrowser to dist/dev and start a new vote thread.
I'm closing this thread. It has FAILED
On Mon, Jun 9, 2014 at 7:53 AM, Piotr Zalewa pzal...@mozilla.com wrote:
I guess I'd
Here is some work that we have been doing -
https://github.com/MSOpenTech/cordova-api-audit/compare/w3
As you can see from the diff, there were 2 approaches we took and would like
feedback from folks here on the best approach to move forward with
1. Automated
a. Picked up type
Please review and vote on the release of this plugins release.
Release issue: https://issues.apache.org/jira/browse/CB-6877
The plugins have been published to
dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-6877/
The packages were published from their corresponding git tags:
Hi Gabriel, we'll be reviewing and either closing or merging PRs there this
week: thx!
On Mon, Jun 9, 2014 at 3:46 AM, Schulhof, Gabriel
gabriel.schul...@intel.com wrote:
Hi, all!
I've signed the ICLA and I've updated the PRs for the CLI and for
plugman, so now they are against
where is that offending bit…and what is the intent behind it. outside of
pretty stack traces I'm still not convinced of the utility of building out
own own exceptions
On Sat, Jun 7, 2014 at 6:19 AM, Andrew Grieve agri...@chromium.org wrote:
Yep, I fully support this refactoring. Just wanted to
Jesse does well answering the queries. Our ideal is to get cordova-browser
somewhere production ready in the coming year.
On Fri, Jun 6, 2014 at 1:24 PM, Jesse purplecabb...@gmail.com wrote:
Hi Jeff,
1. Currently (out of the box) you can load the start page from the network
or the device
+1
- Verified that hashes match the tags.
- Verified hashes sigs
- Verified contents of plugin-camera (assuming others are fine)
On Mon, Jun 9, 2014 at 1:48 PM, Steven Gill stevengil...@gmail.com wrote:
Please review and vote on the release of this plugins release.
Release issue:
Minor bump to cordova-lib to expose a broken out package.
history:
https://git-wip-us.apache.org/repos/asf?p=cordova-lib.git;a=shortlog;h=refs/heads/configparser_module
squashed commit to master:
I think all releases require votes. Only difference is that for urgent
releases we can have a shorter vote period.
Looking at your commit - there's now two package.json files with the same
name. I don't think that's allowed by npm.
Your goal was to make configparser its own package right?
+1
- Ran coho audit-license-headers, all looks good.
- Ran coho verify-tags, all looks good.
- Ran mobile-spec using Android Cordova platform 3.5.0 on Android 4.4.3.
Ignoring the fails in Battery and Contacts, I see 2 other failing tests in
Geolocation which I am tempted to ignore because this
Github user jsoref closed the pull request at:
https://github.com/apache/cordova-blackberry/pull/160
---
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
Github user jsoref commented on the pull request:
https://github.com/apache/cordova-blackberry/pull/160#issuecomment-45533957
merged
---
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
Github user jsoref closed the pull request at:
https://github.com/apache/cordova-blackberry/pull/158
---
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
Github user jsoref commented on the pull request:
https://github.com/apache/cordova-blackberry/pull/158#issuecomment-45533991
merged
---
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
Github user jsoref commented on the pull request:
https://github.com/apache/cordova-blackberry/pull/153#issuecomment-45534097
this was merged
---
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
looking into the duplicate package.json issue
thanks for catching the package.json issue, the duplicate is a
mistaken inclusion
the end goal is that configparser is it's own package, yes. Included
the wrong package.json file
On Mon, Jun 9, 2014 at 12:01 PM, Andrew Grieve agri...@chromium.org
In particular, I thought the root of the repo wasn't supposed to be a node
package, but a bucket for multiple node packages. (ie, should not be a
package.json at the root).
We don't vote on commits (though its nice to ask for review for big hairy
patches like this one, so thanks for that).
Michal: the root package.json is being removed. I do want to perform
an npm publish with a patch version increment, so downstream projects
can reference include by npm registry and not git url. That would
constitute a 'release' of some sort. My understanding was that bug
patches of this sort could
If you are interested in checking out the latest tag in each of the plugin
repos, you can run the following command from the parent directory. This
assumes all of the plugins are siblings.
for l in cordova-plugin-*;do (cd $l; git checkout $(git describe --tags
--abbrev=0)); done;
To test the
We all wish!
On Mon, Jun 9, 2014 at 4:00 PM, Lorin Beer lorin.b...@gmail.com wrote:
Michal: the root package.json is being removed. I do want to perform
an npm publish with a patch version increment, so downstream projects
can reference include by npm registry and not git url. That would
To elaborate a bit more on #1, I’ve seen issues where the cordova.js in the
hosted content gets out-of-sync with the native Cordova runtime installed on
the device. Weird behavior can ensue when there are changes across Cordova
versions in the js-native interactions. One brute-force way to deal
good. lord.
On Mon, Jun 9, 2014 at 1:04 PM, Michal Mocny mmo...@chromium.org wrote:
We all wish!
On Mon, Jun 9, 2014 at 4:00 PM, Lorin Beer lorin.b...@gmail.com wrote:
Michal: the root package.json is being removed. I do want to perform
an npm publish with a patch version increment, so
Going to have to do a vote to release to npm.
On Mon, Jun 9, 2014 at 1:22 PM, Lorin Beer lorin.b...@gmail.com wrote:
good. lord.
On Mon, Jun 9, 2014 at 1:04 PM, Michal Mocny mmo...@chromium.org wrote:
We all wish!
On Mon, Jun 9, 2014 at 4:00 PM, Lorin Beer lorin.b...@gmail.com wrote:
Doing an automated check sounds great in theory, and would be cool to make the
check part of mobile-spec (or its successors). However, I wonder how well the
nuances in the standards would be detected, such as the cancelling of
outstanding vibrations as listed in Lisa’s gap analysis doc. It’s
Meant to say that automated is how we started, and then dug deeper into the
semantics. We were looking at using github to document these.
-Original Message-
From: Marcel Kinard [mailto:cmarc...@gmail.com]
Sent: Monday, June 9, 2014 1:29 PM
To: dev@cordova.apache.org
Subject: Re:
My understanding is that a VOTE was for ./dist and that anything npm is the
domain of the person publishing.
On Mon, Jun 9, 2014 at 1:27 PM, Steven Gill stevengil...@gmail.com wrote:
Going to have to do a vote to release to npm.
On Mon, Jun 9, 2014 at 1:22 PM, Lorin Beer
I also verified the contents of the zip files against my local repos at that
hash (diff -r). All looks good.
On Jun 9, 2014, at 3:33 PM, Marcel Kinard cmarc...@gmail.com wrote:
+1
- Ran coho audit-license-headers, all looks good.
- Ran coho verify-tags, all looks good.
- Ran mobile-spec
On Mon, Jun 9, 2014 at 1:35 PM, Brian LeRoux b...@brian.io wrote:
My understanding is that a VOTE was for ./dist and that anything npm is the
domain of the person publishing.
Here's the policy:
http://www.apache.org/dev/release#what
What Is A Release?
Releases are, by definition,
/me slow clap
On Mon, Jun 9, 2014 at 1:57 PM, Marvin Humphrey mar...@rectangular.com
wrote:
On Mon, Jun 9, 2014 at 1:35 PM, Brian LeRoux b...@brian.io wrote:
My understanding is that a VOTE was for ./dist and that anything npm is
the
domain of the person publishing.
Here's the policy:
And this is why we rarely release anything anymore.
On Mon, Jun 9, 2014 at 2:18 PM, Brian LeRoux b...@brian.io wrote:
/me slow clap
On Mon, Jun 9, 2014 at 1:57 PM, Marvin Humphrey mar...@rectangular.com
wrote:
On Mon, Jun 9, 2014 at 1:35 PM, Brian LeRoux b...@brian.io wrote:
My
Github user ldeluca commented on the pull request:
https://github.com/apache/cordova-plugin-device-motion/pull/13#issuecomment-45548352
Yes, please use crowdin. We don't accept individual language pull
requests. The crowdin tool handles translation for Cordova. See:
https://issues.apache.org/jira/browse/CB-4650 is currently unresolved.
Unfortunately, it shows up when I search for open blackberry bugs.
It has 5 subtasks, 4 of which are done.
I'd like to (as a policy) remove all platform tags from meta bugs when
there's a subtask specific to that platform.
+1
On Mon, Jun 9, 2014 at 2:57 PM, Josh Soref jso...@blackberry.com wrote:
https://issues.apache.org/jira/browse/CB-4650 is currently unresolved.
Unfortunately, it shows up when I search for open blackberry bugs.
It has 5 subtasks, 4 of which are done.
I'd like to (as a policy) remove all
Thanks Martin, is this captured in a JIRA issue just in case people
are away and this thread gets buried?
On Mon, Jun 9, 2014 at 10:39 AM, Martin Gonzalez
martin.c.glez.g...@gmail.com wrote:
I'm working on fix mobile spec automated tests, specifically on those which
involves the File plugin. In
+1
I have removed everything except wp8
also btw. my question in the comments remains unanswered ...
@purplecabbage
risingj.com
On Mon, Jun 9, 2014 at 2:59 PM, Shazron shaz...@gmail.com wrote:
+1
On Mon, Jun 9, 2014 at 2:57 PM, Josh Soref jso...@blackberry.com wrote:
On Mon, Jun 9, 2014 at 2:18 PM, Brian LeRoux b...@brian.io wrote:
/me slow clap
Brian, I realize that you are deeply opposed to voting on releases, and I
understand and respect your arguments. Were Cordova an independent project, I
would not come to the community proposing that release voting
Sure no problem, and CB-6901 is the issue with all the information related.
On Jun 9, 2014 5:06 PM, Jesse purplecabb...@gmail.com wrote:
Yes, thanks Martin.
The issue you created is sufficient. CB-6901
@purplecabbage
risingj.com
On Mon, Jun 9, 2014 at 3:00 PM, Shazron shaz...@gmail.com
This is great, thanks Andrew.
One further enhancement would be to verify the source zip vs
downloading the source at the tag, whether there are any differences
(would help with release)
On Fri, Jun 6, 2014 at 9:18 AM, Andrew Grieve agri...@chromium.org wrote:
Spent some time on it yesterday
Blind copy paste of URLs and blanket repeat emails are not helping either.
We can and do VOTE on artifacts.
(And, FTR, I'm perfectly fine with the ceremony but I'd prefer we cast
votes as tags like we used to. A topic for the board and members to debate
to be sure.)
Your earlier emails
Hey all,
I know a lot of us have trouble generating the documentation. Juggling Ruby
environments and the dependencies can be a sensitive matter.
To make our lives easier, I've added Vagrant support to our documentation
generator [1]. It's easy to setup and works on all the major operating
Marvin's email came across to me as respectful.
Brian and Joe - your responses came across as disrespectful to me. Slow
claps and sarcasm should probably be avoided in email.
This issue has been covered at length, and the a very clear conclusion was
made that unless policies change, anything
Agreed. If no one else gets to it, I'll probably add that next time I go to
verify archive contents.
On Mon, Jun 9, 2014 at 6:38 PM, Shazron shaz...@gmail.com wrote:
This is great, thanks Andrew.
One further enhancement would be to verify the source zip vs
downloading the source at the tag,
Github user marti1125 commented on the pull request:
https://github.com/apache/cordova-firefoxos/pull/13#issuecomment-45569697
When I added firefoxos platform, I got this
problem with defaults.xml
GitHub user dozer47528 opened a pull request:
https://github.com/apache/cordova-plugin-network-information/pull/10
fix NullPointerException
crash when the info is null!
You can merge this pull request into a Git repository by running:
$ git pull
first what? A hotfix
On Jun 9, 2014 6:33 PM, Andrew Grieve agri...@chromium.org wrote:
Marvin's email came across to me as respectful.
Brian and Joe - your responses came across as disrespectful to me. Slow
claps and sarcasm should probably be avoided in email.
This issue has been covered at
59 matches
Mail list logo
