Re: [VOTE] Camera Plugin 8.0.0 Release

[Darryl Pogue]

I vote +1:

* Ran `coho verify-tags`
* Ran `coho verify-archive`
* Ran `coho audit-license-headers` over the relevant repos
* Ran `coho check-license` to ensure Apache-compatible licenses
* Ensured continuous build was green when repos were tagged
* Ran `npm audit` and ensured no vulnerabilities found

~Darryl


On Thu, Oct 31, 2024 at 9:52 AM Niklas Merz  wrote:
>
> I vote +1:
>
> * hash & signature ok
> * tag ok
> * no audit issues
> * CI looks good
> * license headers ok
> * license ok
> * app builds with plugin for android on my machine
>
> On October 30, 2024, Norman Breau  wrote:
> > Please review and vote on the release of this plugins release
> > by replying to this email (and keep discussion on the DISCUSS thread)
> >
> > The plugins have been published to dist/dev:
> > https://dist.apache.org/repos/dist/dev/cordova/camera8.0.0/
> >
> > The packages were published from their corresponding git tags:
> >  cordova-plugin-camera: 8.0.0 (04946dccc7)
> >
> > Upon a successful vote I will upload the archives to dist/, upload
> > them
> > to npm, and post the corresponding blog post.
> >
> > Voting guidelines:
> > https://github.com/apache/cordova-coho/blob/master/docs/release-
> > voting.md
> > How to vote on a plugins release at
> > https://github.com/apache/cordova-coho/blob/master/docs/plugins-
> > release-process.md#voting
> >
> > Voting will go on for a minimum of 48 hours.
> >
> > I vote +1:
> > * Ran coho audit-license-headers over the relevant repos
> > * Ran coho check-license to ensure all dependencies and
> > subdependencies
> > have Apache-compatible licenses
> > * Ensured continuous build was green when repos were tagged
> > * Manual tests on iOS & Android
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [VOTE] cordova-lib 12.0.2 Release

[Darryl Pogue]

Thanks for putting this release together Bryan!

I vote +1:

* Ran `coho verify-tags`
* Ran `coho verify-archive`
* Ran `coho audit-license-headers` over the relevant repos
* Ran `coho check-license` to ensure all dependencies and sub-dependencies have
Apache-compatible licenses
* Ensured continuous build was green when repos were tagged
* Ran `npm test` and ensured all tests pass locally
* Ran `npm audit` and ensured no vulnerabilities found

~Darryl


On Mon, Oct 28, 2024 at 11:03 PM Bryan Ellis  wrote:
>
> Please review and vote on this cordova-lib release v12.0.2
> 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/lib-12.0.2
>
> The package was published from its corresponding git tag:
>
> cordova-lib: 12.0.2 (2df48f184c)
>
> Upon a successful vote I will upload the archive to dist/, publish it to
> npm, and post the blog post.
>
> Voting guidelines:
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
>
> Voting will go on for a minimum of 48 hours.
>
> =
>
> I vote +1:
>
> * Verify GH Action "Release Auditing" Workflow
>   * Audits License Headers
>   * Ensures all dependencies and sub-dependencies have Apache-compatible
> licenses
> * Ensured the continuous build was green when repo was tagged
> * Ran `npm test`
>
> * Ran various `cordova` test w/ sample app:
>   * `cordova`
>   * `cordova -v`
>   * `cordova create`
>   * `cordova info`
>   * `cordova help`
>   * `cordova config ls`
>   * `cordova requirements`
>   * `cordova platform`
>   * `cordova platform add`
>   * `cordova platform rm`
>   * `cordova plugin`
>   * `cordova plugin add`
>   * `cordova plugin rm`
>
> * Ran `npm audit`
>
> found 0 vulnerabilities

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [VOTE] Cordova File Plugin 8.1.2 Release

[Darryl Pogue]

I vote +1:

* Ran coho audit-license-headers over the relevant repos
* Ran coho check-license to ensure all dependencies and sub-dependencies have
Apache-compatible licenses
* Ensured continuous build was green when repos were tagged
- Note that this release contains no changes to iOS code, and the iOS test
  failure is consistent with the previous release

~Darryl


On Sun, Oct 27, 2024 at 6:48 AM Norman Breau  wrote:
>
> Please review and vote on the release of this plugins release
> by replying to this email (and keep discussion on the DISCUSS thread)
>
> The plugins have been published to dist/dev:
> https://dist.apache.org/repos/dist/dev/cordova/fileplugin8.1.2/
>
> The packages were published from their corresponding git tags:
>  cordova-plugin-file: 8.1.2 (d90244d3fc)
>
> Upon a successful vote I will upload the archives to dist/, upload them
> to npm, and post the corresponding blog post.
>
> Voting guidelines:
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
> How to vote on a plugins release at
> https://github.com/apache/cordova-coho/blob/master/docs/plugins-release-process.md#voting
>
> Voting will go on for a minimum of 48 hours.
>
> I vote +1:
> * Ran coho audit-license-headers over the relevant repos
> * Ran coho check-license to ensure all dependencies and subdependencies
> have Apache-compatible licenses
> * Ensured continuous build was green when repos were tagged
>Note: As with 8.1.1 release, there are iOS failures that previously
> existed since at least 8.1.0 release.
> * NPM Audit is green
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [DISCUSS] Making a cordova-ios 8.0.0-beta.1 release

[Darryl Pogue]

Well that's awful and unintuitive :(

Unfortunately there doesn't seem to be a `--force` option for plugin
install that skips the version check. We do our own hacky code there
explicitly stripping off `-dev` and `-nightly.*` suffixes, which would
probably be better replaced with the built-in `includePrerelease` flag
for the semver module.
Doubly unfortunately, this happens deep in cordova-lib, which makes it
inconvenient to solve quickly. I'll try to get a PR open though, since
the current behaviour seems particularly bad.

The "quick fix" for testing is likely going to be downloading the
plugin locally and stripping the version requirement out of its
package.json file, but that's a huge pain for projects with a bunch of
plugins. Or using the cordova-ios@nightly tag instead of the beta, but
we're not allowed to recommend that for end users because it's not a
validated release and will include additional changes as those get
merged.

~Darryl


On Tue, Oct 22, 2024 at 7:56 AM Norman Breau  wrote:
>
> Can it be `--force` ?
>
> I think this is definitely an oversight. SEMVER handles pre-release
> labels in an non-intuitive way, in my opinion.
>
> On 2024-10-22 11:53, Alexandre Alves wrote:
> > Hi,
> >
> > I've tried testing the beta version of cordova-ios 8 beta 1 and I see that 
> > it fails to add some plugins that check ios minimum version.
> >
> > Example:
> > Plugin doesn't support this project's cordova-ios version. cordova-ios: 
> > 8.0.0-beta.1, failed version requirement: >=6.0.0
> > Skipping 'cordova-plugin-statusbar' for ios
> >
> > This, I think is due to the numbering system used for the beta version.
> >
> > How do you think this should be handled? Should the numbering of the beta 
> > version be reviewed to allow version checking?
> >
> > Alexandre Alves
> >
> > 
> > De: Darryl Pogue 
> > Enviado: 15 de outubro de 2024 05:43
> > Para: dev@cordova.apache.org 
> > Assunto: Re: [DISCUSS] Making a cordova-ios 8.0.0-beta.1 release
> >
> > I've created a pull request for adding migration docs for plugin
> > authors. I've tried to review all the API changes and note everything
> > down in there, but if anyone notices anything I've missed or thinks
> > that something could be reworded better, please leave a comment:
> > https://github.com/apache/cordova-ios/pull/1498
> >
> > This will be part of the DocC API documentation for the CordovaLib
> > framework, which now gets published automatically on GitHub Pages:
> > https://apache.github.io/cordova-ios/
> >
> > The hope is that we can make it easier for plugin authors and app
> > developers consuming CordovaLib as a framework to understand how the
> > internals work. If nothing else, it's an interesting exercise to
> > document the internals for ourselves.
> >
> > I'll try to get a tag set up later this week and put the beta.1 up for a 
> > vote.
> > ~Darryl
> >
> >
> > On Sat, Oct 12, 2024 at 6:10 AM Bryan Ellis  wrote:
> >> +1
> >>
> >> I support the idea of providing a beta or release candidate for the
> >> upcoming major release.
> >>
> >> I've already started testing the potential beta release in one of my
> >> ongoing projects. A few third-party plugins will require updates, and I
> >> plan to submit PRs ahead of time to help them prepare for the release.
> >>
> >>
> >> On Fri, Oct 11, 2024 at 9:27 PM Norman Breau  wrote:
> >>
> >>> +1
> >>>
> >>> I can also test the beta when available against one of my projects and
> >>> report back on any issues
> >>> that I encounter. My projects are fairly large and makes use of good set
> >>> of plugins, both
> >>> from the public ecosystem and some private ones as well.
> >>>
> >>> I'm not sure if there already a list of breaking changes available, but
> >>> it would be nice
> >>> to have one for reference, which could probably be later reused for the
> >>> actual 8.0 release announcement.
> >>>
> >>> Cheers,
> >>> Norman
> >>>
> >>> On 2024-10-11 07:25, Niklas Merz wrote:
> >>>> +1
> >>>>
> >>>> I like the idea of doing a pre-release a lot in such case. Other Apache
> >>>> projects do release candidates (rc) shortly before their release but if
> >>>> we are still a bit away from the final release beta is a good nam

Re: [VOTE] cordova-plugin-file 8.1.1 Release

[Darryl Pogue]

I vote +1:

* Ran coho audit-license-headers over the relevant repos
* Ran coho check-license to ensure all dependencies and sub-dependencies have
Apache-compatible licenses
* Ensured continuous build was green when repos were tagged
- Note that this release contains no changes to iOS code, and the iOS test
  failure is consistent with the previous release

~Darryl


On Sun, Oct 20, 2024 at 2:16 PM Norman Breau  wrote:
>
> Please review and vote on the release of this plugins release
> by replying to this email (and keep discussion on the DISCUSS thread)
>
> The plugins have been published to dist/dev:
> https://dist.apache.org/repos/dist/dev/cordova/fileplugin20241020/
>
> The packages were published from their corresponding git tags:
>  cordova-plugin-file: 8.1.1 (e31880d189)
>
> Upon a successful vote I will upload the archives to dist/, upload them
> to npm, and post the corresponding blog post.
>
> Voting guidelines:
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
> How to vote on a plugins release at
> https://github.com/apache/cordova-coho/blob/master/docs/plugins-release-process.md#voting
>
> Voting will go on for a minimum of 48 hours.
>
> I vote +1:
> * Ran coho audit-license-headers over the relevant repos
> * Ran coho check-license to ensure all dependencies and subdependencies
> have Apache-compatible licenses
> - NOTE: Warning on Python 2.0 License, which is a Category A licensed
> listed as "Python Software Foundatation License"
> (https://www.apache.org/legal/resolved.html)
> * Ensured continuous build was green when repos were tagged
> - NOTE: iOS has failures which is not a regression of 8.1.1. These
> failures existed since at least 8.1.0. Therefore I have reasonable
> belief that this release is not any worse on iOS.
> * Ran cordova-paramedic on Android API 24, 29, 32, 34, & 35 simulators.
> * Ran NPM test / Lint
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[ANNOUNCEMENT] Cordova iOS 8.0.0-beta.1 now available!

[Darryl Pogue]

cordova-ios@8.0.0-beta.1 has been published to npm under the beta tag.

The intention of this beta release is for plugin authors and app developers
to test their plugins and projects and provide feedback and bug reports
before the final release of Cordova iOS 8.0.0. This version includes
several breaking API changes and project structure changes, which is why we
are providing this beta release for testing purposes.

Blog post about the release:
https://cordova.apache.org/announcements/2024/10/21/cordova-ios-8.1.1-beta.1.html

Re: [VOTE] Cordova iOS 8.0.0-beta.1 Release

[Darryl Pogue]

The vote has now closed. The results are:

Positive Binding Votes: 4
Darryl Pogue
Norman Breau
Niklas Merz
Bryan Ellis

Negative Binding Votes: 0

The vote has passed.

Thank you all for reviewing, I'll get this published.
~Darryl

On Sun, Oct 20, 2024 at 11:37 PM Bryan Ellis  wrote:
>
> +1
>
> * Confirm tag release management workflow passed
>   * Apache License Headers
>   * License checker to ensure all dependencies have Apache-compatible
> licenses
> * Ensured continuous build was green when repos were tagged
> * Confirmed sigs & hashes with `coho verify-archive` [1]
> * Verified sha1s match tags with `coho verify-tags` [2]
> * Tested installing platform from tarball & building sample Cordova app
>
>
>
> On Mon, Oct 21, 2024 at 3:15 PM Niklas Merz  wrote:
>
> > I vote +1:
> >
> > - signature & hash ok
> > - tag ok
> > - non-native tests ok
> > - no audit issues
> > - licenses ok
> > - headers ok
> > - CI green
> > - release documentation looks good
> >
> > On October 20, 2024, Norman Breau  wrote:
> > > I vote +1:
> > >
> > > - Ran npm test / xcode tests
> > > - Verified Tags
> > > - Verified Archive
> > > - NPM audit reports 0 vulnerabilities
> > >
> > > On 2024-10-18 2:59 a.m., Darryl Pogue wrote:
> > > > Please review and vote on this Cordova-iOS Release v8.0.0-beta.1 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/ios-8.0.0-beta.1
> > > >
> > > > The package was published from its corresponding git tag:
> > > > cordova-ios: 8.0.0-beta.1 (18a80d248c)
> > > >
> > > > Note that you can test it out via:
> > > > cordova platform add https://github.com/apache/cordova-ios#8.0.0-
> > > beta.1
> > > >
> > > > Upon a successful vote I will upload the archive to dist/, publish
> > > it
> > > > to npm, and post on the blog (PR for the blog post will be coming
> > > over
> > > > the weekend).
> > > >
> > > > Voting guidelines:
> > > > https://github.com/apache/cordova-coho/blob/master/docs/release-
> > > voting.md
> > > >
> > > > Voting will go on for a minimum of 48 hours.
> > > >
> > > >
> > > > I vote +1:
> > > > * Ran coho audit-license-headers over the relevant repos
> > > > * Ran coho check-license to ensure all dependencies and
> > > > sub-dependencies have Apache-compatible licenses
> > > > * Ensured continuous build was green when repo was tagged
> > > > * Ran npm audit and confirmed no vulnerability warnings
> > > > * Ran `cordova build` test
> > > > * Ran `cordova run` emulator test
> > > >
> > > >
> > > > Thanks,
> > > > ~Darryl
> > > >
> > > >
> > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > > For additional commands, e-mail: dev-h...@cordova.apache.org
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > For additional commands, e-mail: dev-h...@cordova.apache.org
> >

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[VOTE] Cordova iOS 8.0.0-beta.1 Release

[Darryl Pogue]

Please review and vote on this Cordova-iOS Release v8.0.0-beta.1 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/ios-8.0.0-beta.1

The package was published from its corresponding git tag:
cordova-ios: 8.0.0-beta.1 (18a80d248c)

Note that you can test it out via:
cordova platform add https://github.com/apache/cordova-ios#8.0.0-beta.1

Upon a successful vote I will upload the archive to dist/, publish it
to npm, and post on the blog (PR for the blog post will be coming over
the weekend).

Voting guidelines:
https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md

Voting will go on for a minimum of 48 hours.


I vote +1:
* Ran coho audit-license-headers over the relevant repos
* Ran coho check-license to ensure all dependencies and
sub-dependencies have Apache-compatible licenses
* Ensured continuous build was green when repo was tagged
* Ran npm audit and confirmed no vulnerability warnings
* Ran `cordova build` test
* Ran `cordova run` emulator test


Thanks,
~Darryl

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [DISCUSS] Making a cordova-ios 8.0.0-beta.1 release

[Darryl Pogue]

I've created a pull request for adding migration docs for plugin
authors. I've tried to review all the API changes and note everything
down in there, but if anyone notices anything I've missed or thinks
that something could be reworded better, please leave a comment:
https://github.com/apache/cordova-ios/pull/1498

This will be part of the DocC API documentation for the CordovaLib
framework, which now gets published automatically on GitHub Pages:
https://apache.github.io/cordova-ios/

The hope is that we can make it easier for plugin authors and app
developers consuming CordovaLib as a framework to understand how the
internals work. If nothing else, it's an interesting exercise to
document the internals for ourselves.

I'll try to get a tag set up later this week and put the beta.1 up for a vote.
~Darryl


On Sat, Oct 12, 2024 at 6:10 AM Bryan Ellis  wrote:
>
> +1
>
> I support the idea of providing a beta or release candidate for the
> upcoming major release.
>
> I've already started testing the potential beta release in one of my
> ongoing projects. A few third-party plugins will require updates, and I
> plan to submit PRs ahead of time to help them prepare for the release.
>
>
> On Fri, Oct 11, 2024 at 9:27 PM Norman Breau  wrote:
>
> > +1
> >
> > I can also test the beta when available against one of my projects and
> > report back on any issues
> > that I encounter. My projects are fairly large and makes use of good set
> > of plugins, both
> > from the public ecosystem and some private ones as well.
> >
> > I'm not sure if there already a list of breaking changes available, but
> > it would be nice
> > to have one for reference, which could probably be later reused for the
> > actual 8.0 release announcement.
> >
> > Cheers,
> > Norman
> >
> > On 2024-10-11 07:25, Niklas Merz wrote:
> > > +1
> > >
> > > I like the idea of doing a pre-release a lot in such case. Other Apache
> > > projects do release candidates (rc) shortly before their release but if
> > > we are still a bit away from the final release beta is a good name.
> > >
> > > On October 11, 2024, alexandre alves 
> > > wrote:
> > >> Hi
> > >>
> > >> I agree with the approach and would be able to test the beta version
> > >> with our current apps and plugins.
> > >>
> > >> Alexandre Alves
> > >> 
> > >> De: Darryl Pogue 
> > >> Enviado: 11 de outubro de 2024 08:14
> > >> Para: dev@cordova.apache.org 
> > >> Assunto: [DISCUSS] Making a cordova-ios 8.0.0-beta.1 release
> > >>
> > >> Hi folks,
> > >> There's been a lot[1] of refactoring and modernizing work for
> > >> cordova-ios recently, aiming to get us ready for the 8.0.0 major
> > >> version. Some of that includes deprecating old APIs to adopt more
> > >> modern conventions, and some of that includes breaking changes to the
> > >> generated Xcode project structure. I think (and really hope) that all
> > >> of the big breaking changes are done now.
> > >>
> > >> While there are still some bug fixes that I'm hoping we'll be able to
> > >> address[2], and possibly some new features, it feels like a good time
> > >> to get some initial testing of the breaking changes and deprecations,
> > >> particularly from plugin authors.
> > >>
> > >> To that end, I'm curious what people think about the idea of
> > >> publishing an 8.0.0-beta.1 version for testing.
> > >>
> > >> We would explicitly NOT mark it as latest on npm, so people would have
> > >> to opt in to it for testing, but we would make a post about it on the
> > >> blog with detailed notes for plugin authors about deprecations and
> > >> what might need to be updated in plugin code. Since this would be a
> > >> tagged release, it would need to go through the usual vetting and
> > >> voting process.
> > >>
> > >> I'm happy to start that process (and write the plugin migration guide)
> > >> if folks think this is worth doing.
> > >>
> > >> Thanks,
> > >> ~Darryl
> > >>
> > >> [1] https://github.com/apache/cordova-ios/compare/7.1.1...master
> > >> [2] https://github.com/apache/cordova-ios/milestone/12
> > >>
> > >> -
> > >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > >> For additional commands, e-mail: dev-h...@cordova.apache.org
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
> >

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[DISCUSS] Making a cordova-ios 8.0.0-beta.1 release

[Darryl Pogue]

Hi folks,
There's been a lot[1] of refactoring and modernizing work for
cordova-ios recently, aiming to get us ready for the 8.0.0 major
version. Some of that includes deprecating old APIs to adopt more
modern conventions, and some of that includes breaking changes to the
generated Xcode project structure. I think (and really hope) that all
of the big breaking changes are done now.

While there are still some bug fixes that I'm hoping we'll be able to
address[2], and possibly some new features, it feels like a good time
to get some initial testing of the breaking changes and deprecations,
particularly from plugin authors.

To that end, I'm curious what people think about the idea of
publishing an 8.0.0-beta.1 version for testing.

We would explicitly NOT mark it as latest on npm, so people would have
to opt in to it for testing, but we would make a post about it on the
blog with detailed notes for plugin authors about deprecations and
what might need to be updated in plugin code. Since this would be a
tagged release, it would need to go through the usual vetting and
voting process.

I'm happy to start that process (and write the plugin migration guide)
if folks think this is worth doing.

Thanks,
~Darryl

[1] https://github.com/apache/cordova-ios/compare/7.1.1...master
[2] https://github.com/apache/cordova-ios/milestone/12

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: Proposal for Cordova iOS 8 major version

[Darryl Pogue]

Following up on this, I've started submitting PR for various code cleanups
and refactorings. I'm trying to do multiple separate PRs so that things are
reviewable, but it's challenging when each change builds on the previous
ones.

The biggest change so far is to update the template project to use modern
Xcode conventions and Swift: https://github.com/apache/cordova-ios/pull/1457
Because it's such a significant change, I'd like to give folks time to take
a look at it and raise any concerns. My plan is to wait over the weekend
and (if no objections are raised) to merge it on Monday. Thanks to Bryan
for doing a bunch of testing of this with numerous plugins (both Apache
plugins, 3rd party plugins, and Cocoapod plugins) and uncovering several
additional fixes that were needed.

I expect to have a bunch of PRs submitted over the next week or two (in
addition to the ones I've already got open), so if you're interested in
reviewing please keep an eye out for them and comment with any questions or
concerns you have. We all use Cordova in different ways, and you might
notice something that I'm overlooking, so any feedback is really valuable
and appreciated.

Thanks,
~Darryl

On Tue, Jun 11, 2024 at 12:45 AM Darryl Pogue  wrote:

> Hi folks,
> Now that WWDC24's keynote is behind us (and we survived mostly unscathed),
> I wanted to present a proposal for some larger-scale breaking changes that
> I think would be good to try to accomplish in the next major version of
> Cordova-iOS.
>
> I've put together a proposal on the cordova-discuss repo to allow for easy
> commenting and feedback:
> https://github.com/apache/cordova-discuss/pull/113/files
>
> While several of these sound like bit items, the goal is to keep the
> actual impact of them as minimal as possible in terms of API breakage for
> plugins. Primarily, the goal is to modernize the template app to be more in
> line with current platform best practices, and to make CordovaLib a bit
> easier to work with. I expect I can have draft PRs for most of these
> changes fairly quickly if we decide to move ahead with them, but I would
> suggest we aim to do a release closer to September when iOS 18 officially
> launches (just in case any last-minute issues arise).
>
> There are definitely some other items on the wishlist for Cordova iOS 8,
> as found on the GitHub milestone:
> https://github.com/apache/cordova-ios/milestone/12
>
> I suspect a few other people might have additional (or parallel) ideas for
> Cordova iOS 8, so it would be good to get folks aligned on what we want to
> do moving forward.
>
> Thanks,
> ~Darryl
>

Proposal for Cordova iOS 8 major version

[Darryl Pogue]

Hi folks,
Now that WWDC24's keynote is behind us (and we survived mostly unscathed),
I wanted to present a proposal for some larger-scale breaking changes that
I think would be good to try to accomplish in the next major version of
Cordova-iOS.

I've put together a proposal on the cordova-discuss repo to allow for easy
commenting and feedback:
https://github.com/apache/cordova-discuss/pull/113/files

While several of these sound like bit items, the goal is to keep the actual
impact of them as minimal as possible in terms of API breakage for plugins.
Primarily, the goal is to modernize the template app to be more in line
with current platform best practices, and to make CordovaLib a bit easier
to work with. I expect I can have draft PRs for most of these changes
fairly quickly if we decide to move ahead with them, but I would suggest we
aim to do a release closer to September when iOS 18 officially launches
(just in case any last-minute issues arise).

There are definitely some other items on the wishlist for Cordova iOS 8, as
found on the GitHub milestone:
https://github.com/apache/cordova-ios/milestone/12

I suspect a few other people might have additional (or parallel) ideas for
Cordova iOS 8, so it would be good to get folks aligned on what we want to
do moving forward.

Thanks,
~Darryl

Re: [VOTE] Cordova User/Contributor survey

[Darryl Pogue]

I like this idea!
You might want to include a "Can we contact you for further questions?
" at the end, just in case there's really useful
feedback that we want to follow up on.

In the past I've seen companies use tools like SurveyMonkey and TypeForm
for this, but it might be worth seeing if we can use ASF's limesurvey
account.

~Darryl

On Fri, Nov 3, 2023 at 11:29 AM Niklas Merz  wrote:

> Sorry the text looked better in my client.
>
> Here is the Gist I use to write this with markdown:
> https://gist.github.com/NiklasMerz/9a06a373ac64ec417811e513cb5349d4
>
> On November 3, 2023, Niklas Merz  wrote:
> > Hey everyone,
> >
> > coming from the ASF conference "Community over Code" I got the idea of
> > starting a survey for Cordova users. Surveys can give an interesting
> > insight into what the users are actually doing with the project and
> > how
> > big or active the community is. What do you think about doing a small
> > survey to ask Cordova users about the project?
> >
> > There are a few details to figure out but I started with some
> > questions.
> > If you like or don' like the idea please respond to this email and we
> > can start working on the details of what and how to do this survey.
> >
> > If we agree to do that I think I would create a GitHub discussion,
> > repo
> > or PR to write the questions and think about the tool we use for the
> > survey.
> >
> > Ideas for questions:
> >
> >
> > # Cordova User Survey Questions ## Have you worked on an app using
> > Apache Cordova in the past 6 months [ ] Yes [ ] No ## Which platforms
> > do
> > you support? [ ] Android [ ] iOS [ ] Electron [ ] Browser [ ] Other ##
> > Have you migrated apps from Cordova to alternative solutions? If yes
> > what did you use? [ ] Capacitor [ ] Electron [ ] Flutter [ ] PWA [ ]
> > React-Native [ ] Native Development (Kotlin, Swift, Objective-C, Java)
> > [
> > ] Other (specify) ## Have you contributed to Cordovas platforms,
> > tooling
> > or Apache maintained plugins? [ ] Yes [ ] No [ ] Would love to ##
> > What's
> > holding you back from contributing? > See poll: https://us11.campaign-
> > archive.com/?e=ca69183c1b&u=9d7ced8c4bbd6c2f238673f0f&id=f07f659a95 [
> > ]
> > Time [ ] Imposter syndrome [ ] I need help getting started [ ]
> > Documentation [ ] Mentoring [ ] Other (specify) ## Have you worked on
> > third party plugins? [ ] Yes [ ] No # Do you want to share any
> > feedback
> > about third party plugins? Free text ## Which area of Apache Cordova
> > needs the most improvements? [ ] Core Tooling (cli) [ ] Platforms [ ]
> > Plugins [ ] Documenation ## What are your pain points? Free Text
>

Re: Apple privacy manifest

[Darryl Pogue]

On Sat, Oct 28, 2023 at 9:11 AM Jesse  wrote:
>
> I would expect this info to come from plugin.xml and config.xml. I haven’t 
> looked at Android innards in a long time, but doesn’t this just mirror their 
> intents? Play store tells users the capabilities of each app, and this is all 
> pulled together from the plugins ..

As Norman mentioned, this is sortof a new thing that Apple is
requiring and doesn't match well to any existing metadata being
provided.

I think we could use config.xml/plugin.xml to handle the declarations,
but it should be with new elements and a structure similar to the JSON
that Bryan is proposing, rather than using  or
 to inject directly into the plist.
That will require adding some new tag to act as a container for the
declarations, and tags for the declarations themselves (unless we want
to dump plist formatted data directly into config.xml, which seems
like it's maybe not the best structure).

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: Apple privacy manifest

[Darryl Pogue]

I looked into this a bit yesterday, and think there are a few ways we might
be able to handle this (none of them ideal).

For background, Apple is requiring apps to include a xcprivacy plist file
that has declarations about what privacy-impacting APIs they use (i.e.,
APIs that could be used for fingerprinting) and what data sharing and
tracking they do.
For apps that consume 3rd party SDKs, Apple is making it possible for the
SDK providers to embed their xcprivacy plist as part of a framework bundle.
Apps that use the framework will inherit the privacy declarations of their
SDK frameworks in addition to their own declarations.

Separately, but at the same time, Apple is introducing code signing to
framework bundles to help app developers better trust that their frameworks
came from trusted/consistent sources.


What does this mean for Cordova?


If we take the simplest interpretation: nothing. Cordova is not distributed
as a framework or SDK bundle, it is source code that's included in the app
(both CordovaLib and any installed plugins). Therefore, Cordova itself
technically doesn't need to provide any privacy plists and it's up to the
app developer to handle all the declarations based on how they're using
Cordova.

However, that kinda sucks for app developers, who might not know if a
particular plugin uses privacy-impacting APIs (such as NSUserDefaults, or
file system access). The problem for us is that because plugins are not
distributed as framework bundles, we cannot provide xcprivacy plist files
for each plugin and rely on Apple automatically merging them.


Suggestions for now
---

1. Add a blank PrivacyInfo.xcprivacy plist file to the Cordova iOS template
as a resource.

2. Add a (mostly blank, but accurate) PrivacyInfo.xcprivacy plist file to
CordovaLib as a resource, so that it's available for anyone consuming
CordovaLib from Swift Package Manager or as a framework (unclear to me how
this impacts Cocoapods...)

3. I guess our best option right now is to have plugins that need to make
declarations do so via  into the xcprivacy plist, which is
going to be super prone to conflicts if multiple plugins need to add the
same declarations :(


I really don't like the idea of relying on edit-config/config-file
injection behaviour to manage this plist, because it's almost guaranteed to
cause conflict issues when adding/removing plugins, but I don't have better
ideas at the moment. It doesn't seem feasible to change things such that
each plugin ends up as a framework bundle, since that would be a major
architectural change (although perhaps one that needs to happen?)


If we have specific questions for Apple where we need clarification or
recommendations, I can reach out to someone there and see if we can get any
help.

~Darryl

On Fri, Oct 27, 2023 at 8:28 AM Jesse  wrote:

> Has anyone looked at privacy manifests for iOS apps?
> …
> > > As you may know, in June, Apple announced new features to help users
> understand developers’ privacy and data collection and sharing practices.
> These new features include privacy manifests and signatures, which we
> encourage all third-party SDKs to adopt to provide transparency to users
> and help secure the software supply chain. Third-party SDKs that impact
> user privacy will be expected to include a privacy manifest and signature,
> and starting in Spring 2024, new and updated apps that include these
> third-party SDKs will need to include their manifest and signature to
> submit to the App Store
>
>

Re: How to add Cordova to an existing project progmatically for iOS

[Darryl Pogue]

Hi Mahendra,

This mailing list is primarily focused on development work of Cordova
itself, rather than user support. You might get more response posting on
the Cordova community GitHub Discussions:
https://github.com/apache/cordova/discussions

That said, embedding a Cordova WebView in an existing project is supported,
although not particularly well-documented.
There are some old docs here:
https://cordova.apache.org/docs/en/11.x/guide/platforms/ios/webview.html

One exciting new development is that CordovaLib in cordova-ios 7.0.0 is
available as a Swift Package, which should allow you to skip the steps
about Carthage and Cleaver and adding CordovaLib.xcodeproj as a subproject
to Xcode.
You can simply add "https://github.com/apache/cordova-ios.git"; in Xcode as
a package dependency, with a tag of "rel/7.0.0" to get the latest version.

Hope that helps to steer you in the right direction,
~Darryl

On Fri, Jul 14, 2023 at 11:11 AM Mahendra Liya 
wrote:

> Hello,
>
> I've an existing Swift Project which doesn't use Storyboard or XIBs. All
> the UI Screens are programmatically coded. Instead of adding a simple
> webview, I was inclined towards adding Cordova instead.
>
> I was wondering if it's documented anywhere (which I couldn't find though)
> if Cordova can be programmatically added to an existing Swift (not
> Objective-C though) project and if so, how please?
>
> I was wondering doing something like this:
>
> - Adding CordovaLib to the project and then
>
> *let* cordovaView = CDVViewController()
>
> // any other configuration / initialization that may be required for
> Cordova to work properly
>
> *self*.view.addSubview(cordovaView)
>
>
>
> Any advice or insights would be greatly appreciated.
>
> Cheers,
> Mahendra
>

Re: [VOTE} mailing list for logging github discussions

[Darryl Pogue]

I vote +1

On Fri, Jul 7, 2023 at 8:38 PM Jesse  wrote:

> Please review and vote by replying to this email, and keeping discussion on
> the [DISCUSS] thread. ( note: subject is changed )
> > [DISCUSS] Create new mailing list for logging github discussions
>
> This vote is to direct all github discussion generated email to
> iss...@cordova.apache.org, instead of the current setting which sends it
> all to the dev list.
>
> Upon a successful vote I will update infra settings to direct all github
> discussion activity to iss...@cordova.apache.org.
>
> Voting guidelines:
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
>
> Voting will go on for a minimum of 48 hours.
>
> ===
>
> I vote +1
>

Re: [VOTE] Cordova-IOS 6.3.0 Release

[Darryl Pogue]

I vote +1:

* Confirmed sigs & hashes with `coho verify-archive`
* Verified sha1s match tags with `coho verify-tags`
* Ran coho check-license to ensure all dependencies and
subdependencies have Apache-compatible licenses


On Thu, Apr 13, 2023 at 6:05 AM Norman Breau  wrote:
>
> I vote +1:
>
> * Verified Tags
> * Verified Archive
> * CI is red because 6.3.x branch & 6.3.0 tag is missing configs for codecov,
> however running local test on Mac, including the native objc tests runs
> fine.
> Because the issue is codecov, I don't see this as a blocker. In the
> future we should
> try to attempt to address these kind of issues prior to making a release
> however.
> * NPM Audit returns ok
>
> On 2023-04-13 7:23 a.m., Niklas Merz wrote:
> > As discussed this could be a stopgap release and give us some time to
> > prepare the next major. If this gets not enough positive votes the
> > release will be skipped and we can do the major directly.
> >
> > Please review and vote on this 6.3.0 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/ios630/
> >
> > The package was published from its corresponding git tag:
> > cordova-ios: 6.3.0 (584699ae1e)
> >
> > Note that you can test it out via:
> >
> >  cordova platform add https://github.com/apache/cordova-ios#6.3.0
> >
> > Upon a successful vote I will upload the archive to dist/, publish it to
> > npm, and post the blog post: https://github.com/apache/cordova-
> > docs/pull/1295
> >
> > Voting guidelines: https://github.com/apache/cordova-
> > coho/blob/master/docs/release-voting.md
> >
> > Voting will go on for a minimum of 48 hours.
> >
> > I vote +1:
> > * Ran coho audit-license-headers over the relevant repos
> > * Ran coho check-license to ensure all dependencies and subdependencies
> > have Apache-compatible licenses
> > * Ran tests locally (linux)
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [DISCUSS] cordova-ios patch release

[Darryl Pogue]

On Tue, Apr 11, 2023 at 10:08 AM Norman Breau  wrote:
>
> I also want to point out (as we ran into issues cherry-picking and
> testing locally against our apps)
> that dpogue's PR for NodeJS 18 support won't be cherry-picked easily as
> the function
> being changed has been renamed at
> https://github.com/apache/cordova-ios/commit/21983197042908dff4cd49b00728b0c1d6703322

The function name changed, but the implementation didn't, so
backporting it manually shouldn't be an issue.

If the PR gets accepted to master, I'm happy to do the backport to 6.x.

> So it might be easier to cut off NodeJS 18 support off in
> cordova-ios@6.x (We have never claimed support for it anyway)
> and officially support NodeJS starting in cordova-ios@7

My concern here is just that node 18 is already LTS, and it feels like
we'd be under increased pressure to get 7.0.0 out the door just to fix
this particular bug.

Which is to say, I'm +1 on including both of the fixes in a 6.x
release in the near future.

~Darryl

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: Using npmrc

[Darryl Pogue]

+1 from me

On Sat, Sep 11, 2021 at 6:16 PM Norman Breau  wrote:

> Hi all,
>
> I propose that we start adding a .npmrc file to all of our repos. We
> only need one setting configured: registry=https://registry.npmjs.org
>
> https://registry.npmjs.org is the default value, but this will ensure
> that while in cordova repos, NPM will use the official NPM registry. For
> some people who have different environments (like me...), it's easy to
> run into situations such as
> https://github.com/apache/cordova-lib/pull/879#pullrequestreview-751998001
> (Thanks Nik for thoroughly review, even for something that seemed to
> simple!).
>
> This is a simple proposal, but I wanted to ensure the community had no
> objections before I start forking and making PRs on all the repos.
>
> Cheers!
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

Re: [DISCUSS] Moving forward with the WebView on AndroidX and cordova-android 10

[Darryl Pogue]

To counter a bit, all of my apps are using the standard Cordova
Android WebView, and store all their data in the browser's indexedDB.
I've had no issues with file URLs (although I expect that will change
with API 30 enforcement).

Losing data in an app update is unacceptable, and for many apps it
would be catastrophic (see comments from when Google did a bad
indexedDB migration and people lost data[1]). On iOS with WKWebView,
I'm stuck in the position of continuing to use file URLs to keep
existing data working because there's no supported path for data
migration to the new scheme.

We made the decision with Cordova iOS to use file URLs by default to
ensure that we didn't unexpectedly break existing apps.

We either need to default to using file URLs on Android (which is
risky considering the API 30 enforcement is restricting what works
there), or provide an officially supported update path that preserves
and migrates all the relevant data. (If we opt for the migration path,
it would be nice to have it support iOS as well.)

If we release a Cordova update that causes a bunch of existing Android
apps to lose all their data, it will very likely be a public image
disaster from which we will never recover.

[1] https://bugs.chromium.org/p/chromium/issues/detail?id=1033655

On Tue, Apr 27, 2021 at 8:48 AM Bryan Ellis  wrote:
>
> I also agree.
>
> I think we should move forward with these changes and use the 
> WebViewAssetLoader by default.
>
> If must, we could write a blog post explaining how to use Norman's plugin for 
> data migration. But I do not know if the plugin is complete to cover all data 
> sources and fits this case.
>
> I believe the change though is necessary.
>
> Starting from API 30, Google has disabled file access to the WebView because 
> it introduces possible security risks.
>
>  > Apps should not open file:// URLs from any external source in WebView, 
> don't enable this if your app accepts arbitrary URLs from external sources.
>
> In our recent release of Cordova-Android, we explicitly set the 
> `setAllowFileAccess` to `true` to get around the change that came in the API 
> 30 release. This allowed apps to continue working temporarily, while we would 
> introduce a proper solution in this coming major release, preferably 
> following a secure implementation. I believe we should not default to 
> something that has been publicly announced and known to lead to potential 
> security risks.
>
> If we want to support the file scheme to allow users to avoid data loss, I 
> think a config.xml flag can be introduced that users can manually set if they 
> are willing to accept the potential security risks that exist with it. And it 
> could allow them to move over whenever they decide.
>
>
>
> > On Apr 27, 2021, at 9:07 PM, julio cesar sanchez  
> > wrote:
> >
> > I would vote for defaulting to WebViewAssetLoader but still allow using
> > file:// from a config.xml preference for the people that are not ready to
> > move on.
> > But on cordova-ios 6 I think we ended up defaulting to file:// and use the
> > schemes only as opt-in.
> >
> > About migrating data, I don't think that's our job, but we can point users
> > to plugins if you know some.
> >
> > El mar, 27 abr 2021 a las 8:03, Niklas Apache ()
> > escribió:
> >
> >> Hey folks,
> >>
> >> we recently merged a PR [1] which significantly changes how cordova-
> >> android loads web content in the webview and now need to decide how to
> >> move proceed.
> >>
> >> Google introduced the WebViewAssetLoader to make it possible to use web
> >> content from a standard http(s) scheme instead of file:. This was done
> >> to remove security risks [2] and some apps with routing frameworks like
> >> React and Angular need this for proper routing.
> >>
> >> Because cordova-android 10 now uses AndroidX we could implement the
> >> WebViewAssetLoader and remove some deprecated or security related
> >> WebSettings and move the platform forward to current Android standards.
> >>
> >> This change may break some apps now because the origin changes if the
> >> app now runs on https://localhost for example instead of file://.
> >> Changing the origin means losing access to web storage like
> >> localstorage, indexedb etc. First and foremost we need to announce that
> >> change with the release for developers to act but additionally we could
> >> do:
> >>
> >> 1.) Default back to file:// and make the WebViewAssetLoader opt-in via
> >> config.xml. This exposes apps to the security risk:
> >>
> >>> Note: Apps should not open file:// URLs from any external source in
> >> WebView, don't enable this if your app accepts arbitrary URLs from
> >> external sources. It's recommended to always use
> >> androidx.webkit.WebViewAssetLoader
> >> <
> >> https://developer.android.com/reference/androidx/webkit/WebViewAssetLoader
> >>>
> >> to access files including assets and resources over http(s):// schemes,
> >> instead of file:// URLs. To prevent possible security issues targeting

Re: [VOTE] Deprecate cordova-plugin-wkwebview-engine

[Darryl Pogue]

+1

On Fri, Feb 5, 2021 at 8:54 PM Bryan Ellis  wrote:
>
> +1
>
> On Sat, Feb 6, 2021 at 1:21 PM Jesse  wrote:
>
> > +1
> >
> > > On Feb 5, 2021, at 5:49 PM, Norman Breau  wrote:
> > >
> > > Now that the wkwebview engine plugin is published on NPM, pending
> > announcement (waiting for cordova.apache.org to update with the blog
> > post). I would like to set motion a vote to deprecate this package.
> > >
> > > The reason for deprecation is the plugin's code base has effectively
> > been moved to the core cordova-ios platform, making the plugin deprecated.
> > >
> > > Upon a successful vote to deprecate this plugin, I'll prepare a PR
> > adding deprecation text to the plugin's readme as well as marking the NPM
> > package as deprecated.
> > >
> > > I vote +1.
> > >
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > For additional commands, e-mail: dev-h...@cordova.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
> >

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[ANNOUNCEMENT] cordova-fetch 3.0.1 released!

[Darryl Pogue]

cordova-fetch@3.0.1 has been released and published to npm. This primarily
addresses compatibility issues with the new npm v7 update.

You can view the release blog post at
https://cordova.apache.org/announcements/2021/02/02/cordova-fetch-3.0.1.html

Re: [VOTE] cordova-fetch 3.0.1 release (attempt 2)

[Darryl Pogue]

The vote has now closed. The results are:

Positive Binding Votes: 3

Darryl Pogue
Niklas Merz
Norman Breau

Negative Binding Votes: 0

The vote has passed.

Thanks for voting!
~Darryl


On Wed, Feb 3, 2021 at 6:28 PM Norman Breau  wrote:
>
> +1
>
> * Verify-tags using coho
> * verify-archive using coho
> * Ran npm test successfully with both NPM 6 & NPM 7.
>
> On 2021-02-03 3:03 a.m., Darryl Pogue wrote:
> > Hi folks,
> >
> > Please review and vote on this cordova-fetch release by replying to
> > this email (and keep discussion on the DISCUSS thread).
> >
> > The initial vote was cancelled because coho uploaded the wrong
> > archives to dist/dev, this is a second vote with the correct artifacts
> > uploaded. I don't think I need to bump the version since the issue was
> > entirely at the archive uploading step, not a problem with the tag
> > itself.
> >
> > Release candidate has been published to dist/dev:
> > https://dist.apache.org/repos/dist/dev/cordova/cordova-fetch-3.0.1/
> >
> > The packages were published from their corresponding git tags:
> >  cordova-fetch: draft/3.0.1 (d374bb39ba)
> >
> > Blog announcement draft post:
> > https://github.com/apache/cordova-docs/pull/1155
> >
> >
> > Upon a successful vote I will upload the archives to dist/, publish
> > them to npm, and post the corresponding blog post.
> >
> > Voting guidelines:
> > https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
> >
> > Voting will go on for a minimum of 48 hours.
> >
> > I vote +1:
> > * Ran coho audit-license-headers over the relevant repos
> > * Ran coho check-license to ensure all dependencies and
> > sub-dependencies have Apache-compatible licenses
> > * Ensured continuous build was green when repos were tagged
> >
> > Thanks,
> > ~Darryl
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [VOTE] cordova-plugin-wkwebview-engine@1.2.2 Patch Release

[Darryl Pogue]

+1

* Confirmed sigs & hashes with `coho verify-archive`
* Verified shas match tags with `coho verify-tags`
* Checked licenses and headers


On Tue, Feb 2, 2021 at 11:20 PM Niklas Merz  wrote:
>
> I vote +1
>
> I did:
>
> * Confirmed sigs & hashes with `coho verify-archive`
> * Verified shas match tags with `coho verify-tags`
> * Checked licenses and headers
> * Checked package content briefly
>
> February 3, 2021 4:23 AM, "Norman Breau"  wrote:
>
> > Please review and vote on the release of this plugins release
> > by replying to this email (and keep discussion on the DISCUSS thread)
> >
> > The plugins have been published to dist/dev:
> > https://dist.apache.org/repos/dist/dev/cordova/cordova-plugin-wkwebview-engine-1.2.2
> >
> > The packages were published from their corresponding git tags:
> > cordova-plugin-wkwebview-engine: 1.2.2 (dae003a324)
> >
> > Upon a successful vote I will upload the archives to dist/, upload them to 
> > npm, and post the
> > corresponding blog post.
> >
> > Voting guidelines: 
> > https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
> > How to vote on a plugins release at
> > https://github.com/apache/cordova-coho/blob/master/docs/plugins-release-process.md#voting
> >
> > Voting will go on for a minimum of 48 hours.
> >
> > I vote +1:
> > * Ran coho audit-license-headers over the relevant repos
> > * Ran coho check-license to ensure all dependencies and subdependencies 
> > have Apache-compatible
> > licenses
> > * Ensured continuous build was green when repos were tagged. Note that 
> > Mobilespecs fails because it
> > installs cordova-ios@6, which is incompatible with this plugin (hence this 
> > release).
> > * Ran `npm test` to ensure all tests passes when ran on cordova-ios@5.1.1 
> > platform.
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [VOTE] cordova-ios 6.2.0 Release

[Darryl Pogue]

+1

* Confirmed sigs & hashes with `coho verify-archive`
* Verified sha1s match tags with `coho verify-tags`
* Verified tests pass

On Mon, Feb 1, 2021 at 10:24 AM Niklas Merz  wrote:
>
> Sending again and hopefully now the line breaks work.
>
> Please review and vote on this 6.2.0 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/cordova-ios-6.2.0/
>
> The package was published from its corresponding git tag:
> cordova-ios: 6.2.0 (87c6d53a39)
>
> Note that you can test it out via:
>
> cordova platform add https://github.com/apache/cordova-ios#6.2.0
>
> Upon a successful vote I will upload the archive to dist/, publish it to
> npm, and post the blog post.
>
> Voting guidelines:
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
>
> Please also review the blog post for this release:
> https://github.com/apache/cordova-docs/pull/1151
>
> Voting will go on for a minimum of 48 hours.
>
> I vote +1:
> * Ran coho audit-license-headers over the relevant repos
> * Ran coho check-license to ensure all dependencies and subdependencies
> have Apache-compatible licenses
> * Ensured continuous build was green when repo was tagged
> * Ran ios and lib unit tests successfully
> * Ran builds with new project and bin scripts
>
> Am 01.02.21 um 19:21 schrieb Niklas Merz:
> > |Please review and vote on this 6.2.0 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/cordova-ios-6.2.0/ The
> > package was published from its corresponding git tag: cordova-ios: 6.2.0
> > (87c6d53a39) Note that you can test it out via: cordova platform add
> > https://github.com/apache/cordova-ios#6.2.0 Upon a successful vote I
> > will upload the archive to dist/, publish it to npm, and post the blog
> > post. Voting guidelines:
> > https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
> > Please also review the blog post for this release:
> > https://github.com/apache/cordova-docs/pull/1151 Voting will go on for a
> > minimum of 48 hours. I vote +1: * Ran coho audit-license-headers over
> > the relevant repos * Ran coho check-license to ensure all dependencies
> > and subdependencies have Apache-compatible licenses * Ensured continuous
> > build was green when repo was tagged * Ran ios and lib unit tests
> > successfully * Ran builds with new project and bin scripts|
> >
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[VOTE] cordova-fetch 3.0.1 release (attempt 2)

[Darryl Pogue]

Hi folks,

Please review and vote on this cordova-fetch release by replying to
this email (and keep discussion on the DISCUSS thread).

The initial vote was cancelled because coho uploaded the wrong
archives to dist/dev, this is a second vote with the correct artifacts
uploaded. I don't think I need to bump the version since the issue was
entirely at the archive uploading step, not a problem with the tag
itself.

Release candidate has been published to dist/dev:
https://dist.apache.org/repos/dist/dev/cordova/cordova-fetch-3.0.1/

The packages were published from their corresponding git tags:
cordova-fetch: draft/3.0.1 (d374bb39ba)

Blog announcement draft post:
https://github.com/apache/cordova-docs/pull/1155


Upon a successful vote I will upload the archives to dist/, publish
them to npm, and post the corresponding blog post.

Voting guidelines:
https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md

Voting will go on for a minimum of 48 hours.

I vote +1:
* Ran coho audit-license-headers over the relevant repos
* Ran coho check-license to ensure all dependencies and
sub-dependencies have Apache-compatible licenses
* Ensured continuous build was green when repos were tagged

Thanks,
~Darryl

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [VOTE] cordova-fetch 3.0.1 release

[Darryl Pogue]

Looks like `coho create-archive` isn't compatible with the
`draft/3.0.1` tag format and bundled up 3.0.0 instead :(

I'm now voting -1 and will make a 3.0.2 RC tomorrow.

On Tue, Feb 2, 2021 at 9:13 PM Darryl Pogue  wrote:
>
> Hi folks,
>
> Please review and vote on this cordova-fetch release by replying to
> this email (and keep discussion on the DISCUSS thread).
>
> Release candidate has been published to dist/dev:
> https://dist.apache.org/repos/dist/dev/cordova/cordova-fetch-3.0.1/
>
> The packages were published from their corresponding git tags:
> cordova-fetch: draft/3.0.1 (d374bb39ba)
>
> Blog announcement draft post:
> https://github.com/apache/cordova-docs/pull/1155
>
>
> Upon a successful vote I will upload the archives to dist/, publish
> them to npm, and post the corresponding blog post.
>
> Voting guidelines:
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
>
> Voting will go on for a minimum of 48 hours.
>
> I vote +1:
> * Ran coho audit-license-headers over the relevant repos
> * Ran coho check-license to ensure all dependencies and
> sub-dependencies have Apache-compatible licenses
> * Ensured continuous build was green when repos were tagged
>
> Thanks,
> ~Darryl

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[VOTE] cordova-fetch 3.0.1 release

[Darryl Pogue]

Hi folks,

Please review and vote on this cordova-fetch release by replying to
this email (and keep discussion on the DISCUSS thread).

Release candidate has been published to dist/dev:
https://dist.apache.org/repos/dist/dev/cordova/cordova-fetch-3.0.1/

The packages were published from their corresponding git tags:
cordova-fetch: draft/3.0.1 (d374bb39ba)

Blog announcement draft post:
https://github.com/apache/cordova-docs/pull/1155


Upon a successful vote I will upload the archives to dist/, publish
them to npm, and post the corresponding blog post.

Voting guidelines:
https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md

Voting will go on for a minimum of 48 hours.

I vote +1:
* Ran coho audit-license-headers over the relevant repos
* Ran coho check-license to ensure all dependencies and
sub-dependencies have Apache-compatible licenses
* Ensured continuous build was green when repos were tagged

Thanks,
~Darryl

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[DISCUSS] cordova-fetch 3.0.1 patch release

[Darryl Pogue]

Hey folks,

So npm v7 has hit general availability, and is now the default version of
npm[1]. This is a slight problem for us because the current version of
cordova-fetch is not compatible with npm v7.
Raphael made a pull request to change how cordova-fetch handles
installation[2], which has been merged but not yet released.

Any objections to getting a release of cordova-fetch going?

I think this qualifies as a patch release, but I'd be fine doing a minor if
that's what people prefer.

~Darryl

1. https://github.blog/2021-02-02-npm-7-is-now-generally-available/
2. https://github.com/apache/cordova-fetch/pull/91

Re: [Discuss] Cordova Hangout NewEra#2

[Darryl Pogue]

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
input/corrections from Jesse about historical decisions.

~Darryl

On Wed, Sep 16, 2020 at 1:38 AM Jesse  wrote:
>
> 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
> more than decision making so no one should feel left out, or obligated to
> attend.
>
> That said, we haven't got a lot of time before Thursday morning ... ~30
> hours, and I would like us to have some defined discussion points, ideally
> brought up by people who would like to present them.
>
> How does everyone feel about going ahead with the hangout this week? We
> could also push back a week.
> Who has a topic they would like to present for discussion?
>
> Cheers,
>   Jesse

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[ANNOUNCEMENT] Cordova iOS 6.1.1 released

[Darryl Pogue]

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: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [VOTE] Cordova-iOS 6.1.1 Release

[Darryl Pogue]

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 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 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/
> >
> > The package was published from its corresponding git tag (draft/6.1.1):
> > cordova-ios: 6.1.1 (3ba64485f3)
> >
> > Note that you can test it out via:
> > cordova platform add github:apache/cordova-ios#draft/6.1.1
> >
> > Upon a successful vote I will upload the archive to dist/, publish it
> > to npm, and post the blog post.
> >
> > Voting guidelines:
> > https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
> >
> > Voting will go on for a minimum of 48 hours.
> >
> > I vote +1:
> > * Updated dependencies and verified no npm audit warnings
> > * Ran npm tests locally and confirmed passing
> > * Ran coho audit-license-headers over the relevant repos
> > * Ran coho check-license to ensure all dependencies and
> > subdependencies have Apache-compatible licenses
> > * Ensured continuous build was green when repo was tagged
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
>

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

FYI: Nightly builds moved to GitHub Actions

[Darryl Pogue]

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 Cordova-Coho repo:
https://github.com/apache/cordova-coho/blob/master/.github/workflows/nightly.yml

Thanks Bryan for porting Jenkins scripts to GitHub yml and making it
more accessible and probably more reliable.

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[VOTE] Cordova-iOS 6.1.1 Release

[Darryl Pogue]

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/

The package was published from its corresponding git tag (draft/6.1.1):
cordova-ios: 6.1.1 (3ba64485f3)

Note that you can test it out via:
cordova platform add github:apache/cordova-ios#draft/6.1.1

Upon a successful vote I will upload the archive to dist/, publish it
to npm, and post the blog post.

Voting guidelines:
https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md

Voting will go on for a minimum of 48 hours.

I vote +1:
* Updated dependencies and verified no npm audit warnings
* Ran npm tests locally and confirmed passing
* Ran coho audit-license-headers over the relevant repos
* Ran coho check-license to ensure all dependencies and
subdependencies have Apache-compatible licenses
* Ensured continuous build was green when repo was tagged

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[DISCUSS] cordova-ios 6.1.1 patch release

[Darryl Pogue]

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
patch version to fix running on devices.

~Darryl

Re: Formally deprecate cordova-plugin-wkwebview-engine?

[Darryl Pogue]

I don't know that we want to go as far as deprecating it just yet, but
we should definitely do a release that prevents it from being
installed with cordova-ios 6 (since it conflicts).

On Fri, Jul 3, 2020 at 10:50 AM Chris Brody  wrote:
>
> It would definitely be nice if we don't have to support that plugin any
> longer, and I think it would be good to archive it as well. My one comment
> is that there should be a very clear guide for people who have to continue
> using the same scheme due to data stored by the web view. A couple of
> off-topic items that I think are related:
>
> I think we should recommend that people consider using native plugins such
> as cordova-plugin-file, SQLite, or something similar for storing important
> data.. I have seen quite a few things such as local storage deleting data,
> IndexedDB eviction, and other things going wrong to trust the WebView to
> not lose data.
>
> I think we should deprecate and archive some other plugins in the near
> future, due to the support burden, as I proposed in:
> https://github.com/apache/cordova/issues/185
>
>
> On Fri, Jul 3, 2020 at 1:28 PM Norman Breau  wrote:
>
> > Hi team,
> >
> > I believe previously we decided on a path to deprecate
> > cordova-plugin-wkwebview-engine, but I wanted
> > to make sure that is still our stance.
> >
> > cordova-ios@6 supports both url schemes and the legacy file scheme,
> > effectively making the wkwebview engine plugin redundant. Now that
> > cordova-ios@6 is released, I feel like it's time to formally deprecate
> > the wkwebview plugin according to our Deprecation Policy[1]
> >
> > With that being said, I'm not sure if we also want to archive this
> > repository. According to the policy, we should archive if:
> >
> > "A deprecated repository might also be archived if we don't intend to
> > provide support of any kind (Issues, Pull Requests, Releases) for this
> > component any more."
> >
> > I feel like this is probably our intention as I think all maintenance
> > will now be done in cordova-ios going forward, but I want to gather some
> > thoughts on this.
> >
> > [1] https://cordova.apache.org/deprecation_policy.html
> >
> > Cheers,
> > Norman
> >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
> >

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[ANNOUNCEMENT] Cordova iOS 6.1.0 Release

[Darryl Pogue]

Cordova-iOS@6.1.0 has been released.

Blog post:
https://cordova.apache.org/announcements/2020/06/23/cordova-ios-6.1.0.html

Thanks to Bryan Ellis, it has been published to CocoaPods as well!

Re: [VOTE] Cordova-iOS 6.1.0 Release

[Darryl Pogue]

The vote has now closed. The results are:

Positive Binding Votes: 4
- Darryl Pogue
- Niklas Merz
- Ken Naito
- Bryan Ellis

Negative Binding Votes: 0

The vote has passed.

Thanks everyone who reviewed and voted!
~Darryl

On Mon, Jun 22, 2020 at 12:33 AM Darryl Pogue  wrote:

> Please review and vote on this 6.1.0 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/ios-610/
>
> The package was published from its corresponding git tag:
> cordova-ios: 6.1.0 (c75ff4adbc)
>
> Note that you can test it out via:
> cordova platform add https://github.com/apache/cordova-ios#6.1.0
>
> Upon a successful vote I will upload the archive to dist/, publish it
> to npm, and post the blog post.
> (Blog post PR to come in the morning)
>
> Voting guidelines:
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
>
> Voting will go on for a minimum of 48 hours.
>
> I vote +1:
> * Ran coho audit-license-headers over the relevant repos
> * Ran coho check-license to ensure all dependencies and
> subdependencies have Apache-compatible licenses
> * Ensured continuous build was green when repo was tagged
> * Ensured npm tests passed locally after tagging
> * Ensured a local app generated with Cordova CLI ran in the simulator
> * Ensured a local app generated with the bin tools ran in the simulator
>

Re: [DISCUSS] Cordova OSX Major Release 6.0.0

[Darryl Pogue]

I think the best path forward for Cordova apps on macOS is either
through cordova-ios with Catalyst, or through cordova-electron.

Most plugins don't support the osx platform, but do have
implementations for iOS, so Catalyst is probably the best choice from
an ecosystem perspective for most people. It will also come pretty
close to guaranteeing support for the new Apple Silicon platform.

IMO once we have support for Catalyst in cordova-ios, we should look
to deprecate cordova-osx.

~Darryl

On Tue, Jun 23, 2020 at 1:31 PM Chris Brody  wrote:
>
> Thanks to Niklas for taking care of the release. You should see my +1 vote
> so it should be good to go now. Definitely not worth blocking the release,
> especially on a platform with such low relevance.
>
> I do actually use cordova-osx as a quick way to test my SQLite plugin work
> before going through testing on iOS simulator & device.
>
> Moving forward, an idea could be to make a new cordova-mac or cordova-macos
> platform as a fork off of cordova-ios, maybe even as an unofficial
> platform. This would be a similar idea to how they have "out-of-tree"
> platforms for Windows, macOS, etc. on React Native.
>
> In terms of changing the CPU, I suspect that should be at worse a
> "breaking" build change that would affect Xcode projects and libraries. But
> yeah, definitely good to note.
>
>
> On Tue, Jun 23, 2020 at 3:28 PM Niklas Merz  wrote:
>
> > I didn't even realize that because I just followed the guide and used
> > coho, but yes this is kind of confusing. We may consider fixing coho or
> > the docs to avoid that for future releases.
> >
> > Personally I don't think that is this big of a deal and should block the
> > release.
> >
> > If we could some get some votes, we can get the release done and maybe
> > start the discussion of the future of the OSX platform.
> >
> > Just some random thoughts, but maybe this is better done in another
> > DISCUSS.
> >
> > * cordova-osx seems to be quite irrelevant to me.
> > * there are plans of bringing Catalys to live in cordova-ios which would
> > make cordova-ios apps run on Mac
> > * Apple renamed OSX to macOS again and we still have the old name
> > * Apple announced the switch from Intel based Macs to ARM based Macs
> > just yesterday. What does that mean for the platform? Just update to
> > project with Xcode?
> >
> > Am 23.06.20 um 16:51 schrieb Chris Brody:
> > > I was a bit surprised to see that the major cordova-osx 6.0.0 release tag
> > > was made outside of the master branch.
> > >
> > > This has happened before, as discussed in:
> > > https://github.com/apache/cordova-coho/issues/227
> > >
> > > I hope we can find a way to improve this in the near future.
> > >
> > > On Fri, Jun 12, 2020 at 12:59 PM Niklas Merz 
> > wrote:
> > >
> > >>
> > >> Does anyone have any reason to delay a cordova-osx platform release?
> > >> Any outstanding patches to land?
> > >>
> > >> If not, I will start the release soon after checking the remaining PRs.
> > >> We should get the platforms ready for the new Cordova CLI release and
> > >> NodeJS version deprecations.
> > >>
> > >> -
> > >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > >> For additional commands, e-mail: dev-h...@cordova.apache.org
> > >>
> > >>
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
> >

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[VOTE] Cordova-iOS 6.1.0 Release

[Darryl Pogue]

Please review and vote on this 6.1.0 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/ios-610/

The package was published from its corresponding git tag:
cordova-ios: 6.1.0 (c75ff4adbc)

Note that you can test it out via:
cordova platform add https://github.com/apache/cordova-ios#6.1.0

Upon a successful vote I will upload the archive to dist/, publish it
to npm, and post the blog post.
(Blog post PR to come in the morning)

Voting guidelines:
https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md

Voting will go on for a minimum of 48 hours.

I vote +1:
* Ran coho audit-license-headers over the relevant repos
* Ran coho check-license to ensure all dependencies and
subdependencies have Apache-compatible licenses
* Ensured continuous build was green when repo was tagged
* Ensured npm tests passed locally after tagging
* Ensured a local app generated with Cordova CLI ran in the simulator
* Ensured a local app generated with the bin tools ran in the simulator

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[DISCUSS] Cordova-iOS minor release

[Darryl Pogue]

Hi folks,

Does anyone have a reason to delay a minor release of Cordova-iOS?
List of changes since 6.0.0:
https://github.com/apache/cordova-ios/milestone/7?closed=1

2 of the merged pull requests add new preferences to configure behaviour,
which is why I'm thinking it should be a minor update rather than a patch
update.

The important bits are the fixes around SplashScreens (which have several
poorly handled edge cases in 6.0.0), and hopefully being able to publish
6.1.0 to Cocoapods.

~Darryl

Re: Modernize cordova-android build?

[Darryl Pogue]

On Sun, Jun 7, 2020 at 7:49 PM Chris Brody  wrote:
>
> Another thing is that many build systems are now using a Gradle wrapper,
> while Cordova still needs the Gradle tool to be installed in its search
> path. This may be related to a nasty-looking issue here:
> https://github.com/apache/cordova-android/issues/845

I seem to recall that we have to use the system-installed gradle to
generate our gradle wrapper, because the wrapper depends on a JAR file
and we're not allowed to distribute JAR files.

Previous mailing list discussion regarding gradle wrapper distribution:
https://lists.apache.org/thread.html/9fcaf3cd6b22e9cd6d09e17ff5956bf661c3560be923f734dcc4450e%401403096149%40%3Cdev.cordova.apache.org%3E

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: Strongly deprecating the FileTransfer plugin

[Darryl Pogue]

Not that we want to outright endorse 3rd party plugins without due
diligence, but there are other options than the FileTransfer plugin, such
as https://www.npmjs.com/package/cordova-plugin-advanced-http

On Wed, Jun 3, 2020 at 1:46 PM Tim Brust  wrote:

> While I agree that we should somehow archive old code, I'm still -1 on a
> deprecation of this plugin. (We've had some discussion about it here, too:
> https://github.com/apache/cordova/issues/185)
> XHR is not reliable and causes OOM errors when handling large data.
>
>
>
> On Wed, Jun 3, 2020 at 7:29 PM Norman Breau 
> wrote:
>
> > +1 on archiving/adding  [DEPRECATED] text in the description.
> >
> > On 2020-06-03 4:25 p.m., julio cesar sanchez wrote:
> > > This happens with all the deprecated plugins we have, people keeps
> > > reporting issues on them.
> > > I proposed long ago to archive them, but some people was against it,
> but
> > I
> > > think archiving is the way to go when something is deprecated.
> > >
> > >
> > > El miércoles, 3 de junio de 2020, Jesse 
> > escribió:
> > >
> > >> +1 The deprecation notice needs to be prominent, I missed it myself
> on a
> > >> quick scroll.
> > >> Some of that readme is in a specific format to support appearance in
> > >> docs.cordova.io ( similar to
> > >> https://cordova.apache.org/docs/en/latest/reference/
> > >> cordova-plugin-file/index.html
> > >>   )
> > >> This is no longer a requirement, so we can go prominent.
> > >> We should also ask INFRA to put the text [DEPRECATED] in the
> > description,
> > >> and possibly even archive the repo.
> > >>
> > >>
> > >> On Wed, Jun 3, 2020 at 12:02 PM Norman Breau 
> > >> wrote:
> > >>
> > >>> I'm sure you're not the only one who misses it, considering the repo
> is
> > >>> still pretty active in terms of new issues being reported.
> > >>>
> > >>> On 2020-06-03 3:59 p.m., Darryl Pogue wrote:
> > >>>> Correction: There is in fact a deprecation notice, part-way down the
> > >>>> README, but it's not especially attention grabbing and I missed it
> the
> > >>>> first 2 times I skimmed the file.
> > >>>>
> > >>>> On Wed, Jun 3, 2020 at 11:55 AM Darryl Pogue 
> > wrote:
> > >>>>
> > >>>>> Hey folks,
> > >>>>>
> > >>>>> The File Transfer plugin has been officially deprecated since 2017:
> > >>>>>
> > >>> https://cordova.apache.org/blog/2017/10/18/from-
> > >> filetransfer-to-xhr2.html
> > >>>>> However, the repo and npm have no link to that page or any sort of
> > >>>>> indication that it is not maintained.
> > >>>>>
> > >>>>> With the release of cordova-ios 6, the FileTransfer plugin no
> longer
> > >>>>> compiles on iOS:
> > >>>>> https://github.com/apache/cordova-plugin-file-transfer/issues/258
> > >>>>>
> > >>>>> I want to reply to that issue saying that it's deprecated and not
> > >>>>> maintained, but I feel like we haven't made that very clear.
> > >>>>>
> > >>>>> I would like to propose that we update the README for File Transfer
> > >>> with a
> > >>>>> clear deprecation notice which links to the blog post from 2017,
> and
> > >>> that
> > >>>>> we ask ASF Infra to mark the repo as archived.
> > >>>>>
> > >>>>> Any objections?
> > >>>>>
> > >>>>> ~Darryl
> > >>>>>
> > >>> -
> > >>> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > >>> For additional commands, e-mail: dev-h...@cordova.apache.org
> > >>>
> > >>>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
> >
>
> --
> Tim Brust
> timbrust3...@gmail.com
>
> M: +49 160 9757 3632 <+4916097573632>
>

Re: Strongly deprecating the FileTransfer plugin

[Darryl Pogue]

Correction: There is in fact a deprecation notice, part-way down the
README, but it's not especially attention grabbing and I missed it the
first 2 times I skimmed the file.

On Wed, Jun 3, 2020 at 11:55 AM Darryl Pogue  wrote:

> Hey folks,
>
> The File Transfer plugin has been officially deprecated since 2017:
> https://cordova.apache.org/blog/2017/10/18/from-filetransfer-to-xhr2.html
>
> However, the repo and npm have no link to that page or any sort of
> indication that it is not maintained.
>
> With the release of cordova-ios 6, the FileTransfer plugin no longer
> compiles on iOS:
> https://github.com/apache/cordova-plugin-file-transfer/issues/258
>
> I want to reply to that issue saying that it's deprecated and not
> maintained, but I feel like we haven't made that very clear.
>
> I would like to propose that we update the README for File Transfer with a
> clear deprecation notice which links to the blog post from 2017, and that
> we ask ASF Infra to mark the repo as archived.
>
> Any objections?
>
> ~Darryl
>

Strongly deprecating the FileTransfer plugin

[Darryl Pogue]

Hey folks,

The File Transfer plugin has been officially deprecated since 2017:
https://cordova.apache.org/blog/2017/10/18/from-filetransfer-to-xhr2.html

However, the repo and npm have no link to that page or any sort of
indication that it is not maintained.

With the release of cordova-ios 6, the FileTransfer plugin no longer
compiles on iOS:
https://github.com/apache/cordova-plugin-file-transfer/issues/258

I want to reply to that issue saying that it's deprecated and not
maintained, but I feel like we haven't made that very clear.

I would like to propose that we update the README for File Transfer with a
clear deprecation notice which links to the blog post from 2017, and that
we ask ASF Infra to mark the repo as archived.

Any objections?

~Darryl

Re: the future of cordova-plugin-wkwebview-engine

[Darryl Pogue]

Speaking as someone who raised concerns about this, I don't think
anyone *prefers* file URLs over app schemes, especially given the CORS
issues. However, moving from file URLs to app scheme will result in
apps losing all of their local data (indexedDB, localStorage, cookies,
cache, etc.) due to it being a different origin.

I think this is a major concern for anyone whose apps are already
using WKWebView with file URLs, and it definitely has not been
highlighted as something that apps would need to (somehow) mitigate.
It seems irresponsible for us to release a major version will
knowingly cause data loss for all existing apps. Of the 7 or 8 apps
that I maintain, it would not be acceptable to any of the customers to
lose data, so I would effectively be stuck on Cordova iOS 5.x forever
(or until writing a plugin to copy live databases around).

It seems like the easiest option is to add support for both file URLs
and custom schemes, and allow it via a preference (maybe the existing
scheme preference?):
- If the preference is not set, use file URL
- Update the cordova-app-hello-world template to set the preference
for all newly created apps


Note: There was an SPI (private API) added to WebKit recently that
allows moving localStorage to another origin, but it doesn't handle
other types of data, isn't public API, and doesn't exist in any
current iOS versions:
https://trac.webkit.org/changeset/261038/webkit
There might be a possibility to write a 3rd party plugin to migrate
data, but I'm not sure that's a path we (as Cordova) should go down
ourselves.

~Darryl


On Thu, May 21, 2020 at 9:18 AM julio cesar sanchez
 wrote:
>
> we should discuss about what's going to happen
> with cordova-plugin-wkwebview-engine
>
> cordova-ios 6 is coming soon and it uses WKWebView, but it uses a custom
> scheme to serve the app content instead of serving from file protocol.
> some people prefers file over the custom scheme,
> but cordova-plugin-wkwebview-engine will not work in cordova-ios 6 because
> of some breaking changes introduced.
>
> So, should we
>
> a) continue maintaining cordova-plugin-wkwebview-engine and fix it to work
> on cordova-ios 6?
> b) modify cordova-ios 6 to allow both file and custom scheme and then
> sunset cordova-plugin-wkwebview-engine?
> c) do nothing and tell people who want to use file protocol to stick with
> cordova-ios 5.1.1?
> d) other option I didn't think of (please, describe)

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [DISCUSS] cordova-ios 6.0.0 Major Release

[Darryl Pogue]

I've just merged two very small PRs:
- https://github.com/apache/cordova-ios/pull/615
- https://github.com/apache/cordova-ios/pull/825

There are some others that would be nice to get in, but require more
testing or more work to finish:
- https://github.com/apache/cordova-ios/pull/823
- https://github.com/apache/cordova-ios/pull/790
- https://github.com/apache/cordova-ios/pull/763
- https://github.com/apache/cordova-ios/pull/454

On Fri, Apr 17, 2020 at 10:56 PM Bryan Ellis  wrote:

> Does anyone have any reason to delay a cordova-ios major release (6.0.0)?
>
> Any additional outstanding changes to land?
>
> If not, I will start the release process in the next couple of days.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

Re: [Cordova dev] Use AndroidX by default on Android (?)

[Darryl Pogue]

I am definitely in favour, and this should be done as part of the next
major version.

If we're going to use GitHub for discussion, cordova-android is probably
the best spot for it (although I think we already determined that there
would be almost no changes in cordova-android itself).

On Wed, Jan 8, 2020 at 10:56 AM Chris Brody  wrote:

> There seems to be some interest in switching cordova-android to use
> AndroidX by default, which would basically replace cordova-plugin-androidx
> by
> Dave Allen. This would obviously be a major, breaking change.
>
> Some plugins seem to be already using AndroidX, some other plugins seem to
> be holding back.
>
> I think we should discuss this on GitHub, not sure if it should be in
> apache/cordova or apache/cordova-android.
>

Re: [VOTE] Cordova-ESLint 2.0.0 Release

[Darryl Pogue]

I vote +1:

* Confirmed sigs & hashes with `coho verify-archive`
* Verified sha1s match tags with `coho verify-tags` (after adding the
repo to coho locally)


On Mon, Nov 11, 2019 at 1:59 AM  wrote:
>
> I vote +1:
> * Ensured CI was green at tag
> * Successfully installed and applied the config from the tar ball to
> cordova-browser
>
> Am Mo., 11. Nov. 2019 um 10:44 Uhr schrieb Bryan Ellis :
>
> > Please review and vote on this Cordova ESLint Major 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/eslint-v2.0.0
> >
> > The package was published from its corresponding git tag:
> > cordova-eslint: 2.0.0 (88d5e384eb)
> >
> >
> > Upon a successful vote I will upload the archive to dist/, publish it to
> > npm, and post the blog post.
> >
> > Voting guidelines:
> > https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
> >
> > Voting will go on for a minimum of 48 hours.
> >
> > I vote +1:
> > * Ran coho audit-license-headers over the relevant repos
> > * Ran coho check-license to ensure all dependencies and subdependencies
> > have Apache-compatible licenses
> > * Ensured continuous build was green when repo was tagged
> > * NPM Audit
> > * NPM Test
> >

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Making the most of Hacktoberfest contributions

[Darryl Pogue]

Hi folks,

The annual "Hacktoberfest" open-source participation event from GitHub
and Digital Ocean is back and coming up soon. For those who aren't
familiar, people who register and then open 4 pull requests against
open-source repositories can get rewarded with T-shirts and stickers.

This is a great opportunity to get drive-by contributions to Cordova,
ideally for things that don't require deep knowledge of our packages.

Some ideas:
- Migrating tooling repos from TravisCI and Appveyor to GitHub Actions
- Upgrading to latest eslint and fixing linting errors
- Ensuring all our repos are testing against the right versions of nodeJS
- Migrating from Q promises to native promises
- Documentation updates
- Migrating small pieces of code from ES5-syntax to ES6-syntax

The best way to attract these contributions is to create GitHub issues
that clearly explain the intended change and the scope of the change,
that are labelled with a Hacktoberfest label.

If nobody objects (or beats me to it) I will try to spend a few hours
next week creating some of these issues in our repos. I'm most
familiar with the tooling and platform packages, so maybe someone more
familiar with plugins could take a pass over those repos for similar
easy contribution opportunities.

Thanks,
~Darryl

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [BOARD REPORT DRAFT] September 2019 Cordova Board Report

[Darryl Pogue]

Looks good to me.

On Wed, Sep 11, 2019 at 2:03 AM Jesse  wrote:
>
> Please review and comment here.
>
> https://github.com/apache/cordova-apache-board-reports/blob/master/2019/2019-09.md
>
> Sorry for the lateness of this email, the report is due today.
>
> Cheers,
>  Jesse

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [DISCUSS] Dropping support for Node 8

[Darryl Pogue]

+1 from me


On Mon, Sep 9, 2019 at 7:20 AM Norman Breau  wrote:
>
> Just starting a thread here to whether or not we should drop support for
> Node 8 at the same time of dropping Node 6 support.
> The original thought for this I believe is to avoid having to have 2
> major version bumps as Node 8 EOL is in December 2019, only a few months
> away.
>
> Personally I don't see why we should keep support something that is in
> maintenance mode and is coming to the end of life soon, so I think
> dropping Node 8 is a good idea.
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

UIWebView/WKWebView Migration Strategy for Cordova iOS

[Darryl Pogue]

Background: As of August 2019, Apple is now showing a deprecation
warning when uploading apps to the App Store that include
UIWebView-related code. As a result, all Cordova apps built for iOS
receive this deprecation warning on upload.

We need to determine how Cordova as a project wants to proceed to
solve this problem. There are pull requests already being opened that
I'm quite concerned with end up breaking all existing Cordova apps,
and I think we want to be more careful about that.

I've put together a document in the cordova-discuss repo outlining
some options for discussion:
https://github.com/apache/cordova-discuss/pull/110

It might be easiest to keep all discussion on the GitHub PR for
consistency and bring it back to the mailing list for consensus on
next steps.

~Darryl

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: Is there any current effort or interest in a general crypto plugin for Cordova?

[Darryl Pogue]

It's not possible to use NodeJS-specific modules in Cordova, because
Cordova is just a packaging tool that provides a WebView into which
your application content is loaded.
I would encourage you to investigate using the features that already
exist in the WebView when possible, instead of trying to implement
plugins.

In your case, the WebCrypto API might be sufficient:
https://www.w3.org/TR/WebCryptoAPI/
It is supported in both iOS and Android WebViews.

~Darryl


On Sat, Aug 24, 2019 at 2:39 PM James Marshall  wrote:
>
> Hello,
>
> I'm writing a large cross-platform mobile app, and Cordova is just about
> ideal for what I need-- uses WebView (my app needs to use HTML templates,
> JS expertise is easy to find), open source, and controlled by a non-profit
> rather than a corporation (yes, I need this).  So I was happy to find
> Cordova.
>
> I just discovered that Cordova doesn't support the NodeJS "crypto" module,
> and I need to use extensive encryption.  Are there any plans to support
> it?  Failing that, is there any work happening on a general crypto plugin
> for Cordova?  I've searched a lot but couldn't find any; some use
> encryption but typically only for one specific purpose.
>
> If not, I'd like to start such a plugin.  If there is already such an
> effort, I can contribute to it.  Does anyone know the current status of
> crypto in Cordova?  I searched the mailing list archives for "crypto" but
> didn't find anything.
>
> If I write a plugin, it would start with just Android (I don't know
> Objective C yet), and the specific features I need:  encryption/decryption,
> both symmetric and asymmetric, sign/verify, key pair generation, and
> hashes.  However, I would start it with a structure that could be filled in
> with the other features, and with iOS and other support.
>
> As I understand it, writing a plugin just means creating a unified JS API,
> plus wrapper code to each of the native encryption APIs, right?
>
> Thanks for any guidance!
>
> James

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [Cordova dev] info needed label

[Darryl Pogue]

+1

Might also be worth proposing a rule that issues tagged “info needed” get
closed after X days if there is no information provided. We have a bunch of
issues piling up that are all waiting for info, and we have no process that
allows us to close those.

On Mon, Jul 15, 2019 at 2:11 PM Jesse  wrote:

> +1 I don't think you'll see any objections.
>
> On Mon, Jul 15, 2019 at 2:07 PM Chris Brody  wrote:
>
> > We receive a number of support issues where I think we need an
> > explicit label such as “info needed”, to make it clear that more
> > information is needed before we can provide any support. I think we
> > need to add this label to a number of repos such as apache/cordova,
> > cordova-android, cordova-ios, etc.
> >
> > Any objections if I would add this label to some of the repos on GitHub?
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
> >
>

Re: [DISCUSS] cordova-common tools release

[Darryl Pogue]

+1
I've merged the plist formatting PR, and no other concerns from me about
this release.

I will note that our highest priority issue as a project is probably the
bug with config munging[1][2][3] in cordova-common, but nobody seems to
know where to begin fixing that or have time to look at it :(
[1] https://github.com/apache/cordova-android/issues/704
[2] https://github.com/apache/cordova-common/pull/24
[3] https://github.com/apache/cordova/issues/95

Since nobody has any WIP for that fix, let's go ahead with the minor
release.

~Darryl

On Tue, Jun 11, 2019 at 8:33 AM Chris Brody  wrote:

> I would like to publish a cordova-common@3.2.0 release with fs-extra
> workaround update and a couple other recent changes.
>
> I would also like to merge the following PR to fix plist formatting:
> https://github.com/apache/cordova-common/pull/69
>
> Does anyone have any reason to delay a cordova-common  tools release?
>
> Any outstanding patches to land?
>
> If not, I will start the release tomorrow.
>
> The versions to be released are:
> * cordova-common@3.2.0
>
> Chris
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

Re: [DISCUSS] Remove all documentation translations

[Darryl Pogue]

On Wed, May 15, 2019 at 9:24 AM Dmitry Blotsky  wrote:
>
> Would anyone that works on Cordova full-time be up to prioritise this?

As far as I know, there has been nobody working full-time on Cordova
for the past year. There are a few companies putting some dev time
against the project, but it's almost entirely maintained by people in
their limited spare time nowadays.

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [DISCUSS] non-global Cordova installs

[Darryl Pogue]

I feel pretty strongly that npx is a significant improvement to the
developer experience of using Cordova, and resolves a bunch of cases that
have been causing problems for years.

Encouraging people to install Cordova globally results in permissions
problems on Linux when using nodeJS installed by package managers. It
requires people to use sudo to install it.
Encouraging people to install Cordova globally causes issues when working
on multiple projects that were built with different versions of Cordova.
Essentially, everything is required to be updated to whatever version is
installed globally.

Encouraging people to install Cordova as a development dependency of their
app is definitely something we should encourage, but it doesn't solve the
initial case of creating a new Cordova app.
If Cordova is installed locally to a project, npx will use that local
dependency rather than installing it.

Using npx makes all of these problems go away.

On Tue, May 14, 2019 at 12:21 AM Dmitry Blotsky 
wrote:

> I'm really glad this discussion lit up, because it clearly shows that this
> issue isn't settled.
>
> I personally have few opinions about the "best" solution here, but I
> firmly believe that npx is a non-starter for these 2 reasons:
> 1. It is strictly less secure than the status quo, and all alternatives.
> It is literally downloading code from hundreds of untrusted parties and
> immediately running it. It's worse than piping a curl command into bash (at
> least you can check the curl command's URL, or checksum the downloaded
> script).
> 2. It is strictly less stable than a local installation because now every
> call to Cordova goes through an opaque dependency.
>
> Unless both of those can be addressed, I think we shouldn't consider npx.
>
> Dmitry
>
> > On May 10, 2019, at 4:31 PM, Oliver Salzburg 
> wrote:
> >
> > Our DX is not good and this proposal would have the potential to have a
> > positive impact on that. I'm sorry that you're not convinced yet.
> >
> > Because I don't want to skip back and forth between GitHub and the
> > mailing list, I'll address your points here.
> >
> > - When you start a new project, unless you create a new cordova project
> > every week, you'll download cordova. npx will only help you in
> > downloading the package and if you have downloaded it in the past, it
> > will be pulled from the cache.
> >
> > - Yes, the Cordova CLI behavior can change over time, which is exactly
> > why you would not want to share a single global version with all of your
> > projects. I consider this a pro-local point.
> >
> > - It is 4 more characters to type. Yes. I give you that. But if you want
> > to interact with a local installation of cordova, what exactly is the
> > alternative? Not installing locally? I disagree.
> >
> > - Your suggestion regarding writing a completely new module to initiate
> > a cordova project is completely besides the point here. If you had that
> > module, you'd still want to use it with npx. And using `npx cordova`
> > pulls cordova into the cache where you are going to want to have it
> > anyway. If you had a slimmed down module, you now still need to download
> > cordova.
> >
> > By using npx, given your usage examples, you would have less downloads
> > instead of more.
> >
> > I'm sorry, Brody, I don't see your points and I don't feel like they
> > have been weighed appropriately against the benefits I proposed earlier.
> >
> > I would also appreciate it if we could try to keep the conversation to a
> > single media. The split between mailing list and GitHub is not
> constructive.
> >
> > Almost like putting part of your application in a global context and
> > another part in a local context is not constructive...
> >
> > On 2019-05-10 23:08, Chris Brody wrote:
> >> I am very sorry to say that I am still not convinced about this idea.
> >> I just raised some concerns in a recent comment in:
> >> https://github.com/apache/cordova-docs/issues/838
> >>
> >> And I think I am not the only one right now.
> >>
> >> As I said in cordova-docs#838, I would favor that we mention using
> >> `npx cordova` *as an option* in a limited number of places.
> >>
> >> I would like to express my appreciation to Oliver for the time and
> >> effort has given to improve the documentation, and to contribute a
> >> number of updates and fixes in the past. But I would rather take the
> >> extra time and effort to ensure we keep up the best app DX we can.
> >>
> >> And I don't really follow what you mean about CORDOVA_CMDLINE, would
> >> probably be easiest if we keep it in a separate discussion thread or
> >> issue.
> >>
> >> On Fri, May 10, 2019 at 3:05 PM Oliver Salzburg
> >>  wrote:
> >>>
> >>> I have already started working on a PR to make the necessary changes to
> >>> the documentation, as I was under the impression that consensus
> >>> regarding this issue was already reached:
> >>>
> >>> https://github.com/apache/cordova-docs/pull/987
> >>>
> >>> Specifically this might be of inter

Re: Native (C#, C++) UI plugins for Cordova Windows?

[Darryl Pogue]

On Wed, May 1, 2019 at 2:33 PM Chris Brody  wrote:
> For the future, I wonder if we should consider dropping formal Windows
> support in favor of Electron? (And same for "osx" platform?)

If the "marzipan" rumours are true, cordova-ios might be an option for
making macOS apps in the near future.

For Windows, do we even need Cordova anymore? PWAs can be submitted to
the Windows Store, which sounds to me like fulfillment of the original
Phonegap objective. Electron is definitely an option too.

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [VOTE] cordova-ios 5.0.1 release

[Darryl Pogue]

The vote has now closed. The results are:

Positive Binding Votes: 3
* Darryl Pogue
* Bryan Ellis
* Jan Piotrowski

The vote has passed.

Thanks everyone!

On Mon, Apr 22, 2019 at 10:55 AM Jan Piotrowski  wrote:
>
> +1
>
> * CI is green
> * Diff makes sense
> * release branch looks right
>
> Am Fr., 19. Apr. 2019 um 02:53 Uhr schrieb Bryan Ellis :
> >
> > +1
> >
> > * Verified archive signatures & hashes with `coho verify-archive`
> > * Verified tags SHA with `coho verify-tags`
> > * Re-created npm package to validate matching release candidate content
> > * Ran NPM Test
> > * Tested Platform `add`, `run` and `build`
> >
> >
> >
> >
> > From: Pogue Darryl 
> > Reply: dev@cordova.apache.org 
> > Date: April 19, 2019 at 6:41:23
> > To: dev@cordova.apache.org 
> > Subject:  [VOTE] cordova-ios 5.0.1 release
> >
> > Please review and vote on this 5.0.1 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/ios501
> >
> > The package was published from its corresponding git tag:
> > cordova-ios: 5.0.1 (3b9e044d56)
> >
> > Note that you can test it out via:
> > cordova platform add https://github.com/apache/cordova-ios#5.0.1
> >
> > Upon a successful vote I will upload the archive to dist/, publish it
> > to npm, and post the blog post.
> >
> > Voting guidelines:
> > https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
> >
> > Voting will go on for a minimum of 48 hours.
> >
> > I vote +1:
> > * Ran coho audit-license-headers over the relevant repos
> > * Ran coho check-license to ensure all dependencies and
> > subdependencies have Apache-compatible licenses
> > * Ensured continuous build was green when repo was tagged
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[VOTE] cordova-ios 5.0.1 release

[Darryl Pogue]

Please review and vote on this 5.0.1 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/ios501

The package was published from its corresponding git tag:
cordova-ios: 5.0.1 (3b9e044d56)

Note that you can test it out via:
cordova platform add https://github.com/apache/cordova-ios#5.0.1

Upon a successful vote I will upload the archive to dist/, publish it
to npm, and post the blog post.

Voting guidelines:
https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md

Voting will go on for a minimum of 48 hours.

I vote +1:
* Ran coho audit-license-headers over the relevant repos
* Ran coho check-license to ensure all dependencies and
subdependencies have Apache-compatible licenses
* Ensured continuous build was green when repo was tagged

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[DISCUSS] cordova-ios 5.0.1 patch release

[Darryl Pogue]

If nobody has any objections, I'd like to put together a patch release for
cordova-ios.

The list of merged pull requests can be seen here:
https://github.com/apache/cordova-ios/pulls?utf8=%E2%9C%93&q=milestone%3A5.0.1

Particular highlights:
* Fix the splashscreen plugin potentially hanging on iOS 12
* Fix for CFBundleIdentifier not being set properly during project creation
* Update ios-sim to work with Xcode 10.2 simulators

If nobody raises any concerns, I'll put the release together tomorrow and
set up the voting thread.

~Darryl

Re: [VOTE] Cordova-Plugman 3.0.1 Release

[Darryl Pogue]

I vote +1.

* Confirmed sigs & hashes with `coho verify-archive`
* Verified sha1s match tags with `coho verify-tags`

On Thu, Apr 11, 2019 at 5:25 AM Bryan Ellis  wrote:

> Please review and vote on this Cordova Plugman Release v3.0.1
> 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
>
> The package was published from its corresponding git tag:
> cordova-plugman: 3.0.1 (247122d4b8)
>
> Upon a successful vote I will upload the archive to dist/, publish it to
> npm, and post the blog post.
>
> Voting guidelines:
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
>
> Voting will go on for a minimum of 48 hours.
>
> I vote +1:
> * Ran coho audit-license-headers over the relevant repos
> * Ran coho check-license to ensure all dependencies and subdependencies
> have Apache-compatible licenses
> * NPM Audit
> * NPM Test

Re: [DISCUSS] Node 6.x & 8.x Deprecation & Node 12.x Support

[Darryl Pogue]

+1

One suggestion: If (and this is a big if) we're able to get the iOS
and Android platform updates ready by October/November, we could
consider releasing the next major publicly, but not making it the
default version on npm. This would hopefully gives us a period where
people could try it and identify issues with plugins before we roll it
out to everyone. We should still target a full public release around
the end of the year (but December tends to be bad for doing stuff due
to holidays, so maybe early January?)

Let's try to get node 12.x added to our CI as soon as possible, and
unofficially add support in patch releases.

On Wed, Apr 10, 2019 at 1:56 AM julio cesar sanchez
 wrote:
>
> +1
>
> sounds good
>
> El mié., 10 abr. 2019 a las 9:51, Shazron () escribió:
>
> > +1000
> >
> > On Wed, Apr 10, 2019 at 1:17 PM  wrote:
> >
> > > Sounds reasonable and well thought out to me.
> > >
> > > Bryan Ellis  schrieb am Mi., 10. Apr. 2019, 09:42:
> > >
> > > > I would like to start the discussion around Cordova's planning for
> > > > deprecating Node 6.x and Node 8.x as well as starting to support Node
> > > 12.x.
> > > >
> > > > Since Node 6.x is being deprecated by the end of this month, I am not
> > > > expecting drastic action.
> > > >
> > > > Additionally, Node 8.x is expected to be deprecated by December.
> > > >
> > > > IMO, we could hold out till December to deprecate both versions and
> > just
> > > > warn users about our recommendation to upgrade in the meantime. These
> > > > notices and warnings can be added in April and September as a patch or
> > > > minor release.
> > > >
> > > > As a side note, I suspect Android Q's release (August?) and possible
> > iOS
> > > > (Sept?) to be out before December. For a major release for these new
> > > > platforms, adding Node will fall in nicely.
> > > >
> > > > Blog Post PR: https://github.com/apache/cordova-docs/pull/965
> > > > GH Issue Ticket: https://github.com/apache/cordova/issues/79
> > >
> >

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [VOTE] cordova-lib@9.0.1 Release

[Darryl Pogue]

The vote has now closed. The results are:

Positive Binding Votes: 4
- Darryl Pogue
- Raphael von der Grün
- Gandhi Rajan
- Bryan Ellis

Positive Non-Binding Votes: 1
- Tim Brust

The vote has passed.
Thank you everyone for your reviews :)

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[VOTE] cordova-lib@9.0.1 Release

[Darryl Pogue]

Please review and vote on this cordova-lib release by replying to this
email (and keep discussion on the DISCUSS thread)

Artifacts have been published to dist/dev:
https://dist.apache.org/repos/dist/dev/cordova/lib901/

The packages were published from their corresponding git tags:
cordova-lib: 9.0.1 (d4a0938385)

Upon a successful vote I will upload the archives to dist/, and
publish them to npm. I don't personally think a blog post is needed
for a patch update to a non-user-facing library, but I'll bring that
up in the DISCUSS thread.

Voting guidelines:
https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md

Voting will go on for a minimum of 48 hours.

I vote +1:
* Ran coho audit-license-headers over the relevant repos
* Ran coho check-license to ensure all dependencies and
subdependencies have Apache-compatible licenses
* Ensured continuous build was green when repos were tagged

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[DISCUSS] Cordova-Lib 9.0.1 patch release

[Darryl Pogue]

Does anyone have any reason to delay a patch release for cordova-lib? If
not, I will start the release tomorrow.

The versions to be released are:
cordova-lib@9.0.1

Currently the release will contain two fixes:
* A fix for "version check failed" warnings showing up every build, due to
path quoting issues
* A fix for plugins not correctly being restored from package.json when
running `cordova prepare`

Commit changelog:
https://github.com/apache/cordova-lib/compare/9.0.0...master

~Darryl

Re: [VOTE] Cordova-CLI 9.0.0 Release

[Darryl Pogue]

+1

- Confirmed sigs & hashes with `coho verify-archive`
- Verified sha1s match tags with `coho verify-tags`

On Thu, Mar 21, 2019 at 11:37 PM Ken Naito  wrote:
>
> +1
>
> * coho verify-archive OK
> * coho verify-tags OK
> * The latest commit fcf4d9b764cd97822097abbb6eef35a3c9bd0353 is green
>
> Ken Naito
>
>
> On 2019/03/20 15:39, Bryan Ellis wrote:
> > Please review and vote on this Cordova CLI Release v9.0.0
> > by replying to this email (and keep discussion on the DISCUSS thread)
> >
> > Release issue: https://github.com/apache/cordova/issues/10
> >
> > The archive has been published to dist/dev:
> > https://dist.apache.org/repos/dist/dev/cordova/GH-10
> >
> > The package was published from its corresponding git tag:
> >  cordova-cli: 9.0.0 (24fc3e02c9)
> >
> > Upon a successful vote I will upload the archive to dist/, publish it to 
> > npm, and post the blog post.
> >
> > Voting guidelines: 
> > https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
> >
> > Voting will go on for a minimum of 48 hours.
> >
> > I vote +1:
> > * Ran coho audit-license-headers over the relevant repos
> > * Ran coho check-license to ensure all dependencies and subdependencies 
> > have Apache-compatible licenses
> > * Ensured continuous build was green when repo was tagged
> > * NPM Audit
> > * NPM Test

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [VOTE] Cordova-Plugman 3.0.0 Release

[Darryl Pogue]

+1

- Confirmed sigs & hashes with `coho verify-archive`
- Verified sha1s match tags with `coho verify-tags`

On Thu, Mar 21, 2019 at 11:36 PM Ken Naito  wrote:
>
> +1
>
> * coho verify-archive OK
> * coho verify-tags OK
>
> Ken Naito.
>
>
> On 2019/03/20 14:48, Bryan Ellis wrote:
> > Please review and vote on this Cordova Plugman Release v3.0.0
> > by replying to this email (and keep discussion on the DISCUSS thread)
> >
> > Release issue: https://github.com/apache/cordova/issues/10
> >
> > The archive has been published to dist/dev:
> > https://dist.apache.org/repos/dist/dev/cordova/GH-10
> >
> > The package was published from its corresponding git tag:
> >  cordova-plugman: 3.0.0 (898e9b19ee)
> >
> > Upon a successful vote I will upload the archive to dist/, publish it to 
> > npm, and post the blog post.
> >
> > Voting guidelines: 
> > https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
> >
> > Voting will go on for a minimum of 48 hours.
> >
> > I vote +1:
> > * Ran coho audit-license-headers over the relevant repos
> > * Ran coho check-license to ensure all dependencies and subdependencies 
> > have Apache-compatible licenses
> > * NPM Audit
> > * NPM Test

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [VOTE] Cordova-Fetch 2.0.1 Release

[Darryl Pogue]

+1

- Confirmed sigs & hashes with `coho verify-archive`
- Verified sha1s match tags with `coho verify-tags`
- CI was green when build was tagged

On 2019/03/18 13:08, Bryan Ellis wrote:
>  cordova-fetch: 2.0.1 (d2be9307f3)

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [DISCUSS] Cordova-Android Release

[Darryl Pogue]

On Tue, Feb 12, 2019 at 2:47 PM Chris Brody  wrote:
> [...]
> The easy solution to bug 666 would be to revert PR 664, which would
> consequently reintroduce cordova-android bug 629. I would favor
> resolving it by reading the default targetSdkVersion value from
> project.properties, as briefly discussed on GitHub.

Ideally we'd set it in settings.gradle and get rid of
project.properties entirely :\

Unfortunately, I don't have capacity to pick anything up at the moment.

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [DISCUSS] Cordova-iOS Release

[Darryl Pogue]

On Thu, Feb 7, 2019 at 11:28 AM Chris Brody  wrote:
>
> I was hoping for explicit confirmation that this issue is resolved:
>
> > > I don't think we should release cordova-ios until automatic
> > > provisioning/code signing works in Xcode 10 with the modern build
> > > system. We've spent the past 2 years trying to encourage people to
> > > move their projects to use automatic signing instead of specifying
> > > provisioning profiles UUIDs everywhere, and now we'd be leaving all
> > > those people with broken builds (including me at my job).
>
> I do see that cordova-ios PRs 489 & 508 have been merged, don't know
> if it solved the problem or not. I would love to see this confirmed by
> Darryl.

Yes! I am happy to confirm that Ken found the "one weird trick"[1] to
make automatic signing work properly with the new build system in
Xcode 10. :)

There are a million tiny things I'd love to see get in to this
release, but it's in a state where it works and we have an upcoming
deadline from Apple for requiring Xcode 10, so I don't see any strong
reason to delay releasing this. There will be future releases where we
can take care of the other small bits.

[1] https://github.com/apache/cordova-ios/pull/508

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [DISCUSS] Cordova-iOS Release

[Darryl Pogue]

On Thu, Jan 17, 2019 at 9:57 PM Bryan Ellis  wrote:
>
> Does anyone have any reason to delay a cordova-ios platform release?

I hate to be the guy that blocks a release without contributing
anything to unblock it, but I'm swamped with non-Cordova work for the
next few weeks :(

I don't think we should release cordova-ios until automatic
provisioning/code signing works in Xcode 10 with the modern build
system. We've spent the past 2 years trying to encourage people to
move their projects to use automatic signing instead of specifying
provisioning profiles UUIDs everywhere, and now we'd be leaving all
those people with broken builds (including me at my job).

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: Transferring Cordova issues on GitHub

[Darryl Pogue]

>From the GitHub docs:
> To transfer an open issue to another repository, you must have admin 
> permissions on the repository the issue is in and the repository you're 
> transferring the issue to.

I don't think there's anything INFRA can do to enable it, since repo
admin isn't something they'll provide :(

On Wed, Jan 16, 2019 at 7:22 AM Chris Brody  wrote:
>
> Here is an example where I had to apply a clumsy workaround:
> https://github.com/apache/cordova/issues/68
>
> I submitted the following INFRA ticket:
> https://issues.apache.org/jira/browse/INFRA-17671

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [DISCUSS] cordova-common@3.1.0 tools release

[Darryl Pogue]

Probably late to be asking this question now, but what necessitates a
minor version bump rather than a patch release? I don't think either
of the two items in the changelog add new API to the module or change
behaviour in a consumer-visible way, do they?

On Tue, Dec 18, 2018 at 7:38 PM Chris Brody  wrote:
>
> to include singleton event object as proposed in
> https://github.com/apache/cordova-common/pull/60 and CordovaLogger
> singleton object, in order that this rule no longer has to apply:
> https://github.com/apache/cordova-coho/blob/master/docs/tools-release-process.md#cordova-common-singleton-rule
>
> Does anyone have any reason to delay a tools release?
>
> Any outstanding patches to land?
>
> If not, I will start the release tomorrow.

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: How to disable in Android Webview, the WebSettings attributes "AllowFileAccess" in cordova-android ?

[Darryl Pogue]

On the one hand, I can see why this would get flagged by a security
audit, because it opens the risk of 3rd party sites/scripts having
uncontrolled access to the filesystem.
On the other hand, changing this preference will break the most common
Cordova use case, where files are served from the app bundle instead
of from a remote URL.

We could add a preference for this, but it would need a bunch of
documentation to explain that it only affects Android, and to explain
clearly what it does and when you might need to enable it. A lot of
apps would break if people just turned it on as "good security
practice" without understanding the implications.

On Wed, Dec 5, 2018 at 7:57 AM MALEYRIE Stephane (AIM Services)
 wrote:
>
> Hello all,
>
> Thanks for your answers.
>
> I understand that new features will be only available on master release, with 
> no back port.
> I use cordova 6.4.0 because there is an issue with cordova-plugin-fcm on 
> cordova-android 7.x :
> https://github.com/fechanique/cordova-plugin-fcm/issues/470
> https://github.com/fechanique/cordova-plugin-fcm/issues/535
>
> About the security issue :
> I found an exemple here: 
> https://blog.trustlook.com/2018/01/19/android-webview-class-poses-significant-security-risk/
> It's about loadUrl of file:// type url
> In Cordova plugin whitelist doc, it alwayse accept any type of file://url ...
> So, it doesn't seems to solve the issue.
>
> We've tried to make a plugin to change it, but it doesn't work, seems to be 
> too late in the process.
> For now, we plan to make a private fork of cordova-android-plugin to add the 
> line «  settings.setAllowFileAccess(false);» here : 
> https://github.com/apache/cordova-android/blob/6.4.x/framework/src/org/apache/cordova/engine/SystemWebViewEngine.java#L152
>
> About this idea, more generally, it'd be usefull to configure any WebSettings 
> of the WebView, and not only the allowFileAccess attribute...
> Maybe, it could be possible by java reflection, using a config file 
> containing attributes names and theirs value ?
> I will send a new email/thread for this.
>
> Thanks again.
>
> Stéphane
>

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [dev] Cordova-Android Gradle improvements?

[Darryl Pogue]

I'm experimenting with refactoring the way Cordova's gradle files are
set up. Partly to resolve issues around the availability of Cordova
helper methods[1], the new app bundles features[2], Kotlin support[3],
and to investigate options for making the setting of build-time
variables (like min SDK versions) more consistent.[4]

What I can tell you from my initial skimming of the code on Sunday is
that a lot of the plugin handling is done in a way that tried to
preserve as much as possible from the existing Ant-based project
structure, such as reading from project.properties files and building
up references to inject into the build.gradle file from those.

I'm not sure what you mean by "it should be possible for user-defined
Gradle files to be configured outside the generated cordova-android
project". Plugins can provide their own gradle files to add things
like libraries and override ext variables, but those need to get
included in the app project's build because the plugin source files
themselves are included in the app project's build.

I can try to open a WIP PR for the gradle refactoring I'm doing, but
currently it doesn't work and I'm a bit worried that it's going to end
up held up forever in review with a bunch of requested changes to
stuff that doesn't even work yet.
I'm not making changes to the existing gradle files, I'm literally
deleting them all and rewriting them to try to make them adhere better
to gradle conventions, and it's an experiment that might totally
backfire.

[1] https://github.com/apache/cordova-android/pull/438#discussion_r216195552
[2] https://github.com/apache/cordova-android/issues/596
[3] https://github.com/apache/cordova-android/pull/441
[4] https://github.com/apache/cordova-android/issues/508

On Tue, Dec 4, 2018 at 9:15 AM Chris Brody  wrote:
>
> I think it should be possible for user-defined Gradle files to be
> configured outside the generated cordova-android project to avoid
> issues we have encountered such as changing project structure and
> cordova-android upgrades. While it would be possible for a user to
> make a custom plugin with a custom Gradle file this may not be
> convenient for all Cordova Android apps.
>
> And it would be ideal if we could somehow alleviate the need for
> PLUGIN GRADLE EXTENSIONS START / PLUGIN GRADLE EXTENSIONS END
> placeholder comments as discussed in
> . Maybe we could
> move the plugin Gradle extensions into a separate file?
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [dev] Introduce ES6 classes or not?

[Darryl Pogue]

I both agree and disagree with your points :P

To your first point, yes ES6 classes are just syntactic sugar around
prototypes, but that sugar exists for a reason and it's extremely
popular now. Personally, I've been using class syntax at work for
going on three years now, and looking at some parts of the Cordova
code that are obviously implementing a class pattern with ES5 syntax
just makes it feel like nobody has touched or dusted off the code
since the pre-ES6 days. This is the modern style of JavaScript, and I
find it much easier to glance at a class and see easily which things
belong to the instance vs the class compared to needing to check
whether something was declared on the prototype or not. For better or
worse, there are people coming to JavaScript today who will be much
more comfortable with ES6 classes than with the ES5 style of
prototypical declarations, and I think that using ES6 classes makes
the code clearer, more readable, and more maintainable.

But only where it makes sense to use classes. We should only use
classes where it makes sense, where we have some sort of instance of
something and it's encapsulating data and providing methods to
interact with/manipulate that data.

I definitely feel like the majority of Cordova can and should be set
up in a functional programming-inspired style, where it's just
functions that do one task, and they get chained together.


On Thu, Nov 29, 2018 at 6:22 PM Chris Brody  wrote:
>
> I would not personally favor using ES6 classes, here are my main reasons:
> * ES6 class is really sugar around prototypal inheritance, unlike many
> other languages
> * In many cases it is better to use functional programming and factory
> functions than classes
>
> Some reading:
> * 
> https://artem.today/what-is-behind-syntactical-sugar-in-es6-classes-6dfa4ab4d6a2
> * 
> https://medium.com/javascript-scene/the-two-pillars-of-javascript-ee6f3281e7f3
> * 
> https://medium.com/javascript-scene/why-composition-is-harder-with-classes-c3e627dcd0aa
> * 
> https://hackernoon.com/favor-object-composition-over-class-inheritance-they-said-9f769659b6e
> On Thu, Nov 29, 2018 at 9:20 PM Chris Brody  wrote:
> >
> > I was wondering what our sentiment should be about using ES6 classes?
> >
> > My own opinion in coming in a response email.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: What is the status of plugreg?

[Darryl Pogue]

plugreg was a 3rd party website displaying stats from the Cordova
Plugin Registry (back before we used npm)

I don't believe it was ever officially affiliated with Apache Cordova.

On Tue, Nov 27, 2018 at 2:13 PM Chris Brody  wrote:
>
> I think plugreg was a registry made 5-7 years ago, before PhoneGap
> Build was available and before Cordova was using npm. I think that
> plugreg is not used any more since npm gives us what we need.
>
> Can any PMC members confirm?
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [VOTE] cordova-android@7.1.4 accelerated hotfix release

[Darryl Pogue]

I vote +1 for cordova-android@7.1.4 release and +1 for the accelerated release

* Confirmed sigs & hashes with `coho verify-archive`
* Verified sha1s match tags with `coho verify-tags`

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [DISCUSS] cordova-android@7.1.4 accelerated hotfix release coming

[Darryl Pogue]

Can we please try to figure out how to run mobilespec or paramedic or
some sort of regression test against our core plugins before
releasing?

On Thu, Nov 22, 2018 at 11:36 AM Chris Brody  wrote:
>
> Does anyone have any reason to delay a cordova-android@7.1.4
> accelerated hotfix release?
>
> Any outstanding patches to land?
>
> If not, I will start the release now.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [dev] Cordova config.xml vs package.json?

[Darryl Pogue]

It's not quite as simple as dropping config.xml. In all cases,
config.xml will still need to exist to provide configuration
information about the app.

Historically, when installing platforms and plugins with `--save`,
they were added to config.xml. When running `cordova prepare`, it
would read config.xml and restore any that were listed.
Now that we're using npm for all of our fetching, it makes more sense
to store those platform/plugin dependencies in package.json.

Relevant proposals:
https://github.com/apache/cordova-discuss/blob/master/proposals/save-restore.md
https://github.com/apache/cordova-discuss/pull/53

Currently, Cordova will attempt to use both package.json and
config.xml, and mirror installed plugins to both locations.
Unfortunately, handling of the spec value seems to be buggy depending
on which location it reads from.

It would be great if Cordova 9 could drop the code that mirrors
changes to config.xml and use only package.json, but nobody has really
started work on that yet. The closest is an unfinished helper class
that I was hoping to add to cordova-common to assist with package.json
changes: https://github.com/apache/cordova-common/pull/34

I was also kinda hoping that this could all be tackled as part of the
`cordova install` proposal, but it probably makes sense to handle it
in smaller pieces.


On Tue, Nov 20, 2018 at 9:38 AM Chris Brody  wrote:
>
> My understanding is that Cordova 8 is using both config.xml and
> package.json. Any plugins and platforms specified in config.xml will be
> automatically added in package.json if not already there. My understanding
> is that Cordova will drop config.xml in a new release, forget if this was
> planned for Cordova 9 or not.
>
> Can anyone confirm the following:
>
> Do we plan to drop config.xml support in Cordova 9? If so, any pointers to
> where this was discussed and agreed?
>
> If not, do we plan to drop config.xml support in some other future Cordova
> release? Any pointers to the discussion?

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [VOTE] cordova-android 7.1.3 patch release

[Darryl Pogue]

+1

- npm audit all good
- ran coho verify-archive over release artifacts

On Mon, Nov 19, 2018 at 3:43 PM Jesse  wrote:
>
> +1
>
> - npm audit all good
> - ran coho verify-archive over release artifacts
> - created a new cordova project, and added cordova-android platform ( from
> filesystem ) and build+ran on emulator
>
>
> @purplecabbage
> risingj.com
>
>
> On Mon, Nov 19, 2018 at 2:17 PM Chris Brody  wrote:
>
> > Please review and vote on this cordova-android 7.1.3 patch release, by
> > replying to this email (and keep discussion on the DISCUSS thread)
> >
> > Release changes as proposed in:
> > https://github.com/apache/cordova-android/pull/555
> >
> > The archive has been published to dist/dev:
> > https://dist.apache.org/repos/dist/dev/cordova/GH-555/
> >
> > The package was published from its corresponding git tag:
> > cordova-android: 7.1.3 (e1befaca5a)
> >
> > Note that you can test it out via:
> >
> > cordova platform add https://github.com/apache/cordova-android#7.1.3
> >
> > Upon a successful vote I will upload the archive to dist/, publish it
> > to npm, and post the blog post.
> >
> > Voting guidelines:
> > https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
> >
> > Voting will go on for a minimum of 48 hours.
> >
> > I vote +1:
> > * npm audit shows 0 vulnerabilities
> > * Ran coho audit-license-headers over the relevant repos
> > * Ran coho check-license to ensure all dependencies and
> >   subdependencies have Apache-compatible licenses
> > * Ensured continuous build was green when repo was tagged
> > * Able to run self test on:
> >   https://github.com/brodybits/cordova-sqlite-test-app
> >   with cordova-android version e1befac (7.1.3) from local file system,
> >   along with cordova-sqlite-storage@2.1.5 (with old plugin JAR & .so
> > directory mapping)
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
> >

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [VOTE] Cordova Android 7.1.2 Release

[Darryl Pogue]

The vote has now closed. The results are:

Positive Binding Votes: 4
Darryl Pogue
Chris Brody
Jesse MacFadyen
Gearóid M

The vote has passed.

Thanks everyone for your reviews!


On Tue, Nov 6, 2018 at 3:16 AM Gearóid M  wrote:
>
> +1
>
> - created new project from Github tag, ran as expected
> - tests passing on 7.1.2 branch on Travis CI
>
> On Tue, 6 Nov 2018, at 06:43, Jesse wrote:
> > +1
> >
> > - coho verify-archive
> > - CI green
> > - created a project, added cordova-android@7.1.2 ( via tagged repo ), ran
> > without issue
> >
> >
> >
> >
> > On Mon, Nov 5, 2018 at 1:18 PM Chris Brody  wrote:
> >
> > > +1
> > >
> > > -
> > >
> > > https://github.com/apache/cordova-android/commit/725e75fa0dc35a1b9bbc56c8621121e6dbc4fbdf
> > > (cordova-android@7.1.2
> > > <https://github.com/apache/cordova-android/commit/725e75fa0dc35a1b9bbc56c8621121e6dbc4fbdf(cordova-android@7.1.2>)
> > > is green, passes its own tests OK ✓
> > >
> > > On Mon, Nov 5, 2018 at 3:41 PM Darryl Pogue  wrote:
> > >
> > > > Please review and vote on this 7.1.2 Android 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/android-712
> > > >
> > > > Blog post for review:
> > > > https://github.com/apache/cordova-docs/pull/901
> > > >
> > > > The package was published from its corresponding git tag:
> > > > - cordova-android: 7.1.2 (725e75fa0d)
> > > >
> > > > Note that you can test it out via:
> > > >
> > > > cordova platform add https://github.com/apache/cordova-android#7.1.2
> > > >
> > > > Upon a successful vote I will upload the archive to dist/, publish it
> > > > to npm, and post the blog post.
> > > >
> > > > Voting guidelines:
> > > >
> > > https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
> > > >
> > > > Voting will go on for a minimum of 48 hours.
> > > >
> > > > I vote +1:
> > > > * Ran coho audit-license-headers over the relevant repos
> > > > * Ran coho check-license to ensure all dependencies and
> > > > subdependencies have Apache-compatible licenses
> > > > * Ensured continuous build was green when repo was tagged
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > > For additional commands, e-mail: dev-h...@cordova.apache.org
> > > >
> > > >
> > >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [VOTE] cordova-common 3.0.0 release

[Darryl Pogue]

The vote has now closed. The results are:

Positive Binding Votes: 3

Darryl Pogue
Bryan Ellis
Jesse MacFadyen

The vote has passed.


On Sun, Nov 4, 2018 at 11:15 PM Jesse  wrote:
>
> +1
>
> - coho verify-archive
> - checked out tag, verified commit-sha and history, ran tests
> - ran tests in cordova-lib with cordova-common linked
> - CI green
>
>
> @purplecabbage
> risingj.com
>
>
> On Sun, Nov 4, 2018 at 3:22 AM Bryan Ellis  wrote:
>
> > +1
> >
> >
> > * Confirmed signatures & hashes with `coho verify-archive` (Verified 1
> > signatures and hashes.)
> >
> > * Verified sha1s match tags with `coho verify-tags`.
> > * Checked out tag 3.0.0 and ran test `npm t` successfully.
> >
> > * CI services (Travis & AppVeyor) for tag were green.
> >
> > On Sun, Nov 4, 2018 at 6:25 AM Darryl Pogue  wrote:
> >
> > > Please review and vote on this cordova-common release by replying to
> > > this email (and keep discussion on the DISCUSS thread)
> > >
> > > Archives have been published to dist/dev:
> > > https://dist.apache.org/repos/dist/dev/cordova/common-300/
> > >
> > > The packages were published from their corresponding git tags:
> > > - cordova-common: 3.0.0 (a7dbf098ab)
> > >
> > > Upon a successful vote I will upload the archives to dist/, publish
> > > them to npm, and post the corresponding blog post.
> > >
> > > Voting guidelines:
> > >
> > https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
> > >
> > > Voting will go on for a minimum of 48 hours.
> > >
> > > I vote +1:
> > > * Ran coho audit-license-headers over the relevant repos
> > > * Ran coho check-license to ensure all dependencies and
> > > subdependencies have Apache-compatible licenses
> > > * Ensured continuous build was green when repos were tagged
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > For additional commands, e-mail: dev-h...@cordova.apache.org
> > >
> > >
> >

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[VOTE] Cordova Android 7.1.2 Release

[Darryl Pogue]

Please review and vote on this 7.1.2 Android 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/android-712

Blog post for review:
https://github.com/apache/cordova-docs/pull/901

The package was published from its corresponding git tag:
- cordova-android: 7.1.2 (725e75fa0d)

Note that you can test it out via:

cordova platform add https://github.com/apache/cordova-android#7.1.2

Upon a successful vote I will upload the archive to dist/, publish it
to npm, and post the blog post.

Voting guidelines:
https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md

Voting will go on for a minimum of 48 hours.

I vote +1:
* Ran coho audit-license-headers over the relevant repos
* Ran coho check-license to ensure all dependencies and
subdependencies have Apache-compatible licenses
* Ensured continuous build was green when repo was tagged

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [DISCUSS] cordova-android 7.1.2 patch release

[Darryl Pogue]

What is the status on this release? I keep getting pinged in GitHub
comments asking when it's going to be available.

I have time today to start it and put it up for voting if nobody else has
picked it up.

~Darryl

On Fri, Oct 26, 2018 at 7:46 AM gandhi rajan 
wrote:

> Thanks a lot Chris. Will get in touch with you.
>
> On Friday, October 26, 2018, Chris Brody  wrote:
>
> > I should be able to assist you next week.
> >
> > On Thu, Oct 25, 2018, 12:51 PM gandhi rajan 
> > wrote:
> >
> > > I can try out the release process but need some assistance as its first
> > > time I m doing it. Anyone willing to provide some guidance for me in
> > doing
> > > this?
> > >
> > > On Thursday, October 25, 2018, Darryl Pogue  wrote:
> > >
> > > > Hey folks,
> > > >
> > > > There's been some issues with a bunch of packages published to
> Bintray
> > > > jcenter, and we've been getting a lot of bug reports and PRs to
> > > > reorder the repositories that gradle looks at. We've already merged a
> > > > fix to master, and cherry-picked it to the 7.1.x branch (along with
> > > > some other fixes).
> > > >
> > > > Julio also indicated that some of the cherry-picked fixes will
> resolve
> > > > the longstanding issue of 3rd party plugin compatibility with the new
> > > > Android Studio project structure.
> > > >
> > > > The list of changes and diff on the 7.1.x branch (since 7.1.1) is
> > > > available for viewing at
> > > > https://github.com/apache/cordova-android/compare/7.1.1...36c6f44
> > > >
> > > > Does anyone have any concerns or reasons to delay starting the
> release
> > > > process for 7.1.2?
> > > >
> > > > Further to that, does anyone have time to start the release process?
> > > > I'm swamped at work right now and unlikely to be able to look at it
> > > > until mid-next week :(
> > > >
> > > > ~Darryl
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > > For additional commands, e-mail: dev-h...@cordova.apache.org
> > > >
> > > >
> > >
> > > --
> > > Regards,
> > > Gandhi
> > >
> > > "The best way to find urself is to lose urself in the service of others
> > > !!!"
> > >
> >
>
>
> --
> Regards,
> Gandhi
>
> "The best way to find urself is to lose urself in the service of others
> !!!"
>

[VOTE] cordova-common 3.0.0 release

[Darryl Pogue]

Please review and vote on this cordova-common release by replying to
this email (and keep discussion on the DISCUSS thread)

Archives have been published to dist/dev:
https://dist.apache.org/repos/dist/dev/cordova/common-300/

The packages were published from their corresponding git tags:
- cordova-common: 3.0.0 (a7dbf098ab)

Upon a successful vote I will upload the archives to dist/, publish
them to npm, and post the corresponding blog post.

Voting guidelines:
https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md

Voting will go on for a minimum of 48 hours.

I vote +1:
* Ran coho audit-license-headers over the relevant repos
* Ran coho check-license to ensure all dependencies and
subdependencies have Apache-compatible licenses
* Ensured continuous build was green when repos were tagged

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[DISCUSS] cordova-common v3.0.0 release

[Darryl Pogue]

I believe everything we hoped to merge into cordova-common for the next
major is merged, and we are ready to take the first step[1] towards getting
that released.

Most importantly, this is a necessary step to getting the rest of the
repositories running their tests against cordova-common@3 to uncover any
further issues to be fixed.

Does anyone have any reason to oppose starting a release? I know there are
a lot of wishlist items that aren't finished and didn't get merged, but
that shouldn't be a reason to block the release unless you know for sure
that those changes are required.

If there are no objections, I will start the release process on Saturday
and post to the list for voting.

~Darryl

[1] https://github.com/apache/cordova/issues/10

Re: [DISCUSS] cordova-android 7.1.2 patch release

[Darryl Pogue]

I believe all PRs are merged to the 7.1.x branch, it's just a case of
actually going through the release steps and putting it up to vote.

~Darryl

On Mon, Oct 29, 2018 at 2:18 PM Jesse  wrote:
>
> Okay, back from sabbatical and catching up.
> Which outstanding PRs still need to be merged?
> Is anyone on this already?
>
>
> On Fri, Oct 26, 2018 at 7:46 AM gandhi rajan 
> wrote:
>
> > Thanks a lot Chris. Will get in touch with you.
> >
> > On Friday, October 26, 2018, Chris Brody  wrote:
> >
> > > I should be able to assist you next week.
> > >
> > > On Thu, Oct 25, 2018, 12:51 PM gandhi rajan 
> > > wrote:
> > >
> > > > I can try out the release process but need some assistance as its first
> > > > time I m doing it. Anyone willing to provide some guidance for me in
> > > doing
> > > > this?
> > > >
> > > > On Thursday, October 25, 2018, Darryl Pogue  wrote:
> > > >
> > > > > Hey folks,
> > > > >
> > > > > There's been some issues with a bunch of packages published to
> > Bintray
> > > > > jcenter, and we've been getting a lot of bug reports and PRs to
> > > > > reorder the repositories that gradle looks at. We've already merged a
> > > > > fix to master, and cherry-picked it to the 7.1.x branch (along with
> > > > > some other fixes).
> > > > >
> > > > > Julio also indicated that some of the cherry-picked fixes will
> > resolve
> > > > > the longstanding issue of 3rd party plugin compatibility with the new
> > > > > Android Studio project structure.
> > > > >
> > > > > The list of changes and diff on the 7.1.x branch (since 7.1.1) is
> > > > > available for viewing at
> > > > > https://github.com/apache/cordova-android/compare/7.1.1...36c6f44
> > > > >
> > > > > Does anyone have any concerns or reasons to delay starting the
> > release
> > > > > process for 7.1.2?
> > > > >
> > > > > Further to that, does anyone have time to start the release process?
> > > > > I'm swamped at work right now and unlikely to be able to look at it
> > > > > until mid-next week :(
> > > > >
> > > > > ~Darryl
> > > > >
> > > > > -
> > > > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > > > For additional commands, e-mail: dev-h...@cordova.apache.org
> > > > >
> > > > >
> > > >
> > > > --
> > > > Regards,
> > > > Gandhi
> > > >
> > > > "The best way to find urself is to lose urself in the service of others
> > > > !!!"
> > > >
> > >
> >
> >
> > --
> > Regards,
> > Gandhi
> >
> > "The best way to find urself is to lose urself in the service of others
> > !!!"
> >

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[DISCUSS] cordova-android 7.1.2 patch release

[Darryl Pogue]

Hey folks,

There's been some issues with a bunch of packages published to Bintray
jcenter, and we've been getting a lot of bug reports and PRs to
reorder the repositories that gradle looks at. We've already merged a
fix to master, and cherry-picked it to the 7.1.x branch (along with
some other fixes).

Julio also indicated that some of the cherry-picked fixes will resolve
the longstanding issue of 3rd party plugin compatibility with the new
Android Studio project structure.

The list of changes and diff on the 7.1.x branch (since 7.1.1) is
available for viewing at
https://github.com/apache/cordova-android/compare/7.1.1...36c6f44

Does anyone have any concerns or reasons to delay starting the release
process for 7.1.2?

Further to that, does anyone have time to start the release process?
I'm swamped at work right now and unlikely to be able to look at it
until mid-next week :(

~Darryl

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [VOTE] cordova-lib@8.1.0 minor tools release

[Darryl Pogue]

+1
- coho verify-archive
- coho audit-license-headers
- coho check-license
- npm test on tagged version
- CI was green with tagged version

On Wed, Sep 19, 2018 at 3:44 PM Jesse  wrote:
>
> +1
> - coho verify-archive
> - coho audit-license-headers
> - coho check-license
> - npm test on tagged version
> - CI was green with tagged version
>
> @purplecabbage
> risingj.com
>
>
> On Mon, Sep 17, 2018 at 7:31 PM Chris Brody  wrote:
>
> > Please review and vote on this Tools Release by replying to this email
> > (and keep discussion on the DISCUSS thread)
> >
> > Release issue: https://github.com/apache/cordova-lib/pull/693
> >
> > Minor cordova-lib@8.1.0 minor tools release packages have been
> > published to dist/dev:
> > https://dist.apache.org/repos/dist/dev/cordova/GH-693/cordova-lib-8.1.0.tgz
> >
> > The packages were published from their corresponding git tags:
> >
> > cordova-lib: 8.1.0 (f286b8d208)
> >
> > Upon a successful vote I will upload the archives to dist/, publish
> > them to npm, and post the corresponding blog post.
> >
> > Voting guidelines:
> > https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
> >
> > Voting will go on for a minimum of 48 hours.
> >
> > I vote +1:
> > * Ran coho audit-license-headers over the relevant repos
> > * Ran coho check-license to ensure all dependencies and
> > subdependencies have Apache-compatible licenses
> > * Ensured continuous build was green when repos were tagged
> >
> > Note that I will be offline after 12-15 hours, will be back on Thursday
> > morning.
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
> >

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[iOS] State of Xcode 10 support

[Darryl Pogue]

A few issues have started to come in regarding the state of Cordova
projects on Xcode 10. This is a rough summary of the situation:

Xcode 10 uses a new build system by default (previously available on
an opt-in basis in Xcode 9). The cordova-ios project structure is not
compatible with this new build system and results in failures.
Officially, we do not claim to support Xcode 10.

Currently the best workaround is to opt-out of the new build system.
Users can do this by specifying
`--buildFlag="-UseModernBuildSystem=0"` on the command line, or adding
the following to build.json under the ios key:

"buildFlag": [
  "-UseModernBuildSystem=0"
]


I would like to investigate what is required to get a cordova-ios
project building with the new build system, and (if the changes are
reasonable) try to get a fix into the next major for
cordova-ios@5.0.0. Going to try to get a coworker to help me poke at
this over the next week or so.

Once that's done, we can evaluate the possibility of backporting to a
4.x release, but I consider that low priority given that Xcode 9 will
still be usable for another year and there's a relatively easy
workaround to use the old build system.

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [DISCUSS] Update dependencies for nightly builds in master

[Darryl Pogue]

On Wed, Sep 12, 2018 at 12:29 PM Chris Brody  wrote:
>
> Potentially controversial proposal.
>
> For example: https://github.com/apache/cordova-create/pull/31
>
> The proposal is that Cordova packages in the master branch should
> depend on nightly builds, not on old patch release.
>
> If accepted, I think we should apply a similar change to the master
> branch of all other Cordova tools and platform packages.
>
> I think this would give us better integrity of nightly builds.

We should not need to make any changes to the master branch for
nightlies to point at other nightlies.
As part of the nightly build process, all the other cordova
dependencies of each module are updated to point to the equivalent
nightly versions. So cordova-cli@nightly-x.y.z is using
cordova-create@nightly-x.y.z and cordova-lib@nightly-x.y.z and
cordova-common@nightly.x.y.z. They reference those explicitly, not
using the "nightly" tag.

We should definitely NOT be pointing anything on the master branch to
specific nightly builds. It should point to whatever version (even
unreleased) we depend on, with a ^ caret so npm will grab the latest.

Reminder that nightly builds are for Cordova developer testing, not
for use by end users because they are not approved releases per Apache
policy.

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Release Planning for Next Major Version

[Darryl Pogue]

Hi folks,

In the Hangouts meeting earlier this week, we discussed the effort of
continuing to do bugfix releases of existing release branches compared
to the much larger effort of our roadmap for the next major. The
suggestion was that we should make a major release now, which serves
primarily just to drop node 4 support with almost no other changes,
and then continue on the roadmap items for a future major version.
Essentially, don't get too attached to the concept of a major version
having a bunch of new features ("romantic versioning"), and bump it
because dropping node 4 is considered to be a breaking change
("semantic versioning").

With that in mind, and a bunch of work already in progress, this email
hopes to summarize what work has already been done on master on
various repos and is ready for release, what work is in-progress and
makes sense to include in this next major, and what work would be nice
to complete but not required for this major.

Everything else will get bumped to the next next major, which will
include some larger refactorings.



Next Major
--

Ideally we're aiming to have this sometime in the early fall, after
iOS 12 is released.

This is hopefully only a "major" version in the sense that it drop
support for Node 4, and doesn't contain any changes that require
updates for end users.

Done

* Remove usage of cordova-registry-mapper from tooling
* Remove all old `--no-fetch` code
* Refactor the cordova-fetch code to improve performance
* iOS: Fix for automatic provisioning

In Progress
===
* Drop node 4 support from all repos
* Drop committed node_modules from all platform repos
* iOS: Improved Swift support
* iOS: Bridge WebView plugin for WKWebView transition
* Android: Adaptive Icons support
* Update the Hello Cordova starter to work with WKWebView & safe areas

To Do
=
* Commit package-lock.json in repos
* iOS: Fix CocoaPods support for Xcode 10
* iOS: Anything required for iOS 12 support
* Android: Bring whitelist in-platform



Next Next Major
---

This is where the more ambitious ideas go.

In Progress
===
* Try to drop our Q dependency in favour of native promises
* Splitting platform-specific ConfigParser code out of cordova-common
* iOS: Bring Splashscreen plugin in-platform

To Do
=
* Drop `--browserify` flag from tooling
* Refactor the platform add flow
* Add a `cordova install` command
* Android: Ensure Kotlin support
* Android: Bring SplashScreen plugin in-platform
* iOS: Use LaunchStoryboards in newly generated project
* iOS: Compatibility with Xcode new build system
* Windows: Drop support for Windows 8.1


If you see anything here that is a concern, that I've forgotten to
include, or that you think is too ambitious for the next small major
version, please let me know!

~Darryl

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: Reviving Face-to-Face video meetings?

[Darryl Pogue]

Times in the meeting notes should be in UTC.

On Wed, Aug 15, 2018 at 10:16 AM Chris Brody  wrote:
>
> Thanks Darryl for hosting and taking notes. I was wondering, just out
> of curiosity, which time zone the times are in? CET with daylight
> savings or something else?
> On Wed, Aug 15, 2018 at 1:06 PM Darryl Pogue  wrote:
> >
> > Thanks everyone who attended, it was great to put faces to usernames
> > and have the chance to chat things out!
> >
> > I tried to take some meeting notes, which are available here:
> > https://docs.google.com/document/d/11ozgImr5HV9TqqriL9taRBoSrDE5slKp0AqNFdYUpGs/edit#heading=h.rgw0j11b9pxn
> >
> > On Wed, Aug 15, 2018 at 7:51 AM Darryl Pogue  wrote:
> > >
> > > If you are participating in the meeting, you should be able to join
> > > the hangout from this link:
> > > https://hangouts.google.com/hangouts/_/t6zlmowc4jdyvfnlotns5eimime
> > >
> > > If you are wanting to watch the meeting and participate only in chat,
> > > you can do that here:
> > > http://youtu.be/wu130DQnMVQ
> > >
> > >
> > > On Wed, Aug 15, 2018 at 6:28 AM Chris Brody  wrote:
> > > >
> > > > I just added my comments, looking forward to the link to the meeting.
> > > > On Mon, Aug 13, 2018 at 11:52 PM Darryl Pogue  
> > > > wrote:
> > > > >
> > > > > Rough Agenda (please suggest additions):
> > > > > https://docs.google.com/document/d/1c_dqxVJ8B2RjACB3faIJNljEfpOoBWL0H9lulX82oFk/edit#heading=h.xymt8g6roq2
> > > > >
> > > > > On Mon, Aug 13, 2018 at 1:01 AM Shazron  wrote:
> > > > > >
> > > > > > Thanks Darryl! I'll try to make this one...
> > > > > > On Sat, Aug 11, 2018 at 11:12 AM Darryl Pogue  
> > > > > > wrote:
> > > > > > >
> > > > > > > Okay, it looks like the date that works best for everyone is 
> > > > > > > Wednesday:
> > > > > > >
> > > > > > > Wednesday, August 15th, 2018 at 15:00 - 17:00 UTC
> > > > > > >
> > > > > > > For that event in your local timezone, please consult
> > > > > > > https://www.timeanddate.com/worldclock/fixedtime.html?msg=Cordova+Video+Meeting&iso=20180815T15&p1=1440&ah=2
> > > > > > >
> > > > > > > In the past we've used Google Hangouts on Air so that 
> > > > > > > non-participants
> > > > > > > are able to watch the meeting on YouTube and it's recorded for 
> > > > > > > later.
> > > > > > > I'll try to figure out what's involved in setting that up, and we 
> > > > > > > can
> > > > > > > fallback to something like Skype or Zoom if need be.
> > > > > > >
> > > > > > > I'll also try to put together a rough agenda Google Doc for 
> > > > > > > review on Monday.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > ~Darryl
> > > > > > >
> > > > > > >
> > > > > > > On Thu, Aug 9, 2018 at 2:21 AM Chris Brody 
> > > > > > >  wrote:
> > > > > > > >
> > > > > > > > Looking forward to the final result (hope you send by email), 
> > > > > > > > thanks!
> > > > > > > > On Thu, Aug 9, 2018 at 2:32 AM Darryl Pogue 
> > > > > > > >  wrote:
> > > > > > > > >
> > > > > > > > > Yes! Sorry for missing my intended deadline here, some 
> > > > > > > > > unexpected work
> > > > > > > > > challenges combined with moving house and not having my full 
> > > > > > > > > computer
> > > > > > > > > set up yet have caused me to drop a few things, including 
> > > > > > > > > following up
> > > > > > > > > on scheduling this.
> > > > > > > > >
> > > > > > > > > I've set up a Doodle poll with dates for next week, let's try 
> > > > > > > > > to have
> > > > > > > > > a date picked by this coming Friday (August 10th).
> > > > > > > > >
> > > > > > > > > *** TIMES ARE IN UTC. 

Re: Reviving Face-to-Face video meetings?

[Darryl Pogue]

Thanks everyone who attended, it was great to put faces to usernames
and have the chance to chat things out!

I tried to take some meeting notes, which are available here:
https://docs.google.com/document/d/11ozgImr5HV9TqqriL9taRBoSrDE5slKp0AqNFdYUpGs/edit#heading=h.rgw0j11b9pxn

On Wed, Aug 15, 2018 at 7:51 AM Darryl Pogue  wrote:
>
> If you are participating in the meeting, you should be able to join
> the hangout from this link:
> https://hangouts.google.com/hangouts/_/t6zlmowc4jdyvfnlotns5eimime
>
> If you are wanting to watch the meeting and participate only in chat,
> you can do that here:
> http://youtu.be/wu130DQnMVQ
>
>
> On Wed, Aug 15, 2018 at 6:28 AM Chris Brody  wrote:
> >
> > I just added my comments, looking forward to the link to the meeting.
> > On Mon, Aug 13, 2018 at 11:52 PM Darryl Pogue  wrote:
> > >
> > > Rough Agenda (please suggest additions):
> > > https://docs.google.com/document/d/1c_dqxVJ8B2RjACB3faIJNljEfpOoBWL0H9lulX82oFk/edit#heading=h.xymt8g6roq2
> > >
> > > On Mon, Aug 13, 2018 at 1:01 AM Shazron  wrote:
> > > >
> > > > Thanks Darryl! I'll try to make this one...
> > > > On Sat, Aug 11, 2018 at 11:12 AM Darryl Pogue  
> > > > wrote:
> > > > >
> > > > > Okay, it looks like the date that works best for everyone is 
> > > > > Wednesday:
> > > > >
> > > > > Wednesday, August 15th, 2018 at 15:00 - 17:00 UTC
> > > > >
> > > > > For that event in your local timezone, please consult
> > > > > https://www.timeanddate.com/worldclock/fixedtime.html?msg=Cordova+Video+Meeting&iso=20180815T15&p1=1440&ah=2
> > > > >
> > > > > In the past we've used Google Hangouts on Air so that non-participants
> > > > > are able to watch the meeting on YouTube and it's recorded for later.
> > > > > I'll try to figure out what's involved in setting that up, and we can
> > > > > fallback to something like Skype or Zoom if need be.
> > > > >
> > > > > I'll also try to put together a rough agenda Google Doc for review on 
> > > > > Monday.
> > > > >
> > > > > Thanks,
> > > > > ~Darryl
> > > > >
> > > > >
> > > > > On Thu, Aug 9, 2018 at 2:21 AM Chris Brody  
> > > > > wrote:
> > > > > >
> > > > > > Looking forward to the final result (hope you send by email), 
> > > > > > thanks!
> > > > > > On Thu, Aug 9, 2018 at 2:32 AM Darryl Pogue  
> > > > > > wrote:
> > > > > > >
> > > > > > > Yes! Sorry for missing my intended deadline here, some unexpected 
> > > > > > > work
> > > > > > > challenges combined with moving house and not having my full 
> > > > > > > computer
> > > > > > > set up yet have caused me to drop a few things, including 
> > > > > > > following up
> > > > > > > on scheduling this.
> > > > > > >
> > > > > > > I've set up a Doodle poll with dates for next week, let's try to 
> > > > > > > have
> > > > > > > a date picked by this coming Friday (August 10th).
> > > > > > >
> > > > > > > *** TIMES ARE IN UTC. PLEASE CHECK CONVERSION TO YOUR LOCAL TIME
> > > > > > > BEFORE REPLYING. ***
> > > > > > > https://doodle.com/poll/c6nhksdmv2tgd8rf
> > > > > > >
> > > > > > > I'm hoping we can find something that can work not only for North
> > > > > > > Americans, but also for our European contributors as well as our
> > > > > > > Japanese ones. However, given that those are roughly equally 
> > > > > > > spaced
> > > > > > > around the globe, somebody is probably going to be stuck with
> > > > > > > something outside of ideal hours. You can click twice in the 
> > > > > > > checkbox
> > > > > > > to mark it as "possible, but not ideal".
> > > > > > >
> > > > > > > ~Darryl
> > > > > > >
> > > > > > > On Wed, Aug 8, 2018 at 7:14 PM Bryan Ellis 
> > > > > > >  wrote:
> > > > > > > >
> > > > > > &g

Re: Reviving Face-to-Face video meetings?

[Darryl Pogue]

If you are participating in the meeting, you should be able to join
the hangout from this link:
https://hangouts.google.com/hangouts/_/t6zlmowc4jdyvfnlotns5eimime

If you are wanting to watch the meeting and participate only in chat,
you can do that here:
http://youtu.be/wu130DQnMVQ


On Wed, Aug 15, 2018 at 6:28 AM Chris Brody  wrote:
>
> I just added my comments, looking forward to the link to the meeting.
> On Mon, Aug 13, 2018 at 11:52 PM Darryl Pogue  wrote:
> >
> > Rough Agenda (please suggest additions):
> > https://docs.google.com/document/d/1c_dqxVJ8B2RjACB3faIJNljEfpOoBWL0H9lulX82oFk/edit#heading=h.xymt8g6roq2
> >
> > On Mon, Aug 13, 2018 at 1:01 AM Shazron  wrote:
> > >
> > > Thanks Darryl! I'll try to make this one...
> > > On Sat, Aug 11, 2018 at 11:12 AM Darryl Pogue  wrote:
> > > >
> > > > Okay, it looks like the date that works best for everyone is Wednesday:
> > > >
> > > > Wednesday, August 15th, 2018 at 15:00 - 17:00 UTC
> > > >
> > > > For that event in your local timezone, please consult
> > > > https://www.timeanddate.com/worldclock/fixedtime.html?msg=Cordova+Video+Meeting&iso=20180815T15&p1=1440&ah=2
> > > >
> > > > In the past we've used Google Hangouts on Air so that non-participants
> > > > are able to watch the meeting on YouTube and it's recorded for later.
> > > > I'll try to figure out what's involved in setting that up, and we can
> > > > fallback to something like Skype or Zoom if need be.
> > > >
> > > > I'll also try to put together a rough agenda Google Doc for review on 
> > > > Monday.
> > > >
> > > > Thanks,
> > > > ~Darryl
> > > >
> > > >
> > > > On Thu, Aug 9, 2018 at 2:21 AM Chris Brody  
> > > > wrote:
> > > > >
> > > > > Looking forward to the final result (hope you send by email), thanks!
> > > > > On Thu, Aug 9, 2018 at 2:32 AM Darryl Pogue  
> > > > > wrote:
> > > > > >
> > > > > > Yes! Sorry for missing my intended deadline here, some unexpected 
> > > > > > work
> > > > > > challenges combined with moving house and not having my full 
> > > > > > computer
> > > > > > set up yet have caused me to drop a few things, including following 
> > > > > > up
> > > > > > on scheduling this.
> > > > > >
> > > > > > I've set up a Doodle poll with dates for next week, let's try to 
> > > > > > have
> > > > > > a date picked by this coming Friday (August 10th).
> > > > > >
> > > > > > *** TIMES ARE IN UTC. PLEASE CHECK CONVERSION TO YOUR LOCAL TIME
> > > > > > BEFORE REPLYING. ***
> > > > > > https://doodle.com/poll/c6nhksdmv2tgd8rf
> > > > > >
> > > > > > I'm hoping we can find something that can work not only for North
> > > > > > Americans, but also for our European contributors as well as our
> > > > > > Japanese ones. However, given that those are roughly equally spaced
> > > > > > around the globe, somebody is probably going to be stuck with
> > > > > > something outside of ideal hours. You can click twice in the 
> > > > > > checkbox
> > > > > > to mark it as "possible, but not ideal".
> > > > > >
> > > > > > ~Darryl
> > > > > >
> > > > > > On Wed, Aug 8, 2018 at 7:14 PM Bryan Ellis  
> > > > > > wrote:
> > > > > > >
> > > > > > > Hi Darryl,
> > > > > > >
> > > > > > > I see it had past Aug 3rd and I wanted to find out if we are 
> > > > > > > still planning to set up a web conference.
> > > > > > >
> > > > > > > I am looking forward to the web conference. Please let me know if 
> > > > > > > there is anything I can do to help get this moving.
> > > > > > >
> > > > > > >
> > > > > > > > On Jul 19, 2018, at 14:23, Shazron  wrote:
> > > > > > > >
> > > > > > > > +1!
> > > > > > > > On Thu, Jul 19, 2018 at 1:17 PM Bryan Ellis 
> > > > > > > >  wrote:
> >

Re: Reviving Face-to-Face video meetings?

[Darryl Pogue]

I was hoping to use Hangouts on Air, because then it's also available
for viewing on YouTube, but apparently that doesn't exist anymore and
has been merged into YouTube Live Streaming, which isn't available for
my account. Skype Meetings looks like they require an Office 365
business account.

I think I can do a non-on-air Hangout at
https://hangouts.google.com/hangouts/_/calendar/ZHZwZGluZXIyQGdtYWlsLmNvbQ.5482gan5i8uff8fn1muo1slhil
but we won't be able to livestream it on YouTube :(

On Tue, Aug 14, 2018 at 11:33 PM Rabindra Nayak
 wrote:
>
> Any update on which tool we are going to use for today's meeting
> skype/hangeout/Google .
>
> Rabindra
>
> On Tue, Aug 14, 2018, 09:22 Darryl Pogue  wrote:
>
> > Rough Agenda (please suggest additions):
> >
> > https://docs.google.com/document/d/1c_dqxVJ8B2RjACB3faIJNljEfpOoBWL0H9lulX82oFk/edit#heading=h.xymt8g6roq2
> >
> > On Mon, Aug 13, 2018 at 1:01 AM Shazron  wrote:
> > >
> > > Thanks Darryl! I'll try to make this one...
> > > On Sat, Aug 11, 2018 at 11:12 AM Darryl Pogue 
> > wrote:
> > > >
> > > > Okay, it looks like the date that works best for everyone is Wednesday:
> > > >
> > > > Wednesday, August 15th, 2018 at 15:00 - 17:00 UTC
> > > >
> > > > For that event in your local timezone, please consult
> > > >
> > https://www.timeanddate.com/worldclock/fixedtime.html?msg=Cordova+Video+Meeting&iso=20180815T15&p1=1440&ah=2
> > > >
> > > > In the past we've used Google Hangouts on Air so that non-participants
> > > > are able to watch the meeting on YouTube and it's recorded for later.
> > > > I'll try to figure out what's involved in setting that up, and we can
> > > > fallback to something like Skype or Zoom if need be.
> > > >
> > > > I'll also try to put together a rough agenda Google Doc for review on
> > Monday.
> > > >
> > > > Thanks,
> > > > ~Darryl
> > > >
> > > >
> > > > On Thu, Aug 9, 2018 at 2:21 AM Chris Brody 
> > wrote:
> > > > >
> > > > > Looking forward to the final result (hope you send by email), thanks!
> > > > > On Thu, Aug 9, 2018 at 2:32 AM Darryl Pogue 
> > wrote:
> > > > > >
> > > > > > Yes! Sorry for missing my intended deadline here, some unexpected
> > work
> > > > > > challenges combined with moving house and not having my full
> > computer
> > > > > > set up yet have caused me to drop a few things, including
> > following up
> > > > > > on scheduling this.
> > > > > >
> > > > > > I've set up a Doodle poll with dates for next week, let's try to
> > have
> > > > > > a date picked by this coming Friday (August 10th).
> > > > > >
> > > > > > *** TIMES ARE IN UTC. PLEASE CHECK CONVERSION TO YOUR LOCAL TIME
> > > > > > BEFORE REPLYING. ***
> > > > > > https://doodle.com/poll/c6nhksdmv2tgd8rf
> > > > > >
> > > > > > I'm hoping we can find something that can work not only for North
> > > > > > Americans, but also for our European contributors as well as our
> > > > > > Japanese ones. However, given that those are roughly equally spaced
> > > > > > around the globe, somebody is probably going to be stuck with
> > > > > > something outside of ideal hours. You can click twice in the
> > checkbox
> > > > > > to mark it as "possible, but not ideal".
> > > > > >
> > > > > > ~Darryl
> > > > > >
> > > > > > On Wed, Aug 8, 2018 at 7:14 PM Bryan Ellis 
> > wrote:
> > > > > > >
> > > > > > > Hi Darryl,
> > > > > > >
> > > > > > > I see it had past Aug 3rd and I wanted to find out if we are
> > still planning to set up a web conference.
> > > > > > >
> > > > > > > I am looking forward to the web conference. Please let me know
> > if there is anything I can do to help get this moving.
> > > > > > >
> > > > > > >
> > > > > > > > On Jul 19, 2018, at 14:23, Shazron  wrote:
> > > > > > > >
> > > > > > > > +1!
> > > > > > > > On Thu, Jul 19, 2018 at 1:17 PM Bry