Return-Path: 
 <dev-return-23716-apmail-cordova-dev-archive=cordova.apache.org@cordova.apache.org>
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 168131073D
	for <apmail-cordova-dev-archive@www.apache.org>;
 Wed, 12 Jun 2013 22:56:55 +0000 (UTC)
Received: (qmail 33317 invoked by uid 500); 12 Jun 2013 22:56:54 -0000
Delivered-To: apmail-cordova-dev-archive@cordova.apache.org
Received: (qmail 33269 invoked by uid 500); 12 Jun 2013 22:56:54 -0000
Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@cordova.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@cordova.apache.org>
List-Post: <mailto:dev@cordova.apache.org>
List-Id: <dev.cordova.apache.org>
Reply-To: dev@cordova.apache.org
Delivered-To: mailing list dev@cordova.apache.org
Received: (qmail 33261 invoked by uid 99); 12 Jun 2013 22:56:54 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Jun 2013 22:56:54 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of bowserj@gmail.com designates
 209.85.223.169 as permitted sender)
Received: from [209.85.223.169] (HELO mail-ie0-f169.google.com)
 (209.85.223.169)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Jun 2013 22:56:48 +0000
Received: by mail-ie0-f169.google.com with SMTP id 10so11267069ied.0
        for <dev@cordova.apache.org>; Wed, 12 Jun 2013 15:56:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=KoIWwi9iKOEo3FMWPSOMGZqehGbaClprEtAYji3PUeY=;
        b=jhdnDetQ8+GUL49xD9y4hqw2LvaPBbEiUJr/n1jQedPew3QQie/3XP1katDFYqxnqE
         tCrHf9dDm7kgI3bxS2/EJKMY3P/pTrh3fYXny5t2YQ/lOZ7uEFr+IWwOQutF+5HJ9cZX
         aeLV8NgpRFCbTlwoBuIqGhYCKYrVqf88K3SQCfXulxz8WdtxlkroKDu9Drk8GymUHXOs
         bnSkJ+arWw5UJwNctx6a1xaB9u6dqMQjjbrbZ8u1xedGNBFMTAj9FPVAac8TBMQBcQ13
         D88aiNf8k0zqaB7GdFOaICeMf/Pd/3tz9jBbrjW32GvJLLraJR4BoOMy1dO129fXr0N2
         nmYw==
MIME-Version: 1.0
X-Received: by 10.50.136.138 with SMTP id qa10mr4472292igb.53.1371077787188;
 Wed, 12 Jun 2013 15:56:27 -0700 (PDT)
Received: by 10.50.45.134 with HTTP; Wed, 12 Jun 2013 15:56:26 -0700 (PDT)
Date: Wed, 12 Jun 2013 15:56:26 -0700
Message-ID: 
 <CAOBL_k5vNKSq=iu+rZ5UKp3yjK26U69msbPgwuzsNj5v+_V+mA@mail.gmail.com>
Subject: 2.9.0rc1 this coming monday??
From: Joe Bowser <bowserj@gmail.com>
To: dev <dev@cordova.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Checked: Checked by ClamAV on apache.org

Hey

I know this is pretty soon, but how does a 2.9.0rc1 on Monday sound?
Since this is supposed to be a hardening release anyway, I don't see
why we shouldn't start with the RCs.

Any thoughts?

Joe