Pretty sure that this is going to come up rather often.. I think we should cut a new release.
On 6/11/12 12:13 PM, "Brian LeRoux" <[email protected]> wrote: >From a policy point of view I think we should just issue point >releases on the src but not go through cutting an entire release. >(Unless its a security fix which we should issue general release and >make a big hoo hah about it.) > >On Mon, Jun 11, 2012 at 11:29 AM, Shazron <[email protected]> wrote: >> I doubt it's *our* fault, there's very little difference btw iOS 4 and >> 5, and it works for iOS 3.x when I tested it. I had to bring an iPod >> Touch with 4.2.1 in to test. Probably a PEBKAC but need to make >> sure... >> >> On Mon, Jun 11, 2012 at 11:17 AM, Filip Maj <[email protected]> wrote: >>> It's probably my rewrite of the geolocation plugin. Blame Fil. Always. >>> >>> On 6/11/12 11:13 AM, "Shazron" <[email protected]> wrote: >>> >>>>Not sure. I'm investigating this geo issue on iOS 4.x right now, don't >>>>know if it's a user error or our implementation. If it is our impl., >>>>I'll fix it for 1.8.1 as well: >>>>https://issues.apache.org/jira/browse/CB-884 >>>> >>>>On Mon, Jun 11, 2012 at 11:02 AM, Filip Maj <[email protected]> wrote: >>>>> Sounds like a serious issue :s >>>>> >>>>> What's our approach in these cases? Do we generally want to only tag >>>>>a >>>>> single platform? It wouldn't be a big deal to tag all platforms 1.8.1 >>>>> (especially since Joe tagged a pre-CordovaWebView version of Android: >>>>> THANK YOU JOE!), methinks. >>>>> >>>>> On 6/8/12 4:42 PM, "Shazron" <[email protected]> wrote: >>>>> >>>>>>https://issues.apache.org/jira/browse/CB-885 >>>>>> >>>>>>No big all platforms release, just tagging it in the repo source. No >>>>>>binaries. Objections? >>>>>>Just as a pointer for devs that need this fix. >>>>> >>>
