... and platform updates that can break existing functionality, which come out every about every 3 months between our various devices/platforms. If people are willing to not update their devices or machines or software, and there are never any security exploits then everything will just work forever. I think 3-5 years is absurd, browsers barely guarantee that 5 year old html/css/js will work.
@purplecabbage risingj.com On Fri, May 13, 2016 at 10:33 AM, Joe Bowser <[email protected]> wrote: > On Fri, May 13, 2016 at 10:19 AM, julio cesar sanchez < > [email protected]> wrote: > > > But for the CLI? For each platform? > > > > I don't think it makes sense on iOS platform where a new iOS version is > > released every year and apple ends forcing to use latest SDK sooner or > > later, and on new releases some things are broken and people needs to > > update cordova-ios to make them work. > > Might make sense on android wher google allows you to use the sdk you > want > > and things keep working in a "compatibility mode". > > > > I don't think we have the resources to maintain a compatibility mode > version of Cordova for Android and a version that compiles against the edge > version. Also, there's the whole problem with backporting security > vulnerabilities. I know that a lot of people want things to just not > change ever, but that's completely unrealistic given that we have people > trying to attack Cordova-based applications. > > > > > > But making sure the plugins keep working on all the LTS versions for 3-5 > > years will need a lot of work > > > > El viernes, 13 de mayo de 2016, Nikhil Khandelwal < > [email protected]> > > escribió: > > > > > I wanted to bring this to the dev list's attention: > > > https://github.com/cordova/cordova-discuss/issues/39. > > > > > > The idea is to have an LTS version of cordova. It might be a good idea > to > > > re-visit & document our release cadence as well. > > > > > > -Nikhil > > > > > > > > >
