[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jakarta-commons-dev
Subject:    svn commit: r607581 - /commons/proper/commons-build/trunk/xdocs/patches.xml
From:       rahul () apache ! org
Date:       2007-12-30 19:16:51
Message-ID: 20071230191651.9ED821A9838 () eris ! apache ! org
[Download RAW message or body]

Author: rahul
Date: Sun Dec 30 11:16:49 2007
New Revision: 607581

URL: http://svn.apache.org/viewvc?rev=607581&view=rev
Log:
Remove Jakarta references and other improvements. Reported by Roland Weber <ossfwot \
AT dubioso DOT net>.

Modified:
    commons/proper/commons-build/trunk/xdocs/patches.xml

Modified: commons/proper/commons-build/trunk/xdocs/patches.xml
URL: http://svn.apache.org/viewvc/commons/proper/commons-build/trunk/xdocs/patches.xml?rev=607581&r1=607580&r2=607581&view=diff
 ==============================================================================
--- commons/proper/commons-build/trunk/xdocs/patches.xml (original)
+++ commons/proper/commons-build/trunk/xdocs/patches.xml Sun Dec 30 11:16:49 2007
@@ -25,8 +25,8 @@
  <body>
   <section name="On Contributing Patches">
   <p>
-  The commons gets a fair number of submissions from developers new to jakarta.
-  A lot of information to help you do this exists around jakarta but it can be hard \
to find. +  The commons gets a fair number of submissions from developers new to \
contributing patches. +  A lot of information to help you do this exists, but it can \
be hard to find.  This document gathers up material about patches into one handy \
reference.  </p>
   <p>
@@ -112,7 +112,7 @@
     </li>
     <li>
         By mailing the patch as an attachment to the 
-        <a href='http://commons.apache.org/mail-lists.html'>appropriate dev mailing \
list</a>.  +        <a href='http://commons.apache.org/mail-lists.html'>dev mailing \
                list</a>. 
         The email subject should describe what the patch does and should be prefixed \
                
         by <code>[PATCH]</code>. Make sure that it's clear which component the patch \
                is for. 
         Ideally the component name should be the next word after \
<code>[PATCH]</code>. @@ -120,13 +120,14 @@
   </ul>
   </p>
   <p>
-  <em>But which way is better?</em> They are both equally acceptable! 
+  <em>But which way is better?</em> Please use JIRA, patches sent to the mailing \
lists are +  hard to track unless they are immediately acted upon! 
   </p>
   <p>If it's a big patch 
   then adding it to a bug report will save bandwidth on the mailing list (but \
remember   to include the url in any follow-up discussions). Using a bug report also \
allows you to   be automatically posted with status updates. Note that new bug \
                reports (and comments on
-  existing ones) automatically get mailed to the commons-dev email list so there's \
no +  existing ones) automatically get mailed to the issues email list so there's no
   need to post a separate email indicating that the patch has been created.
   </p>
   <p>
@@ -135,7 +136,7 @@
   developers out there wasting their time by developing independent fixes!
   </p>
   <p>
-  If there has already been discussion of the issue on the dev mailing list (but no \
bugzilla +  If there has already been discussion of the issue on the dev mailing list \
(but no JIRA  entry has been created), then posting the patch direct to the mailing \
list can be simpler.  </p>
   <p>


[prev in list] [next in list] [prev in thread] [next in thread]

Configure | About | News | Add a list | Sponsored by KoreLogic