Create and publish an official Trilinos Change Management Policy
Created by: maherou
While the Trilinos project has a rigorous backward compatibility policy, other forms of change management are not well define. This issue is for creating a more comprehensive statement of how we manage changes. The policy should cover these things (and probably more):
-
How we inform users of commits to the repository that could change numerical results. -
When these kinds of changes can be pushed into the repository and how. -
As we start to introduce non-deterministic algorithms, how do we indicate when a function may produce results that vary from run to run.
cc: @trilinos/framework