On 12/18/12 9:50 AM, "Om" <bigosma...@gmail.com> wrote:
> In theory, yes. But the RCs are changing so fast that it is hard to keep
> track of. Since the next RC is going to be cut from the release branch, I
> think testing the release branch should be fine.
Actually, I think I am going to claim that the only "correct" procedure is
to test the actual RC. That ensures that nothing went wrong in the
packaging. Otherwise, how can you really vote on the RC? I guess you can
bin-diff the files in the RC vs the release branch and show that there are
no differences, but that seems like an extra and slow step.
Also, right now I think that there might be some changes to mustella in the
develop branch that haven't been sync'd over to release 4.9. Step 0 in the
future should be to run mustella on the develop branch before cutting the
release branch.
My recipe (on Win, will try to run Mac tonight):
-Download the RC.
-Unzip to a folder (c:\apacheflex4.9)
-Change the build.properties if you are trying different player version
-Setup the required environment variables
-Make sure FLASHPLAYER_DEBUGGER environment variable is pointing to right
player if you are using a different player version
-run ant main checkintests
-Set FLEX_HOME environment variable to the folder
(FLEX_HOME=c:/apacheflex4.9). Note the forward slash for Cygwin.
-Change to develop branch's mustella folder
-Uncomment and edit local.properties to point sdk.dir to c:/apacheflex4.9
-run ./mini_run.sh -all
-run ./mini_run.sh -failures -rerun
Prerequisites:
Ant
AIR SDK
PlayerGlobal.swc
HTTP server (assumes port 80, if you need to use 8080, then add
-addArg=-include=Localhost8080 to mustella runs.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
