Return-Path: X-Original-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 75394B943 for ; Wed, 18 Jan 2012 21:06:49 +0000 (UTC) Received: (qmail 59505 invoked by uid 500); 18 Jan 2012 21:06:49 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 59436 invoked by uid 500); 18 Jan 2012 21:06:48 -0000 Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: flex-dev@incubator.apache.org Delivered-To: mailing list flex-dev@incubator.apache.org Received: (qmail 59428 invoked by uid 99); 18 Jan 2012 21:06:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jan 2012 21:06:48 +0000 X-ASF-Spam-Status: No, hits=0.6 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [74.125.149.209] (HELO na3sys009aog113.obsmtp.com) (74.125.149.209) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jan 2012 21:06:40 +0000 Received: from mail-ww0-f43.google.com ([74.125.82.43]) (using TLSv1) by na3sys009aob113.postini.com ([74.125.148.12]) with SMTP ID DSNKTxc0SXZm7LXnF5vQsYQgs/G4T5oacJn9@postini.com; Wed, 18 Jan 2012 13:06:20 PST Received: by mail-ww0-f43.google.com with SMTP id dr11so4059957wgb.12 for ; Wed, 18 Jan 2012 13:06:17 -0800 (PST) MIME-Version: 1.0 Received: by 10.180.73.72 with SMTP id j8mr28774206wiv.2.1326920777553; Wed, 18 Jan 2012 13:06:17 -0800 (PST) Received: by 10.216.171.18 with HTTP; Wed, 18 Jan 2012 13:06:17 -0800 (PST) In-Reply-To: References: <4F163487.9010504@spoon.as> <4F170553.5090102@spoon.as> Date: Wed, 18 Jan 2012 13:06:17 -0800 Message-ID: Subject: Re: Flex 3.x SDK? From: Deirdre Holub To: flex-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=f46d0438922397584d04b6d3d19d X-Virus-Checked: Checked by ClamAV on apache.org --f46d0438922397584d04b6d3d19d Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I want to stress this point. If the 3.x SDK does not make it in to Apache Flex, then all current code written in 3.x immediately becomes legacy code with no obvious path forward. Once that happens, it becomes much harder to argue in favor of giving Apache Flex a chance instead of just switching now to html/js/etc, because the risks of rewriting an app in one or the other is perceived to be equal. On Wed, Jan 18, 2012 at 9:53 AM, Quentin Le H=E9naff wro= te: > I totally agree, I do not understand why it would not be ; still some > innovating products are based on Flex 3 and not Flex 4 as the migration h= ad > some drawbacks and is expensive. > > Many projects have their own Flex base code, I've re-done many base > components ; this is very important to share them all or so much work wi= ll > be wasted. > > On Wed, Jan 18, 2012 at 6:45 PM, Keith Sutton wrote: > > > On 1/18/2012 8:21 AM, Doug McCune wrote: > > > >> Oh wow, I had no idea the 3.X branch might never make it into the Apac= he > >> project. I think that's a really bad idea. As others have mentioned, > lots > >> of large enterprises use 3.X (the app I work on included). I always ju= st > >> assumed that 3.6 would make it into Apache at the same time the latest > 4.x > >> branch would too. > >> > >> It was requested repeatedly at the Summit and Deepa and Danny > definitely > > said yes it would be. From a enterprise customer perspective it seems > > unavoidable. > > > --f46d0438922397584d04b6d3d19d--