Because has been said that some (or most) iOS 6 issues will be not part of it...
On 10/8/12 9:03 AM, "Joe Bowser" <bows...@gmail.com> wrote: >Why do you feel that this release wouldn't be a stable release? > >On Sun, Oct 7, 2012 at 11:37 PM, Giorgio Natili <g.nat...@gnstudio.com> >wrote: >> Just my 2 cents but you don't think is better to wait 2 weeks more and >> have a pretty stable one? >> >> Giorgio >> >> On 10/3/12 7:56 PM, "Simon MacDonald" <simon.macdon...@gmail.com> wrote: >> >>>I think we are looking good for 2.2.0 on Android. It will mostly be a >>>bug fix/performance release for us. I suspect we'll need until 2.3.0 >>>to get all the Camera code sorted. >>> >>>Simon Mac Donald >>>http://hi.im/simonmacdonald >>> >>> >>>On Wed, Oct 3, 2012 at 1:05 PM, Bryce Curtis <curtis.br...@gmail.com> >>>wrote: >>>> It sounds like resolving iOS6 issues will drive when 2.2.0 can be >>>> tagged. What is the readiness of the other platforms so we can have a >>>> 2.2 release when iOS is ready? Does it sound reasonable to have a >>>> release candidate in a week or so, then give a couple of weeks of >>>> testing before tagging 2.2? >>>> >>>> On Tue, Oct 2, 2012 at 10:36 AM, Filip Maj <f...@adobe.com> wrote: >>>>> If you folks see benefit for the iOS implementation, then I'm for >>>>>waiting. >>>>> >>>>> On 10/2/12 8:48 AM, "Andrew Grieve" <agri...@chromium.org> wrote: >>>>> >>>>>>I was thinking the same thing. We still have new iOS6-related bugs >>>>>>being >>>>>>reported, so it might make sense to give this more time. >>>>>> >>>>>> >>>>>>On Tue, Oct 2, 2012 at 11:43 AM, Becky Gibson >>>>>><gibson.be...@gmail.com>wrote: >>>>>> >>>>>>> So, where do we stand on this? I think working towards 2.2 sooner >>>>>>>rather >>>>>>> than later would be the best solution since there appear to be many >>>>>>>issues >>>>>>> with cutting a point release. Where do the other platforms stand >>>>>>>wrt >>>>>>>2.2? >>>>>>> What more needs to be done? >>>>>>> >>>>>>> -becky >>>>>>> >>>>>>> >>>>>>> On Fri, Sep 28, 2012 at 1:38 PM, Michal Mocny <mmo...@chromium.org> >>>>>>>wrote: >>>>>>> >>>>>>> > Nevermind, I'm not able to repro the report. >>>>>>> > >>>>>>> > >>>>>>> > On Fri, Sep 28, 2012 at 1:05 PM, Michal Mocny >>>>>>><mmo...@chromium.org> >>>>>>> wrote: >>>>>>> > >>>>>>> > > someone just reported an issue with FileWriter on ios6 ( >>>>>>> > > https://issues.apache.org/jira/browse/CB-1559) similar to a >>>>>>>FileReader >>>>>>> > > issue I fixed a few weeks back. Fix is likely easy, just >>>>>>>taking >>>>>>>a >>>>>>>look >>>>>>> > > right now to confirm and see if any other things need fixing. >>>>>>>Should >>>>>>> be >>>>>>> > > solved today. >>>>>>> > > >>>>>>> > > >>>>>>> > > On Fri, Sep 28, 2012 at 11:04 AM, Andrew Grieve >>>>>>><agri...@chromium.org >>>>>>> > >wrote: >>>>>>> > > >>>>>>> > >> The main fixes we'll need are: >>>>>>> > >> >>>>>>> > >> 2 days ago Patrick Mueller [ios] route console methods to >>>>>>>original >>>>>>> > >> console commit >>>>>>> > >> | commitdiff | tree | snapshot >>>>>>> > >> 2 days ago Patrick Mueller [ios] route console methods to >>>>>>>original >>>>>>> > >> console commit >>>>>>> > >> | commitdiff | tree | snapshot >>>>>>> > >> 2 days ago Andrew Grieve [ios] Change default bridge from >>>>>>> XHR_NO_PAYLOAD >>>>>>> > >> to... commit | commitdiff | tree | snapshot >>>>>>> > >> 2 days ago Andrew Grieve [ios] Attempt to fix a crash in iOS >>>>>>>XHR >>>>>>> bridge >>>>>>> > >> mode. commit | commitdiff | tree | snapshot >>>>>>> > >> 2 days ago Andrew Grieve [ios] Fix XHR exec bridge not working >>>>>>>for >>>>>>> > >> non-file... commit | commitdiff | tree | snapsho >>>>>>> > >> >>>>>>> > >> However, there were also extra params added to FileTransfer >>>>>>>that >>>>>>>will >>>>>>> > also >>>>>>> > >> need to be included to avoid a JS/Native mismatch. >>>>>>> > >> >>>>>>> > >> There looks to be some Globalization plugin JS commits as >>>>>>>well, >>>>>>>but I >>>>>>> > >> haven't followed whether those will cause issues if left out. >>>>>>> > >> >>>>>>> > >> >>>>>>> > >> On Thu, Sep 27, 2012 at 7:06 PM, Michael Brooks < >>>>>>> > mich...@michaelbrooks.ca >>>>>>> > >> >wrote: >>>>>>> > >> >>>>>>> > >> > When we decide to roll 2.1.1, we should use JIRA to track >>>>>>>the >>>>>>> release. >>>>>>> > >> > Unfortunately, that means JIRA spam... >>>>>>> > >> > >>>>>>> > >> > On Thu, Sep 27, 2012 at 3:44 PM, Filip Maj <f...@adobe.com> >>>>>>>wrote: >>>>>>> > >> > >>>>>>> > >> > > iOS folks: are there any commits needed newer than the >>>>>>>2.1.0 >>>>>>>tag >>>>>>> in >>>>>>> > >> the >>>>>>> > >> > JS >>>>>>> > >> > > for any critical fixes? >>>>>>> > >> > > >>>>>>> > >> > > On 9/27/12 3:40 PM, "Jesse MacFadyen" >>>>>>><purplecabb...@gmail.com> >>>>>>> > >> wrote: >>>>>>> > >> > > >>>>>>> > >> > > >Just iOS afaik >>>>>>> > >> > > > >>>>>>> > >> > > >Cheers, >>>>>>> > >> > > > Jesse >>>>>>> > >> > > > >>>>>>> > >> > > >Sent from my iPhone6 >>>>>>> > >> > > > >>>>>>> > >> > > >On 2012-09-27, at 3:36 PM, Filip Maj <f...@adobe.com> >>>>>>>wrote: >>>>>>> > >> > > > >>>>>>> > >> > > >> So which platforms are we fixing horrible bugs for in >>>>>>>2.1.1? >>>>>>> WP7 >>>>>>> > + >>>>>>> > >> > iOS? >>>>>>> > >> > > >> >>>>>>> > >> > > >> Basically: do any of the failing platforms that >>>>>>>_require_ >>>>>>>fixes >>>>>>> > >> need >>>>>>> > >> > any >>>>>>> > >> > > >> JS fixes? >>>>>>> > >> > > >> >>>>>>> > >> > > >> On 9/27/12 3:32 PM, "Jesse" <purplecabb...@gmail.com> >>>>>>>wrote: >>>>>>> > >> > > >> >>>>>>> > >> > > >>> Where / When are we tagging cordova-js ? >>>>>>> > >> > > >>> >>>>>>> > >> > > >>> >>>>>>> > >> > > >>> >>>>>>> > >> > > >>> On Thu, Sep 27, 2012 at 2:41 AM, Jesse MacFadyen >>>>>>> > >> > > >>> <purplecabb...@gmail.com> wrote: >>>>>>> > >> > > >>>> Not disagreeing. >>>>>>> > >> > > >>>> >>>>>>> > >> > > >>>> Cheers, >>>>>>> > >> > > >>>> Jesse >>>>>>> > >> > > >>>> >>>>>>> > >> > > >>>> Sent from my iPhone6 >>>>>>> > >> > > >>>> >>>>>>> > >> > > >>>> On 2012-09-27, at 2:31 AM, Brian LeRoux <b...@brian.io> >>>>>>>wrote: >>>>>>> > >> > > >>>> >>>>>>> > >> > > >>>>> One click builds are not just for CI! Hand rolling >>>>>>>always >>>>>>> > error >>>>>>> > >> > > >>>>>prone, >>>>>>> > >> > > >>>>> and >>>>>>> > >> > > >>>>> time consuming repatative business like that is a >>>>>>>job >>>>>>>for a >>>>>>> > >> robot. >>>>>>> > >> > > >>>>>You >>>>>>> > >> > > >>>>> then >>>>>>> > >> > > >>>>> can focus on code, and others can see (and therefor >>>>>>>improve >>>>>>> > >> upon) >>>>>>> > >> > > >>>>> release >>>>>>> > >> > > >>>>> packaging. >>>>>>> > >> > > >>>>> >>>>>>> > >> > > >>>>> Regardless of all those benefits we want to get to a >>>>>>>CI >>>>>>> > future. >>>>>>> > >> > > >>>>> >>>>>>> > >> > > >>>>> (recommended reading on this, and more: >>>>>>> > >> > > >>>>> http://pragprog.com/the-pragmatic-programmer) >>>>>>> > >> > > >>>>> >>>>>>> > >> > > >>>>> On Thursday, September 27, 2012, Jesse MacFadyen >>>>>>>wrote: >>>>>>> > >> > > >>>>> >>>>>>> > >> > > >>>>>> I agree in a continuous integration scenario that >>>>>>>makes >>>>>>> > sense, >>>>>>> > >> but >>>>>>> > >> > > >>>>>>we >>>>>>> > >> > > >>>>>> are not there yet, and probably not soon either. >>>>>>> > >> > > >>>>>> >>>>>>> > >> > > >>>>>> Cheers, >>>>>>> > >> > > >>>>>> Jesse >>>>>>> > >> > > >>>>>> >>>>>>> > >> > > >>>>>> Sent from my iPhone6 >>>>>>> > >> > > >>>>>> >>>>>>> > >> > > >>>>>> On 2012-09-26, at 12:46 PM, Brian LeRoux >>>>>>><b...@brian.io> >>>>>>> wrote: >>>>>>> > >> > > >>>>>> >>>>>>> > >> > > >>>>>>> Ya lets not ship a release with different ver >>>>>>>numbers >>>>>>> inside >>>>>>> > >> > > >>>>>>>bundled. >>>>>>> > >> > > >>>>>>> That's askin for (more) issue tracking hell. A >>>>>>>release >>>>>>>tag >>>>>>> > is >>>>>>> > >> > just >>>>>>> > >> > > >>>>>>>a >>>>>>> > >> > > >>>>>>> one >>>>>>> > >> > > >>>>>>> liner / automated. If it isn't: it should be. :p >>>>>>> > >> > > >>>>>>> >>>>>>> > >> > > >>>>>>> On Wednesday, September 26, 2012, Filip Maj wrote: >>>>>>> > >> > > >>>>>>> >>>>>>> > >> > > >>>>>>>> Link fail! >>>>>>> > >> > > >>>>>>>> https://issues.apache.org/jira/browse/CB-1531 >>>>>>> > >> > > >>>>>>>> >>>>>>> > >> > > >>>>>>>> >>>>>>> > >> > > >>>>>>>> On 9/26/12 12:22 PM, "Jesse MacFadyen" < >>>>>>> > >> purplecabb...@gmail.com >>>>>>> > >> > > >>>>>>> > >> > > >>>>>>>> wrote: >>>>>>> > >> > > >>>>>>>> >>>>>>> > >> > > >>>>>>>>> Address which for windows phone? >>>>>>> > >> > > >>>>>>>>> >>>>>>> > >> > > >>>>>>>>> Cheers, >>>>>>> > >> > > >>>>>>>>> Jesse >>>>>>> > >> > > >>>>>>>>> >>>>>>> > >> > > >>>>>>>>> Sent from my iPhone6 >>>>>>> > >> > > >>>>>>>>> >>>>>>> > >> > > >>>>>>>>> On 2012-09-26, at 12:01 PM, Filip Maj >>>>>>><f...@adobe.com> >>>>>>> > >> wrote: >>>>>>> > >> > > >>>>>>>>> >>>>>>> > >> > > >>>>>>>>>> O ya and we should possibly address this for >>>>>>>windows >>>>>>> > phone >>>>>>> > >> 7 >>>>>>> > >> > > >>>>>>>>>>2.1.1 >>>>>>> > >> > > >>>>>>>>>> >>>>>>> > >> > > >>>>>>>>>> Jesse are there any instructions anywhere on >>>>>>>how >>>>>>>to >>>>>>>put >>>>>>> > >> > together >>>>>>> > >> > > >>>>>>>>>> those >>>>>>> > >> > > >>>>>>>>>> starter packages? >>>>>>> > >> > > >>>>>>>>>> >>>>>>> > >> > > >>>>>>>>>> On 9/26/12 10:04 AM, "Jesse MacFadyen" < >>>>>>> > >> > purplecabb...@gmail.com >>>>>>> > >> > > > >>>>>>> > >> > > >>>>>> wrote: >>>>>>> > >> > > >>>>>>>>>> >>>>>>> > >> > > >>>>>>>>>>> I think we should allow some latitude in the >>>>>>>point >>>>>>> > >> releases >>>>>>> > >> > to >>>>>>> > >> > > >>>>>>>>>>> avoid >>>>>>> > >> > > >>>>>>>>>>> the cascade of meaningless tags, and extra >>>>>>>work. >>>>>>> > >> > > >>>>>>>>>>> >>>>>>> > >> > > >>>>>>>>>>> Can we release 2.1.1 and just say that it >>>>>>>contains >>>>>>> 2.1.1 >>>>>>> > >> for >>>>>>> > >> > > >>>>>>>>>>>iOS >>>>>>> > >> > > >>>>>>>>>>> and >>>>>>> > >> > > >>>>>>>>>>> 2.1.0 for the rest? There are no API changes >>>>>>>right? >>>>>>> > >> > > >>>>>>>>>>> >>>>>>> > >> > > >>>>>>>>>>> >>>>>>> > >> > > >>>>>>>>>>> Cheers, >>>>>>> > >> > > >>>>>>>>>>> Jesse >>>>>>> > >> > > >>>>>>>>>>> >>>>>>> > >> > > >>>>>>>>>>> Sent from my iPhone6 >>>>>>> > >> > > >>>>>>>>>>> >>>>>>> > >> > > >>>>>>>>>>> On 2012-09-26, at 9:54 AM, Michael Brooks >>>>>>> > >> > > >>>>>>>>>>> <mich...@michaelbrooks.ca> >>>>>>> > >> > > >>>>>>>>>>> wrote: >>>>>>> > >> > > >>>>>>>>>>> >>>>>>> > >> > > >>>>>>>>>>>> As Becky mentioned, there's some big issues >>>>>>>for >>>>>>>iOS >>>>>>> and >>>>>>> > >> our >>>>>>> > >> > > >>>>>>>>>>>> user's >>>>>>> > >> > > >>>>>>>>>>>> would >>>>>>> > >> > > >>>>>>>>>>>> really like to see a quick patch. >>>>>>> > >> > > >>>>>>>>>>>> >>>>>>> > >> > > >>>>>>>>>>>> I'd be in favour of tagging 2.1.1, where iOS >>>>>>>tags >>>>>>> > master >>>>>>> > >> and >>>>>>> > >> > > >>>>>>>>>>>> every >>>>>>> > >> > > >>>>>>>>>>>> other >>>>>>> > >> > > >>>>>>>>>>>> platform tags 2.1.1 on the same commit as >>>>>>>2.1.0. >>>>>>> > >> > > >>>>>>>>>>>> >>>>>>> > >> > > >>>>>>>>>>>> Michael >>>>>>> > >> > > >>>>>>>>>>>> >>>>>>> > >> > > >>>>>>>>>>>> On Wed, Sep 26, 2012 at 8:59 AM, Brian >>>>>>>LeRoux < >>>>>>> > >> b...@brian.io> >>>>>>> > >> > > >>>>>>>>>>>> wrote: >>>>>>> > >> > > >>>>>>>>>>>> >>>>>>> > >> > > >>>>>>>>>>>>> I'd rather we point 2.1.1 at the 2.1 tag as >>>>>>> suggested >>>>>>> > >> for >>>>>>> > >> > > >>>>>>>>>>>>> Android, >>>>>>> > >> > > >>>>>>>>>>>>> continue work on 2.2 as planned, and ship a >>>>>>>fresh >>>>>>> > >> release >>>>>>> > >> > for >>>>>>> > >> > > >>>>>>>>>>>>> iOS >>>>>>> > >> > > >>>>>>>>>>>>> wherein the big showstopper type problems >>>>>>>exist. >>>>>>> > >> > > >>>>>>>>>>>>> >>>>>>> > >> > > >>>>>>>>>>>>> On Wed, Sep 26, 2012 at 5:48 PM, Joe Bowser >>>>>>> > >> > > >>>>>>>>>>>>><bows...@gmail.com> >>>>>>> > >> > > >>>>>>>>>>>>> wrote: >>>>>>> > >> > > >>>>>>>>>>>>>> I think we should just start cutting a >>>>>>>2.2.0 >>>>>>> release. >>>>>>> > >> > This >>>>>>> > >> > > >>>>>>>>>>>>>> change >>>>>>> > >> > > >>>>>>>>>>>>>> log >>>>>>> > >> > > >>>>>>>>>>>>>> looks too big for a point release and >>>>>>>there's >>>>>>> enough >>>>>>> > >> > > >>>>>>>>>>>>>> improvements >>>>>>> > >> > > >>>>>> to >>>>>>> > >> > > >>>>>>>>>>>>> merit >>>>>>> > >> > > >>>>>>>>>>>>>> it. >>>>>>> > >> > > >>>>>>>>>>>>>> >>>>>>> > >> > > >>>>>>>>>>>>>> That being said, Cordova 2.1.0 still isn't >>>>>>> officially >>>>>>> > >> out, >>>>>>> > >> > > >>>>>>>>>>>>>> which >>>>>>> > >> > > >>>>>>>>>>>>>> complicates things. Any word on that? >>>>>>> > >> > > >>>>>>>>>>>>>> On Sep 26, 2012 6:33 AM, "Andrew Grieve" >>>>>>> > >> > > >>>>>>>>>>>>>> <agri...@chromium.org> >>>>>>> > >> > > >>>>>>>>>>>>>> wrote: >>>>>>> > >> > > >>>>>>>>>>>>>> >>>>>>> > >> > > >>>>>>>>>>>>>>> Another breakage that has been coming up a >>>>>>>lot >>>>>>>is >>>>>>> > that >>>>>>> > >> > the >>>>>>> > >> > > >>>>>>>>>>>>>>> new >>>>>>> > >> > > >>>>>> XHR >>>>>>> > >> > > >>>>>>>>>>>>> bridge >>>>>>> > >> > > >>>>>>>>>>>>>>> didn't work on non file:/// hosted paged. >>>>>>>It's >>>>>>> fixed >>>>>>> > >> now, >>>>>>> > >> > > >>>>>>>>>>>>>>>so >>>>>>> > >> > > >>>>>> would >>>>>>> > >> > > >>>>>>>>>>>>>>> be >>>>>>> > >> > > >>>>>>>>>>>>> good >>>>>>> > >> > > >>>>>>>>>>>>>>> to get it out ther >>>>>>> > >> > > >>> >>>>>>> > >> > > >>> >>>>>>> > >> > > >>> >>>>>>> > >> > > >>> -- >>>>>>> > >> > > >>> @purplecabbage >>>>>>> > >> > > >>> risingj.com >>>>>>> > >> > > >> >>>>>>> > >> > > >>>>>>> > >> > > >>>>>>> > >> > >>>>>>> > >> >>>>>>> > > >>>>>>> > > >>>>>>> > >>>>>>> >>>>> >> >>
