POLICIES

(Note: Will likely be making pages for each page link, thus having to change links to new pages)

Policies

Below are some of the policies used by the Trilinos Project.

Definitions

• Primary, secondary, and tertiary stable code versus experimental code
• Primary development platform versus secondary development and testing platforms

Policies

Trilinos Framework and Tools Issues

• Collaborating through the publicTrilinos public git repository

• Policies associated with and list of Trilinos repositories

• Updating publicTrilinos, filtering public_Trilinos, and modifying exclusions for the release tarball

• How to make feature requests for the Trilinos Framework

• How to ask questions about the CMake build system or the CTest test driver

• Adding a new Trilinos package

• Backlog management

• Framework-level processes for maintaining stability

• Changing the official policies

• Creating a public branch

Source Code Issues

• Treatment of primary stable code verses secondary stable code

• Treatment of primary stable code verses experimental code

• Changing code in other packages for which you aren't a developer

• Namespace safety and use of standard C++ headers

Testing

• Proper pre-checkin process

• Remote testing and push process

• Trilinos Developer Policy for Maintaining the Stability of Trilinos

• Expectations for failed builds or tests

• Expectations for failed builds or tests for SIERRA

• Setting up automated nightly testing on personal machines

• Previewing website modifications