So my intepretation of these comments is: - backport fixes to 2.9 for serious platform breakages and "easy" plugin changes, not new features (new device OS capability such as iOS 7 is considered a new feature) - stop backporting anything to 2.9 when 3.5 comes out
If so, should this be spelled out somwhere, such as cordova.apache.org/blog? On Oct 15, 2013, at 8:24 PM, Brian LeRoux <b...@brian.io> wrote: > 3.5 > > (Or six months.) > > But ya, what Jesse said. > > On Tuesday, October 15, 2013, Jesse wrote: > >> I would not add iOS7 support. >> I would consider adding any plugin changes if it is not too difficult to do >> so. >> >> @purplecabbage >> risingj.com >> >> >> On Tue, Oct 15, 2013 at 4:56 PM, Shazron <shaz...@gmail.com <javascript:;>> >> wrote: >> >>> Nothing is "completely" broken in iOS 7, although with iOS 7 issues that >> is >>> debatable. If we keep patching 2.9.x no one will move on to 3.x... (at >>> least for iOS). There has to be an ending... >>> >>> >>> On Tue, Oct 15, 2013 at 4:53 PM, Jesse >>> <purplecabb...@gmail.com<javascript:;>> >> wrote: >>> >>>> Decide what is completely broken in your platform, that is reasonable >> to >>>> fix, and fix it. >>>> No promises ... just fix what we can, and document that it is fixed. I >>>> think... >>>> >>>> @purplecabbage >>>> risingj.com >>>> >>>> >>>> On Tue, Oct 15, 2013 at 3:10 PM, Shazron <shaz...@gmail.com<javascript:;>> >> wrote: >>>> >>>>> One question about this that was not answered. When does back-porting >>>> end? >>>>> I'm not sure what we promised for 2.9.x support going forward... >>>>> >>>>> >>>>> On Tue, Oct 15, 2013 at 1:16 PM, Jesse >>>>> <purplecabb...@gmail.com<javascript:;> >>> >>> wrote: >>>>> >>>>>> Okay, I am actively working on back-porting plugin fixes into 2.9.1 >>> for >>>>>> WP7, WP8, and Windows8 >>>>>> What is the status of Android, BB, iOS, ... ? >>>>>> >>>>>> >>>>>> >>>>>> @purplecabbage >>>>>> risingj.com >>>>>> >>>>>> >>>>>> On Mon, Oct 7, 2013 at 12:58 PM, Jesse MacFadyen < >>>>> purplecabb...@gmail.com <javascript:;> >>>>>>> wrote: >>>>>> >>>>>>> Yes, now that 3.1.0 is out the door, we can do this. >>>>>>> >>>>>>> Sent from my iPad >>>>>>> >>>>>>>> On Oct 7, 2013, at 10:36 AM, Joe Bowser >>>>>>>> <bows...@gmail.com<javascript:;> >>> >>> wrote: >>>>>>>> >>>>>>>> I think we need to just have everyone go through their work >> over >>>> the >>>>>>>> past month and see if they missed backports. I didn't actually >>>> have >>>>>>>> very much missed, and I just backported the File plugin in the >>>> 2.9.1 >>>>>>>> branch. Of course, with backporting, we need more people to >> look >>>> at >>>>>>>> what was in 3.1.0 and the plugins and check to make sure we >>>> backport >>>>>>>> everything, since this is really tricky and spans all the >> plugin >>>>>>>> repos. :( >>>>>>>> >>>>>>>>> On Mon, Oct 7, 2013 at 10:00 AM, Marcel Kinard < >>>> cmarc...@gmail.com <javascript:;>> >>>>>>> wrote: >>>>>>>>> This thread seems to have gone quiet without a consensus. >> Should >>>>> there >>>>>>> be additional 2.9.x releases going forward? >>>>>>>>> >>>>>>>>> If so, how often? What kind of fixes should be backported? >>> Include >>>>>>> updated docs? >>>>>>>>> >>>>>>>>>> On Oct 1, 2013, at 2:50 PM, Jesse >>>>>>>>>> <purplecabb...@gmail.com<javascript:;> >>> >>>> wrote: >>>>>>>>>> >>>>>>>>>> As soon as we are done with 3.1.0 it would be a good time to >> go >>>>> back >>>>>>> and >>>>>>>>>> back-fill for a 2,9,1 release. >>>>>>>>>> >>>>>>>>>> Who's with me? >>>>>>> >>>>>> >>>>> >>>> >>> >>
