raphinesse merged pull request #17:
URL: https://github.com/apache/cordova-test-platform/pull/17
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
raphinesse commented on a change in pull request #17:
URL:
https://github.com/apache/cordova-test-platform/pull/17#discussion_r499161520
##
File path: package.json
##
@@ -18,17 +20,6 @@
"author": "Apache Software Foundation",
"license": "Apache-2.0",
"bugs":
timbru31 merged pull request #18:
URL: https://github.com/apache/cordova-test-platform/pull/18
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
timbru31 opened a new pull request #18:
URL: https://github.com/apache/cordova-test-platform/pull/18
### Platforms affected
### Motivation and Context
### Description
### Testing
### Checklist
- [ ]
erisu commented on a change in pull request #17:
URL:
https://github.com/apache/cordova-test-platform/pull/17#discussion_r499159095
##
File path: package.json
##
@@ -18,17 +20,6 @@
"author": "Apache Software Foundation",
"license": "Apache-2.0",
"bugs":
erisu commented on a change in pull request #17:
URL:
https://github.com/apache/cordova-test-platform/pull/17#discussion_r499158727
##
File path: package.json
##
@@ -18,17 +20,6 @@
"author": "Apache Software Foundation",
"license": "Apache-2.0",
"bugs":
raphinesse opened a new pull request #17:
URL: https://github.com/apache/cordova-test-platform/pull/17
- chore(pkg): remove field "maintainers"
- fix(pkg): fix declaration for binary "create"
This is an automated
raphinesse merged pull request #16:
URL: https://github.com/apache/cordova-test-platform/pull/16
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
raphinesse opened a new pull request #16:
URL: https://github.com/apache/cordova-test-platform/pull/16
See https://github.com/apache/cordova/issues/55
This is an automated message from the Apache Git Service.
To respond to
The vote has now closed. The results are:
Positive Binding Votes: 3
* Bryan Ellis
* Niklas Merz
* Ken Naito
Negative Binding Votes: 0
The vote has passed.
Thanks everyone!
> On Sep 20, 2020, at 8:33, Niklas Merz wrote:
>
> I vote +1
>
> I did:
> * checked hash and signature
> * checked
+1
I did:
* coho verify-archive OK
* coho verify-tags OK
* The last commit
https://github.com/apache/cordova-electron/commit/143cd27d31480e9e1dd5b20c257df81567f3cbe8
is green
On 2020/09/18 11:51, Bryan Ellis wrote:
cordova-electron: 2.0.0 (ec9655c99d)
I vote +1
I did:
* checked hash and signature
* checked no audit issues
* tests pass locally (linux)
* checked licenses and headers
* create new app and run with local clone of tag successfully
Am 18.09.20 um 04:51 schrieb Bryan Ellis:
> Please review and vote on this Electron Release v2.0.0
>
The vote has now closed. The results are:
Positive Binding Votes: 3
* Bryan Ellis
* Niklas Merz
* Jesse MacFadyen
Negative Binding Votes: 0
The vote has passed.
Thanks everyone!
On Thu, Sep 17, 2020 at 5:43 PM Jesse wrote:
> +1
>
> - coho verify-archive
> - created project (ios) added
Please review and vote on this Electron Release v2.0.0
by replying to this email (and keep discussion on the DISCUSS thread)
The archive has been published to dist/dev:
https://dist.apache.org/repos/dist/dev/cordova/electron-v2.0.0
The package was published from its corresponding git tag:
https://youtu.be/lPe6_YF9L9Q
It was awesome to hang out with everyone today, thanks!
My understanding is that we will have the next meeting in exactly 2 weeks:
Thursday October 1 11AM EDT (NYC time).
I noticed that most of the discussion is in a private Slack channel. I
would really appreciate it if we could keep our
+1
- coho verify-archive
- created project (ios) added plugin and built+ran
- code/repo changes review
On Sun, Sep 13, 2020 at 11:38 PM Niklas Merz wrote:
> I vote +1
>
> I checked
> * signature and hash ok
> * no audit issues
> * license and notice exist
> * CI for Android and iOS green
> *
I may be a little late due to a previously scheduled meeting.
I would love it if we can find out what the objections were to using the
donation towards updating the documentation, and if there is anything we
could do to address those objections.
On Wed, Sep 16, 2020 at 7:29 PM Norman Breau
I'm not sure if I'll be able to attend, but to at least put the topic on the
radar... there is a problem with using cookies on WKWebView where the cookie
doesn't appear to be in sync. I'm not sure on the exact details since I don't
use cookies myself, but it's an issue that frequently comes up
Okay, sounds like we have enough interest to go ahead with the Thursday
call.
Topics so far:
- Tim: putting that generous donation to use
- Darryl: issues with platform-centric workflow ( I can help by providing
some historical context )
Any other topics?
Cheers,
Jesse
On Wed, Sep 16, 2020
Tomorrow works for me.
I think one topic that might be good to cover is the history of the
Platform Centric Workflow, and the current problems with it, so that
folks have some more context for discussions about potentially
removing it. I'm happy to present this, but might need some
I'm +1 for doing the meeting tomorrow.
For the lazy people, I've once again put the date into the world clock:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Cordova+Committer+Video+Chat=20200917T15=%3A=1
Maybe we can talk about the donation offer once again and (finally?) make a
As alluded to in the private conversations in #slack, we are tentatively
having a meetup on Thursday the 17th at 8 AM PDT. This timeframe does not
work great for everyone, but none ever will, and I think that is okay, we
are distributed, and these meetings are about discussion and collaboration
I vote +1
I checked
* signature and hash ok
* no audit issues
* license and notice exist
* CI for Android and iOS green
* local tests green
* license headers ok
Am 14.09.20 um 05:39 schrieb Bryan Ellis:
> Please review and vote on this Cordova Plugin Camera Release v5.0.0
> by replying to this
+1 go for it
Am 14.09.20 um 06:36 schrieb Bryan Ellis:
> Does anyone have any reason to delay a cordova-electron major release (2.0.0)?
>
> Any additional outstanding changes to land?
>
> If not, I will start the release process shortly.
>
Does anyone have any reason to delay a cordova-electron major release (2.0.0)?
Any additional outstanding changes to land?
If not, I will start the release process shortly.
Please review and vote on this Cordova Plugin Camera Release v5.0.0
by replying to this email (and keep discussion on the DISCUSS thread)
The archive has been published to dist/dev:
https://dist.apache.org/repos/dist/dev/cordova/camera-20200914
The package was published from its corresponding
I completely understand, thanks for the quick turnaround:)
On Thu, Sep 10, 2020 at 2:53 AM Jesse wrote:
> Thanks Chris,
>
> I added a blurb, Report has been posted.
> Sorry for the short turn around on this one,
>
> Cheers,
> Jesse
>
> On Wed, Sep 9, 2020 at 10:30 PM Chris Brody wrote:
>
>
timbru31 opened a new issue #12:
URL: https://github.com/apache/cordova-apache-board-reports/issues/12
@purplecabbage The board calendar is very outdated. Can you gather the
newest dates? Otherwise, I'd vote to remove it from the README.
Thanks Chris,
I added a blurb, Report has been posted.
Sorry for the short turn around on this one,
Cheers,
Jesse
On Wed, Sep 9, 2020 at 10:30 PM Chris Brody wrote:
> I think we should include a note that there is a donation and there is
> ongoing discussion what to do with it.
>
>
> On
purplecabbage merged pull request #11:
URL: https://github.com/apache/cordova-apache-board-reports/pull/11
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
I think we should include a note that there is a donation and there is
ongoing discussion what to do with it.
On Wed, Sep 9, 2020 at 11:17 PM Jesse wrote:
> The quarterly board report draft is here:
> https://github.com/apache/cordova-apache-board-reports/pull/11
>
> Comments, additions,
The quarterly board report draft is here:
https://github.com/apache/cordova-apache-board-reports/pull/11
Comments, additions, suggestions welcome.
Cheers,
Jesse
Hi
Thanks for the responses. I did read the responses. And I did subscribe myself
to the dev list.
There seems to be some different visions.
Some highlights:
Niklas stated:
'
A new major version could possibly change that if we can get consensus about
this but someone would need to do the
purplecabbage opened a new pull request #11:
URL: https://github.com/apache/cordova-apache-board-reports/pull/11
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub
I'm +1 for this and would add my bio. I'll take a look at your PR this week.
Before merging, I think we should gather at least 5 volunteers who would
add their bio, too.
Best,
Tim
On Sun, Sep 6, 2020 at 10:18 PM Niklas Merz wrote:
> Hi everyone,
>
> I would like to bring this back up. I
Hello Zhen,
This list is for talking about the development of Apache cordova project,
not for asking questions about its use, or getting help with issues in your
application.
I suggest you look through stack-overflow and post your question there.
Additionally, you can ask for help from other
This mailing list is for discussions regarding development of Cordova, and not
for support.
If you require support, you should try asking on our slack at
http://slack.cordova.io/
Hello Cordova:
How to solve the white screen problem of cordova9 packaged Android project
(can't lower the cordova version)?
Thanks
zhen
It would be good that instead of just saying what you would like to see
changed, you also say why you would like it (benefits, reasoning, etc.)
El lunes, 7 de septiembre de 2020, Niklas Merz
escribió:
> Hi Pieter
>
> At first a warm welcome to the list.
>
> If you would like to open a proposal
Welcome Pieter,
The best proposals are pull-requests.
All your suggestions sound perfectly reasonable, and I personally would love to
see this happen.
Cheers,
Jesse
> On Sep 6, 2020, at 3:38 PM, Niklas Merz wrote:
>
> Hi Pieter
>
> At first a warm welcome to the list.
>
> If you would
Hi Pieter
At first a warm welcome to the list.
If you would like to open a proposal for discussion I can point you to
the cordova-discuss repository:
https://github.com/apache/cordova-discuss/ . We track some proposals in
issues and pull requests there.
I am not really familiar with the plugin
Here is the repository on GitHub for quick reference:
https://github.com/apache/cordova-plugin-network-information
Unfortunately I am not familiar enough to make the 3.0.0 release. I would
recommend that you ping others on Slack and maybe raise an issue on GitHub.
Maintainers seem to be somewhat
Hey Cordova devs
You are doing a great job with Cordova.
I've got a question, suggestion for the cordova-plugin-network-information.
Is it possible to open an issue, a milestone, a metaticket or something to
discuss the future requirements of the plugin (v4).
Something like a whitepaper.
My
Hi everyone,
I would like to bring this back up. I managed to get this built
automatically from markdown files, where every team member could
describe themselves if they like to. I really liked the introduction
part of the last hangout and this would basically be the written form.
I would really
Yes I think this needs a formal vote. I will look up the template, would
appreciate any pointers.
I think there should be separate votes to deprecate cordova-osx and
cordova-windows.
I am setting the PRs to DRAFT pending the outcome of the votes.
On Fri, Sep 4, 2020 at 4:51 AM Tim Brust
Great idea Julio. I've updated the readme to point to the forked plugin.
Simon Mac Donald
http://simonmacdonald.com
On Thu, Sep 3, 2020 at 7:09 PM julio cesar sanchez
wrote:
>
> The push plugin is already forked and got a few code updates, so if you
> could point to it in the phonegap one would
Hi,
correct me if I'm wrong, but isn't the deprecation missing a formal vote?
Best,
Tim
On Fri, Sep 4, 2020 at 4:52 AM Chris Brody wrote:
> I have now raised the following PRs:
>
> - https://github.com/apache/cordova-lib/pull/851
> - https://github.com/apache/cordova-lib/pull/852
> -
I have now raised the following PRs:
- https://github.com/apache/cordova-lib/pull/851
- https://github.com/apache/cordova-lib/pull/852
- https://github.com/apache/cordova-docs/pull/1117
- https://github.com/apache/cordova-docs/pull/1118
On Fri, Jun 26, 2020 at 4:38 AM Niklas Merz wrote:
> +1
The push plugin is already forked and got a few code updates, so if you
could point to it in the phonegap one would be good. Will have a different
name, so people will have to replace it.
For the barcode, the aar used on android is 4 year old and it’s built from
a zxing app that was abandoned 2
Yeah, no worries folks. If you don't have the bandwidth to pull them
under the Apache umbrella I completely understand.
As for licensing, we'd be able to figure it out. I work with 4 lawyers
on this stuff so they would be able to figure out a path that works.
Simon Mac Donald
At this point I would be a little reluctant to start supporting more
plugins.
Issues and unmerged PRs seem to keep piling up in multiple places. Here are
a couple of very sad examples:
- https://github.com/apache/cordova-ios/pull/795
- https://github.com/apache/cordova-plugin-file/pull/242
On
I would favor discussing this idea in
https://github.com/apache/cordova/issues or
https://github.com/apache/cordova-discuss/issues
I am thinking it would be really nice if Cordova would use the Cordova
plugin packages from node_modules rather than plugins in the future. I
think this would be more
+1
Just need to try and make the bot smart enough to catch the requests vs
something legit issue. I like the idea on how you have a threshold count.
Bot should also leave a good generic message as well before closing. Something
about how we are working in various repos and do not provide set
I think I've found the main blocker:
GH Actions secrets are not exposed to PRs from forks. :(
There is an open feature request for this though:
https://github.community/t/make-secrets-available-to-builds-of-forks/16166
Cheers,
Tim
On Mon, Aug 31, 2020 at 8:53 PM Jan Piotrowski wrote:
> You
> The Android bug that prevented the 4.2.0 release is fixed in the meantime?
Yes, it was fixed in July.
> On Sep 3, 2020, at 17:21, Tim Brust
> wrote:
>
> The Android bug that prevented the 4.2.0 release is fixed in the meantime?
> Can't recall if there is a to-do left.
>
> On Thu, Sep 3,
The Android bug that prevented the 4.2.0 release is fixed in the meantime?
Can't recall if there is a to-do left.
On Thu, Sep 3, 2020 at 6:49 AM Bryan Ellis wrote:
> Does anyone have any reason to delay a cordova-plugin-camera major release
> (5.0.0)?
>
> Any additional outstanding changes to
Does anyone have any reason to delay a cordova-plugin-camera major release
(5.0.0)?
Any additional outstanding changes to land?
- Android tasks to use AndroidX will not be included in this release since
Cordova-Android does not have AndroidX enabled by default.
If not, I will start the
It could be integrated into Apache.
What exactly would the process of integrating look like?
I suspect it would start with a vote email?
Since the existing plugin license is MIT, what happens here? I don't know the
rules or process on how we can change the license. I had read that there were
We have released a patch update for the iOS platform:
- cordova-ios@6.1.1
You can view the release blog post at
https://cordova.apache.org/announcements/2020/08/31/cordova-ios-6.1.1.html
-
To unsubscribe, e-mail:
You might go slow on this - somewhere in the back of my head I have
_something_ why we did not follow through with this in the past but I can
not figure out what it was, sorry :/ Hopefully it is nothing and will just
work.
J
Am So., 30. Aug. 2020 um 19:55 Uhr schrieb Tim Brust :
> Hi there,
>
Thanks everyone, the vote has now closed. The results are:
Positive Binding Votes: 4
- Darryl Pogue
- Niklas Merz
- Tim Brust
- Ken Naito
Negative Binding Votes: 0
The vote has passed.
On Sun, Aug 30, 2020 at 10:45 PM Ken Naito wrote:
>
> +1
>
> I did:
> * coho verify-archive OK
> * coho
Hi everyone,
I’m George Henne. I have been working with Cordova (and PhoneGap) since 2010,
mostly as one of the developers of AppStudio. AppStudio creates web apps then
passes them to Cordova/PhoneGap.
I’m also part of the VoltBuilder dev team, which uses Cordova to provide a
modern
+1
I did:
* coho verify-archive OK
* coho verify-tags OK
* The commit
https://github.com/apache/cordova-ios/commit/0b48eaf3aa232052e11e7a265f752e7aa6ef3b21
is green.
Thanks!
On 2020/08/29 6:31, Darryl Pogue wrote:
Hi folks,
Apologies for the delay in getting this release together!
Please
I vote +1
- CI is green
- changes make sense
- npm audit is happy
- coho verify-archive is happy
Thanks Darryl for making the release!
On Sat, Aug 29, 2020 at 9:01 AM Niklas Merz wrote:
> I vote +1
>
> * verified tag and hash
> * no audit issues
> * draft tag matches sha in email (checked
Hi there,
I'd like to continue to migrate our testing setup from TravisCI to GitHub
Actions. Currently, our plugins are all running on Travis and test against
VMs on Sauce Labs [1] and are not yet migrated.
They currently use the Travis-encrypted credentials of Alexander ("snay").
Since I do not
I vote +1
* verified tag and hash
* no audit issues
* draft tag matches sha in email (checked manually)
* checked LICENSE + NOTICE
* CI green
* changes look good
One minor issue: coho verify-tags does not work with new "draft" naming
Am 28.08.20 um 23:31 schrieb Darryl Pogue:
> Hi folks,
>
We've had nightly builds of the Cordova tooling and platforms for a
few years now. Recently the ASF Infrastructure team was replacing the
Jenkins system that previously ran them, so Bryan Ellis ported the
build scripts over to GitHub actions.
For those who are curious, the workflow lives in the
Hi folks,
Apologies for the delay in getting this release together!
Please review and vote on this 6.1.1 Cordova-iOS release by replying
to this email (and keep discussion on the DISCUSS thread)
The archive has been published to dist/dev:
https://dist.apache.org/repos/dist/dev/cordova/ios611/
Thanks Simon
We'll look at this. Erisu appears to already be actively working on
havesource/cordova-plugin-push
Cheers,
Jesse
On Fri, Aug 28, 2020 at 1:22 PM Simon MacDonald
wrote:
> Hi folks,
>
> Long time no chat. As you are no doubt aware Adobe announced they are
> no longer in the
Hi folks,
Long time no chat. As you are no doubt aware Adobe announced they are
no longer in the PhoneGap business. To that end I archived the
following plugins that are still being used widely:
phonegap-plugin-push - 7,659 weekly downloads
phonegap-plugin-barcodescanner - 11,058 weekly
> and it would help us to keep the issues and discussions all in one place.
I would challenge you actually want that. To be able to properly work on
one plugin, you would need to have labelled all issues and PRs and then
filter all views for that.
In my experience this only makes sense for
Welcome Narveer,
Glad to see interest in the community!
Norman Breau
Software Developer
nor...@normanbreau.com
(https://link.getmailspring.com/link/741441ee-8628-4aa4-975d-1b5d99e5e...@getmailspring.com/0?redirect=mailto%3Anorman%40normanbreau.com=ZGV2QGNvcmRvdmEuYXBhY2hlLm9yZw%3D%3D)
I think Erisu was planning on making nightly releases for plugins, but I
generally agree. I think Monorepo may make more sense for the core, but not for
the entire code base.
And I think the point that mono repos make it hard to install from github is a
very good point to make.
Hi Narveer,
a warm welcome to you!
Looking forward to seeing some contributions from you. :)
Cheers,
Tim
On Thu, Aug 27, 2020 at 8:20 PM Narveer Rathore <
rathore.narveer1...@gmail.com> wrote:
> Hello, I have been using cordova for the past 3 years on one of our core
> products. Glad to be
Hello, I have been using cordova for the past 3 years on one of our core
products. Glad to be part of the community and opportunities to learn more.
Thanks,
Narveer Singh Rathore
rathore.narveer1...@gmail.com
Maybe it makes more sense for the tooling packages, common, cli, lib, etc,
as they get less issues reported and it's usually more confusing for users
(and me) to report in the proper place as a bug in one of those modules can
be caused by another module. But I would keep platforms and plugins in
Someone had an idea to convert Cordova into a single monorepo. There
are some very well-known benefits, and it would help us to keep the
issues and discussions all in one place. Lerna seems to be a nice tool
to keep things consistent and in sync.
I think the original PhoneGap that Cordova was
OK,
I changed my point-of-view on this topic and will close the discussion as
`not-to-fix`.
We don't need to deprecate any NPM package.
I have looked at a few major projects and almost all of them have never
deprecated a package. Only a few projects use heavily used the `npm deprecate`
Okay, not sure if doodle notifies y'all but I closed it with the 8AM
Thursday August 27 (PST) option.
Thanks to Bryan Ellis for agreeing to sign on at midnight his time.
I don't have a formal.agenda, I think it would be good to just connect,
chat and catch up.
If you like, please feel free to add
The vote has now closed. The results are:
Positive Binding Votes: 3
* Bryan Ellis
* Norman Breau
* Jan Piotrowski
Negative Binding Votes: 0
The vote has passed.
Thanks everyone!
> On Aug 19, 2020, at 4:05, Jan Piotrowski wrote:
>
> +1
>
> Am Di., 18. Aug. 2020 um 06:59 Uhr schrieb Norman
The vote has now closed. The results are:
Positive Binding Votes: 5
* Bryan Ellis
* Norman Breau
* Dave Alden
* Tim Brust
* Jan Piotrowski
Negative Binding Votes: 0
The vote has passed.
Thanks everyone!
> On Aug 19, 2020, at 4:05, Jan Piotrowski wrote:
>
> +1
>
> Am Di., 18. Aug. 2020 um
The vote has now closed. The results are:
Positive Binding Votes: 3
* Bryan Ellis
* Dave Alden
* Jan Piotrowski
Negative Binding Votes: 0
The vote has passed.
Thanks everyone!
> On Aug 19, 2020, at 4:05, Jan Piotrowski wrote:
>
> +1
>
> Am Di., 18. Aug. 2020 um 08:46 Uhr schrieb Dave
Thursday would be perfect for me. Another Doodle is fine too.
August 24, 2020 8:18 AM, "Jesse" wrote:
> So far the times where we have all 6 are:
>
> Tuesday Aug 25th
> 8AM OR 9AM
> Wednesday, Aug 26
> 9AM
> Thursday, Aug 27
> 8AM, 9AM
>
> All times PDT
> My preference would be for one of the
So far the times where we have all 6 are:
Tuesday Aug 25th
8AM OR 9AM
Wednesday, Aug 26
9AM
Thursday, Aug 27
8AM, 9AM
All times PDT
My preference would be for one of the Thursday slots, as my Wednesday is
already filling up.
Should I start another doodle with just the 5 dates that all 6 can
Where did this land?
So, agreed, you did not say to deprecate minor, I meant to say we should
not deprecate any minor OR patch ...
If someone has an issue with a patch, the solution is always just to move
forward to the latest patch ... there is no 'support' expectation
Patching a patch would
Nightly build #1513 for cordova has succeeded!
The latest nightly has been published and you can try it out with 'npm i -g
cordova@nightly'
For details check build console at
https://builds.apache.org/job/cordova-nightly/1513/consoleFull
-
Jenkins for Apache Cordova
+1 good
On 2020/08/21 4:29, Darryl Pogue wrote:
Anyone have any objections to making a cordova-ios 6.1.1 patch release?
Namely, it fixes an issue where deploying to devices doesn't work.
Diff from 6.1.0:
https://github.com/apache/cordova-ios/compare/6.1.0...master
I don't really want to try
Nightly build #1512 for cordova has succeeded!
The latest nightly has been published and you can try it out with 'npm i -g
cordova@nightly'
For details check build console at
https://builds.apache.org/job/cordova-nightly/1512/consoleFull
-
Jenkins for Apache Cordova
+1
Thanks for taking the initiative, Darryl!
Sent from my iPhone
> On 20. Aug 2020, at 9:53 PM, Niklas Merz wrote:
>
> +1 sounds like a good time to release a patch
>
>> Am 20.08.20 um 21:38 schrieb Chris Brody:
>> +1
>>
>>> On Thu, Aug 20, 2020 at 3:30 PM Darryl Pogue wrote:
>>>
>>>
+1 sounds like a good time to release a patch
Am 20.08.20 um 21:38 schrieb Chris Brody:
> +1
>
> On Thu, Aug 20, 2020 at 3:30 PM Darryl Pogue wrote:
>>
>> Anyone have any objections to making a cordova-ios 6.1.1 patch release?
>> Namely, it fixes an issue where deploying to devices doesn't
+1
On Thu, Aug 20, 2020 at 3:30 PM Darryl Pogue wrote:
>
> Anyone have any objections to making a cordova-ios 6.1.1 patch release?
> Namely, it fixes an issue where deploying to devices doesn't work.
>
> Diff from 6.1.0:
> https://github.com/apache/cordova-ios/compare/6.1.0...master
>
> I don't
Anyone have any objections to making a cordova-ios 6.1.1 patch release?
Namely, it fixes an issue where deploying to devices doesn't work.
Diff from 6.1.0:
https://github.com/apache/cordova-ios/compare/6.1.0...master
I don't really want to try to rush anything else into this release, just a
Nightly build #1511 for cordova has succeeded!
The latest nightly has been published and you can try it out with 'npm i -g
cordova@nightly'
For details check build console at
https://builds.apache.org/job/cordova-nightly/1511/consoleFull
-
Jenkins for Apache Cordova
I guess you mean this issue
https://github.com/apache/cordova-plugin-device-orientation/issues/52
To be clear, the web API still works on iOS 13, but it requires to request
a permission first with DeviceMotionEvent.requestPermission();
But the permission request has a few issues that I have
I too face the same issue.
I have a large file - between 100 MB and 300MB which I need to download and
save in the local file system (SQLite database file that I don't want to split).
When using regular angular/ionic http client on iOS the app crashes to the
"white screen of death".
Using this
Nightly build #1510 for cordova has failed.
Please check failure details on build details page at
https://builds.apache.org/job/cordova-nightly/1510/
You can also take a look at build console:
https://builds.apache.org/job/cordova-nightly/1510/consoleFull
-
Jenkins for Apache Cordova
> At this point I think almost all clean tags should match accepted rel
> (release) tags.
>
> Any clean tags that are for rejected drafts should definitely be deleted.
>
> Just as a small, personal preference, I would not favor deleting any
> clean tags that already match accepted rel (release)
>> I think this stance is too aggressive.
>> For minor version bumps there is no need to deprecate the previous minor
>> as any support request should be met with ‘update’
I also did not say to deprecate a minor.
> When releasing a minor, nothing happens.
Minors are typically just a new feature
> `draft/` tag prefix is for drafts
+1
> `rel/` tag prefix is for releases
+1
> No more clean tags will be created
OK as discussed below
> `rel/` tags has and will always be the accepted release tag, unless changed
> in the future.
+1
> We never used clean tags as an official release. We
901 - 1000 of 53339 matches
Mail list logo
