Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of omuppi1@gmail.com designates
 209.85.212.173 as permitted sender)
MIME-Version: 1.0
Sender: omuppi1@gmail.com
In-Reply-To: <095B61A5-3BDD-4730-8070-DA7AC9115C0E@realeyes.com>
References: <CCE38096.496A4%aharui@adobe.com>
 <095B61A5-3BDD-4730-8070-DA7AC9115C0E@realeyes.com>
From: Om <bigosmallm@gmail.com>
Date: Tue, 4 Dec 2012 11:16:58 -0800
Message-ID: 
 <CACK5iZeh1j8A9qP74Ns=+XwrocSKVzZmO5ES+J5saw2eCoAr5A@mail.gmail.com>
Subject: Re: Next SDK Release Timing
To: flex-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=f46d04388e4980e3a304d00bb7f8

--f46d04388e4980e3a304d00bb7f8
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

My guess is that it will take at least a month to sort out the code, build,
test and have the artifacts prepared for a release.  Also, we want to make
changes to the Installer (ex. removing download of TLF since it is part of
the SDK now)

I think it would be better if we wait instead of trying to push another
release before we graduate.

Thanks,
Om

On Tue, Dec 4, 2012 at 10:42 AM, Jun Heider <jun@realeyes.com> wrote:

>
> On Dec 4, 2012, at 11:27 AM, Alex Harui wrote:
> > I=92m leaning towards waiting, but I feel bad for folks who are waiting=
 to
> see their work get out the door.  This will truly separate the Apache Fle=
x
> SDK from the Adobe Flex SDK because non-Adobe code will finally be releas=
ed!
> >
> > Thoughts?
>
> Good things come to those who wait is my thought.

--f46d04388e4980e3a304d00bb7f8--