Difference between revisions of "Developer Documentation"
From Mpich
| Line 1: | Line 1: | ||
* [[Getting And Building MPICH]] | * [[Getting And Building MPICH]] | ||
** [[Building MPICH For Development]] | ** [[Building MPICH For Development]] | ||
| − | ** [ | + | ** [[Git|Git usage in mpich]] |
* [[Branch Management]] | * [[Branch Management]] | ||
* [[Coding Standards]] | * [[Coding Standards]] | ||
Revision as of 19:02, 23 May 2013
- Getting And Building MPICH
- Branch Management
- Coding Standards
- Creating New Bug Tickets
- Using the Hydra Process Manager
- Checkpointing
- Student Projects
- Tools
- Frequently Asked Questions
- Testing
- Nightly Tests
- Special Tests - These tests are run manually, usually as part of gearing up for a release. Be sure to look at the date to make sure that you aren't looking at stale results. Information on running the special tests is at Testing MPICH#Running the Special Tests.
- Writing New Tests
- Testing Crons
- Code Coverage Reports
- Miscellaneous
- Design Docs: Category:Design Documents
- Using etags on the MPICH source tree
- Mailing lists
- Bug Tracking
- Recent Changes
- Fixing Bugs in Released Code
- Rules For Installation Targets
- Adding New Error Messages
- Creating a Release
- Managing Commits in Trunk and Release Branches
- Proposed MPIEXEC Extensions such as a standard set of command-line options for environment variables and support for multi-threaded applications.
- A list of assorted Compiler Quirks to be aware of.
- Auto-generated pages
