flex-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r858514 - in /websites/staging/flex/trunk: cgi-bin/ content/ content/community-getinvolved.html
Date Mon, 15 Apr 2013 08:38:43 GMT
Author: buildbot
Date: Mon Apr 15 08:38:43 2013
New Revision: 858514

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 08:38:43 2013
@@ -1 +1 @@
-1466916
+1467898

Propchange: websites/staging/flex/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Apr 15 08:38:43 2013
@@ -1 +1 @@
-1466916
+1467898

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 08:38:43 2013
@@ -212,12 +212,11 @@ a code sample that can help us reproduce
 squash bugs, do the following :</p>
 <ol>
 <li>Find a bug you want to work on, or submit one into <a href="https://issues.apache.org/jira/browse/FLEX">JIRA</a>.
 We have some marked as "easy" if you play with the JIRA filters if you want to start with
an easy one.  Make a comment on the ticket that you plan on working on it so others don't
duplicate your work.</li>
-<li>Check out the source code from SVN.  You may want to use an IDE like Eclipse or
IntelliJ with the proper plugins to do this
-for you.  More information is available on the <a href="dev-sourcecode.html">Source</a>
page.</li>
+<li>Check out the source code from GIT.  More information is available on the <a
href="dev-sourcecode.html">Source</a> page.</li>
 <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 [Mustella][5] on your code.  The
[Mustella tests][5] 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 SVN, VCS or Source Control
menus for this option.  If you are using svn from the command line, use <code>svn diff
&gt; myPatch.patch</code>.</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 SourceTree has it under the Actions menu.  If you are using git from the command
line, use <code>git show &gt; myPatch.patch</code>.</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>
@@ -229,7 +228,7 @@ they don't own and a 3rd party having a 
 <p>That being said, if you are interested in contributing code, you can submit patches
to the project via <a href="https://issues.apache.org/jira/browse/FLEX">JIRA</a>.
 To do this, create a new issue that describes what the code you are contributing, and submit
a .patch file with your
 code changes, just like from the bug squashing directions above.  If you submit a few patches
that meet the Apache
-standards, you will probably be contacted by the PMC to get you direct access to the SVN
and for you to be recognized
+standards, you will probably be contacted by the PMC to get you direct access to the GIT
and for you to be recognized
 for your work as a committer.</p>
 
 <!-- Home Page Exception -->



Mime
View raw message