Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D627E200B4F for ; Tue, 26 Jul 2016 15:59:27 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D4B65160A75; Tue, 26 Jul 2016 13:59:27 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 25981160A69 for ; Tue, 26 Jul 2016 15:59:26 +0200 (CEST) Received: (qmail 39165 invoked by uid 500); 26 Jul 2016 13:59:26 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 39152 invoked by uid 99); 26 Jul 2016 13:59:25 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Jul 2016 13:59:25 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 6354B1A728F for ; Tue, 26 Jul 2016 13:59:25 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.198 X-Spam-Level: * X-Spam-Status: No, score=1.198 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id P6m3yW-VP_ES for ; Tue, 26 Jul 2016 13:59:24 +0000 (UTC) Received: from mail-io0-f180.google.com (mail-io0-f180.google.com [209.85.223.180]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id AB7D45F295 for ; Tue, 26 Jul 2016 13:59:23 +0000 (UTC) Received: by mail-io0-f180.google.com with SMTP id b62so21255517iod.3 for ; Tue, 26 Jul 2016 06:59:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=WtxLIwCUzIGdUdYPtgRau+aOlsjd3e+/NEzYpvHmwYk=; b=n5P9gPKjv5F8rRp5wEsbQaNv27mM5dc3Ln4tFa/u6GKj7LWkX4ImzbzHjUX/K38r4T BlTMgxG9z1ka4Kj92mW8FP5D4YbgX7WwZhgzhpvHY/a9amzYL3aus65iMIzYAaKL3+YY WaoaQQr0uuOCiC933P8Q9VQ1L+kvQpDB+xg2c/jBEIYf72HIX/uZupJ8/GvHt1Qtu78q 7GW1BQHDqOS6AQLaEQIkOWu9iROBWlLr8dQJCpoHXXprLuF89RHKB3FX5gJ79uAGAEGH +cNwh1FYvcQ2mx2tyeT7HI1jEvnGNcz04vjBZr2LKTg5RMJDMOvS/4DTCJUM2cGFGAXl Bxww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=WtxLIwCUzIGdUdYPtgRau+aOlsjd3e+/NEzYpvHmwYk=; b=XEIiZr+Oo07juBUK49EIlH4PVO2inXbLiqh5dL8OgEBKCCEioz9/PuBA16S1VYPCef A1ZV+KnE8Lo+7SVlPK8cMF/OQJvCt49g1lg/i88Cv7fWDB2pj1eg3V/7qGYfBQAb9923 G5JxdPs1rPSsWzqConQiv+c+FCNDeUXbehj4zOiTQIAm39T/GsRHa86cq2UZGhYl5QC/ qAcwfZ+M9PQDbvvC40sVFpxlud+MjjDJcP4e7NaRCF0DPhahfX2BIuB6/dswlou36z0i d7AwBmGtsBdxmJMZwX/mOWATpVyjN8E9/W78TpuGj3GLkvrkdXhfKREck3SThnVcE9lV v1ew== X-Gm-Message-State: AEkoouuNK745c6P63kboCe6jcvul33yNNkVajmModjBn8myzBFy7aVgdTTJCtTuWnhLq3elXFxZi9YMMBswsYQ== X-Received: by 10.157.7.119 with SMTP id 110mr11862605ote.145.1469541562366; Tue, 26 Jul 2016 06:59:22 -0700 (PDT) MIME-Version: 1.0 From: Victor Sosa Date: Tue, 26 Jul 2016 13:59:13 +0000 Message-ID: Subject: Android 5.2.1 not pinned in latest tools 6.3.0? To: "dev@cordova.apache.org" Content-Type: multipart/alternative; boundary=001a113dad7ccec12105388a4ee0 archived-at: Tue, 26 Jul 2016 13:59:28 -0000 --001a113dad7ccec12105388a4ee0 Content-Type: text/plain; charset=UTF-8 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! --001a113dad7ccec12105388a4ee0--