You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flex.apache.org by ha...@apache.org on 2013/04/15 14:16:53 UTC
svn commit: r1467962 - /flex/site/trunk/content/community-getinvolved.cmsPage
Author: harbs
Date: Mon Apr 15 12:16:53 2013
New Revision: 1467962
URL: http://svn.apache.org/r1467962
Log:
Changed svn references on the get-involved page to git cont.
Modified:
flex/site/trunk/content/community-getinvolved.cmsPage
Modified: flex/site/trunk/content/community-getinvolved.cmsPage
URL: http://svn.apache.org/viewvc/flex/site/trunk/content/community-getinvolved.cmsPage?rev=1467962&r1=1467961&r2=1467962&view=diff
==============================================================================
--- flex/site/trunk/content/community-getinvolved.cmsPage (original)
+++ flex/site/trunk/content/community-getinvolved.cmsPage Mon Apr 15 12:16:53 2013
@@ -38,7 +38,7 @@ squash bugs, do the following :
3. Setup your build environment. Check out the README included in the source code on how to do this. You will want to make sure that you can perform a compile before you go much further.
4. Fix the bug. If you need help, ask the dev@flex.apache.org mailing list. I'm sure we have pointers to help you out.
5. (optional) Run the functional test suite called [Mustella][5] on your code. The [Mustella tests][5] are available from the ANT script, but make sure you set it up first.
-6. Create a .patch file. If you are using an IDE, check your application menus for this option. [SourceTree][6] has it under the Actions menu. If you are using git from the command line, use `git format-patch <BRANCH> --stdout > <FLEX-007>.patch` where <BRANCH> is the branch you want your patch be merged into from whether the branch you're working on, you can omit it if the origin and destination branch are the same and <FLEX-007>, the Jira Issue Id relative to your patch.
+6. Create a .patch file. If you are using an IDE, check your application menus for this option. [SourceTree][6] has it under the Actions menu. If you are using git from the command line, use `git format-patch <BRANCH> --stdout > <FLEX-007>.patch` where <BRANCH> is the branch you want your patch be merged into from whether the branch you're working on, you can omit it if the origin and destination branch are the same and <FLEX-007>, the Jira Issue Id relative to your patch.
7. Attach the .patch file to the JIRA ticket you noted earlier. A committer will review the patch and make sure it dosen't break anything else.
8. Sit back and bask in the glory that you helped make Flex better!