Jesse is away until Thursday or Friday so the windows platforms won't get tagged until then (unless someone has an environment setup to be able to test for all those platforms). So the release wouldn't get out until Monday anyways..
I stay we stick to it and release 2.4.0 on Monday. If something is broken, we can always do a 2.4.1, or if it can wait, 2.5.0rc1. On 1/29/13 12:41 PM, "Andrew Grieve" <[email protected]> wrote: >I can tag JS & iOS & Android @ rc2 today. > > >On Tue, Jan 29, 2013 at 3:33 PM, Becky Gibson ><[email protected]>wrote: > >> would be nice if we could tag a cordova-js so we are all working off the >> same version >> >> >> On Tue, Jan 29, 2013 at 2:29 PM, fabian boulegue <[email protected]> >>wrote: >> >> > Even if its no change on official repo maybe we should test it in a >>small >> > group...? >> > >> > _____________________ >> > Fabian Boulegue >> > tea inc. >> > CEO - Founder >> > Meierbrede 9 >> > 33100 Paderborn >> > >> > Mobile >> > >> > Am 29.01.2013 um 20:27 schrieb Filip Maj <[email protected]>: >> > >> > > The reason we aimed for Monday is because we have various >>committers in >> > > transit atm and tagging is difficult today + tomorrow. >> > > >> > > On 1/29/13 11:20 AM, "Steven Gill" <[email protected]> wrote: >> > > >> > >> Could we just tag iOS rc2 today and still aim to release 2.4.0 on >> > Monday? >> > >> People interested in testing could just work off the source. >> > >> >> > >> -Steve >> > >> >> > >> On Tue, Jan 29, 2013 at 11:14 AM, Andrew Grieve >> > >> <[email protected]>wrote: >> > >> >> > >>> Changes of note: >> > >>> [CB-2235] Fixed file transfer whitelisting for iOS6. >> > >>> [CB-2290] iOS: 'CDVJSON.h' file not found when adding a plugin >> > >>> Fixed InAppBrowser becoming subject to the opener's whitelist >> > >>> Fixed InAppBrowser not working on iOS5 >> > >>> >> > >>> On Android, I don't see any changes since the tag that warrant an >> rc2. >> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > >>> On Tue, Jan 29, 2013 at 1:57 PM, Filip Maj <[email protected]> wrote: >> > >>> >> > >>>> I'll defer to Andrew's opinion as he has been hands-on with the >>iOS >> > >>> repo >> > >>>> recently (at least more than I have). >> > >>>> >> > >>>> On 1/29/13 10:52 AM, "fabian boulegue" <[email protected]> wrote: >> > >>>> >> > >>>>> Well If we could commit a r2 soon I could let it been tested >>here, >> > >>> about >> > >>>>> the known issues. >> > >>>>> So we would stay on time. >> > >>>>> _____________________ >> > >>>>> Fabian Boulegue >> > >>>>> tea inc. >> > >>>>> CEO - Founder >> > >>>>> Meierbrede 9 >> > >>>>> 33100 Paderborn >> > >>>>> >> > >>>>> Mobile >> > >>>>> >> > >>>>> Am 29.01.2013 um 19:45 schrieb Filip Maj <[email protected]>: >> > >>>>> >> > >>>>>> I'm uncertain and worried that we'd slip to mid-Feb before >> > >>> releasing >> > >>>>>> 2.4.0. >> > >>>>>> >> > >>>>>> On 1/29/13 10:38 AM, "Andrew Grieve" <[email protected]> >> wrote: >> > >>>>>> >> > >>>>>>> There have been several fixes to iOS since rc1. I think this >> would >> > >>>>>>> warrant >> > >>>>>>> an rc2. >> > >>>>>>> >> > >>>>>>> >> > >>>>>>> On Tue, Jan 29, 2013 at 12:49 PM, Filip Maj <[email protected]> >> wrote: >> > >>>>>>> >> > >>>>>>>> We will go straight from 2.4.0rc1 to 2.4.0, unless >>contributors >> > >>> and >> > >>>>>>>> committers think there are some unresolved issues left over >> > >>> from, or >> > >>>>>>>> new >> > >>>>>>>> ones introduced in, 2.4.0rc1 . >> > >>>>>>>> >> > >>>>>>>> On 1/29/13 9:39 AM, "fabian boulegue" <[email protected]> >>wrote: >> > >>>>>>>> >> > >>>>>>>>> So any update on release for r2? >> > >>>>>>>>> >> > >>>>>>>>> Am Jan 29, 2013 um 6:24 PM schrieb Giorgio Natili >> > >>>>>>>> <[email protected] >> > >>>>>>>>> : >> > >>>>>>>>> >> > >>>>>>>>>> +1 >> > >>>>>>>>>> >> > >>>>>>>>>> On 1/28/13 8:11 PM, "Brian LeRoux" <[email protected]> wrote: >> > >>>>>>>>>> >> > >>>>>>>>>>> remember: silence is assent! >> > > >> > >>
