aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGuenter Geiger <ggeiger@users.sourceforge.net>2004-10-25 10:39:25 +0000
committerGuenter Geiger <ggeiger@users.sourceforge.net>2004-10-25 10:39:25 +0000
commite0fc7af22c9975b46f0828e0ef6597994dd5392d (patch)
tree4a9954b40a64dc1c9f8ee0f591e831e90efca457
parent7bb4bd5e8769d0c35ba9aaef1b306759eb749e5d (diff)
updated Patches and Bugs information
svn path=/trunk/; revision=2155
-rw-r--r--htdocs/bug-report.php24
1 files changed, 16 insertions, 8 deletions
diff --git a/htdocs/bug-report.php b/htdocs/bug-report.php
index 6f15e6a5..31397890 100644
--- a/htdocs/bug-report.php
+++ b/htdocs/bug-report.php
@@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<!-- $Id: bug-report.php,v 1.3 2004-10-19 15:47:33 ggeiger Exp $ -->
+<!-- $Id: bug-report.php,v 1.4 2004-10-25 10:39:25 ggeiger Exp $ -->
<HTML>
@@ -24,11 +24,14 @@
<div id="Content">
<!-- Quote of the day -->
+
+Bugs, Patches and Requested Features can be submitted via the Sourceforge
+tracker system. Please read through the sections below.
+
<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.
+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
@@ -36,19 +39,24 @@ 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>open bug reports</a> page.
</p>
+Please, before reporting a bug, try out the latest version of the software.
<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).
+cleanly against the latest version of Pd. The latest version can either be
+found as a <a href="http://crca.ucsd.edu/~msp/Software/">downloadable file on Miller Puckettes site</a> or in the <a href="http://cvs.sourceforge.net/viewcvs.py/pure-data/pd/">HEAD branch of the CVS</a>.
</p>
<br>
<p>
+The main purpose of the patches tracker is to make it easier to incorporate
+changes and bug fixes into the Pd core. Including new stuff may take some
+time, and the inclusion of some features might not get accepted. This
+can have more reasons. We will try to comment on each rejected patch.
+</p>
+
+<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