Difference between revisions of "Developer Documentation"
From Mpich
Line 22: | Line 22: | ||
** [[Etags|Using etags on the MPICH source tree]] | ** [[Etags|Using etags on the MPICH source tree]] | ||
** [http://www.mpich.org/support/mailing-lists/ Mailing lists] | ** [http://www.mpich.org/support/mailing-lists/ Mailing lists] | ||
− | ** [https://trac.mpich.org/mpich/report Bug Tracking] | + | ** [https://trac.mpich.org/projects/mpich/report Bug Tracking] |
** [https:///trac.mpich.org/mpich/timeline Recent Changes] ''(requires ANL login)'' | ** [https:///trac.mpich.org/mpich/timeline Recent Changes] ''(requires ANL login)'' | ||
** [[Fixing Bugs in Released Code]] | ** [[Fixing Bugs in Released Code]] |
Revision as of 22:07, 20 November 2012
- 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 (requires ANL login)
- 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