From e0fc7af22c9975b46f0828e0ef6597994dd5392d Mon Sep 17 00:00:00 2001 From: Guenter Geiger Date: Mon, 25 Oct 2004 10:39:25 +0000 Subject: updated Patches and Bugs information svn path=/trunk/; revision=2155 --- htdocs/bug-report.php | 24 ++++++++++++++++-------- 1 file changed, 16 insertions(+), 8 deletions(-) (limited to 'htdocs') 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 @@ - + @@ -24,11 +24,14 @@
+ +Bugs, Patches and Requested Features can be submitted via the Sourceforge +tracker system. Please read through the sections below. +

Bug reporting

-Bug reporting is done via the tracker system on sourceforge. Click on -Submit Bug to submit a bug against one of the subprojects. +Click on Submit Bug to submit a bug against one of the subprojects.

It is important that you assign the bug to the correct subproject. This @@ -36,18 +39,23 @@ 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 open bug reports page.

+Please, before reporting a bug, try out the latest version of the software.

Patches

-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 downloadable file on Miller Puckettes site or in the HEAD branch of the CVS.


+

+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. +

+

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 -- cgit v1.2.1