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
|
This file has some information on how to get access
to the latest PDL sources (mainly of interest
for potential developers). This should not be confused
with the latest public release which will always
be available from CPAN (if you don't know what that
is check the FAQ).
Public CVS repository at www.sourceforge.org
--------------------------------------------
From version PDL-2.003 onwards the source distribution is
in a publicly accessible CVS repository. The project is
hosted at the sourceforge site at
http://www.sourceforge.org/project/?form_grp=612
Starting from that URL you will find directions on how to check
out the current sources, browse the CVS repository online, etc.
If you would like to actively contribute to PDL development
don't hesitate to contact one of the project admins (listed
at the above URL) to apply for write access to the repository.
We strongly believe in the power of open source development!
If you do not know how to use CVS try 'man cvs' or 'info cvs'
and/or have a look at some of the online tutorials available
on the web. A nice concise one is at
http://www.cyclic.com/cvs/doc-blandy-text.html
Very good and complete is the online version of the CVS book at
http://cvsbook.red-bean.com/cvsbook.html
PDL Developer Guidelines:
-------------------------
The following guidelines are for any developer that has access
to the PDL CVS repository.
1) Before committing a change to the repository you should update:
- CHANGES file with a description of the change made.
- MANIFEST (using 'make manifest'), MANIFEST.SKIP, TODO files
if applicable.
2) Remember to include POD documentation for any functions you add to
the distribution.
- See Basic/Core/Core.pm for an example of
including POD documentation in .pm files.
- See Basic/Core/Primitive/Primitive.pd for
an example of including POD documentation
in PDL .pd files.
- read the documentation in PDL::Doc for a detailed
description of the PDL documentation conventions
2) Make sure you add a test case in the 't' directory for any
significant additional capability you add to the PDL
package.
3) Don't commit before you successfully built and passed
'make test'. But then again, don't keep your changes
private for too long to avoid conflicts with other
developers.
4) Bugs reported on the list should be entered into the bug
database and bugs closed when a patch has been committed as
a fix. (Primary responsibility for this task is the pumpking,
but other devels should be able to help.)
|
