PDL Development


Report a bug	Request a feature	Help with development

Report a bug

To report a bug, open a "New issue" on PDL's GitHub page. You may have to sign in or sign up for a GitHub account before reporting a new bug.

Request a feature

To request a feature, open a "New issue" on PDL's GitHub page. You may have to sign in or sign up for a GitHub account before requesting a new feature.

Help with development

For over 20 years, PDL development was hosted by SourceForge. With the release of PDL 2.019 in May 2018, development is now hosted at GitHub. However, the project still uses a few items at SourceForge.

Tool	GitHub	SourceForge
Mailing Lists	No	pdl-general and pdl-devel mailing lists
Bugs, Feature requests	New issues	No (historical only)
Source Code	PDL and related modules	pdl.perl.org website
Large derivative files	Attached to Releases	No (historical only)

Hints for developers

If you are not familiar with Git, there are many online resources, tutorials, and cheat sheets from which to learn.
Before committing a change to the repository you should update
- MANIFEST (using make manifest), MANIFEST.SKIP, TODO files if applicable.
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.
Make sure you add a test case in the 't' directory for any significant additional capability you add to the PDL package.
Don't commit before you successfully built and passed make test. Use Git branches and GitHub's Pull Requests to test your changes on a wide variety of platforms, Perl versions, and environment combinations before merging your changes into the master branch.
Use branches for long-running projects. Git has excellent support for branching and merging. Use it!
Bugs reported on the list should be entered into the issue tracker 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.)