Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of fil@adobe.com designates
 64.18.1.37 as permitted sender)
From: Filip Maj <fil@adobe.com>
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Date: Thu, 11 Jul 2013 09:59:09 -0700
Subject: Re: Release 2.9.1 and 2.9.2
Thread-Topic: Release 2.9.1 and 2.9.2
Thread-Index: Ac5+V/jnG1gpUZTaQhK+SZzWafXyRQ==
Message-ID: <CE0431BC.22336%fil@adobe.com>
In-Reply-To: <15631647725E1342BFD5662917E1063A1E756C@sydexchtmp4.au.fjanz.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.3.5.130515
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Answers in-line.

On 7/11/13 1:39 AM, "Fowler, Angela" <angelaf@fast.au.fujitsu.com> wrote:

>Will 2.9.1 be available as a zip download? What changes will it include
>(in addition to the video duration issue)?

I think you are talking about cordova-cli. The tools are versioned
separately from the libraries, so 2.9.2, for example, does not contain any
updates to the libraries, only to the tools. So the answer is no.

>
>The latest version on npm is 2.9.2 but the VERSION is "dev". Is there an
>official date for this (and 2.9.1)?

No. The updates to the tools, especially patch versions, are released as
issues are found and resolved _for the tools themselves_. Minor revisions
are generally updated on the monthly releases of updates to the libraries.

>
>We would like to make a decision very soon on migrating from 2.7 to
>2.9.x but facing a few hurdles
>https://issues.apache.org/jira/browse/CB-4149

This issue reports a cordova-js issue, not a cli issue. Are you sure you
linked to the correct issue?

>
>Thanks,
>Angela
>
>-----Original Message-----
>From: agrieve@google.com [mailto:agrieve@google.com] On Behalf Of Andrew
>Grieve
>Sent: Monday, 8 July 2013 10:44 PM
>To: dev
>Subject: Re: Android Froyo (2.2 - 2.2.3) Deprecation in Cordova v2.9 or
>v3.0?
>
>The git commit log would be the most accurate source of truth. The .zip
>releases of Cordova include the git log output between releases (e.g.
>"git log 2.8.0..2.9.0" for each repository in the release)
>
>
>On Sun, Jul 7, 2013 at 10:21 PM, Fowler, Angela
><angelaf@fast.au.fujitsu.com
>> wrote:
>
>> Thanks for replies. We would prefer to go with a supported version of
>> Cordova rather than an older release if possible. What is the best way
>
>> to determine what has changed in a particular version?
>>
>> It seems that the change log for a version is based on the JIRA "fix
>> version" which may not accurately reflect what is changed in each
>> release. Is this correct?
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=3D12312
>> 42
>> 0&version=3D12324023
>>
>> For example the codec deprecation issue has fix version 3.0 listed
>> https://issues.apache.org/jira/browse/CB-3281
>>
>> There are also a number of issues which are fixed but have no fix
>> version (some maybe haven't been picked yet) and so will not appear in
>
>> the release notes
>> https://issues.apache.org/jira/issues/?jql=3Dproject%20%3D%20CB%20AND%20
>> re solution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20EMPTY
>>
>>
>> -----Original Message-----
>> From: brian.leroux@gmail.com [mailto:brian.leroux@gmail.com] On Behalf
>
>> Of Brian LeRoux
>> Sent: Saturday, 6 July 2013 8:25 AM
>> To: dev@cordova.apache.org
>> Subject: Re: Android Froyo (2.2 - 2.2.3) Deprecation in Cordova v2.9
>> or v3.0?
>>
>> That said, its important to note that the code and therefore tags
>> lives so you can still target those devices w/ older releases of
>> Cordova for as long as you need to.
>>
>> On Fri, Jul 5, 2013 at 1:12 PM, Joe Bowser <bowserj@gmail.com> wrote:
>> > Turns out that removing this didn't break anything on Froyo, so we
>> > did
>>
>> > it early.  We really wanted to remove support because we are running
>
>> > out of test devices and can't guarantee it'll still work.
>> >
>> > Basically any old version that has less than 5% of devices on Google
>
>> > Play will end up getting deprecated.
>> >  On Jul 5, 2013 12:18 AM, "Fowler, Angela"
>> > <angelaf@fast.au.fujitsu.com>
>> > wrote:
>> >
>> >> Hi devs,
>> >>
>> >>
>> >>
>> >> We are looking at moving from Cordova v2.7.0 to v2.9.x and have
>> >> some concerns about which Android platforms are still supported.
>> >> Froyo accounts for 3% of users on the Google Play Store.
>> >>
>> >>
>> >>
>> >> According to the deprecation policy, Froyo should still be in until
>> >> v3.0 http://wiki.apache.org/cordova/DeprecationPolicy
>> >>
>> >> The issue to remove Commons Codec dependency
>> >> https://issues.apache.org/jira/browse/CB-3281 has fix version 3.0
>> >>
>> >>
>> >>
>> >> I noticed in v2.9.0 that
>> >>
>> >> -          the create script no longer uses Commons Codec
>> >> https://github.com/apache/cordova-android/blob/2.9.x/bin/create.js
>> >>
>> >> -          org.apache.cordova.FileUtils and CameraLauncher replace
>> codec
>> >> with android.util.Base64
>> >> https://github.com/apache/cordova-android/commit/78efe2a960ba2b3206
>> >> 80
>> >> da1
>> >> 8b7c0fc20d442c604
>> >>
>> >> This issue also lists fix version 3.0
>> >> https://issues.apache.org/jira/browse/CB-3358
>> >>
>> >>
>> >>
>> >> Question 1: Should these changes be in version 2.9.x or 3.0.x? Also
>
>> >> are there any other changes you know of that may reduce supported
>> >> Android versions in v2.9?
>> >>
>> >>
>> >>
>> >> android.util.Base64
>> >>
>> >> The Android API says android.util.Base64 was added in API level 8
>> >> (Froyo
>> >> 2.2.x)
>> >> http://developer.android.com/reference/android/util/Base64.html
>> >>
>> >>
>> >>
>> >> Question 2 : Will Froyo continue to work in v2.9 or not?
>> >>
>> >> I've set the target SDK version to 8 to try this out in an emulator
>
>> >> but would be great to know if someone has checked on a Froyo
>device.
>> >>
>> >>
>> >>
>> >> Thanks
>> >>
>> >> Angela
>> >>
>> >>
>> >>
>> >>
>>
>>
>>
>