htdocs/bug-report.php


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93

<!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 $  -->

<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>open 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>
The patches collection might also be useful for users, as it makes it possible
to get the freshest bugfixes and new features that didn't make it into the  
main distribution yet.
<a href="http://sourceforge.net/tracker/?group_id=55736&atid=478072">Check out the patches</a>.

<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 an 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>
<a href="http://sourceforge.net/tracker/?group_id=55736&atid=478073">Take a look at the feature requests"</a> that are already registered.
<BR>
<BR>
<CENTER>
<?php include('webring.inc'); ?>
</CENTER>
<BR>
<?php include('lastmodified.inc'); ?>

</div>

</BODY>