Also, I think it might be a good idea that if we include a 'prepare for RC' phase, I can switch the Mustella VM from the 'develop' branch to the 'RC' branch. That way, we know we're good for an RC if those runs pass and not if they fail. The 'develop' branch is always in motion and difficult to stabilise for a release.
Also, during an release, we might want to point the 'flex-sdk_release' job on builds@a.o at the 'RC' branch, so the nightlies from that point on to release will basically be the RC. This would also mean that the period we work on a release becomes more extended, which means more people (like myself) can plan to make some extra time available to help out... EdB On Sun, Oct 13, 2013 at 7:17 AM, Justin Mclean <jus...@classsoftware.com> wrote: > Hi, > >> I saw you were working towards a new release, but I had no idea what day >> you were actually going to go package stuff up and post it. > See my email on the 5th with the title "Apache Flex 4.11 release test", I did > ask if there was any objections then. > >> Therefore I'm not going to bother to review the RELEASE_NOTES > I've been update the RELEASE_NOTE s as we went along so there's shouldn't be > any major changes that are required. > > I've seen one minor issue in RC1 which has been fixed. > >> Please help me out by reviewing the README and RELEASE_NOTES > I asked that in JIRA. see https://issues.apache.org/jira/browse/FLEX-33755 > >> Haven't looked yet. > OK would be appreciated if you have some time. > > Thanks, > Justin > -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
