Update of /cvsroot/pure-data/htdocs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv23279
Modified Files: menu.inc Added Files: bug-report.php Log Message: added bug report,patches and feature requests description
--- NEW FILE: bug-report.php --- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<!-- $Id: bug-report.php,v 1.1 2004/10/19 14:59:32 ggeiger Exp $ -->
<HTML>
<HEAD> <TITLE>Pure Data External Repository</TITLE> <link rel="stylesheet" type="text/css" href="pd.css" media="screen"> </HEAD>
<BODY text="#000000" bgcolor="#ffffff" >
<h1>Pure Data External Repository</h1>
<div id="Menu">
<?php include('menu.inc'); ?> <br> <br> <?php include('quote.inc'); ?>
</div> <div id="Content"> <!-- Quote of the day -->
<h2>Bug reporting</h2>
<p> Bug reporting is done via the tracker system on sourceforge. Click on <a href="http://sourceforge.net/tracker/?func=add&group_id=55736&atid=478070">Submit Bug</a> to submit a bug against one of the subprojects. </p> <p> It is important that you assign the bug to the correct subproject. This is done by selecting the appropriate Category from the category tab. Before submitting a bug report, you might check if the bug you encountered hasn't been reported already by looking at the <a href=http://sourceforge.net/tracker/?group_id=55736&atid=478070%3Eopen bug reports</a> page. </p>
<h2>Patches</h2>
<p> There is another tracker which is used to submit patches against Pd and the subprojects. This tracker is a collection of up to date patches (patches that apply cleanly against the latest version of Pd in CVS). Patches that don't apply cleanly will be removed from the list (after notification, so the author has time to fix the problem). </p> <br> <p> All patches need to have a detailed description. This can later be used to decide if the patch can go into the main Pd distribution or not, and should also minimize the work that has to be done in order to adapt new ideas. Click to <a href="http://sourceforge.net/tracker/?func=add&group_id=55736&atid=478072">Submit a patch</a>. </p> <br> <p> If you submit a patch, take care that you only send the parts that have to be changed. Formatting changes and changes in whitespace will only make the patch less readable. Send the patch in unified diff format.<br> <br> e.g. from a CVS directory: <br> <br> cvs diff -uBw > cool_feature.patch <br>
<h2>Feature Requests</h2>
<p> There is also a tracker for feature requests. A feature request can be sent if you are missing a functionality, but you don't know how to code it. This could be and additional external, or functionality of the Pd core. </p> Click <a href="http://sourceforge.net/tracker/?func=add&group_id=55736&atid=478073">Add Feature Request</a> to add a new feature request.
<BR> <BR> <CENTER> <?php include('webring.inc'); ?> </CENTER> <BR> <?php include('lastmodified.inc'); ?>
</div>
</BODY>
Index: menu.inc =================================================================== RCS file: /cvsroot/pure-data/htdocs/menu.inc,v retrieving revision 1.3 retrieving revision 1.4 diff -C2 -d -r1.3 -r1.4 *** menu.inc 19 Oct 2004 11:55:43 -0000 1.3 --- menu.inc 19 Oct 2004 14:59:32 -0000 1.4 *************** *** 3,7 **** | <a href="documentation.php" title=""><b>Documentation</b></a><br> | <a href="developer.php" title=""><b>Developers</b></a><br> ! | <a href="bug-report.php" title=""><b>Bug reporting</b></a><br> | <a href="http://pure-data.info/community/lists/"><b>Mailing Lists</b></a><br> | <a href="contact.php" title=""><b>Contact</b></a><br> --- 3,7 ---- | <a href="documentation.php" title=""><b>Documentation</b></a><br> | <a href="developer.php" title=""><b>Developers</b></a><br> ! | <a href="bug-report.php" title=""><b>Bugs, Patches, FR</b></a><br> | <a href="http://pure-data.info/community/lists/"><b>Mailing Lists</b></a><br> | <a href="contact.php" title=""><b>Contact</b></a><br>
-
Guenter Geiger