I think we have consensus now to start dropping support for Android 4.4 & 5.0, minimum is now 5.1. Reasoning and explanations are clear to me, seem to be clear to others. I think we would go through the normal process on GitHub, which we know to be a major breaking change.
Switching the browser code to ES6 would be a separate discussion, which I would be interested in as well. Thanks! On Tue, Jan 28, 2020 at 12:02 PM Norman Breau <nor...@normanbreau.com> wrote: > > 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 start converting the > JS ran in the webview to es6. > > On 2020-01-28 12:27 p.m., julio cesar sanchez wrote: > > 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 might not have the webview up to date. > > And devs testing if their apps work on Android 5-6 will probably test on > > emulators, which don't support ES6 and their webview can't be updated. > > > > And worst of all, there are no stats about that, so we can't know for sure > > how many users will be affected by this. > > > > > > > > El mar., 28 ene. 2020 a las 17:14, Bryan Ellis (<er...@apache.org>) > > escribió: > > > >> 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 severe memory leak that users were > >> experiencing and resolved in 5.1. > >> > >> We would set the minSdk higher but that does not mean users cant lower it > >> to support 5.0, at their own risk. This value could be set 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. These are changes that would possibly come. > >> We just have to think about the "updatable webview" when that time comes. > >> > >> > >> On Wed, Jan 29, 2020 at 12:53 AM Chris Brody <chris.br...@gmail.com> > >> 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 usage was my primary reasoning for my +1. > >>> +1 to drop 5.0 and +1 on the reasoning here > >>> > >>> I don't recall seeing a device running 5.0 for quite a few years. I > >>> recall seeing "Android 5" or "Android 5.0" devices actually running > >>> 5.1 or 5.1.1. (Unfortunately my memory is a bit hazy on this.) > >>> > >>> A side question is the how. Would we just set a higher > >>> minimumSdkVersion number (if I spelled it right) or do something else? > >>> > >>> --------------------------------------------------------------------- > >>> 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
