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 justinmclean@gmail.com
 designates 209.85.220.47 as permitted sender)
Sender: Justin Mclean <justinmclean@gmail.com>
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1283)
Subject: Re: Working towards a 4.9 Release Candidate
From: Justin Mclean <justin@classsoftware.com>
In-Reply-To: <CCE4C6F8.1FECE%cframpto@adobe.com>
Date: Thu, 6 Dec 2012 03:43:05 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <65D1160A-0B19-4116-8E90-F649C8BB2AC6@classsoftware.com>
References: <CCE4C6F8.1FECE%cframpto@adobe.com>
To: flex-dev@incubator.apache.org

Hi,

> What version of FP and AIR are you planning to use for the release?
Very good question. Does anyone have any stats on modern FP usage? While =
there's not any major reason I can see to up the FP version, I'm sure =
there would be interest in an updated AIR version.

> I will check in the chart tests before the end of the week.  We got
> permission from the Adobe VP to do so.
OK thanks. If you could merge those into the release branch when you do =
so that would be appreciated.

> I am working on integrating the adobe.next changes into develop.  I've
> submitted about 80-90% of the bug fixes already.  Right now I'm =
working on
> the s:DataGrid changes and I have a few other random bug fixes I =
haven't
> submitted yet.
Might be useful if they also get merged into the release branch, but I =
guess we have the draw a line somewhere.

> Justin - I thought develop would be merged to trunk and we'd release =
from
> there yet I see you made another branch.

My understanding of the gitflow model[1] is that you need to create a =
release branch and work in that, once it's all working then you merge =
into trunk. If you look at the diagram in [1] master can be thought of =
as trunk.

Thanks,
Justin

[1] http://nvie.com/posts/a-successful-git-branching-model/=