Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
MIME-Version: 1.0
In-Reply-To: <CANDRhHD26f1f_m4iFSMRzPe6OPZPcL56z=a_FSdpyOA4Dr-6Lg@mail.gmail.com>
References: <CANDRhHD26f1f_m4iFSMRzPe6OPZPcL56z=a_FSdpyOA4Dr-6Lg@mail.gmail.com>
Date: Tue, 26 Jul 2016 07:51:04 -0700
Message-ID: <CAMSbhBg1v6rKStgAAp_2FYD=-H3gpJ3JDWbWsASsyzuKKqHi=w@mail.gmail.com>
Subject: Re: Android 5.2.1 not pinned in latest tools 6.3.0?
From: Steven Gill <stevengill97@gmail.com>
To: dev@cordova.apache.org
Content-Type: multipart/alternative; boundary=001a113d2dfeb137cf05388b0722
archived-at: Tue, 26 Jul 2016 14:51:11 -0000

--001a113d2dfeb137cf05388b0722
Content-Type: text/plain; charset=UTF-8

It should be ~5.2.0 that is pinned which grabs minor updates automatically.
So 5.2.1 should be default android.

On Jul 26, 2016 6:59 AM, "Victor Sosa" <sosah.victor@gmail.com> wrote:

> Hello all.
>
> I'm just noticing that the latest tools release (6.3.0) has Android
> platform v5.2.0 as the pinned version.
>
> http://cordova.apache.org/news/2016/07/13/tools-release.html
>
> I'm was keeping an eye on the fix for this defect
> https://issues.apache.org/jira/browse/CB-9489
>
> And it came in 5.2.1, which was released on July 11th, even before the
> tools release which happened on July 13th.
>
> http://cordova.apache.org/announcements/2016/07/11/cordova-android-5.2.1.html
>
> Just wondering if this is on purpose. If so, I'm assuming it is because the
> short time to test it and also assuming it'll be pinned in the next tools
> release (or a later android version with the fix in it).
>
> Thanks!
>

--001a113d2dfeb137cf05388b0722--