crossley 02/01/31 17:37:18
Modified: src/documentation/xdocs contrib.xml
Log:
Drat, i knew that other old words remained, about sending patches
to cocoon-dev. Direct them to Bugzilla instead.
Revision Changes Path
1.5 +6 -4 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.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- contrib.xml 31 Jan 2002 19:43:42 -0000 1.4
+++ contrib.xml 1 Feb 2002 01:37:18 -0000 1.5
@@ -40,8 +40,9 @@
<link href="http://xml.apache.org/from-cvs/xml-cocoon2/";>CVS snapshots</link>).
Review the <link href="todo.html">todo</link> list, choose a task
(or perhaps you have noticed something that needs patching). Make the
- changes, do the testing, generate a patch, and post to the cocoon-dev
- mailing list. (Do not worry - the process is easy and explained below.)
+ changes, do the testing, generate a patch, if you need then discuss it on
+ the cocoon-dev mailing list, and add the patch to Bugzilla.
+ (Do not worry - the process is easy and explained below.)
</p>
<p>
@@ -257,8 +258,9 @@
<p>
To contribute your modifications, you need to produce a plain-text file
- containing the differences between the master copy and yours. You will send
- this, along with an explanation of why it is required, to the
+ containing the differences between the master copy and yours. You will
+ submit this to Bugzilla along with an explanation of why it is required,
+ and perhaps discuss it on the
<code>cocoon-dev</code> mailing list. One of the authorised
maintainers of the repository will review the patch and then apply it to the
relevant branch.
----------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
