From IGSTK

Contents 1 Transition to Git 1.1 How to maintain IGSTK main and Sandbox source control protocols 2 Modularization (reorganize source code directory after transition to GIT) 2.1 Proposed source directory structure 3 New features to be released 4 Supporting ITKv4 [Timing issue] 4.1 Proposal [To be discussed]

Transition to Git

How to maintain IGSTK main and Sandbox source control protocols

1. Have git master HEAD be the stable release of IGSTK main, tag major release and patches
2. Keep a permanent parallel branch : sandbox
3. Integrate bugTracking with main repository [How???]
4. Rules for push to master head
   • Only bug fixes
   • New features should go through code review and quality check and will be considered a release [to be discussed]
   • Rebase Sandbox branch after each push to master head, and resolve conflicts and test sandbox build

Modularization (reorganize source code directory after transition to GIT)

Proposed source directory structure

• Source
  • Algorithm
  • Common
  • DataIO
  • GUI
  • OpenIGTLink
  • Tracker
  • VideoGrabber
  • Visualization
• Utilities
  • SceneGraphVisualization
• ThirdParty
  • MicronTracker
  • NDI Certus
• Examples
• Testing
  • Data [Creates git submodule?]

New features to be released

• igstkAscension3DGTracker
• igstkNDICertusTracker
• Example/DataLogger

Supporting ITKv4 [Timing issue]

Proposal [To be discussed]

• Just do a cvs release with added features listed above
• Then move to git and only support ITKv4 in future releases.