Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of shazron@gmail.com designates
 209.85.128.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAE6O_-Zi8-3m8+FyawAehyoLs44R-6cO8hiKSRi_6-4ktBkkBQ@mail.gmail.com>
References: <967FE4CB-8DDF-4EDD-8282-2D6B0333A005@gmail.com>
 <CE707E2F.176A5%jheifetz@rim.com>
 <CAOBL_k5RNQY51ZjtRauw0v=66xmN=9DX_dPz2Bcmnp=E7XkCkg@mail.gmail.com>
 <CAE6O_-Zi8-3m8+FyawAehyoLs44R-6cO8hiKSRi_6-4ktBkkBQ@mail.gmail.com>
From: Shazron <shazron@gmail.com>
Date: Tue, 1 Oct 2013 12:39:40 -0700
Message-ID: 
 <CAE6O_-ZALGQHZNsuxizW3C9F4bKODjPj4SeLkXeu6LTmj6q69Q@mail.gmail.com>
Subject: Re: Tagging 3.1.0 today?
To: "dev@cordova.apache.org" <dev@cordova.apache.org>,
 "bowserj@apache.org" <bowserj@apache.org>
Content-Type: multipart/alternative; boundary=001a11c29f407ee92304e7b31fdb

--001a11c29f407ee92304e7b31fdb
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

One failure in Media plugin (set position) for both iOS 6 and 7. Should
this hold the release up? I would say no since we can always update the
plugin.

Unfortunately the splashscreen plugin has a typo (my bad) that results in a
visual failure on iOS 6 (decrementing a value twice):
https://git-wip-us.apache.org/repos/asf?p=3Dcordova-plugin-splashscreen.git=
;a=3Dblobdiff;f=3Dsrc/ios/CDVSplashScreen.m;h=3D8159ce17bda7a4d10277aa4cbc1=
32fa2c8e6e39d;hp=3Dba8d108b725f1a1d2331f8e8fc56627aac929ba5;hb=3D1111c8b3b9=
b8fe28d6c9fe9c9a1bc548a679e4ac;hpb=3D5f83eda5e829ac7a11e1803de653cb7cf95764=
af

I will have to patch that in dev and probably cherry-pick(?) into master -
how will this go?

iOS 6
one failure - Media media.spec.12 position should be set properly
Expected 0 to be greater than 0

iOS 7
one failure - Media media.spec.12 position should be set properly
Expected -0.023 to be greater than 0


On Tue, Oct 1, 2013 at 11:27 AM, Shazron <shazron@gmail.com> wrote:

> Going to tag iOS within the next hour.
>
>
> On Tuesday, October 1, 2013, Joe Bowser wrote:
>
>> Just tagged Android.  There's some weird inconsistencies across
>> devices, but overall the platform itself still seems solid.  There's
>> nothing here that would prevent a release.
>>
>> We should really start that API audit though.  These inconsistencies
>> don't make me super confident in the plugins. :(
>>
>> On Tue, Oct 1, 2013 at 10:27 AM, Jeffrey Heifetz
>> <jheifetz@blackberry.com> wrote:
>> > Since I believe Lorin is away, I have tagged the release for blackberr=
y.
>> >
>> > On 13-10-01 1:01 PM, "Marcel Kinard" <cmarcelk@gmail.com> wrote:
>> >
>> >>If any platform owners don't have time to do this today, let me know h=
ow
>> >>I can help.
>> >>
>> >>On Oct 1, 2013, at 11:11 AM, Andrew Grieve <agrieve@chromium.org>
>> wrote:
>> >>
>> >>> I think all that needs
>> >>> to happen now is for all platform owners to update their JS snapshot
>> >>>again
>> >>> and push a "3.1.0" tag.
>> >>
>> >
>> > ---------------------------------------------------------------------
>> > 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-publ=
ic
>> information. Any use of this information by anyone other than the intend=
ed
>> 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 unlaw=
ful.
>> >
>>
>

--001a11c29f407ee92304e7b31fdb--