Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <AB90EE23CEBB46248A52EF0107851BFD@KORODESKTOP>
From: "Dimitri k." <koro@noos.fr>
To: <flex-dev@incubator.apache.org>
References: <373d2df9$4c494033$2f247720$@com>
 <CAD0VuCJ3boqTKE4FtHB9MeLDF-9b39HhB9pMM9KLG-K=fuAkfA@mail.gmail.com>
Subject: Re: First Flex release as soon as possible? (was: So,
 what should we do first?)
Date: Thu, 5 Jan 2012 14:03:24 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit

From: "Iwo Banas" <banas.iwo@gmail.com>
>> I would go as far as to suggest that the first Apache Flex release should
>> equivalent in code to the current Adobe Flex 4.6 release.
>
> We can even keep the version as Apache Flex 4.6 to avoid the impression
> that we are releasing some new features.

I don't -1 it, but maybe this should require some thoughts.
If Apache would release a 4.6 SDK without any other benefit than a name 
change (keep in mind that the Adobe one is already open-source), and even 
with real drawbacks (no cached RSLs, maybe some tooling/IDE little issues), 
who would use it over the Adobe 4.6 one?

I understand the "spirit" behind it, but I think there is so much to do 
right now, that putting some of "our" ressources in a "symbolic" release 
would not be a good first step in our new era.
In Adobe's usual words, how much of your 100$ are you ready to invest in a 
symbolic release ;)