You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flex.apache.org by bu...@apache.org on 2013/04/15 14:16:58 UTC
svn commit: r858532 - in /websites/staging/flex/trunk: cgi-bin/ content/
content/community-getinvolved.html
Author: buildbot
Date: Mon Apr 15 12:16:57 2013
New Revision: 858532
Log:
Staging update by buildbot for flex
Modified:
websites/staging/flex/trunk/cgi-bin/ (props changed)
websites/staging/flex/trunk/content/ (props changed)
websites/staging/flex/trunk/content/community-getinvolved.html
Propchange: websites/staging/flex/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Apr 15 12:16:57 2013
@@ -1 +1 @@
-1467959
+1467962
Propchange: websites/staging/flex/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Apr 15 12:16:57 2013
@@ -1 +1 @@
-1467959
+1467962
Modified: websites/staging/flex/trunk/content/community-getinvolved.html
==============================================================================
--- websites/staging/flex/trunk/content/community-getinvolved.html (original)
+++ websites/staging/flex/trunk/content/community-getinvolved.html Mon Apr 15 12:16:57 2013
@@ -216,7 +216,7 @@ squash bugs, do the following :</p>
<li>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.</li>
<li>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.</li>
<li>(optional) Run the functional test suite called <a href="https://cwiki.apache.org/FLEX/mustella-overview.html">Mustella</a> on your code. The <a href="https://cwiki.apache.org/FLEX/mustella-overview.html">Mustella tests</a> are available from the ANT script, but make sure you set it up first.</li>
-<li>Create a .patch file. If you are using an IDE, check your application menus for this option. <a href="http://www.sourcetreeapp.com/">SourceTree</a> has it under the Actions menu. If you are using git from the command line, use <code>git format-patch &lt;BRANCH&gt; --stdout > &lt;FLEX-007&gt;.patch</code> 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.</li>
+<li>Create a .patch file. If you are using an IDE, check your application menus for this option. <a href="http://www.sourcetreeapp.com/">SourceTree</a> has it under the Actions menu. If you are using git from the command line, use <code>git format-patch <BRANCH> --stdout > <FLEX-007>.patch</code> 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.</li>
<li>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.</li>
<li>Sit back and bask in the glory that you helped make Flex better!</li>
</ol>