Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Received-SPF: pass (google.com: domain of justin@classsoftware.com designates
 10.68.201.1 as permitted sender) client-ip=10.68.201.1;
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1257)
Subject: Re: [Wiki] Decisions so far
From: Justin Mclean <justin@classsoftware.com>
In-Reply-To: 
 <CABtvQ7LDhnij55ctx_iRu=eJHXoVoxUwqHrcsMo6PaL=buKZyQ@mail.gmail.com>
Date: Thu, 1 Mar 2012 13:49:41 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E398C826-B9A9-4AED-B120-9A6CC45DB798@classsoftware.com>
References: 
 <CABtvQ7LDhnij55ctx_iRu=eJHXoVoxUwqHrcsMo6PaL=buKZyQ@mail.gmail.com>
To: flex-dev@incubator.apache.org

Hi,

That's a good start.

In regards to building with Ant I hate to bing this up (yet again) but =
it's probably better to say that Ant is the current way of building the =
project and people are welcome to submit other methods of building the =
SDK. There's been no decision as such it's just that the donated code =
base uses Ant as it's build tool.

Re versioning I thought (but could be mistaken) we we going for 4.8 as =
the initial release as Adobe may come out with some security patches =
etc.

I'd also add.
Until after the initial parity release it's preferred that any commits =
be made into a separate branch. The "patches" branch have been set up =
for this.

Until the Adobe JIRA bug base has been import it best to try and avoid =
creating JIRA issues that already exist in the Adobe JIRA bug base.

Coding style could be in the same format as the existing code. ie If you =
adding a patch to a file you should code in the same style as what is =
currently in the file.

Thanks,
Justin