ITK/Policies and Procedures: Difference between revisions
Line 53: | Line 53: | ||
== Adding New Code to ITKv4 == | == Adding New Code to ITKv4 == | ||
[[ITK_Release_4/New_Code_Contribution_Process|ITK Policy and Procedures for Adding New Code to ITKv4]] | [[ITK_Release_4/New_Code_Contribution_Process|ITK Policy and Procedures for Adding New Code to ITKv4]] | ||
== Adding Tests == | == Adding Tests to ITKv4== | ||
[[ | [[ITK_Release_4/Modularization/_Add_tests|ITK Policy and Procedures for Adding Tests]] | ||
== Internationalization == | == Internationalization == | ||
[[ITK Policy and Procedures for Internationalization|Policy and Procedures for Internationalization]] | [[ITK Policy and Procedures for Internationalization|Policy and Procedures for Internationalization]] |
Revision as of 20:03, 15 September 2011
ITK policies describe the rules or guidelines for elements of the ITK software engineering process. Procedures describe how to implement these rules or guideline. Each policy includes either a procedure or has a corresponding page describing the procedure. This document organizes the policies and procedures in a single location.
A study of the Debian open source governance is described here.
NOTE; This page is under construction.
Adding Features
Policy and Procedures for Contributing New_Classes and Algorithms
Backward Compatibility
Backward Compatibility White Paper
Backward Compatibility Open Discussion
Design Principles
Coding Style
Code Coverage
Dynamic Analysis
Reporting and Fixing Bugs
Policy and Procedures for Reporting and Fixing Bugs
Generating a Release
Procedure for Generating a Release
Fixing Bugs in a Release
Procedure for Fixing Bugs in a Release Updated procedure for git
Becoming an ITK Developer
Policy and Procedures for Adding Developers
Adding Dashboards
Policy and Procedure for Adding Dashboards
Adding New Code to ITKv4
ITK Policy and Procedures for Adding New Code to ITKv4
Adding Tests to ITKv4
ITK Policy and Procedures for Adding Tests