You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Jesse <pu...@gmail.com> on 2013/10/22 01:38:45 UTC
2.9.1 Backport release
Having a tonne of fun putting the bunny back in the box.
Here is a list of plugin defects [1] that have been closed between 2.9.0
and 3.1.0
Please have a look and decide if you think each is worth the effort of
backporting.
[1] https://issues.apache.org/jira/browse/CB-5136
@purplecabbage
risingj.com
Re: 2.9.1 Backport release
Posted by Andrew Grieve <ag...@chromium.org>.
Useful stuff Josh & Jesse! Thanks for putting this together.
On Mon, Oct 21, 2013 at 7:57 PM, Josh Soref <js...@blackberry.com> wrote:
> On 10/21/13 7:38 PM, "Jesse" <pu...@gmail.com> wrote:
> >Having a tonne of fun putting the bunny back in the box.
> >Here is a list of plugin defects [1] that have been closed between 2.9.0
> >and 3.1.0
> >Please have a look and decide if you think each is worth the effort of
> >backporting.
> >
> >[1] https://issues.apache.org/jira/browse/CB-5136
>
> While I don't intend to ever use old versions, here's a short opinion on
> each:
>
> + CB-4656 <https://issues.apache.org/jira/browse/CB-4656> ( android )
> + CB-4958 <https://issues.apache.org/jira/browse/CB-4958> ( iOS 7 )
> + CB-4471 <https://issues.apache.org/jira/browse/CB-4471> ( android )
>
> - CB-4181 <https://issues.apache.org/jira/browse/CB-4181> ( iOS )
> - CB-4192 <https://issues.apache.org/jira/browse/CB-4192> ( all )
> + CB-4900 <https://issues.apache.org/jira/browse/CB-4900> ( Win8 )
> - CB-4592 <https://issues.apache.org/jira/browse/CB-4592> ( BB )
> + CB-4090 <https://issues.apache.org/jira/browse/CB-4090> ( WPx )
> + CB-2607 <https://issues.apache.org/jira/browse/CB-2607> ( WPx )
> + CB-1543 <https://issues.apache.org/jira/browse/CB-1543> ( WPx )
> - CB-3569 <https://issues.apache.org/jira/browse/CB-3569> ( android )
> - CB-4480 <https://issues.apache.org/jira/browse/CB-4480> ( iOS )
> - CB-2828 <https://issues.apache.org/jira/browse/CB-2828> ( WPx )
> + CB-4054 <https://issues.apache.org/jira/browse/CB-4054> ( WPx )
> - CB-4264 <https://issues.apache.org/jira/browse/CB-4264> ( iOS )
> + CB-4514 <https://issues.apache.org/jira/browse/CB-4514> ( android )
> + CB-4771 <https://issues.apache.org/jira/browse/CB-4771> ( all )
> x CB-4090 <https://issues.apache.org/jira/browse/CB-4090> ( WPx )
> -- you listed this already
> + CB-4521 <https://issues.apache.org/jira/browse/CB-4521> ( android )
> + CB-4147 <https://issues.apache.org/jira/browse/CB-4147> ( iOS )
> - CB-4864 <https://issues.apache.org/jira/browse/CB-4864> ( android )
> x CB-4988 <https://issues.apache.org/jira/browse/CB-4988> ( iOS 7 )
> -- this is really CB-4930
>
>
>
> + CB-3747 <https://issues.apache.org/jira/browse/CB-3747> ( android )
> + CB-4858 <https://issues.apache.org/jira/browse/CB-4858> ( android )
> + CB-4087 <https://issues.apache.org/jira/browse/CB-4087> ( android )
> + CB-4930 <https://issues.apache.org/jira/browse/CB-4930> ( iOS 7 )
> + CB-4926 <https://issues.apache.org/jira/browse/CB-4926> ( win8 )
> + CB-4586 <https://issues.apache.org/jira/browse/CB-4586> ( android )
> + CB-4847 <https://issues.apache.org/jira/browse/CB-4847> ( iOS 7 )
> x CB-4471 <https://issues.apache.org/jira/browse/CB-4471> ( android )
> -- you listed this already
>
> + CB-3628 <https://issues.apache.org/jira/browse/CB-3628> ( android )
> -- good luck, the bug has no indication of what work was done
> x CB-4847 <https://issues.apache.org/jira/browse/CB-4847> ( iOS 7 )
> -- you listed this already
>
>
> Key:
> + probably worth it
> - not worth it
> x duplicate of another line in the list
>
> Roughly:
> - I don't see any reason to do work on mobile-spec -- it's a test right?
> - For really obscure things, you have better things to do w/ your time.
> - For crashers, it's probably worth doing
> - For missing functionality to key areas, it's probably worth doing
> (PUT is not in this bucket IMO, if people need it, let them upgrade to 3.x)
> - For ugly behavior on a platform, it's probably worth doing
>
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential
> information, privileged material (including material protected by the
> solicitor-client or other applicable privileges), or constitute non-public
> information. Any use of this information by anyone other than the intended
> recipient is prohibited. If you have received this transmission in error,
> please immediately reply to the sender and delete this information from
> your system. Use, dissemination, distribution, or reproduction of this
> transmission by unintended recipients is not authorized and may be unlawful.
>
>
Re: 2.9.1 Backport release
Posted by Carlos Santana <cs...@gmail.com>.
Suggestion: "Known Issues in 2.9.1"
>From this list ony, things that don't get fix in 2.9.1 they should be
listed in the Release Note or Blog Post as "Known Issues in 2.9.1"
Then it will be cleared to consumers that an issue is a known issue but is
not address in 2.9.1, If we know is addressed in 3.x, then even more useful
to state this. It will be useful information for the end user if they
really need an issue resolved badly then they can be more motivated to
start process to move to 3.x
--Carlos
On Tue, Oct 22, 2013 at 11:17 AM, Joe Bowser <bo...@gmail.com> wrote:
> There are some 3.0.0 bugs that don't exist in 2.9.0.
>
> On Mon, Oct 21, 2013 at 4:57 PM, Josh Soref <js...@blackberry.com> wrote:
> > On 10/21/13 7:38 PM, "Jesse" <pu...@gmail.com> wrote:
> >>Having a tonne of fun putting the bunny back in the box.
> >>Here is a list of plugin defects [1] that have been closed between 2.9.0
> >>and 3.1.0
> >>Please have a look and decide if you think each is worth the effort of
> >>backporting.
> >>
> >>[1] https://issues.apache.org/jira/browse/CB-5136
> >
> > While I don't intend to ever use old versions, here's a short opinion on
> > each:
> >
> > + CB-4656 <https://issues.apache.org/jira/browse/CB-4656> ( android )
> (Not applicable to 2.9.x, caused by UriResource Bug)
>
> > + CB-4471 <https://issues.apache.org/jira/browse/CB-4471> ( android )
> (Sadly, this isn't a fix, it's just suppressing the NPE. This is in
> the 2.9.x branch)
>
> > - CB-3569 <https://issues.apache.org/jira/browse/CB-3569> ( android )
> This still needs to be done. If someone who is familiar with URI
> resolvers want to take a crack at it, that'd be good.
>
> > + CB-4514 <https://issues.apache.org/jira/browse/CB-4514> ( android )
> This is in 2.9.x
>
> > + CB-4521 <https://issues.apache.org/jira/browse/CB-4521> ( android )
> This is in 2.9.x
>
> > - CB-4864 <https://issues.apache.org/jira/browse/CB-4864> ( android )
> This doesn't need to be in 2.9.x
>
> > + CB-3747 <https://issues.apache.org/jira/browse/CB-3747> ( android )
> > + CB-4858 <https://issues.apache.org/jira/browse/CB-4858> ( android )
> > + CB-4087 <https://issues.apache.org/jira/browse/CB-4087> ( android )
> > + CB-4586 <https://issues.apache.org/jira/browse/CB-4586> ( android )
> InAppBrowser bugs that need to go in. We should backport InAppBrowser
> entirely, but I would like the resolutions fleshed out a bit, since I
> have no idea how these were fixed other than the commit. I couldn't
> reproduce the stupid video bug on any of the devices that I tested
> this on.
>
> Also, there's JS changes that were made. Andrew, since you own this
> one, can you backport this?
>
> > + CB-3628 <https://issues.apache.org/jira/browse/CB-3628> ( android )
> > -- good luck, the bug has no indication of what work was done
> This is a 3.x bug only.
>
> I think this exercise shows that we have to be better about write-ups
> when we close bugs, or at least better about repro cases and writing
> tests. There's some cases where I have a test, but that test doesn't
> have a home because it's Android-Specific so it doesn't belong in
> Mobile-Spec, and it's a JS test so it doesn't really belong in the
> test directory. :(
>
--
Carlos Santana
<cs...@gmail.com>
Re: 2.9.1 Backport release
Posted by purplecabbage <pu...@gmail.com>.
I made some headway but am not done with WPx. I've had to work through many js issues.
I am away until Monday though and haven't had a chance to update windows8. If someone wants to look at that it would be a huge help.
I expect ios7 support is going to push the release back to be inline with 3.2.0 anyway though.
I will be back on the list tonight to catch up.
Sent from my iPhone
> On Oct 22, 2013, at 4:25 PM, Shazron <sh...@gmail.com> wrote:
>
> Gonna look over all the iOS issues tomorrow. Most of them are just straight
> copy and paste jobs (yay for them all being plugins!). When is the schedule
> for release? (since we have 3.2 on the plate as well)
>
>
>> On Tue, Oct 22, 2013 at 8:26 AM, Andrew Grieve <ag...@chromium.org> wrote:
>>
>> Thanks Joe!
>>
>> Will work on the IAB & UriResolvers issues right now.
>>
>>
>>> On Tue, Oct 22, 2013 at 11:17 AM, Joe Bowser <bo...@gmail.com> wrote:
>>>
>>> There are some 3.0.0 bugs that don't exist in 2.9.0.
>>>
>>> On Mon, Oct 21, 2013 at 4:57 PM, Josh Soref <js...@blackberry.com>
>> wrote:
>>>> On 10/21/13 7:38 PM, "Jesse" <pu...@gmail.com> wrote:
>>>>> Having a tonne of fun putting the bunny back in the box.
>>>>> Here is a list of plugin defects [1] that have been closed between
>> 2.9.0
>>>>> and 3.1.0
>>>>> Please have a look and decide if you think each is worth the effort of
>>>>> backporting.
>>>>>
>>>>> [1] https://issues.apache.org/jira/browse/CB-5136
>>>>
>>>> While I don't intend to ever use old versions, here's a short opinion
>> on
>>>> each:
>>>>
>>>> + CB-4656 <https://issues.apache.org/jira/browse/CB-4656> ( android )
>>> (Not applicable to 2.9.x, caused by UriResource Bug)
>>>
>>>> + CB-4471 <https://issues.apache.org/jira/browse/CB-4471> ( android )
>>> (Sadly, this isn't a fix, it's just suppressing the NPE. This is in
>>> the 2.9.x branch)
>>>
>>>> - CB-3569 <https://issues.apache.org/jira/browse/CB-3569> ( android )
>>> This still needs to be done. If someone who is familiar with URI
>>> resolvers want to take a crack at it, that'd be good.
>>>
>>>> + CB-4514 <https://issues.apache.org/jira/browse/CB-4514> ( android )
>>> This is in 2.9.x
>>>
>>>> + CB-4521 <https://issues.apache.org/jira/browse/CB-4521> ( android )
>>> This is in 2.9.x
>>>
>>>> - CB-4864 <https://issues.apache.org/jira/browse/CB-4864> ( android )
>>> This doesn't need to be in 2.9.x
>>>
>>>> + CB-3747 <https://issues.apache.org/jira/browse/CB-3747> ( android )
>>>> + CB-4858 <https://issues.apache.org/jira/browse/CB-4858> ( android )
>>>> + CB-4087 <https://issues.apache.org/jira/browse/CB-4087> ( android )
>>>> + CB-4586 <https://issues.apache.org/jira/browse/CB-4586> ( android )
>>> InAppBrowser bugs that need to go in. We should backport InAppBrowser
>>> entirely, but I would like the resolutions fleshed out a bit, since I
>>> have no idea how these were fixed other than the commit. I couldn't
>>> reproduce the stupid video bug on any of the devices that I tested
>>> this on.
>>>
>>> Also, there's JS changes that were made. Andrew, since you own this
>>> one, can you backport this?
>>>
>>>> + CB-3628 <https://issues.apache.org/jira/browse/CB-3628> ( android )
>>>> -- good luck, the bug has no indication of what work was done
>>> This is a 3.x bug only.
>>>
>>> I think this exercise shows that we have to be better about write-ups
>>> when we close bugs, or at least better about repro cases and writing
>>> tests. There's some cases where I have a test, but that test doesn't
>>> have a home because it's Android-Specific so it doesn't belong in
>>> Mobile-Spec, and it's a JS test so it doesn't really belong in the
>>> test directory. :(
>>
Re: 2.9.1 Backport release
Posted by Shazron <sh...@gmail.com>.
No iOS changes to docs.
Here's what changed in iOS:
https://github.com/apache/cordova-ios/commit/0f79933977213ed32f75690edfb1edcde679fcbe
On Fri, Nov 1, 2013 at 1:33 PM, Joe Bowser <bo...@gmail.com> wrote:
> Android is now tagged.
>
> On Fri, Nov 1, 2013 at 1:19 PM, Steven Gill <st...@gmail.com>
> wrote:
> > Awesome. So Android is left to tag now! Thoughts on what we should do for
> > docs? Just point people to 2.9.0 docs or create 2.9.1 based of 2.9.0? Any
> > changes in docs between the two?
> >
> >
> >
> >
> > On Fri, Nov 1, 2013 at 12:50 PM, Shazron <sh...@gmail.com> wrote:
> >
> >> iOS 2.9.1 tested (all tests pass:
> >> https://issues.apache.org/jira/browse/CB-5189) and tagged.
> >>
> >> 2.9.1 Release issue: https://issues.apache.org/jira/browse/CB-5136
> >>
> >>
> >> On Wed, Oct 30, 2013 at 6:07 PM, Jesse <pu...@gmail.com> wrote:
> >>
> >> > tagged
> >> >
> >> > @purplecabbage
> >> > risingj.com
> >> >
> >> >
> >> > On Wed, Oct 30, 2013 at 5:41 PM, Shazron <sh...@gmail.com> wrote:
> >> >
> >> > > iOS is ready for js, then retest.
> >> > >
> >> > > On Wednesday, October 30, 2013, Jesse wrote:
> >> > >
> >> > > > Okay, I am ready to tag the js, and get to releasing ...
> >> > > > Where is everyone else at?
> >> > > >
> >> > > > @purplecabbage
> >> > > > risingj.com
> >> > > >
> >> > > >
> >> > > > On Thu, Oct 24, 2013 at 2:43 PM, Shazron <sh...@gmail.com>
> wrote:
> >> > > >
> >> > > > > https://issues.apache.org/jira/browse/CB-5189
> >> > > > >
> >> > > > > Integrated everything for iOS, and tested on iOS 7 and 6 (I
> have no
> >> > > iOS 5
> >> > > > > device).
> >> > > > >
> >> > > > > Results below.
> >> > > > >
> >> > > > > AutoTests:
> >> > > > > =======
> >> > > > > iOS 7.0.3 (all pass)
> >> > > > > iOS 6.1.4 (all pass)
> >> > > > >
> >> > > > > Manual Tests (iOS 6.1.4)
> >> > > > > ===========
> >> > > > > Media Record (pass)
> >> > > > > Splashscreen (pass)
> >> > > > > InAppBrowser (pass - but got a "multiple loadstart events (2)"
> >> popup
> >> > > > error
> >> > > > > each time a page was loaded - I think this the test is causing
> >> this)
> >> > > > > Accelerometer (pass)
> >> > > > > Camera (pass)
> >> > > > > Media Capture Audio (pass)
> >> > > > >
> >> > > > > Manual Tests (iOS 7.0.3)
> >> > > > > ===========
> >> > > > > Media Record (pass)
> >> > > > > Splashscreen (pass)
> >> > > > > InAppBrowser (pass)
> >> > > > > Accelerometer (pass)
> >> > > > > Camera (pass)
> >> > > > > Media Capture Audio (pass, but UI is "shifted up" a bit,
> instead of
> >> > > > > sticking to the bottom, un-related to recording)
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > > > On Wed, Oct 23, 2013 at 5:16 PM, Shazron <sh...@gmail.com>
> >> wrote:
> >> > > > >
> >> > > > > > iOS tracked as subtask under
> >> > > > > https://issues.apache.org/jira/browse/CB-5189
> >> > > > > >
> >> > > > > >
> >> > > > > > On Wed, Oct 23, 2013 at 2:55 PM, Shazron <sh...@gmail.com>
> >> > wrote:
> >> > > > > >
> >> > > > > >> Will integrate:
> >> > > > > >>
> >> > > > > >> 1. https://issues.apache.org/jira/browse/CB-4958 (Camera -
> iOS
> >> 7)
> >> > > > > >> 2. https://issues.apache.org/jira/browse/CB-4930(InAppBrowser
> >> -
> >> > > iOS
> >> > > > 7)
> >> > > > > >> 3. https://issues.apache.org/jira/browse/CB-4847(Media/Media
> >> > > > Capture -
> >> > > > > >> iOS 7)
> >> > > > > >> 4. https://issues.apache.org/jira/browse/CB-4825 (Device
> >> Motion)
> >> > > > > >> 5. https://issues.apache.org/jira/browse/CB-5035 (Device
> >> Motion)
> >> > > > > >>
> >> > > > > >> These should be relatively straightforward copy paste jobs,
> then
> >> > > test
> >> > > > on
> >> > > > > >> mobile spec.
> >> > > > > >>
> >> > > > > >> This one is more of a cordova-js thing where it affects all
> >> > > platforms:
> >> > > > > >> https://issues.apache.org/jira/browse/CB-4771
> >> > > > > >>
> >> > > > > >>
> >> > > > > >> On Tue, Oct 22, 2013 at 4:25 PM, Shazron <sh...@gmail.com>
> >> > wrote:
> >> > > > > >>
> >> > > > > >>> Gonna look over all the iOS issues tomorrow. Most of them
> are
> >> > just
> >> > > > > >>> straight copy and paste jobs (yay for them all being
> plugins!).
> >> > > When
> >> > > > > is the
> >> > > > > >>> schedule for release? (since we have 3.2 on the plate as
> well)
> >> > > > > >>>
> >> > > > > >>>
> >> > > > > >>> On Tue, Oct 22, 2013 at 8:26 AM, Andrew Grieve <
> >> > > agrieve@chromium.org
> >> > > > > >wrote:
> >> > > > > >>>
> >> > > > > >>>> Thanks Joe!
> >> > > > > >>>>
> >> > > > > >>>> Will work on the IAB & UriResolvers issues right now.
> >> > > > > >>>>
> >> > > > > >>>>
> >> > > > > >>>> On Tue, Oct 22, 2013 at 11:17 AM, Joe Bowser <
> >> bowserj@gmail.com
> >> > >
> >> > > > > wrote:
> >> > > > > >>>>
> >> > > > > >>>> > There are some 3.0.0 bugs that don't exist in 2.9.0.
> >> > > > > >>>> >
> >> > > > > >>>> > On Mon, Oct 21, 2013 at 4:57 PM, Josh Soref <
> >> > > > jsoref@blackberry.com>
> >> > > > > >>>> wrote:
> >> > > > > >>>> > > On 10/21/13 7:38 PM, "Jesse" <pu...@gmail.com>
> >> > wrote:
> >> > > > > >>>> > >>Having a tonne of fun
> >> > >
> >> >
> >>
>
Re: 2.9.1 Backport release
Posted by Joe Bowser <bo...@gmail.com>.
Android is now tagged.
On Fri, Nov 1, 2013 at 1:19 PM, Steven Gill <st...@gmail.com> wrote:
> Awesome. So Android is left to tag now! Thoughts on what we should do for
> docs? Just point people to 2.9.0 docs or create 2.9.1 based of 2.9.0? Any
> changes in docs between the two?
>
>
>
>
> On Fri, Nov 1, 2013 at 12:50 PM, Shazron <sh...@gmail.com> wrote:
>
>> iOS 2.9.1 tested (all tests pass:
>> https://issues.apache.org/jira/browse/CB-5189) and tagged.
>>
>> 2.9.1 Release issue: https://issues.apache.org/jira/browse/CB-5136
>>
>>
>> On Wed, Oct 30, 2013 at 6:07 PM, Jesse <pu...@gmail.com> wrote:
>>
>> > tagged
>> >
>> > @purplecabbage
>> > risingj.com
>> >
>> >
>> > On Wed, Oct 30, 2013 at 5:41 PM, Shazron <sh...@gmail.com> wrote:
>> >
>> > > iOS is ready for js, then retest.
>> > >
>> > > On Wednesday, October 30, 2013, Jesse wrote:
>> > >
>> > > > Okay, I am ready to tag the js, and get to releasing ...
>> > > > Where is everyone else at?
>> > > >
>> > > > @purplecabbage
>> > > > risingj.com
>> > > >
>> > > >
>> > > > On Thu, Oct 24, 2013 at 2:43 PM, Shazron <sh...@gmail.com> wrote:
>> > > >
>> > > > > https://issues.apache.org/jira/browse/CB-5189
>> > > > >
>> > > > > Integrated everything for iOS, and tested on iOS 7 and 6 (I have no
>> > > iOS 5
>> > > > > device).
>> > > > >
>> > > > > Results below.
>> > > > >
>> > > > > AutoTests:
>> > > > > =======
>> > > > > iOS 7.0.3 (all pass)
>> > > > > iOS 6.1.4 (all pass)
>> > > > >
>> > > > > Manual Tests (iOS 6.1.4)
>> > > > > ===========
>> > > > > Media Record (pass)
>> > > > > Splashscreen (pass)
>> > > > > InAppBrowser (pass - but got a "multiple loadstart events (2)"
>> popup
>> > > > error
>> > > > > each time a page was loaded - I think this the test is causing
>> this)
>> > > > > Accelerometer (pass)
>> > > > > Camera (pass)
>> > > > > Media Capture Audio (pass)
>> > > > >
>> > > > > Manual Tests (iOS 7.0.3)
>> > > > > ===========
>> > > > > Media Record (pass)
>> > > > > Splashscreen (pass)
>> > > > > InAppBrowser (pass)
>> > > > > Accelerometer (pass)
>> > > > > Camera (pass)
>> > > > > Media Capture Audio (pass, but UI is "shifted up" a bit, instead of
>> > > > > sticking to the bottom, un-related to recording)
>> > > > >
>> > > > >
>> > > > >
>> > > > > On Wed, Oct 23, 2013 at 5:16 PM, Shazron <sh...@gmail.com>
>> wrote:
>> > > > >
>> > > > > > iOS tracked as subtask under
>> > > > > https://issues.apache.org/jira/browse/CB-5189
>> > > > > >
>> > > > > >
>> > > > > > On Wed, Oct 23, 2013 at 2:55 PM, Shazron <sh...@gmail.com>
>> > wrote:
>> > > > > >
>> > > > > >> Will integrate:
>> > > > > >>
>> > > > > >> 1. https://issues.apache.org/jira/browse/CB-4958 (Camera - iOS
>> 7)
>> > > > > >> 2. https://issues.apache.org/jira/browse/CB-4930 (InAppBrowser
>> -
>> > > iOS
>> > > > 7)
>> > > > > >> 3. https://issues.apache.org/jira/browse/CB-4847 (Media/Media
>> > > > Capture -
>> > > > > >> iOS 7)
>> > > > > >> 4. https://issues.apache.org/jira/browse/CB-4825 (Device
>> Motion)
>> > > > > >> 5. https://issues.apache.org/jira/browse/CB-5035 (Device
>> Motion)
>> > > > > >>
>> > > > > >> These should be relatively straightforward copy paste jobs, then
>> > > test
>> > > > on
>> > > > > >> mobile spec.
>> > > > > >>
>> > > > > >> This one is more of a cordova-js thing where it affects all
>> > > platforms:
>> > > > > >> https://issues.apache.org/jira/browse/CB-4771
>> > > > > >>
>> > > > > >>
>> > > > > >> On Tue, Oct 22, 2013 at 4:25 PM, Shazron <sh...@gmail.com>
>> > wrote:
>> > > > > >>
>> > > > > >>> Gonna look over all the iOS issues tomorrow. Most of them are
>> > just
>> > > > > >>> straight copy and paste jobs (yay for them all being plugins!).
>> > > When
>> > > > > is the
>> > > > > >>> schedule for release? (since we have 3.2 on the plate as well)
>> > > > > >>>
>> > > > > >>>
>> > > > > >>> On Tue, Oct 22, 2013 at 8:26 AM, Andrew Grieve <
>> > > agrieve@chromium.org
>> > > > > >wrote:
>> > > > > >>>
>> > > > > >>>> Thanks Joe!
>> > > > > >>>>
>> > > > > >>>> Will work on the IAB & UriResolvers issues right now.
>> > > > > >>>>
>> > > > > >>>>
>> > > > > >>>> On Tue, Oct 22, 2013 at 11:17 AM, Joe Bowser <
>> bowserj@gmail.com
>> > >
>> > > > > wrote:
>> > > > > >>>>
>> > > > > >>>> > There are some 3.0.0 bugs that don't exist in 2.9.0.
>> > > > > >>>> >
>> > > > > >>>> > On Mon, Oct 21, 2013 at 4:57 PM, Josh Soref <
>> > > > jsoref@blackberry.com>
>> > > > > >>>> wrote:
>> > > > > >>>> > > On 10/21/13 7:38 PM, "Jesse" <pu...@gmail.com>
>> > wrote:
>> > > > > >>>> > >>Having a tonne of fun
>> > >
>> >
>>
Re: 2.9.1 Backport release
Posted by Steven Gill <st...@gmail.com>.
Awesome. So Android is left to tag now! Thoughts on what we should do for
docs? Just point people to 2.9.0 docs or create 2.9.1 based of 2.9.0? Any
changes in docs between the two?
On Fri, Nov 1, 2013 at 12:50 PM, Shazron <sh...@gmail.com> wrote:
> iOS 2.9.1 tested (all tests pass:
> https://issues.apache.org/jira/browse/CB-5189) and tagged.
>
> 2.9.1 Release issue: https://issues.apache.org/jira/browse/CB-5136
>
>
> On Wed, Oct 30, 2013 at 6:07 PM, Jesse <pu...@gmail.com> wrote:
>
> > tagged
> >
> > @purplecabbage
> > risingj.com
> >
> >
> > On Wed, Oct 30, 2013 at 5:41 PM, Shazron <sh...@gmail.com> wrote:
> >
> > > iOS is ready for js, then retest.
> > >
> > > On Wednesday, October 30, 2013, Jesse wrote:
> > >
> > > > Okay, I am ready to tag the js, and get to releasing ...
> > > > Where is everyone else at?
> > > >
> > > > @purplecabbage
> > > > risingj.com
> > > >
> > > >
> > > > On Thu, Oct 24, 2013 at 2:43 PM, Shazron <sh...@gmail.com> wrote:
> > > >
> > > > > https://issues.apache.org/jira/browse/CB-5189
> > > > >
> > > > > Integrated everything for iOS, and tested on iOS 7 and 6 (I have no
> > > iOS 5
> > > > > device).
> > > > >
> > > > > Results below.
> > > > >
> > > > > AutoTests:
> > > > > =======
> > > > > iOS 7.0.3 (all pass)
> > > > > iOS 6.1.4 (all pass)
> > > > >
> > > > > Manual Tests (iOS 6.1.4)
> > > > > ===========
> > > > > Media Record (pass)
> > > > > Splashscreen (pass)
> > > > > InAppBrowser (pass - but got a "multiple loadstart events (2)"
> popup
> > > > error
> > > > > each time a page was loaded - I think this the test is causing
> this)
> > > > > Accelerometer (pass)
> > > > > Camera (pass)
> > > > > Media Capture Audio (pass)
> > > > >
> > > > > Manual Tests (iOS 7.0.3)
> > > > > ===========
> > > > > Media Record (pass)
> > > > > Splashscreen (pass)
> > > > > InAppBrowser (pass)
> > > > > Accelerometer (pass)
> > > > > Camera (pass)
> > > > > Media Capture Audio (pass, but UI is "shifted up" a bit, instead of
> > > > > sticking to the bottom, un-related to recording)
> > > > >
> > > > >
> > > > >
> > > > > On Wed, Oct 23, 2013 at 5:16 PM, Shazron <sh...@gmail.com>
> wrote:
> > > > >
> > > > > > iOS tracked as subtask under
> > > > > https://issues.apache.org/jira/browse/CB-5189
> > > > > >
> > > > > >
> > > > > > On Wed, Oct 23, 2013 at 2:55 PM, Shazron <sh...@gmail.com>
> > wrote:
> > > > > >
> > > > > >> Will integrate:
> > > > > >>
> > > > > >> 1. https://issues.apache.org/jira/browse/CB-4958 (Camera - iOS
> 7)
> > > > > >> 2. https://issues.apache.org/jira/browse/CB-4930 (InAppBrowser
> -
> > > iOS
> > > > 7)
> > > > > >> 3. https://issues.apache.org/jira/browse/CB-4847 (Media/Media
> > > > Capture -
> > > > > >> iOS 7)
> > > > > >> 4. https://issues.apache.org/jira/browse/CB-4825 (Device
> Motion)
> > > > > >> 5. https://issues.apache.org/jira/browse/CB-5035 (Device
> Motion)
> > > > > >>
> > > > > >> These should be relatively straightforward copy paste jobs, then
> > > test
> > > > on
> > > > > >> mobile spec.
> > > > > >>
> > > > > >> This one is more of a cordova-js thing where it affects all
> > > platforms:
> > > > > >> https://issues.apache.org/jira/browse/CB-4771
> > > > > >>
> > > > > >>
> > > > > >> On Tue, Oct 22, 2013 at 4:25 PM, Shazron <sh...@gmail.com>
> > wrote:
> > > > > >>
> > > > > >>> Gonna look over all the iOS issues tomorrow. Most of them are
> > just
> > > > > >>> straight copy and paste jobs (yay for them all being plugins!).
> > > When
> > > > > is the
> > > > > >>> schedule for release? (since we have 3.2 on the plate as well)
> > > > > >>>
> > > > > >>>
> > > > > >>> On Tue, Oct 22, 2013 at 8:26 AM, Andrew Grieve <
> > > agrieve@chromium.org
> > > > > >wrote:
> > > > > >>>
> > > > > >>>> Thanks Joe!
> > > > > >>>>
> > > > > >>>> Will work on the IAB & UriResolvers issues right now.
> > > > > >>>>
> > > > > >>>>
> > > > > >>>> On Tue, Oct 22, 2013 at 11:17 AM, Joe Bowser <
> bowserj@gmail.com
> > >
> > > > > wrote:
> > > > > >>>>
> > > > > >>>> > There are some 3.0.0 bugs that don't exist in 2.9.0.
> > > > > >>>> >
> > > > > >>>> > On Mon, Oct 21, 2013 at 4:57 PM, Josh Soref <
> > > > jsoref@blackberry.com>
> > > > > >>>> wrote:
> > > > > >>>> > > On 10/21/13 7:38 PM, "Jesse" <pu...@gmail.com>
> > wrote:
> > > > > >>>> > >>Having a tonne of fun
> > >
> >
>
Re: 2.9.1 Backport release
Posted by Shazron <sh...@gmail.com>.
iOS 2.9.1 tested (all tests pass:
https://issues.apache.org/jira/browse/CB-5189) and tagged.
2.9.1 Release issue: https://issues.apache.org/jira/browse/CB-5136
On Wed, Oct 30, 2013 at 6:07 PM, Jesse <pu...@gmail.com> wrote:
> tagged
>
> @purplecabbage
> risingj.com
>
>
> On Wed, Oct 30, 2013 at 5:41 PM, Shazron <sh...@gmail.com> wrote:
>
> > iOS is ready for js, then retest.
> >
> > On Wednesday, October 30, 2013, Jesse wrote:
> >
> > > Okay, I am ready to tag the js, and get to releasing ...
> > > Where is everyone else at?
> > >
> > > @purplecabbage
> > > risingj.com
> > >
> > >
> > > On Thu, Oct 24, 2013 at 2:43 PM, Shazron <sh...@gmail.com> wrote:
> > >
> > > > https://issues.apache.org/jira/browse/CB-5189
> > > >
> > > > Integrated everything for iOS, and tested on iOS 7 and 6 (I have no
> > iOS 5
> > > > device).
> > > >
> > > > Results below.
> > > >
> > > > AutoTests:
> > > > =======
> > > > iOS 7.0.3 (all pass)
> > > > iOS 6.1.4 (all pass)
> > > >
> > > > Manual Tests (iOS 6.1.4)
> > > > ===========
> > > > Media Record (pass)
> > > > Splashscreen (pass)
> > > > InAppBrowser (pass - but got a "multiple loadstart events (2)" popup
> > > error
> > > > each time a page was loaded - I think this the test is causing this)
> > > > Accelerometer (pass)
> > > > Camera (pass)
> > > > Media Capture Audio (pass)
> > > >
> > > > Manual Tests (iOS 7.0.3)
> > > > ===========
> > > > Media Record (pass)
> > > > Splashscreen (pass)
> > > > InAppBrowser (pass)
> > > > Accelerometer (pass)
> > > > Camera (pass)
> > > > Media Capture Audio (pass, but UI is "shifted up" a bit, instead of
> > > > sticking to the bottom, un-related to recording)
> > > >
> > > >
> > > >
> > > > On Wed, Oct 23, 2013 at 5:16 PM, Shazron <sh...@gmail.com> wrote:
> > > >
> > > > > iOS tracked as subtask under
> > > > https://issues.apache.org/jira/browse/CB-5189
> > > > >
> > > > >
> > > > > On Wed, Oct 23, 2013 at 2:55 PM, Shazron <sh...@gmail.com>
> wrote:
> > > > >
> > > > >> Will integrate:
> > > > >>
> > > > >> 1. https://issues.apache.org/jira/browse/CB-4958 (Camera - iOS 7)
> > > > >> 2. https://issues.apache.org/jira/browse/CB-4930 (InAppBrowser -
> > iOS
> > > 7)
> > > > >> 3. https://issues.apache.org/jira/browse/CB-4847 (Media/Media
> > > Capture -
> > > > >> iOS 7)
> > > > >> 4. https://issues.apache.org/jira/browse/CB-4825 (Device Motion)
> > > > >> 5. https://issues.apache.org/jira/browse/CB-5035 (Device Motion)
> > > > >>
> > > > >> These should be relatively straightforward copy paste jobs, then
> > test
> > > on
> > > > >> mobile spec.
> > > > >>
> > > > >> This one is more of a cordova-js thing where it affects all
> > platforms:
> > > > >> https://issues.apache.org/jira/browse/CB-4771
> > > > >>
> > > > >>
> > > > >> On Tue, Oct 22, 2013 at 4:25 PM, Shazron <sh...@gmail.com>
> wrote:
> > > > >>
> > > > >>> Gonna look over all the iOS issues tomorrow. Most of them are
> just
> > > > >>> straight copy and paste jobs (yay for them all being plugins!).
> > When
> > > > is the
> > > > >>> schedule for release? (since we have 3.2 on the plate as well)
> > > > >>>
> > > > >>>
> > > > >>> On Tue, Oct 22, 2013 at 8:26 AM, Andrew Grieve <
> > agrieve@chromium.org
> > > > >wrote:
> > > > >>>
> > > > >>>> Thanks Joe!
> > > > >>>>
> > > > >>>> Will work on the IAB & UriResolvers issues right now.
> > > > >>>>
> > > > >>>>
> > > > >>>> On Tue, Oct 22, 2013 at 11:17 AM, Joe Bowser <bowserj@gmail.com
> >
> > > > wrote:
> > > > >>>>
> > > > >>>> > There are some 3.0.0 bugs that don't exist in 2.9.0.
> > > > >>>> >
> > > > >>>> > On Mon, Oct 21, 2013 at 4:57 PM, Josh Soref <
> > > jsoref@blackberry.com>
> > > > >>>> wrote:
> > > > >>>> > > On 10/21/13 7:38 PM, "Jesse" <pu...@gmail.com>
> wrote:
> > > > >>>> > >>Having a tonne of fun
> >
>
Re: 2.9.1 Backport release
Posted by Jesse <pu...@gmail.com>.
tagged
@purplecabbage
risingj.com
On Wed, Oct 30, 2013 at 5:41 PM, Shazron <sh...@gmail.com> wrote:
> iOS is ready for js, then retest.
>
> On Wednesday, October 30, 2013, Jesse wrote:
>
> > Okay, I am ready to tag the js, and get to releasing ...
> > Where is everyone else at?
> >
> > @purplecabbage
> > risingj.com
> >
> >
> > On Thu, Oct 24, 2013 at 2:43 PM, Shazron <sh...@gmail.com> wrote:
> >
> > > https://issues.apache.org/jira/browse/CB-5189
> > >
> > > Integrated everything for iOS, and tested on iOS 7 and 6 (I have no
> iOS 5
> > > device).
> > >
> > > Results below.
> > >
> > > AutoTests:
> > > =======
> > > iOS 7.0.3 (all pass)
> > > iOS 6.1.4 (all pass)
> > >
> > > Manual Tests (iOS 6.1.4)
> > > ===========
> > > Media Record (pass)
> > > Splashscreen (pass)
> > > InAppBrowser (pass - but got a "multiple loadstart events (2)" popup
> > error
> > > each time a page was loaded - I think this the test is causing this)
> > > Accelerometer (pass)
> > > Camera (pass)
> > > Media Capture Audio (pass)
> > >
> > > Manual Tests (iOS 7.0.3)
> > > ===========
> > > Media Record (pass)
> > > Splashscreen (pass)
> > > InAppBrowser (pass)
> > > Accelerometer (pass)
> > > Camera (pass)
> > > Media Capture Audio (pass, but UI is "shifted up" a bit, instead of
> > > sticking to the bottom, un-related to recording)
> > >
> > >
> > >
> > > On Wed, Oct 23, 2013 at 5:16 PM, Shazron <sh...@gmail.com> wrote:
> > >
> > > > iOS tracked as subtask under
> > > https://issues.apache.org/jira/browse/CB-5189
> > > >
> > > >
> > > > On Wed, Oct 23, 2013 at 2:55 PM, Shazron <sh...@gmail.com> wrote:
> > > >
> > > >> Will integrate:
> > > >>
> > > >> 1. https://issues.apache.org/jira/browse/CB-4958 (Camera - iOS 7)
> > > >> 2. https://issues.apache.org/jira/browse/CB-4930 (InAppBrowser -
> iOS
> > 7)
> > > >> 3. https://issues.apache.org/jira/browse/CB-4847 (Media/Media
> > Capture -
> > > >> iOS 7)
> > > >> 4. https://issues.apache.org/jira/browse/CB-4825 (Device Motion)
> > > >> 5. https://issues.apache.org/jira/browse/CB-5035 (Device Motion)
> > > >>
> > > >> These should be relatively straightforward copy paste jobs, then
> test
> > on
> > > >> mobile spec.
> > > >>
> > > >> This one is more of a cordova-js thing where it affects all
> platforms:
> > > >> https://issues.apache.org/jira/browse/CB-4771
> > > >>
> > > >>
> > > >> On Tue, Oct 22, 2013 at 4:25 PM, Shazron <sh...@gmail.com> wrote:
> > > >>
> > > >>> Gonna look over all the iOS issues tomorrow. Most of them are just
> > > >>> straight copy and paste jobs (yay for them all being plugins!).
> When
> > > is the
> > > >>> schedule for release? (since we have 3.2 on the plate as well)
> > > >>>
> > > >>>
> > > >>> On Tue, Oct 22, 2013 at 8:26 AM, Andrew Grieve <
> agrieve@chromium.org
> > > >wrote:
> > > >>>
> > > >>>> Thanks Joe!
> > > >>>>
> > > >>>> Will work on the IAB & UriResolvers issues right now.
> > > >>>>
> > > >>>>
> > > >>>> On Tue, Oct 22, 2013 at 11:17 AM, Joe Bowser <bo...@gmail.com>
> > > wrote:
> > > >>>>
> > > >>>> > There are some 3.0.0 bugs that don't exist in 2.9.0.
> > > >>>> >
> > > >>>> > On Mon, Oct 21, 2013 at 4:57 PM, Josh Soref <
> > jsoref@blackberry.com>
> > > >>>> wrote:
> > > >>>> > > On 10/21/13 7:38 PM, "Jesse" <pu...@gmail.com> wrote:
> > > >>>> > >>Having a tonne of fun
>
Re: 2.9.1 Backport release
Posted by Shazron <sh...@gmail.com>.
iOS is ready for js, then retest.
On Wednesday, October 30, 2013, Jesse wrote:
> Okay, I am ready to tag the js, and get to releasing ...
> Where is everyone else at?
>
> @purplecabbage
> risingj.com
>
>
> On Thu, Oct 24, 2013 at 2:43 PM, Shazron <sh...@gmail.com> wrote:
>
> > https://issues.apache.org/jira/browse/CB-5189
> >
> > Integrated everything for iOS, and tested on iOS 7 and 6 (I have no iOS 5
> > device).
> >
> > Results below.
> >
> > AutoTests:
> > =======
> > iOS 7.0.3 (all pass)
> > iOS 6.1.4 (all pass)
> >
> > Manual Tests (iOS 6.1.4)
> > ===========
> > Media Record (pass)
> > Splashscreen (pass)
> > InAppBrowser (pass - but got a "multiple loadstart events (2)" popup
> error
> > each time a page was loaded - I think this the test is causing this)
> > Accelerometer (pass)
> > Camera (pass)
> > Media Capture Audio (pass)
> >
> > Manual Tests (iOS 7.0.3)
> > ===========
> > Media Record (pass)
> > Splashscreen (pass)
> > InAppBrowser (pass)
> > Accelerometer (pass)
> > Camera (pass)
> > Media Capture Audio (pass, but UI is "shifted up" a bit, instead of
> > sticking to the bottom, un-related to recording)
> >
> >
> >
> > On Wed, Oct 23, 2013 at 5:16 PM, Shazron <sh...@gmail.com> wrote:
> >
> > > iOS tracked as subtask under
> > https://issues.apache.org/jira/browse/CB-5189
> > >
> > >
> > > On Wed, Oct 23, 2013 at 2:55 PM, Shazron <sh...@gmail.com> wrote:
> > >
> > >> Will integrate:
> > >>
> > >> 1. https://issues.apache.org/jira/browse/CB-4958 (Camera - iOS 7)
> > >> 2. https://issues.apache.org/jira/browse/CB-4930 (InAppBrowser - iOS
> 7)
> > >> 3. https://issues.apache.org/jira/browse/CB-4847 (Media/Media
> Capture -
> > >> iOS 7)
> > >> 4. https://issues.apache.org/jira/browse/CB-4825 (Device Motion)
> > >> 5. https://issues.apache.org/jira/browse/CB-5035 (Device Motion)
> > >>
> > >> These should be relatively straightforward copy paste jobs, then test
> on
> > >> mobile spec.
> > >>
> > >> This one is more of a cordova-js thing where it affects all platforms:
> > >> https://issues.apache.org/jira/browse/CB-4771
> > >>
> > >>
> > >> On Tue, Oct 22, 2013 at 4:25 PM, Shazron <sh...@gmail.com> wrote:
> > >>
> > >>> Gonna look over all the iOS issues tomorrow. Most of them are just
> > >>> straight copy and paste jobs (yay for them all being plugins!). When
> > is the
> > >>> schedule for release? (since we have 3.2 on the plate as well)
> > >>>
> > >>>
> > >>> On Tue, Oct 22, 2013 at 8:26 AM, Andrew Grieve <agrieve@chromium.org
> > >wrote:
> > >>>
> > >>>> Thanks Joe!
> > >>>>
> > >>>> Will work on the IAB & UriResolvers issues right now.
> > >>>>
> > >>>>
> > >>>> On Tue, Oct 22, 2013 at 11:17 AM, Joe Bowser <bo...@gmail.com>
> > wrote:
> > >>>>
> > >>>> > There are some 3.0.0 bugs that don't exist in 2.9.0.
> > >>>> >
> > >>>> > On Mon, Oct 21, 2013 at 4:57 PM, Josh Soref <
> jsoref@blackberry.com>
> > >>>> wrote:
> > >>>> > > On 10/21/13 7:38 PM, "Jesse" <pu...@gmail.com> wrote:
> > >>>> > >>Having a tonne of fun
Re: 2.9.1 Backport release
Posted by Jesse <pu...@gmail.com>.
Okay, I am ready to tag the js, and get to releasing ...
Where is everyone else at?
@purplecabbage
risingj.com
On Thu, Oct 24, 2013 at 2:43 PM, Shazron <sh...@gmail.com> wrote:
> https://issues.apache.org/jira/browse/CB-5189
>
> Integrated everything for iOS, and tested on iOS 7 and 6 (I have no iOS 5
> device).
>
> Results below.
>
> AutoTests:
> =======
> iOS 7.0.3 (all pass)
> iOS 6.1.4 (all pass)
>
> Manual Tests (iOS 6.1.4)
> ===========
> Media Record (pass)
> Splashscreen (pass)
> InAppBrowser (pass - but got a "multiple loadstart events (2)" popup error
> each time a page was loaded - I think this the test is causing this)
> Accelerometer (pass)
> Camera (pass)
> Media Capture Audio (pass)
>
> Manual Tests (iOS 7.0.3)
> ===========
> Media Record (pass)
> Splashscreen (pass)
> InAppBrowser (pass)
> Accelerometer (pass)
> Camera (pass)
> Media Capture Audio (pass, but UI is "shifted up" a bit, instead of
> sticking to the bottom, un-related to recording)
>
>
>
> On Wed, Oct 23, 2013 at 5:16 PM, Shazron <sh...@gmail.com> wrote:
>
> > iOS tracked as subtask under
> https://issues.apache.org/jira/browse/CB-5189
> >
> >
> > On Wed, Oct 23, 2013 at 2:55 PM, Shazron <sh...@gmail.com> wrote:
> >
> >> Will integrate:
> >>
> >> 1. https://issues.apache.org/jira/browse/CB-4958 (Camera - iOS 7)
> >> 2. https://issues.apache.org/jira/browse/CB-4930 (InAppBrowser - iOS 7)
> >> 3. https://issues.apache.org/jira/browse/CB-4847 (Media/Media Capture -
> >> iOS 7)
> >> 4. https://issues.apache.org/jira/browse/CB-4825 (Device Motion)
> >> 5. https://issues.apache.org/jira/browse/CB-5035 (Device Motion)
> >>
> >> These should be relatively straightforward copy paste jobs, then test on
> >> mobile spec.
> >>
> >> This one is more of a cordova-js thing where it affects all platforms:
> >> https://issues.apache.org/jira/browse/CB-4771
> >>
> >>
> >> On Tue, Oct 22, 2013 at 4:25 PM, Shazron <sh...@gmail.com> wrote:
> >>
> >>> Gonna look over all the iOS issues tomorrow. Most of them are just
> >>> straight copy and paste jobs (yay for them all being plugins!). When
> is the
> >>> schedule for release? (since we have 3.2 on the plate as well)
> >>>
> >>>
> >>> On Tue, Oct 22, 2013 at 8:26 AM, Andrew Grieve <agrieve@chromium.org
> >wrote:
> >>>
> >>>> Thanks Joe!
> >>>>
> >>>> Will work on the IAB & UriResolvers issues right now.
> >>>>
> >>>>
> >>>> On Tue, Oct 22, 2013 at 11:17 AM, Joe Bowser <bo...@gmail.com>
> wrote:
> >>>>
> >>>> > There are some 3.0.0 bugs that don't exist in 2.9.0.
> >>>> >
> >>>> > On Mon, Oct 21, 2013 at 4:57 PM, Josh Soref <js...@blackberry.com>
> >>>> wrote:
> >>>> > > On 10/21/13 7:38 PM, "Jesse" <pu...@gmail.com> wrote:
> >>>> > >>Having a tonne of fun putting the bunny back in the box.
> >>>> > >>Here is a list of plugin defects [1] that have been closed
> between
> >>>> 2.9.0
> >>>> > >>and 3.1.0
> >>>> > >>Please have a look and decide if you think each is worth the
> effort
> >>>> of
> >>>> > >>backporting.
> >>>> > >>
> >>>> > >>[1] https://issues.apache.org/jira/browse/CB-5136
> >>>> > >
> >>>> > > While I don't intend to ever use old versions, here's a short
> >>>> opinion on
> >>>> > > each:
> >>>> > >
> >>>> > > + CB-4656 <https://issues.apache.org/jira/browse/CB-4656> (
> >>>> android )
> >>>> > (Not applicable to 2.9.x, caused by UriResource Bug)
> >>>> >
> >>>> > > + CB-4471 <https://issues.apache.org/jira/browse/CB-4471> (
> >>>> android )
> >>>> > (Sadly, this isn't a fix, it's just suppressing the NPE. This is in
> >>>> > the 2.9.x branch)
> >>>> >
> >>>> > > - CB-3569 <https://issues.apache.org/jira/browse/CB-3569> (
> >>>> android )
> >>>> > This still needs to be done. If someone who is familiar with URI
> >>>> > resolvers want to take a crack at it, that'd be good.
> >>>> >
> >>>> > > + CB-4514 <https://issues.apache.org/jira/browse/CB-4514> (
> >>>> android )
> >>>> > This is in 2.9.x
> >>>> >
> >>>> > > + CB-4521 <https://issues.apache.org/jira/browse/CB-4521> (
> >>>> android )
> >>>> > This is in 2.9.x
> >>>> >
> >>>> > > - CB-4864 <https://issues.apache.org/jira/browse/CB-4864> (
> >>>> android )
> >>>> > This doesn't need to be in 2.9.x
> >>>> >
> >>>> > > + CB-3747 <https://issues.apache.org/jira/browse/CB-3747> (
> >>>> android )
> >>>> > > + CB-4858 <https://issues.apache.org/jira/browse/CB-4858> (
> >>>> android )
> >>>> > > + CB-4087 <https://issues.apache.org/jira/browse/CB-4087> (
> >>>> android )
> >>>> > > + CB-4586 <https://issues.apache.org/jira/browse/CB-4586> (
> >>>> android )
> >>>> > InAppBrowser bugs that need to go in. We should backport
> InAppBrowser
> >>>> > entirely, but I would like the resolutions fleshed out a bit, since
> I
> >>>> > have no idea how these were fixed other than the commit. I couldn't
> >>>> > reproduce the stupid video bug on any of the devices that I tested
> >>>> > this on.
> >>>> >
> >>>> > Also, there's JS changes that were made. Andrew, since you own this
> >>>> > one, can you backport this?
> >>>> >
> >>>> > > + CB-3628 <https://issues.apache.org/jira/browse/CB-3628> (
> >>>> android )
> >>>> > > -- good luck, the bug has no indication of what work was done
> >>>> > This is a 3.x bug only.
> >>>> >
> >>>> > I think this exercise shows that we have to be better about
> write-ups
> >>>> > when we close bugs, or at least better about repro cases and writing
> >>>> > tests. There's some cases where I have a test, but that test
> doesn't
> >>>> > have a home because it's Android-Specific so it doesn't belong in
> >>>> > Mobile-Spec, and it's a JS test so it doesn't really belong in the
> >>>> > test directory. :(
> >>>> >
> >>>>
> >>>
> >>>
> >>
> >
>
Re: 2.9.1 Backport release
Posted by Shazron <sh...@gmail.com>.
https://issues.apache.org/jira/browse/CB-5189
Integrated everything for iOS, and tested on iOS 7 and 6 (I have no iOS 5
device).
Results below.
AutoTests:
=======
iOS 7.0.3 (all pass)
iOS 6.1.4 (all pass)
Manual Tests (iOS 6.1.4)
===========
Media Record (pass)
Splashscreen (pass)
InAppBrowser (pass - but got a "multiple loadstart events (2)" popup error
each time a page was loaded - I think this the test is causing this)
Accelerometer (pass)
Camera (pass)
Media Capture Audio (pass)
Manual Tests (iOS 7.0.3)
===========
Media Record (pass)
Splashscreen (pass)
InAppBrowser (pass)
Accelerometer (pass)
Camera (pass)
Media Capture Audio (pass, but UI is "shifted up" a bit, instead of
sticking to the bottom, un-related to recording)
On Wed, Oct 23, 2013 at 5:16 PM, Shazron <sh...@gmail.com> wrote:
> iOS tracked as subtask under https://issues.apache.org/jira/browse/CB-5189
>
>
> On Wed, Oct 23, 2013 at 2:55 PM, Shazron <sh...@gmail.com> wrote:
>
>> Will integrate:
>>
>> 1. https://issues.apache.org/jira/browse/CB-4958 (Camera - iOS 7)
>> 2. https://issues.apache.org/jira/browse/CB-4930 (InAppBrowser - iOS 7)
>> 3. https://issues.apache.org/jira/browse/CB-4847 (Media/Media Capture -
>> iOS 7)
>> 4. https://issues.apache.org/jira/browse/CB-4825 (Device Motion)
>> 5. https://issues.apache.org/jira/browse/CB-5035 (Device Motion)
>>
>> These should be relatively straightforward copy paste jobs, then test on
>> mobile spec.
>>
>> This one is more of a cordova-js thing where it affects all platforms:
>> https://issues.apache.org/jira/browse/CB-4771
>>
>>
>> On Tue, Oct 22, 2013 at 4:25 PM, Shazron <sh...@gmail.com> wrote:
>>
>>> Gonna look over all the iOS issues tomorrow. Most of them are just
>>> straight copy and paste jobs (yay for them all being plugins!). When is the
>>> schedule for release? (since we have 3.2 on the plate as well)
>>>
>>>
>>> On Tue, Oct 22, 2013 at 8:26 AM, Andrew Grieve <ag...@chromium.org>wrote:
>>>
>>>> Thanks Joe!
>>>>
>>>> Will work on the IAB & UriResolvers issues right now.
>>>>
>>>>
>>>> On Tue, Oct 22, 2013 at 11:17 AM, Joe Bowser <bo...@gmail.com> wrote:
>>>>
>>>> > There are some 3.0.0 bugs that don't exist in 2.9.0.
>>>> >
>>>> > On Mon, Oct 21, 2013 at 4:57 PM, Josh Soref <js...@blackberry.com>
>>>> wrote:
>>>> > > On 10/21/13 7:38 PM, "Jesse" <pu...@gmail.com> wrote:
>>>> > >>Having a tonne of fun putting the bunny back in the box.
>>>> > >>Here is a list of plugin defects [1] that have been closed between
>>>> 2.9.0
>>>> > >>and 3.1.0
>>>> > >>Please have a look and decide if you think each is worth the effort
>>>> of
>>>> > >>backporting.
>>>> > >>
>>>> > >>[1] https://issues.apache.org/jira/browse/CB-5136
>>>> > >
>>>> > > While I don't intend to ever use old versions, here's a short
>>>> opinion on
>>>> > > each:
>>>> > >
>>>> > > + CB-4656 <https://issues.apache.org/jira/browse/CB-4656> (
>>>> android )
>>>> > (Not applicable to 2.9.x, caused by UriResource Bug)
>>>> >
>>>> > > + CB-4471 <https://issues.apache.org/jira/browse/CB-4471> (
>>>> android )
>>>> > (Sadly, this isn't a fix, it's just suppressing the NPE. This is in
>>>> > the 2.9.x branch)
>>>> >
>>>> > > - CB-3569 <https://issues.apache.org/jira/browse/CB-3569> (
>>>> android )
>>>> > This still needs to be done. If someone who is familiar with URI
>>>> > resolvers want to take a crack at it, that'd be good.
>>>> >
>>>> > > + CB-4514 <https://issues.apache.org/jira/browse/CB-4514> (
>>>> android )
>>>> > This is in 2.9.x
>>>> >
>>>> > > + CB-4521 <https://issues.apache.org/jira/browse/CB-4521> (
>>>> android )
>>>> > This is in 2.9.x
>>>> >
>>>> > > - CB-4864 <https://issues.apache.org/jira/browse/CB-4864> (
>>>> android )
>>>> > This doesn't need to be in 2.9.x
>>>> >
>>>> > > + CB-3747 <https://issues.apache.org/jira/browse/CB-3747> (
>>>> android )
>>>> > > + CB-4858 <https://issues.apache.org/jira/browse/CB-4858> (
>>>> android )
>>>> > > + CB-4087 <https://issues.apache.org/jira/browse/CB-4087> (
>>>> android )
>>>> > > + CB-4586 <https://issues.apache.org/jira/browse/CB-4586> (
>>>> android )
>>>> > InAppBrowser bugs that need to go in. We should backport InAppBrowser
>>>> > entirely, but I would like the resolutions fleshed out a bit, since I
>>>> > have no idea how these were fixed other than the commit. I couldn't
>>>> > reproduce the stupid video bug on any of the devices that I tested
>>>> > this on.
>>>> >
>>>> > Also, there's JS changes that were made. Andrew, since you own this
>>>> > one, can you backport this?
>>>> >
>>>> > > + CB-3628 <https://issues.apache.org/jira/browse/CB-3628> (
>>>> android )
>>>> > > -- good luck, the bug has no indication of what work was done
>>>> > This is a 3.x bug only.
>>>> >
>>>> > I think this exercise shows that we have to be better about write-ups
>>>> > when we close bugs, or at least better about repro cases and writing
>>>> > tests. There's some cases where I have a test, but that test doesn't
>>>> > have a home because it's Android-Specific so it doesn't belong in
>>>> > Mobile-Spec, and it's a JS test so it doesn't really belong in the
>>>> > test directory. :(
>>>> >
>>>>
>>>
>>>
>>
>
Re: 2.9.1 Backport release
Posted by Shazron <sh...@gmail.com>.
iOS tracked as subtask under https://issues.apache.org/jira/browse/CB-5189
On Wed, Oct 23, 2013 at 2:55 PM, Shazron <sh...@gmail.com> wrote:
> Will integrate:
>
> 1. https://issues.apache.org/jira/browse/CB-4958 (Camera - iOS 7)
> 2. https://issues.apache.org/jira/browse/CB-4930 (InAppBrowser - iOS 7)
> 3. https://issues.apache.org/jira/browse/CB-4847 (Media/Media Capture -
> iOS 7)
> 4. https://issues.apache.org/jira/browse/CB-4825 (Device Motion)
> 5. https://issues.apache.org/jira/browse/CB-5035 (Device Motion)
>
> These should be relatively straightforward copy paste jobs, then test on
> mobile spec.
>
> This one is more of a cordova-js thing where it affects all platforms:
> https://issues.apache.org/jira/browse/CB-4771
>
>
> On Tue, Oct 22, 2013 at 4:25 PM, Shazron <sh...@gmail.com> wrote:
>
>> Gonna look over all the iOS issues tomorrow. Most of them are just
>> straight copy and paste jobs (yay for them all being plugins!). When is the
>> schedule for release? (since we have 3.2 on the plate as well)
>>
>>
>> On Tue, Oct 22, 2013 at 8:26 AM, Andrew Grieve <ag...@chromium.org>wrote:
>>
>>> Thanks Joe!
>>>
>>> Will work on the IAB & UriResolvers issues right now.
>>>
>>>
>>> On Tue, Oct 22, 2013 at 11:17 AM, Joe Bowser <bo...@gmail.com> wrote:
>>>
>>> > There are some 3.0.0 bugs that don't exist in 2.9.0.
>>> >
>>> > On Mon, Oct 21, 2013 at 4:57 PM, Josh Soref <js...@blackberry.com>
>>> wrote:
>>> > > On 10/21/13 7:38 PM, "Jesse" <pu...@gmail.com> wrote:
>>> > >>Having a tonne of fun putting the bunny back in the box.
>>> > >>Here is a list of plugin defects [1] that have been closed between
>>> 2.9.0
>>> > >>and 3.1.0
>>> > >>Please have a look and decide if you think each is worth the effort
>>> of
>>> > >>backporting.
>>> > >>
>>> > >>[1] https://issues.apache.org/jira/browse/CB-5136
>>> > >
>>> > > While I don't intend to ever use old versions, here's a short
>>> opinion on
>>> > > each:
>>> > >
>>> > > + CB-4656 <https://issues.apache.org/jira/browse/CB-4656> ( android
>>> )
>>> > (Not applicable to 2.9.x, caused by UriResource Bug)
>>> >
>>> > > + CB-4471 <https://issues.apache.org/jira/browse/CB-4471> ( android
>>> )
>>> > (Sadly, this isn't a fix, it's just suppressing the NPE. This is in
>>> > the 2.9.x branch)
>>> >
>>> > > - CB-3569 <https://issues.apache.org/jira/browse/CB-3569> ( android
>>> )
>>> > This still needs to be done. If someone who is familiar with URI
>>> > resolvers want to take a crack at it, that'd be good.
>>> >
>>> > > + CB-4514 <https://issues.apache.org/jira/browse/CB-4514> ( android
>>> )
>>> > This is in 2.9.x
>>> >
>>> > > + CB-4521 <https://issues.apache.org/jira/browse/CB-4521> ( android
>>> )
>>> > This is in 2.9.x
>>> >
>>> > > - CB-4864 <https://issues.apache.org/jira/browse/CB-4864> ( android
>>> )
>>> > This doesn't need to be in 2.9.x
>>> >
>>> > > + CB-3747 <https://issues.apache.org/jira/browse/CB-3747> ( android
>>> )
>>> > > + CB-4858 <https://issues.apache.org/jira/browse/CB-4858> ( android
>>> )
>>> > > + CB-4087 <https://issues.apache.org/jira/browse/CB-4087> ( android
>>> )
>>> > > + CB-4586 <https://issues.apache.org/jira/browse/CB-4586> ( android
>>> )
>>> > InAppBrowser bugs that need to go in. We should backport InAppBrowser
>>> > entirely, but I would like the resolutions fleshed out a bit, since I
>>> > have no idea how these were fixed other than the commit. I couldn't
>>> > reproduce the stupid video bug on any of the devices that I tested
>>> > this on.
>>> >
>>> > Also, there's JS changes that were made. Andrew, since you own this
>>> > one, can you backport this?
>>> >
>>> > > + CB-3628 <https://issues.apache.org/jira/browse/CB-3628> ( android
>>> )
>>> > > -- good luck, the bug has no indication of what work was done
>>> > This is a 3.x bug only.
>>> >
>>> > I think this exercise shows that we have to be better about write-ups
>>> > when we close bugs, or at least better about repro cases and writing
>>> > tests. There's some cases where I have a test, but that test doesn't
>>> > have a home because it's Android-Specific so it doesn't belong in
>>> > Mobile-Spec, and it's a JS test so it doesn't really belong in the
>>> > test directory. :(
>>> >
>>>
>>
>>
>
Re: 2.9.1 Backport release
Posted by Shazron <sh...@gmail.com>.
Will integrate:
1. https://issues.apache.org/jira/browse/CB-4958 (Camera - iOS 7)
2. https://issues.apache.org/jira/browse/CB-4930 (InAppBrowser - iOS 7)
3. https://issues.apache.org/jira/browse/CB-4847 (Media/Media Capture - iOS
7)
4. https://issues.apache.org/jira/browse/CB-4825 (Device Motion)
5. https://issues.apache.org/jira/browse/CB-5035 (Device Motion)
These should be relatively straightforward copy paste jobs, then test on
mobile spec.
This one is more of a cordova-js thing where it affects all platforms:
https://issues.apache.org/jira/browse/CB-4771
On Tue, Oct 22, 2013 at 4:25 PM, Shazron <sh...@gmail.com> wrote:
> Gonna look over all the iOS issues tomorrow. Most of them are just
> straight copy and paste jobs (yay for them all being plugins!). When is the
> schedule for release? (since we have 3.2 on the plate as well)
>
>
> On Tue, Oct 22, 2013 at 8:26 AM, Andrew Grieve <ag...@chromium.org>wrote:
>
>> Thanks Joe!
>>
>> Will work on the IAB & UriResolvers issues right now.
>>
>>
>> On Tue, Oct 22, 2013 at 11:17 AM, Joe Bowser <bo...@gmail.com> wrote:
>>
>> > There are some 3.0.0 bugs that don't exist in 2.9.0.
>> >
>> > On Mon, Oct 21, 2013 at 4:57 PM, Josh Soref <js...@blackberry.com>
>> wrote:
>> > > On 10/21/13 7:38 PM, "Jesse" <pu...@gmail.com> wrote:
>> > >>Having a tonne of fun putting the bunny back in the box.
>> > >>Here is a list of plugin defects [1] that have been closed between
>> 2.9.0
>> > >>and 3.1.0
>> > >>Please have a look and decide if you think each is worth the effort of
>> > >>backporting.
>> > >>
>> > >>[1] https://issues.apache.org/jira/browse/CB-5136
>> > >
>> > > While I don't intend to ever use old versions, here's a short opinion
>> on
>> > > each:
>> > >
>> > > + CB-4656 <https://issues.apache.org/jira/browse/CB-4656> ( android )
>> > (Not applicable to 2.9.x, caused by UriResource Bug)
>> >
>> > > + CB-4471 <https://issues.apache.org/jira/browse/CB-4471> ( android )
>> > (Sadly, this isn't a fix, it's just suppressing the NPE. This is in
>> > the 2.9.x branch)
>> >
>> > > - CB-3569 <https://issues.apache.org/jira/browse/CB-3569> ( android )
>> > This still needs to be done. If someone who is familiar with URI
>> > resolvers want to take a crack at it, that'd be good.
>> >
>> > > + CB-4514 <https://issues.apache.org/jira/browse/CB-4514> ( android )
>> > This is in 2.9.x
>> >
>> > > + CB-4521 <https://issues.apache.org/jira/browse/CB-4521> ( android )
>> > This is in 2.9.x
>> >
>> > > - CB-4864 <https://issues.apache.org/jira/browse/CB-4864> ( android )
>> > This doesn't need to be in 2.9.x
>> >
>> > > + CB-3747 <https://issues.apache.org/jira/browse/CB-3747> ( android )
>> > > + CB-4858 <https://issues.apache.org/jira/browse/CB-4858> ( android )
>> > > + CB-4087 <https://issues.apache.org/jira/browse/CB-4087> ( android )
>> > > + CB-4586 <https://issues.apache.org/jira/browse/CB-4586> ( android )
>> > InAppBrowser bugs that need to go in. We should backport InAppBrowser
>> > entirely, but I would like the resolutions fleshed out a bit, since I
>> > have no idea how these were fixed other than the commit. I couldn't
>> > reproduce the stupid video bug on any of the devices that I tested
>> > this on.
>> >
>> > Also, there's JS changes that were made. Andrew, since you own this
>> > one, can you backport this?
>> >
>> > > + CB-3628 <https://issues.apache.org/jira/browse/CB-3628> ( android )
>> > > -- good luck, the bug has no indication of what work was done
>> > This is a 3.x bug only.
>> >
>> > I think this exercise shows that we have to be better about write-ups
>> > when we close bugs, or at least better about repro cases and writing
>> > tests. There's some cases where I have a test, but that test doesn't
>> > have a home because it's Android-Specific so it doesn't belong in
>> > Mobile-Spec, and it's a JS test so it doesn't really belong in the
>> > test directory. :(
>> >
>>
>
>
Re: 2.9.1 Backport release
Posted by Shazron <sh...@gmail.com>.
Gonna look over all the iOS issues tomorrow. Most of them are just straight
copy and paste jobs (yay for them all being plugins!). When is the schedule
for release? (since we have 3.2 on the plate as well)
On Tue, Oct 22, 2013 at 8:26 AM, Andrew Grieve <ag...@chromium.org> wrote:
> Thanks Joe!
>
> Will work on the IAB & UriResolvers issues right now.
>
>
> On Tue, Oct 22, 2013 at 11:17 AM, Joe Bowser <bo...@gmail.com> wrote:
>
> > There are some 3.0.0 bugs that don't exist in 2.9.0.
> >
> > On Mon, Oct 21, 2013 at 4:57 PM, Josh Soref <js...@blackberry.com>
> wrote:
> > > On 10/21/13 7:38 PM, "Jesse" <pu...@gmail.com> wrote:
> > >>Having a tonne of fun putting the bunny back in the box.
> > >>Here is a list of plugin defects [1] that have been closed between
> 2.9.0
> > >>and 3.1.0
> > >>Please have a look and decide if you think each is worth the effort of
> > >>backporting.
> > >>
> > >>[1] https://issues.apache.org/jira/browse/CB-5136
> > >
> > > While I don't intend to ever use old versions, here's a short opinion
> on
> > > each:
> > >
> > > + CB-4656 <https://issues.apache.org/jira/browse/CB-4656> ( android )
> > (Not applicable to 2.9.x, caused by UriResource Bug)
> >
> > > + CB-4471 <https://issues.apache.org/jira/browse/CB-4471> ( android )
> > (Sadly, this isn't a fix, it's just suppressing the NPE. This is in
> > the 2.9.x branch)
> >
> > > - CB-3569 <https://issues.apache.org/jira/browse/CB-3569> ( android )
> > This still needs to be done. If someone who is familiar with URI
> > resolvers want to take a crack at it, that'd be good.
> >
> > > + CB-4514 <https://issues.apache.org/jira/browse/CB-4514> ( android )
> > This is in 2.9.x
> >
> > > + CB-4521 <https://issues.apache.org/jira/browse/CB-4521> ( android )
> > This is in 2.9.x
> >
> > > - CB-4864 <https://issues.apache.org/jira/browse/CB-4864> ( android )
> > This doesn't need to be in 2.9.x
> >
> > > + CB-3747 <https://issues.apache.org/jira/browse/CB-3747> ( android )
> > > + CB-4858 <https://issues.apache.org/jira/browse/CB-4858> ( android )
> > > + CB-4087 <https://issues.apache.org/jira/browse/CB-4087> ( android )
> > > + CB-4586 <https://issues.apache.org/jira/browse/CB-4586> ( android )
> > InAppBrowser bugs that need to go in. We should backport InAppBrowser
> > entirely, but I would like the resolutions fleshed out a bit, since I
> > have no idea how these were fixed other than the commit. I couldn't
> > reproduce the stupid video bug on any of the devices that I tested
> > this on.
> >
> > Also, there's JS changes that were made. Andrew, since you own this
> > one, can you backport this?
> >
> > > + CB-3628 <https://issues.apache.org/jira/browse/CB-3628> ( android )
> > > -- good luck, the bug has no indication of what work was done
> > This is a 3.x bug only.
> >
> > I think this exercise shows that we have to be better about write-ups
> > when we close bugs, or at least better about repro cases and writing
> > tests. There's some cases where I have a test, but that test doesn't
> > have a home because it's Android-Specific so it doesn't belong in
> > Mobile-Spec, and it's a JS test so it doesn't really belong in the
> > test directory. :(
> >
>
Re: 2.9.1 Backport release
Posted by Andrew Grieve <ag...@chromium.org>.
Thanks Joe!
Will work on the IAB & UriResolvers issues right now.
On Tue, Oct 22, 2013 at 11:17 AM, Joe Bowser <bo...@gmail.com> wrote:
> There are some 3.0.0 bugs that don't exist in 2.9.0.
>
> On Mon, Oct 21, 2013 at 4:57 PM, Josh Soref <js...@blackberry.com> wrote:
> > On 10/21/13 7:38 PM, "Jesse" <pu...@gmail.com> wrote:
> >>Having a tonne of fun putting the bunny back in the box.
> >>Here is a list of plugin defects [1] that have been closed between 2.9.0
> >>and 3.1.0
> >>Please have a look and decide if you think each is worth the effort of
> >>backporting.
> >>
> >>[1] https://issues.apache.org/jira/browse/CB-5136
> >
> > While I don't intend to ever use old versions, here's a short opinion on
> > each:
> >
> > + CB-4656 <https://issues.apache.org/jira/browse/CB-4656> ( android )
> (Not applicable to 2.9.x, caused by UriResource Bug)
>
> > + CB-4471 <https://issues.apache.org/jira/browse/CB-4471> ( android )
> (Sadly, this isn't a fix, it's just suppressing the NPE. This is in
> the 2.9.x branch)
>
> > - CB-3569 <https://issues.apache.org/jira/browse/CB-3569> ( android )
> This still needs to be done. If someone who is familiar with URI
> resolvers want to take a crack at it, that'd be good.
>
> > + CB-4514 <https://issues.apache.org/jira/browse/CB-4514> ( android )
> This is in 2.9.x
>
> > + CB-4521 <https://issues.apache.org/jira/browse/CB-4521> ( android )
> This is in 2.9.x
>
> > - CB-4864 <https://issues.apache.org/jira/browse/CB-4864> ( android )
> This doesn't need to be in 2.9.x
>
> > + CB-3747 <https://issues.apache.org/jira/browse/CB-3747> ( android )
> > + CB-4858 <https://issues.apache.org/jira/browse/CB-4858> ( android )
> > + CB-4087 <https://issues.apache.org/jira/browse/CB-4087> ( android )
> > + CB-4586 <https://issues.apache.org/jira/browse/CB-4586> ( android )
> InAppBrowser bugs that need to go in. We should backport InAppBrowser
> entirely, but I would like the resolutions fleshed out a bit, since I
> have no idea how these were fixed other than the commit. I couldn't
> reproduce the stupid video bug on any of the devices that I tested
> this on.
>
> Also, there's JS changes that were made. Andrew, since you own this
> one, can you backport this?
>
> > + CB-3628 <https://issues.apache.org/jira/browse/CB-3628> ( android )
> > -- good luck, the bug has no indication of what work was done
> This is a 3.x bug only.
>
> I think this exercise shows that we have to be better about write-ups
> when we close bugs, or at least better about repro cases and writing
> tests. There's some cases where I have a test, but that test doesn't
> have a home because it's Android-Specific so it doesn't belong in
> Mobile-Spec, and it's a JS test so it doesn't really belong in the
> test directory. :(
>
Re: 2.9.1 Backport release
Posted by Joe Bowser <bo...@gmail.com>.
There are some 3.0.0 bugs that don't exist in 2.9.0.
On Mon, Oct 21, 2013 at 4:57 PM, Josh Soref <js...@blackberry.com> wrote:
> On 10/21/13 7:38 PM, "Jesse" <pu...@gmail.com> wrote:
>>Having a tonne of fun putting the bunny back in the box.
>>Here is a list of plugin defects [1] that have been closed between 2.9.0
>>and 3.1.0
>>Please have a look and decide if you think each is worth the effort of
>>backporting.
>>
>>[1] https://issues.apache.org/jira/browse/CB-5136
>
> While I don't intend to ever use old versions, here's a short opinion on
> each:
>
> + CB-4656 <https://issues.apache.org/jira/browse/CB-4656> ( android )
(Not applicable to 2.9.x, caused by UriResource Bug)
> + CB-4471 <https://issues.apache.org/jira/browse/CB-4471> ( android )
(Sadly, this isn't a fix, it's just suppressing the NPE. This is in
the 2.9.x branch)
> - CB-3569 <https://issues.apache.org/jira/browse/CB-3569> ( android )
This still needs to be done. If someone who is familiar with URI
resolvers want to take a crack at it, that'd be good.
> + CB-4514 <https://issues.apache.org/jira/browse/CB-4514> ( android )
This is in 2.9.x
> + CB-4521 <https://issues.apache.org/jira/browse/CB-4521> ( android )
This is in 2.9.x
> - CB-4864 <https://issues.apache.org/jira/browse/CB-4864> ( android )
This doesn't need to be in 2.9.x
> + CB-3747 <https://issues.apache.org/jira/browse/CB-3747> ( android )
> + CB-4858 <https://issues.apache.org/jira/browse/CB-4858> ( android )
> + CB-4087 <https://issues.apache.org/jira/browse/CB-4087> ( android )
> + CB-4586 <https://issues.apache.org/jira/browse/CB-4586> ( android )
InAppBrowser bugs that need to go in. We should backport InAppBrowser
entirely, but I would like the resolutions fleshed out a bit, since I
have no idea how these were fixed other than the commit. I couldn't
reproduce the stupid video bug on any of the devices that I tested
this on.
Also, there's JS changes that were made. Andrew, since you own this
one, can you backport this?
> + CB-3628 <https://issues.apache.org/jira/browse/CB-3628> ( android )
> -- good luck, the bug has no indication of what work was done
This is a 3.x bug only.
I think this exercise shows that we have to be better about write-ups
when we close bugs, or at least better about repro cases and writing
tests. There's some cases where I have a test, but that test doesn't
have a home because it's Android-Specific so it doesn't belong in
Mobile-Spec, and it's a JS test so it doesn't really belong in the
test directory. :(
Re: 2.9.1 Backport release
Posted by Josh Soref <js...@blackberry.com>.
On 10/21/13 7:38 PM, "Jesse" <pu...@gmail.com> wrote:
>Having a tonne of fun putting the bunny back in the box.
>Here is a list of plugin defects [1] that have been closed between 2.9.0
>and 3.1.0
>Please have a look and decide if you think each is worth the effort of
>backporting.
>
>[1] https://issues.apache.org/jira/browse/CB-5136
While I don't intend to ever use old versions, here's a short opinion on
each:
+ CB-4656 <https://issues.apache.org/jira/browse/CB-4656> ( android )
+ CB-4958 <https://issues.apache.org/jira/browse/CB-4958> ( iOS 7 )
+ CB-4471 <https://issues.apache.org/jira/browse/CB-4471> ( android )
- CB-4181 <https://issues.apache.org/jira/browse/CB-4181> ( iOS )
- CB-4192 <https://issues.apache.org/jira/browse/CB-4192> ( all )
+ CB-4900 <https://issues.apache.org/jira/browse/CB-4900> ( Win8 )
- CB-4592 <https://issues.apache.org/jira/browse/CB-4592> ( BB )
+ CB-4090 <https://issues.apache.org/jira/browse/CB-4090> ( WPx )
+ CB-2607 <https://issues.apache.org/jira/browse/CB-2607> ( WPx )
+ CB-1543 <https://issues.apache.org/jira/browse/CB-1543> ( WPx )
- CB-3569 <https://issues.apache.org/jira/browse/CB-3569> ( android )
- CB-4480 <https://issues.apache.org/jira/browse/CB-4480> ( iOS )
- CB-2828 <https://issues.apache.org/jira/browse/CB-2828> ( WPx )
+ CB-4054 <https://issues.apache.org/jira/browse/CB-4054> ( WPx )
- CB-4264 <https://issues.apache.org/jira/browse/CB-4264> ( iOS )
+ CB-4514 <https://issues.apache.org/jira/browse/CB-4514> ( android )
+ CB-4771 <https://issues.apache.org/jira/browse/CB-4771> ( all )
x CB-4090 <https://issues.apache.org/jira/browse/CB-4090> ( WPx )
-- you listed this already
+ CB-4521 <https://issues.apache.org/jira/browse/CB-4521> ( android )
+ CB-4147 <https://issues.apache.org/jira/browse/CB-4147> ( iOS )
- CB-4864 <https://issues.apache.org/jira/browse/CB-4864> ( android )
x CB-4988 <https://issues.apache.org/jira/browse/CB-4988> ( iOS 7 )
-- this is really CB-4930
+ CB-3747 <https://issues.apache.org/jira/browse/CB-3747> ( android )
+ CB-4858 <https://issues.apache.org/jira/browse/CB-4858> ( android )
+ CB-4087 <https://issues.apache.org/jira/browse/CB-4087> ( android )
+ CB-4930 <https://issues.apache.org/jira/browse/CB-4930> ( iOS 7 )
+ CB-4926 <https://issues.apache.org/jira/browse/CB-4926> ( win8 )
+ CB-4586 <https://issues.apache.org/jira/browse/CB-4586> ( android )
+ CB-4847 <https://issues.apache.org/jira/browse/CB-4847> ( iOS 7 )
x CB-4471 <https://issues.apache.org/jira/browse/CB-4471> ( android )
-- you listed this already
+ CB-3628 <https://issues.apache.org/jira/browse/CB-3628> ( android )
-- good luck, the bug has no indication of what work was done
x CB-4847 <https://issues.apache.org/jira/browse/CB-4847> ( iOS 7 )
-- you listed this already
Key:
+ probably worth it
- not worth it
x duplicate of another line in the list
Roughly:
- I don't see any reason to do work on mobile-spec -- it's a test right?
- For really obscure things, you have better things to do w/ your time.
- For crashers, it's probably worth doing
- For missing functionality to key areas, it's probably worth doing
(PUT is not in this bucket IMO, if people need it, let them upgrade to 3.x)
- For ugly behavior on a platform, it's probably worth doing
---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.