Can you explain why latest plugins will not be compatible with older versions of Cordova? Can this be avoided by any means? When you mean they would not be compatible - will it result in a build or runtime failure?
For marshmallow, what is the guidance that we need to issue to the larger Cordova plugin ecosystem? Joe you are ahead of the curve here compared to most other plugin developers - a blot post explaining what are known gotchas would be great. I really hope we can use our Cordova blog to communicate these changes actively to the plugin ecosystem. This mailing list only gets 400+ subscribers. Can you re-base your cordova-android over the current master? It's hard to see a diff in the current form: https://github.com/apache/cordova-android/compare/master...infil00p:smores -Nikhil -----Original Message----- From: Joe Bowser [mailto:bows...@gmail.com] Sent: Monday, September 21, 2015 2:14 PM To: dev <dev@cordova.apache.org> Subject: [Android] 5.0.x release branch? Hey In the next two weeks, Marshmallow will most likely getting released with the brand new Nexus 6P being released from Huawei. Given that most of the Nexus devices will be getting this release, we should probably release the 5.0.x branch of Android soon, and get the new plugins updated. It should be noted that the latest plugins will not be compatible with older versions of Cordova, which is a big deal. This is due to the use of various compatibility checks to make sure they support Marshmallow and older versions of Android. So, if everyone can look over the smores branches of my GitHub before I create the 5.0.x branch and pull the changes into it, that would be awesome. https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2finfil00p%2fcordova-android%2ftree%2fsmores&data=01%7c01%7cnikhilkh%40microsoft.com%7c1785194b1f82494fc2d908d2c2c99f36%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=%2fPKmL8KTsz5dnC3A75yMatXLQUnfK0Nv07%2bve4PVcCE%3d https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2finfil00p%2fcordova-plugin-geolocation%2ftree%2fsmores&data=01%7c01%7cnikhilkh%40microsoft.com%7c1785194b1f82494fc2d908d2c2c99f36%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=o6cLXM4f3kpUGCTlIv65ft8lKv6pc5qbeY%2bdUxiP4bc%3d https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2finfil00p%2fcordova-plugin-camera%2ftree%2fsmores&data=01%7c01%7cnikhilkh%40microsoft.com%7c1785194b1f82494fc2d908d2c2c99f36%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=kNsHIv6Uw2ITcT1ABmNq1JCmPTSigCGRb4zWC8maWpE%3d https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2finfil00p%2fcordova-plugin-contacts%2ftree%2fsmores&data=01%7c01%7cnikhilkh%40microsoft.com%7c1785194b1f82494fc2d908d2c2c99f36%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=rZ%2f1AALPAtUwgSXyOL1uk1b0Y%2feEmqLOdU%2fwua2TbLU%3d Work on audio is still outstanding, BUT for some reason Audio broke recently on both Lollipop and Marshmallow. I didn't test it out on KitKat or Jellybean yet, but I'm wondering whether we should keep maintaining this or support the standard HTML5 audio and deal with the asset issue somehow (which isn't straight forward). I hopefully want to get a 5.0.x branch happening this week if we can. What do people think? Joe
