VTK/Patch Procedure
From KitwarePublic
< VTK
Jump to navigationJump to search
Revision as of 15:34, 16 March 2009 by David.cole (talk | contribs) (New page: == VTK Patches == To submit a patch for inclusion in a VTK release branch (VTK-5-4 is the current release branch) please follow the directions on this page. Only those changes that have p...)
VTK Patches
To submit a patch for inclusion in a VTK release branch (VTK-5-4 is the current release branch) please follow the directions on this page. Only those changes that have passed the nightly dashboard test will be accepted for merging to the release branch. No exceptions.
Zack Galbreath (zack . galbreath _at_ kitware . com) is the current master of VTK merges.
- Commit your changes to CVS HEAD of VTK -- save the output of all cvs commits associated with your changes. This is critical for making corresponding merges on the release branch. Without this information, your patch will not be merged to the release branch.
- Wait overnight until the dashboard results are in
- If there are any problems on the dashboard, make changes to fix them and repeat from the "Commit" step
- Send email to Zack Galbreath with "VTK-5-4 Merge Request" as the subject
- Include your commit log comment and the cvs commit output for all your changes
