+1 to drop Android 4.4 - 5.0.
+1 to support Android >= 5.1
On 2020-01-28 10:59 a.m., Bryan Ellis wrote:
I would like to open the discussion and vote to *drop Android 4.4 (KitKat)
support* in the upcoming next major release.
As of Dec 2019, Stat Counter reports that the *market share for
+1 for dropping Android 4.4 since it doesn't have updatable webview and
it's a pain to maintain such old chromium version
Do we have a reason for 5.1 instead of 5.0 other than the low usage?
El mar., 28 ene. 2020 a las 16:13, Norman Breau ()
escribió:
> +1 to drop Android 4.4 - 5.0.
> +1 to
+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
I would like to open the discussion and vote to *drop Android 4.4 (KitKat)
support* in the upcoming next major release.
As of Dec 2019, Stat Counter reports that the *market share for Android 4.4
is only at 2.6%*.
Additionally, there is a report of *128 vulnerabilities in Android 4.4.4*.
As far
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.
On 2020-01-28 11:32 a.m., julio cesar sanchez wrote:
+1 for dropping Android 4.4 since it
+1 to drop everything before 5.1
> On Jan 28, 2020, at 7:53 AM, Chris Brody wrote:
>
> +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
My primary view for dropping 5.0 was also based off of low usage.
Obviously there will always be vulnerabilities. The CVE list showed a
dropped from 5.0.0 to 5.0.2 but an increase again in 5.1. This, of course,
will always be expected on minor and major releases.
It was also known that 5.0 has a
+1 on setting the minimum to 5.1
Personally, I always set the minimum for my own apps to 5.1 anyway as React
doesn't work on 5.0 or below without polyfills
On Tue, 28 Jan 2020, at 16:27, julio cesar sanchez wrote:
> I like the "we officially support SDK 22, SDK 21 might work", I'm +1 on SDK
>
I think ES6 is a legit concern. The only way I think we can use ES6
features and *guarantee* there will work for all users is if we use a
transpiler such as babel to convert es6 syntax to es3, or whatever the
minimum we believe to be safe.
So simply dropping 4.4 and 5.0 doesn't mean we can
I like the "we officially support SDK 22, SDK 21 might work", I'm +1 on SDK
22 then
But for ES6, I think that's a bigger problem.
Android 5+ is supposed to have the updatable webview, but that's not always
true, some vendors didn't implement it for some reason.
Also, even if implemented, users
Nightly build #1308 for cordova has succeeded!
The latest nightly has been published and you can try it out with 'npm i -g
cordova@nightly'
For details check build console at
https://builds.apache.org/job/cordova-nightly/1308/consoleFull
-
Jenkins for Apache Cordova
11 matches
Mail list logo