FYI I think it should be no problem to find a free or affordable survey
tool, found a couple articles from a quick search:
- https://blog.hubspot.com/service/free-survey-maker-software
- https://www.webfx.com/blog/internet/11-free-online-survey-tools-compared/
On Mon, Nov 6, 2023 at 4:29 PM
As a counterpoint I would propose just releasing what we have as 7.0.0.
This would get all of our existing work into developer's hands and reduce
the number of things that could be issues coming in from the field. I think
this would be more agile and more consistent with the modern philosophy of
+1
I do have a super-minor nit that the #deprecation-notice part of the link
in the cordova-docs PR does not seem to have any effect. There seems to be
no deprecation-notice anchor in the updated readme in cordova-osx.
On Mon, Mar 21, 2022 at 6:27 AM Niklas Merz wrote:
> Last call! I did all
I think there is an issue with using plug-ins together with Cordova-osx
would be happy to further explain or demonstrate if needed.
On Tue, Feb 1, 2022, 2:43 PM Niklas Merz wrote:
> Hi all,
>
> I just merged a PR [1] that makes the OSX platform work on M1 Macs,
> because some people need it.
I would recommend that you ask for this to be documented in cordova-docs.
Others may recommend that you go to Slack or, unfortunately, Stack Overflow.
There are freelancers such as myself who would be happy to investigate and
document these things for hire as well.
On Tue, Jul 20, 2021 at 5:03
> >> code, in which case the solution seems to be to install version
> >> 21.0.6113669 instead of 22.1.7171670. If this is the case, it would be
> up
> >> to the user (or the plugin author, if they decide to take
> responsibility)
> >> to ensure that the environmen
Hello I just encountered this after having reinstalled my system on macOS,
installing recent NDK via Android Studio:
Starting a Gradle Daemon (subsequent builds will be faster)
*> Task :app:stripDebugDebugSymbols* FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution
FYI the build seemed to be red due to a timeout; I just restarted the
build; hope it will be green.
On Tue, Mar 30, 2021 at 1:46 PM Norman Breau wrote:
> 9.0 used the latest available release at the time of the release with no
> issue. Gradle 6.5 is just the minimum required version according
021-02-01 11:40 p.m., Chris Brody wrote:
> > Just to be pedantic: do we know what would have happened if someone tried
> > installing this plugin with cordova-ios 6?
> >
> >
> > On Mon, Feb 1, 2021 at 10:28 PM Bryan Ellis wrote:
> >
> >> +1 for the pat
gt; > No you're right, it should have a major version bump. I can prepare a
> > > PR to do this.
> > >
> > > On 2021-02-01 11:14 p.m., Chris Brody wrote:
> > >> Shouldn't the goal "not to install on cordova-ios 6.x or above" be
> > >> considered a
Shouldn't the goal "not to install on cordova-ios 6.x or above" be
considered a breaking change? Or am I being too pedantic about this?
On Mon, Feb 1, 2021 at 10:09 PM Norman Breau wrote:
> Hi team,
>
> I'm planning on making a release for cordova-plugin-wkwebview-engine
> version 1.2.2.
> The
Approved with the following nit:
I noticed that for some reason, the 6.2.0 tag is *not* on the master branch.
I recall this happening in the past and am definitely aware that this
happens due to the way that cordova-coho works.
I sincerely hope that steps will be taken to keep major and minor
Hi Julian I would recommend you consider announcing and sharing
whatever you have, in case it may help others or receive any contributions.
Thanks!
On Tue, Dec 22, 2020 at 11:28 AM Julien Lamure
wrote:
> Hi Mathias,
>
> With this feature, we don't need to do anything on the device to be able
>
/1118
On Fri, Sep 4, 2020 at 9:59 AM Chris Brody wrote:
> Yes I think this needs a formal vote. I will look up the template, would
> appreciate any pointers.
>
> I think there should be separate votes to deprecate cordova-osx and
> cordova-windows.
>
> I am setting the
The 2 weeks since the last hangout which I missed sure went fast. I wonder
if once a month would be enough to keep us in sync?
On Thu, Oct 29, 2020 at 10:23 AM Jesse wrote:
> Hello Cordova,
>
> Sorry all, I totally zoned out on the hangout schedule this week. I won’t
> be able to
https://youtu.be/lPe6_YF9L9Q
discussions in a public
forum such as email or public Slack channel.
On Wed, Sep 16, 2020 at 7:35 PM Chris Brody wrote:
> I may be a little late due to a previously scheduled meeting.
>
> I would love it if we can find out what the objections were to using the
> donation towa
I may be a little late due to a previously scheduled meeting.
I would love it if we can find out what the objections were to using the
donation towards updating the documentation, and if there is anything we
could do to address those objections.
On Wed, Sep 16, 2020 at 7:29 PM Norman Breau
I completely understand, thanks for the quick turnaround:)
On Thu, Sep 10, 2020 at 2:53 AM Jesse wrote:
> Thanks Chris,
>
> I added a blurb, Report has been posted.
> Sorry for the short turn around on this one,
>
> Cheers,
> Jesse
>
> On Wed, Sep 9, 2020 at
I think we should include a note that there is a donation and there is
ongoing discussion what to do with it.
On Wed, Sep 9, 2020 at 11:17 PM Jesse wrote:
> The quarterly board report draft is here:
> https://github.com/apache/cordova-apache-board-reports/pull/11
>
> Comments, additions,
Here is the repository on GitHub for quick reference:
https://github.com/apache/cordova-plugin-network-information
Unfortunately I am not familiar enough to make the 3.0.0 release. I would
recommend that you ping others on Slack and maybe raise an issue on GitHub.
Maintainers seem to be somewhat
:
> Hi,
>
> correct me if I'm wrong, but isn't the deprecation missing a formal vote?
>
> Best,
> Tim
>
> On Fri, Sep 4, 2020 at 4:52 AM Chris Brody wrote:
>
> > I have now raised the following PRs:
> >
> > - https://github.com/apache/cordova-lib/pul
+1 from me
>
> Am 26. Juni 2020, 03:20, um 03:20, Chris Brody
> schrieb:
> >I would continue to vote for immediate deprecation of both cordova-osx
> >and
> >cordova-windows.
> >
> >Not only would cordova-osx lose relevance due to both Catalyst and
>
At this point I would be a little reluctant to start supporting more
plugins.
Issues and unmerged PRs seem to keep piling up in multiple places. Here are
a couple of very sad examples:
- https://github.com/apache/cordova-ios/pull/795
- https://github.com/apache/cordova-plugin-file/pull/242
On
I would favor discussing this idea in
https://github.com/apache/cordova/issues or
https://github.com/apache/cordova-discuss/issues
I am thinking it would be really nice if Cordova would use the Cordova
plugin packages from node_modules rather than plugins in the future. I
think this would be more
Someone had an idea to convert Cordova into a single monorepo. There
are some very well-known benefits, and it would help us to keep the
issues and discussions all in one place. Lerna seems to be a nice tool
to keep things consistent and in sync.
I think the original PhoneGap that Cordova was
+1
On Thu, Aug 20, 2020 at 3:30 PM Darryl Pogue wrote:
>
> Anyone have any objections to making a cordova-ios 6.1.1 patch release?
> Namely, it fixes an issue where deploying to devices doesn't work.
>
> Diff from 6.1.0:
> https://github.com/apache/cordova-ios/compare/6.1.0...master
>
> I don't
> `draft/` tag prefix is for drafts
+1
> `rel/` tag prefix is for releases
+1
> No more clean tags will be created
OK as discussed below
> `rel/` tags has and will always be the accepted release tag, unless changed
> in the future.
+1
> We never used clean tags as an official release. We
> https://nodejs.org/en/about/releases/
>
>
>
> > On Aug 18, 2020, at 6:31 AM, Chris Brody wrote:
> >
> >
> >>
> >> * When releasing a patch, deprecate the last patch release within the
> same subset.
> >
> > +1
>
> > The name "draft" for tags in the release process is not that clear to me. I
> > suggest "rc" for release candidate. And yes we should clean these tags up.
-1 on "rc" on my part. I have seen other projects use "rc" to mean an
rc version that comes before a stable version.
> During the vote,
> * When releasing a patch, deprecate the last patch release within the same
> subset.
+1
> * When releasing a minor, nothing happens.
I would favor a slightly more flexible approach on this:
- only support 1-2 minor versions back
- It goes without saying that if a security release needs a
My understanding from private correspondence is that this is open for
anyone to join or listen into (Jesse can you clarify?) and join the poll on
Doodle, priority is of course a little higher for committers & PMC members.
Thanks Jesse for organizing this, much needed!
On Mon, Aug 17, 2020 at
I think we should not be making our own password-based or other secure
build tools within the Cordova project unless it is absolutely necessary.
This looks like a problem that is not unique to Cordova app development.
I think this is something that should be done by other tools such as
Gradle,
this release. Even if we add warnings, that
> can be done in a minor release.
>
> El El lun, 29 jun 2020 a las 4:05, Chris Brody
> escribió:
>
> > Thanks. Am I right to assume we can start the deprecation in a minor
> > release?
> >
> >
> > On Sun, Jun 28,
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
platform major releases are not required to be performed before a major
> release of Lib or CLI. They can be released at any time. Only a patch/minor
> release of Lib and CLI is needed.
>
>
> > On Jun 29, 2020, at 10:15, Chris Brody wrote:
> >
> > I think src/platforms/p
I think src/platforms/platformsConfig.json should be updated for the recent
cordova-osx & upcoming cordova-android major releases.
I would also like to see cordova-osx and cordova-windows deprecated now,
for reasons discussed in another thread:
- cordova-osx has outdated platform name (minor)
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
>
> June 24, 2020 4:40 AM, "Chris Brody" wrote:
>
+1, with some comments:
Tag for 9.0.0 looks consistent between git and the coho output.
I tested adding cordova version 9.0.0 from GitHub into
cordova-sqlite-storage test app.
A major customer has been using recent cordova-android version from GitHub,
as needed to get the response cutoff bugfix
It seems to me like both cordova-osx and cordova-windows are now outdated
for various known reasons:
- cordova-osx has outdated platform name and does not support CocoaPods
- cordova-windows requires previous Visual Studio version 2017 to build
Given that:
- These desktop platforms are known to
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 X
+1
- confirmed that the proposed published git tag for cordova-osx 6.0.0 is
consistent with the cordova-osx 6.0.0 tag on GitHub
- installed apache/cordova-ios version 6.0.0 from GitHub into the
cordova-sqlite-storage test app and ran the test app from the command line
On Tue, Jun 23, 2020 at
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
I think we should add a couple more labels for awaiting response and needs
investigation.
Maybe rename info-needed to awaiting-response?
My one objection is what looks like lack of handling of external
contributions, in particular this one:
https://github.com/apache/cordova-android/pull/971
On Thu, Jun 11, 2020 at 10:42 PM Bryan Ellis wrote:
> I am looking at restarting this thread.
>
> Let’s get this release going by Friday of
For some reason the cordova-android build on GitHub seems to be flakey due
to a TCP connect timeout in the codecov action. I had been able to get it
green by restarting the build but hope we can find a better solution.
Sorry for the bother - any chance for a review of this proposal:
https://github.com/apache/cordova-android/pull/987
I would like to merge this soon if there are no objections. It would
definitely reduce the support burden for a major customer.
Thanks!
To be clear, I would definitely not favor blocking this release. Thanks
again.
On Mon, Jun 8, 2020 at 8:12 AM Chris Brody wrote:
> While it would be ideal to get this fixed, ideally by migrating to GitHub
> actions, probably not worth holding up the release.
>
> Thanks f
While it would be ideal to get this fixed, ideally by migrating to GitHub
actions, probably not worth holding up the release.
Thanks for your work on this.
On Mon, Jun 8, 2020 at 3:19 AM Niklas Merz wrote:
> The master branch is now ready for release.
>
> While trying to get another PR in, I
It looks like cordova-android expects Java/JDK 1.8 to be installed. But my
understanding is that it should be possible to use a newer OpenJDK version
such as 13. See this thread on Homebrew:
https://discourse.brew.sh/t/gradle-and-jdk-dependency/7969
As I said in that thread, I was able to use
Looks like we missed breaking PR #795:
https://github.com/apache/cordova-ios/pull/795
I just put #795 into new 7.0.0 milestone, along with the podspec issue:
https://github.com/apache/cordova-ios/issues/887
On Wed, May 20, 2020 at 4:13 AM Bryan Ellis wrote:
> This is a followup, I will be
ouldn't block a release.
>
> Am 04.06.20 um 17:14 schrieb Chris Brody:
> > I would favor updating the minimum Cordova requirement in both
> package.json
> > and plugin.xml, as I just commented in PR #685. I wish I would have seen
> it
> > before PR #685 was merged.
>
I would favor updating the minimum Cordova requirement in both package.json
and plugin.xml, as I just commented in PR #685. I wish I would have seen it
before PR #685 was merged.
On Thu, Jun 4, 2020 at 10:59 AM Niklas Merz wrote:
> I merged two outstanding patches just now.
>
> If no reviews
data
load.
On Sun, May 24, 2020 at 1:23 PM Chris Brody wrote:
> In this source:
> https://github.com/apache/cordova-android/blob/master/framework/src/org/apache/cordova/NativeToJsMessageQueue.java
>
> the MAX_PAYLOAD_SIZE seems to be 500 MB which could be way, way too large.
> I
In this source:
https://github.com/apache/cordova-android/blob/master/framework/src/org/apache/cordova/NativeToJsMessageQueue.java
the MAX_PAYLOAD_SIZE seems to be 500 MB which could be way, way too large.
I have client who reported an issue with OutOfMemoryError, looks like an
attempt to
off-topic: unfortunately I have extremely limited time to review these
proposals. I can probably take a look later next week if needed, may need a
reminder. I do hope some others will have a chance to review and vote on
the new release packages.
On Mon, Apr 6, 2020 at 8:11 AM Bryan Ellis wrote:
how to get this going. I guess we need to find a technical
> > > writer/developer capable of doing it.
> > >
> > > {1} https://cordova.apache.org/howto/2020/03/18/wkwebviewonly.html
> > >
> > > April 1, 2020 2:58 AM, "Chris Brody" wrote:
>
Improvement has already been sponsored by an anonymous donor. Repeated
requests for help with getting it started have been met with no response so
far. I think this recent thread is an example of how our documentation
could use some improvement:
The answer is already documented. We would really appreciate it if users
could a little more research since maintainers are generally overloaded,
especially while they are busy with a new major release.
That said, here is a recommended link that I found from a quick search:
Triggered by this:
https://github.com/apache/cordova-plugin-battery-status/pull/82
I am now wondering if there is any more need for us to continue Windows
platform support, now that both the major backer and VS 2019 support are
gone?
I think it is self-evident that our maintainer resources are
I vote +1
- listed package git ID matches 4.0.0 on GitHub
- it is green on GitHub
- I downloaded & extracted the proposed TGZ file; diff -u --recursive shows
me that all significant artifacts are in place with no changes
- npm audit shows me no warnings
As a side question: my understanding from
I am assuming this will wait for cordova-eslint, which I hope will include
the recent proposals in a new major (since eslint upgrade should be
considered breaking).
I do also find it a bit unfortunate that we cannot drop q without potential
repercussions.
On Mon, Mar 23, 2020 at 2:41 AM Bryan
I wouldn't mind a new major release with the proposed changes together.
On Mon, Mar 23, 2020 at 2:37 AM Bryan Ellis wrote:
> Does anyone have any reason to delay a cordova-eslint minor release
> (2.1.0)?
>
> Any additional outstanding changes to land?
>
> The follow will be merged for this
ated, is a breaking
> change. At least in other plugins we did a major release after that.
>
> El vie., 20 mar. 2020 a las 19:22, Chris Brody ()
> escribió:
>
> > Can you remind forgetful people like me what would trigger a major
> release
> > here?
> >
> >
ays. Triage PRs and try to
> prepare a major.
>
> Am 20. März 2020, 17:01, um 17:01, Chris Brody
> schrieb:
> >+1 for making the release if we can get some of the more important PRs
> >merged soon.
> >
> >We do have discussions of deprecating plugins but I think
+1 for making the release if we can get some of the more important PRs
merged soon.
We do have discussions of deprecating plugins but I think they are not
really solid plans yet.
On Fri, Mar 20, 2020 at 11:42 AM julio cesar sanchez
wrote:
> The idea was to integrate it into the platforms, but
At this point we do not seem to have a good way to track plugin
documentation issues like this recent one:
https://github.com/apache/cordova-plugin-screen-orientation/issues/59
An idea to start using labels would be nice, don't know how we can do the
search across multiple plugin repositories.
I noticed a question on the PMC Slack channel if there were any kind of
formal coding styles?
It seems like we don't have much of any, beyond starting to use a new
@cordova/eslint-config which seems to be based on semistandard (with indent
spacing of 4) and almost the same as how we have linted
I think we should add some kind of tracking for this project:
https://github.com/apache/cordova-docs/issues/1057
Basically, this is the PMC donation that was received for the purpose of
improving cordova-docs.
I have sent multiple requests for some help and guidance from Apache
Fundraising with
Thanks Niklas for getting this started, it is definitely much needed.
I will likely need a bit more time to take a proper look.
One thing I think should be improved is that the team page should have its
own link in the header bar, next to: "Contribute" for example.
Another thing is that I would
; being an official PMC member.
> >
> > This is just my opinion. @Chris I thinks it's good that you brought up
> > this discussion. I just wanted to point out that we should think
> carefully
> > before introducing another channel. It can become hard to follow-up all
>
I started thinking it might be cool to have Cordova dev discussions in
issues separate from apache/cordova/issues, which I think is the standard,
default place where users raise general issues they encounter and where we
can communicate major things such as breaking changes and deprecated
I just raised and pinned an issue to drop support for platform-centered
workflows, as already discussed on GitHub. I did also unpin
https://github.com/apache/cordova/issues/142 (sharable ESLint config) to
hopefully ensure the user community can see the major functionality we
would like to
Please raise this on cordova-docs, thanks. And please do feel free to
follow up with us. I hope you will understand that maintainers seem to be a
bit overloaded these days.
On Tue, Feb 11, 2020 at 9:30 PM Roopmay Roy wrote:
> Hi,
> We have developed an application using Cordova and it has done
+100
On Mon, Feb 10, 2020 at 8:51 AM Bryan Ellis wrote:
> I would like to open the discussion and vote to *update the Cordova iOS
> Xcode "Project Format" setting to Xcode 11-compatible* for the upcoming
> next major release.
>
> I have already created a PR that performs the changes but would
in config.xml.
> >>
> >> What we would say could be along the lines of, it might work with 5.0 but
> >> we officially support is 5.1.
> >>
> >> Lastly, if we started to convert the browser code to ES6, for example, it
> >> will not work on Android 4.4.
+1 to drop Android 4.4 support
> Do we have a reason for 5.1 instead of 5.0 other than the low usage?
>
> Originally, I was thinking 5.0+, but after seeing low usage, I leaned
> over to 5.1. So low usage was my primary reasoning for my +1.
+1 to drop 5.0 and +1 on the reasoning here
I don't
We can see from issues like
https://github.com/xpbrew/cordova-sqlite-storage/issues/856 that extremely
weird behavior can happen when projects become outdated.
I think there should be a CLI command that cleans up the project workarea:
purge out old plugins and platforms and ensure that all
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
+1
Tested from master branch on GitHub using
https://github.com/dpa99c/cordova-plugin-inappbrowser-test
on iOS for 3.2.0 RC2 (no changes to Android since first 3.2.0 minor release
candidate)
checked that the git tag is consistent
On Mon, Jan 6, 2020 at 1:39 AM Niklas Merz wrote:
> Please
The vote has now closed. Thanks to Niklas and Jesse for the quick response!
The results are:
Positive Binding Votes: 3
* Niklas Merz
* Jesse MacFadyen
* Chris Brody
Negative Binding Votes: 0
The vote has passed.
On Mon, Jan 6, 2020 at 2:16 AM Jesse wrote:
> +1
>
> - coho verif
Can I get one more vote on the VOTE thread for this?
This has a bug fix for WinJS that has been waiting since last April.
On Wed, Jan 1, 2020 at 3:07 PM Niklas Merz wrote:
> @Chris Brody Great, you should see your key automatically added to
> https://people.apache.org/keys/group/cordo
+1
I tested from master branch on GitHub using
https://github.com/dpa99c/cordova-plugin-inappbrowser-test
(which should have the exact same behavior as proposed release 3.2.0)
Basic InAppBrowser functionality works on Android and iOS
I checked that the git tag is consistent.
On Sat, Jan 4,
I would favor unblocking 3.2.0 by merging PR #584 and leaving PR #503 for
another release. (#503 looks like a minor improvement that not many people
are waiting for.)
would be happy to give the new release a try in Dave Alden's inappbrowser
test app, cannot promise I will get very far with it.
I just added my gpg fingerprint to my profile in id.apache.org, as
suggested by Niklas Merz. I hope I did it right, please let me know if I
got it wrong. Thanks for the quick review.
On Sun, Dec 29, 2019 at 2:03 PM Chris Brody wrote:
> Resending with version number corrected in both subj
I generally clone with the https address and then add a second git remote
with the ssh URL that I can push to.
I use this technique to hopefully reduce the chance of doing git push with
something wrong.
One trick I discovered is that you can use the https address from the
address bar when
Happy New Year! Please review and vote on this cordova-windows@7.0.1 patch
release by replying to this email (and keep discussion in the DISCUSS
thread).
A quick review of the release notes would be much appreciated as well:
https://github.com/apache/cordova-docs/pull/1048
Please note the
d helps.
>
> On Tue, Dec 31, 2019 at 10:37 AM Bryan Ellis
> wrote:
>
> > A minor release is currently in progress so we will not do a major
> version
> > bump until the minor is finished.
> >
> > On Tue, Dec 31, 2019 at 10:29 AM Chris Brody
> > wrote:
I would like to propose that we do this major version bump, review
https://github.com/apache/cordova-plugin-inappbrowser/pull/600 then merge
it in order to resolve multiple issues stemming from window.open overwrite.
My purpose is to help relieve some plugin support burden moving forward.
I
Resending with version number corrected in both subject and body:
Does anyone have any reason to delay a cordova-windows 7.0.1 patch release?
Any outstanding patches to land?
If not, I will start the release tomorrow.
Purpose is to resolve an issue with WinJS which seems to affect many users
Gracias - my bad!
New email with the correct version in the subject is coming for the sake of
maximum possible clarity on my part.
On Sun, Dec 29, 2019 at 1:57 PM julio cesar sanchez
wrote:
> 7.0.1, not 2.0.1
>
> El El dom, 29 dic 2019 a las 19:46, Chris Brody
> escribió:
>
Does anyone have any reason to delay a cordova-windows 2.0.1 patch release?
Any outstanding patches to land?
If not, I will start the release tomorrow.
Purpose is to resolve an issue with WinJS which seems to affect many users
including myself. I have cherry-picked a very limited number of
Thanks to Jesse MacFadyen and Niklas Merz for the timely review of my build
during this special season. Would anyone mind giving me a quick review of
the release notes here: https://github.com/apache/cordova-docs/pull/1037
On Sun, Dec 22, 2019 at 10:51 AM Chris Brody wrote:
> I did update
pache/cordova-coho/blob/master/docs/setting-up-gpg.md#importing-pmc-members-pgp-keys
>
> That may be correct, but I stumbled on this while verifying.
>
> Regards Niklas
>
>
>
> From: "Chris Brody"
> To: dev@cordova.apache.org
> Date: 18.12.2019 19:08
&g
the rejected tag of platform
release does follow the documented cordova-coho procedure ref:
https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md#if-the-vote-does-not-pass
On Sat, Dec 21, 2019 at 7:35 PM Chris Brody wrote:
> I think I will have to close out the V
ve
> - CI is green
> - reviewed changes
>
> On Sun, Dec 15, 2019 at 7:12 PM Chris Brody wrote:
>
> > Please review and vote on this cordova-windows@7.1.0 release by
> > replying to this email (and keep discussion on the DISCUSS thread)
> >
> > The a
ago has a bad bug with WinJS (
https://github.com/apache/cordova-windows/issues/341).
On Thu, Dec 19, 2019 at 6:28 PM Chris Brody wrote:
> Thanks Bryan. I tried to make cut a release with no more changes to
> cordova.js than had already been applied before. Reason is that I wanted to
t version.
> >>
> >>
> >> This file needs to be either:
> >>
> >> A) fixed first before continuing the release
> >>
> >> B) confirmed that it is no longer used anywhere in code.
> >>
> >>
> >> If it can be conf
Sorry for the delay!
>
> Sent from my iPhone
>
> > On 18. Dec 2019, at 7:07 PM, Chris Brody wrote:
> >
> > Any chance I can get a couple reviews on the VOTE thread?
> >
> >> On Thu, Dec 12, 2019 at 8:15 PM Chris Brody
> wrote:
> >>
> >&
Any chance I can get a couple reviews on the VOTE thread?
On Thu, Dec 12, 2019 at 1:22 PM Chris Brody wrote:
> I am now starting the release process. In case of any objections please
> send **immediately**.
>
> On Sun, Dec 1, 2019 at 8:03 PM Chris Brody wrote:
>
>> I will
1 - 100 of 415 matches
Mail list logo
