/
Checklist for Developing Features and Bug Fixes
Checklist for Developing Features and Bug Fixes
Step | Required for a feature? | Required for a bug? |
---|---|---|
Code follows coding style | Required | Required |
Design document in project documentation area | Required | Helpful for complex bugs |
Added PTL tests, or, if necessary, manual tests | Required | Required |
Added test output/logs | ||
Checked for memory leaks | ||
Join the pbspro community forum | Optional | Optional |
Sign the CLA | ||
Pull request consists of a single commit | ||
Commit is up to date | Whenever possible | Whenever possible |
Git ticket filed | Optional | Optional |
Code is signed off by at least one maintainer, and another contributor | Required | Required |
Code header contains license text | Required | Required |
PTL test header created by developer contains license text | Required | Required |
, multiple selections available,
Related content
Step-by-step Instructions for Bugfix or Feature
Step-by-step Instructions for Bugfix or Feature
More like this
Quick Start for OpenPBS Development
Quick Start for OpenPBS Development
Read with this
Choosing Something to Work On
Choosing Something to Work On
More like this
Design
Design
More like this
How to File Bugs and Feature Requests Against PBS Pro
How to File Bugs and Feature Requests Against PBS Pro
More like this
Where to Find It: GitHub, Confluence, etc.
Where to Find It: GitHub, Confluence, etc.
More like this