Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B18741007E for ; Thu, 17 Oct 2013 14:32:12 +0000 (UTC) Received: (qmail 33657 invoked by uid 500); 17 Oct 2013 14:32:12 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 33632 invoked by uid 500); 17 Oct 2013 14:32:12 -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 33624 invoked by uid 99); 17 Oct 2013 14:32:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Oct 2013 14:32:11 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mmocny@google.com designates 209.85.128.179 as permitted sender) Received: from [209.85.128.179] (HELO mail-ve0-f179.google.com) (209.85.128.179) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Oct 2013 14:32:07 +0000 Received: by mail-ve0-f179.google.com with SMTP id cz12so1037989veb.24 for ; Thu, 17 Oct 2013 07:31:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=HIuSGWKHuTvzT/DY3UV19cfGknraz4H6BczV41sW8QE=; b=Mcxtp1JhvZDnGKSECPpNCa6xAidJE+upAUrBiGAjPrqhGnT2xYjzyDIl/oDNK4qrFl hU5LS6eTOYGn+YcVB4ra1NQvqsfNS4eK6sg2KRM5+B7nSze/pLKqdC/eBz/nWxeeLLOB QgmyQPGY34CgnfCo6wBzT/8MkOiGPs2IdDHpWtn9bYLr+4Dh25HtlniHxpN4HFTjRnMA diU/OTYZFxdFSrM9oLYNRIRZXdxJ/3LW5bfjiNjIZHZCOiGotEb7nq5ItsuZCi36oV2b a5AVJh+2Rr9bHlEd6jPzRAPX/QBWLCz+dGTRVgdgocyJindJlxyFAIOYTJLXa1sC+cta z2NA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=HIuSGWKHuTvzT/DY3UV19cfGknraz4H6BczV41sW8QE=; b=EsFC+FPcGyaPLvMAZoKWTjziI0sAzNyu4rkKgpCF2o3Kw7Bi+iBtq5/zGLygUE6U/g Pw75bDDVxDBWt/pLKvakNPsnt+FE6ovGSa2cicN5ejVok/4QzeF6DhbxXFZRbcuAc3K6 jlsstdEX1o1oPrgPr2BX6peYrHslmE7Q1jkxA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:content-type; bh=HIuSGWKHuTvzT/DY3UV19cfGknraz4H6BczV41sW8QE=; b=PJvEUDIFP/nRA81OPB9mODUjESlDd5U5bR7pKL8X7QJZgIknGMvyY/UGedZTKs0o1G ROqDoMsniY4Fg8sJ7kEu2ZekuWVW+fb9VmAawkmcoDk2Z8nk8kRf90RshzxhN+MhNlIn Gf9rwZs3QMPCz+iWZiJOuEibgk8KGeRgBwiLSyLEQ0OOkmKeA9FsZMa7jukn9BtScrEU wfV5tgldC5D3yyZKKrv2dFf8WWrm+TostULqKXAnAsHjspuUVLG2PUM6YpVEkxcfxsz4 gtN0Rm+44H6q/1YqbIfhkFl9mvZQRb4jDjLqrYUBC8C31/JyU3g1/aLYaP0yf6VFHitG zZYw== X-Gm-Message-State: ALoCoQkQU0DTXL+N5CjGC56TZosvoCFiQve//nSTAVTEjKI30OmYrwEV0OfcCIPaVTyo+Bi9PCBBGOCfgFJYsmpGAlodU4pTJ1H9drTwds91KbiPLAq8ga8z3/iJr/toWsSjZJtdfeqKTAaxgblutpWkq4WqdBDn7y+59ODWpiwkU7mKiB2Kswx5dZbBeXb/dfS/AwexpQMflrsKOeNVLlLZojLuTOdJFQ== X-Received: by 10.52.118.98 with SMTP id kl2mr785105vdb.30.1382020306130; Thu, 17 Oct 2013 07:31:46 -0700 (PDT) MIME-Version: 1.0 Sender: mmocny@google.com Received: by 10.52.120.35 with HTTP; Thu, 17 Oct 2013 07:31:25 -0700 (PDT) In-Reply-To: References: From: Michal Mocny Date: Thu, 17 Oct 2013 10:31:25 -0400 X-Google-Sender-Auth: ORJp2UD8l9jaMNccHbD1dVNlYRM Message-ID: Subject: Re: Medic/Buildbot - building release versions To: dev Content-Type: multipart/alternative; boundary=089e013a0e046b6e6a04e8f0ad7e X-Virus-Checked: Checked by ClamAV on apache.org --089e013a0e046b6e6a04e8f0ad7e Content-Type: text/plain; charset=ISO-8859-1 I think using MS at master with released platform/cli was a powder keg waiting to explode. We shipped a broken 3.1 mobile spec, and so +1 to your suggestion of fixing it and moving CI back to test testing cadence releases with the matching MobileSpec. Side note: part of the problem seems to be that mobile spec is both an app and a set of plugins, and those plugins (namely the dependency plugin) weren't being updated on the plugin update schedule (weekly). We should make a note to do so in the future (or even move MS plugins out to another repo and add to registry?) -Michal On Thu, Oct 17, 2013 at 8:40 AM, David Kemp wrote: > TL;DR : Android release 3.1 is hard to test again due to added tests (to > master) that fail. patching 3.1 mobile-spec would be a good thing. > > Our plan here was to continuously build iOS and Android, both current > release and master (4 builds). To do this we build: > IOS_Master : iOS (master), plugins(dev), mobile-spec(master) > IOS_Release : iOS (3.1), plugins(master), mobile-spec(master) > Android_Master : iOS (master), plugins(dev), mobile-spec(master) > Android_Release : iOS (3.1), plugins(master, mobile-spec(master) > > The reason that mobile-spec master is used for release branches is because > the plugins were renamed just before 3.1, but the dependencies listed in > mobile-spec were not updated. > (cordova-mobile-spec/dependencies-plugin/plugin.xml) > > To avoid that problem, we switched to testing 3.1 with master mobile-spec. > Until last night that worked. > > However, now mobile-spec (master) has new tests added that will always fail > for 3.1. > > SO, I would like to patch 3.1 mobilespec with the plugin dependencies from > master. > > Any concerns? > --089e013a0e046b6e6a04e8f0ad7e--