Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of fil@adobe.com designates
 64.18.1.29 as permitted sender)
From: Filip Maj <fil@adobe.com>
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Date: Wed, 2 Jan 2013 11:21:42 -0800
Subject: Re: 2.3.0 final?
Thread-Topic: 2.3.0 final?
Thread-Index: Ac3pHiHsWLWsFaO2Qp+J1ojWRBIJEg==
Message-ID: <CD09C8BB.14C52%fil@adobe.com>
In-Reply-To: 
 <CAMSbhBgV91j8uEo+vTwyyTk0RML_Lt=zSgeeb7kmQx9ueVE5_w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.2.5.121010
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

I'll set up the 2.3.0 tag issues in JIRA.

On 1/2/13 10:15 AM, "Steven Gill" <stevengill97@gmail.com> wrote:

>Lets tag this week!
>
>On Sun, Dec 30, 2012 at 11:36 AM, Filip Maj <fil@adobe.com> wrote:
>
>> Early JAN release it is! I went into holiday mode early :P
>>
>> On 12/20/12 12:35 PM, "Jesse MacFadyen" <purplecabbage@gmail.com> 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 <purplecabbage@gmail.com> 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 <b@brian.io> 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 <bowserj@gmail.com>
>>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 <fil@adobe.com> 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" <bowserj@gmail.com> wrote:
>> >> >>
>> >> >>>Can we start tagging the release today?
>> >> >>>
>> >> >>>On Wed, Dec 19, 2012 at 6:33 AM, Marcel Kinard
>><cmarcelk@gmail.com>
>> >> 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
>>
>>