cocoon-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: xml-cocoon2/src/documentation/xdocs contrib.xml
Date Sun, 20 Jan 2002 23:59:38 GMT
crossley    02/01/20 15:59:38

  Modified:    src/documentation/xdocs contrib.xml
  Try to clarify patch submission procedure - still needs more editing.
  Revision  Changes    Path
  1.2       +13 -6     xml-cocoon2/src/documentation/xdocs/contrib.xml
  Index: contrib.xml
  RCS file: /home/cvs/xml-cocoon2/src/documentation/xdocs/contrib.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- contrib.xml	3 Jan 2002 12:31:01 -0000	1.1
  +++ contrib.xml	20 Jan 2002 23:59:38 -0000	1.2
  @@ -142,17 +142,15 @@
     <s2 title="Testing Requirements for Cocoon Contrib and Distribution">
  -   <p>All new code should be tested under the following servlet engines:</p>
  +   <p>All new code should be tested under at least the following servlet engines:</p>
       <li>Apache Tomcat 3.2.2</li>
  -    <li>[TODO]</li>
  -    <li>[TODO]</li>
  -   <p>It should also be tested on the following:</p>
  +   <p>It should also be tested on the following platforms:</p>
       <li>A Windows operating system</li>
       <li>A UNIX-type operating system</li>
  -    <li>A JDK version 1.2.x</li>
  +    <li>At least JDK version 1.2.x</li>
      <p>And obviously, it should be tested against the current CVS snapshot of Cocoon!</p>
  @@ -356,10 +354,19 @@
      As a rule-of-thumb, discuss an issue on the <code>cocoon-dev</code>
      mailing list first to work out any details.
      After it is confirmed to be worthwhile, and you are clear about it,
  -   then submit the bug description or patch via Bugzilla.
  +   then submit the bug description via Bugzilla.
  +   When you are sure about your proposed patch, then please submit it
  +   via Bugzilla, rather than as email to <code>cocoon-dev</code>.
  +   Be sure to add [Patch] to the summary line, as this enables the automatic
  +   patch alert system to keep track of it.
  +  </p>
  +  <p>
  +   When posting discussion topics to the <code>cocoon-dev</code> list,
  +   then please be patient.
      Perhaps you do not get any answer on your first reply, so just post
      it again until you get one. (But please not every hour - allow a few
      days for the list to deal with it.) Do not be impatient - remember that

In case of troubles, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message