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 38705E561 for ; Wed, 2 Jan 2013 18:16:21 +0000 (UTC) Received: (qmail 35289 invoked by uid 500); 2 Jan 2013 18:16:20 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 35259 invoked by uid 500); 2 Jan 2013 18:16:20 -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 35251 invoked by uid 99); 2 Jan 2013 18:16:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Jan 2013 18:16:20 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of stevengill97@gmail.com designates 209.85.219.48 as permitted sender) Received: from [209.85.219.48] (HELO mail-oa0-f48.google.com) (209.85.219.48) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Jan 2013 18:16:14 +0000 Received: by mail-oa0-f48.google.com with SMTP id h2so13010040oag.7 for ; Wed, 02 Jan 2013 10:15:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=LyR9qj6xw47nmDwDjdE0a1qqlAzsuY5c23dJ8b5PETM=; b=AURAJCIz2fDRbS6Ilx5OHT90DOGB8xWPPWgQKgJTSJQRzjWjTkR4gtLCvu/ZkqM0My fUz5YhKTi3sv6PlwfzDYddt3r1/Z3PEL3d8Md+UBTnJBCkhfxRjpeHNVIpLi/MYy+Let nkgUsNZTMSvZXwYotUwZwy2krGDsYWoLb5j4ks6PlydnRxEcoxS8ByI52hX1vrNSF+7R 8W/lt1LymWZ7EKJF4Ul+xf+RRHjGeAPAWHZdGI9fiTqDWaSyQ3at3B93+h6+Mpo0aofq 6pRTT49CRAVGAwe1ut3wKnN/gmUhVMpN06uyDjTnMMTZxVIa6at3M/RTWp2v5lVfMdvA rIig== Received: by 10.60.27.166 with SMTP id u6mr25558523oeg.80.1357150553567; Wed, 02 Jan 2013 10:15:53 -0800 (PST) MIME-Version: 1.0 Received: by 10.76.27.230 with HTTP; Wed, 2 Jan 2013 10:15:33 -0800 (PST) In-Reply-To: References: <-108404182911554501@unknownmsgid> From: Steven Gill Date: Wed, 2 Jan 2013 10:15:33 -0800 Message-ID: Subject: Re: 2.3.0 final? To: dev@cordova.apache.org Content-Type: multipart/alternative; boundary=e89a8fb2058ea6f05904d2523c5e X-Virus-Checked: Checked by ClamAV on apache.org --e89a8fb2058ea6f05904d2523c5e Content-Type: text/plain; charset=ISO-8859-1 Lets tag this week! On Sun, Dec 30, 2012 at 11:36 AM, Filip Maj wrote: > Early JAN release it is! I went into holiday mode early :P > > On 12/20/12 12:35 PM, "Jesse MacFadyen" wrote: > > >Here's the chance to prove it doesn't take a week. Let's release 2.3.0 ! > >Today! > > > >Cheers, > > Jesse > > > > > >On 2012-12-19, at 12:05 PM, Jesse wrote: > > > >I would like to push 2.3.0 out before the break as well, before the end of > >the week. > >2.3.0 adds support for WP8, and while it IS currently available in rc2, it > >would be nice if it was available as part of the download from > >phonegap.com, > >which means a release. As it is, Microsoft and I will have several blog > >posts and videos alluding to 2.3.0 + WP8 but no link to go get it. > > > > > > > > > >On Wed, Dec 19, 2012 at 11:43 AM, Brian LeRoux wrote: > > > >> Michael brought this up yesterday w/ the suggestion that we make > >> cutting a release even easier still by including a standard ./release > >> script (actually he suggested ./configure but I think that convention > >> might come w/ unintended baggage). > >> > >> I'm not convinced the speed issue w/ cutting a release is the actual > >> compile/compose we do today---but it would make the Coho tool > >> significantly dumber which would make it way easier for downstream > >> distributions to live w/ what we do. > >> > >> I'm realizing--this warrants a new thread---I'll kick that up. > >> > >> On Wed, Dec 19, 2012 at 10:38 AM, Joe Bowser wrote: > >> > Actually, given that it takes us a week to actually do a release, I > >> > don't think we can get the final release out by the end of the week, > >> > even though it appears activity on the repositories is slowing down. > >> > :S > >> > > >> > I'll have to agree to a January release. > >> > > >> > On Wed, Dec 19, 2012 at 10:14 AM, Filip Maj wrote: > >> >> It's getting awfully close to a break. I'm heading out on vacation > >> >> tomorrow. > >> >> > >> >> How do people feel about letting rc2 simmer over the break and > >>releasing > >> >> 2.3 first thing January? > >> >> > >> >> On 12/19/12 10:10 AM, "Joe Bowser" wrote: > >> >> > >> >>>Can we start tagging the release today? > >> >>> > >> >>>On Wed, Dec 19, 2012 at 6:33 AM, Marcel Kinard > >> wrote: > >> >>>> +1, FWIW. I'd like to see 2.3.0 out before the break. > >> >>>> > >> >>>> -- Marcel Kinard > >> >>>> > >> >>>> > >> >>>> On 12/17/2012 1:25 PM, Joe Bowser wrote: > >> >>>>> > >> >>>>> Hey > >> >>>>> > >> >>>>> How about Wednesday/Thursday for tagging 2.3.0 final? I know > >>that we > >> >>>>> haven't fully released 2.3.0rc2, but I know that many, if not the > >> >>>>> majority of the committers are going to be on holiday at the end > >>of > >> >>>>> this week and it would be good if we could get 2.3.0 out before > >> break. > >> >>>>> > >> >>>>> Thoughts? > >> >>>>> > >> >>>>> Joe > >> >>>> > >> >>>> > >> >> > >> > > > > > > > >-- > >@purplecabbage > >risingj.com > > --e89a8fb2058ea6f05904d2523c5e--