Hi Carlos,
I'll follow the steps mentioned.
Got concerned since the number of Passes & Fails didn't match the lists
on wiki.
Thanks.
On 8/28/2012 5:46 PM, Carlos Rovira wrote:
Hi Kiel,
take into account that github is not synced with SVN right now, so
there you will not find the latest fixes to mustella for at least 2
weeks.
the team is working with INFRA to get official GIT support. For the
latest news this will resolved in the following 1 to 3 weeks.
In the meanwhile, we and others use the following path to work:
1) get SVN "develop" branch.
2) work in your local copy.
3) when you are done with a fix, extract the folder (I do this with
eclipse-subversive)
now:
4) in github, fork apache flex
5) in your machine clone the fork
6) create a branch
7) copy the extract folder created in 3) overlaying it (overwrite)
8) commit to the new branch
9) push to origin (github)
10) create a JIRA ticket
11) create a pull request
12) link the jira ticket to the pull request and viceversa
13) submit to this mailing list
This works because the layout folder structure is the same and the
failing mustella folders are untouched at the moment so you can
overwrite with your changes and make a pull request only with the
changes.
Alex, Peter and Carol are getting this pull request as patches without problem.
Best,
Carlos
2012/8/28 Kiel <kiel.s.sinfu...@gmail.com>:
Greetings,
How to do the Mustella tests on Git(Github)?
Will I fork "unstable"?
