ITK Release 4/Users Migration Guide/Developer Migration Guide Workflow: Difference between revisions

From KitwarePublic
Jump to navigationJump to search
No edit summary
No edit summary
 
Line 1: Line 1:
[[File:MigrationGuideWorkFlow.pdf|PDF File]]
[[File:MigrationGuideWorkFlow.pdf|PDF File]]


Line 50: Line 49:
| [[File:MigrationGuideWorkFlow11.png]]
| [[File:MigrationGuideWorkFlow11.png]]
| '''Add Migration Guide Links'''
| '''Add Migration Guide Links'''
* Add a list to the XML file that shows each unique compilation error and links to the fix
* When committing changes to sequestered applications, developer will be asked for ID of Migration Guide Page
* Need more details on where fixes will live (phpBB, Git repo, ...?)
* Changes will be automatically linked to published migration guide page
|-
| [[File:MigrationGuideWorkFlow12.png]]
| '''Merge Directly to master'''
* Once all applications are fixed, merge the updated XML file directly to ''master''
* Do not need to go through Gerrit review process
|}
|}

Latest revision as of 19:37, 3 November 2010

File:MigrationGuideWorkFlow.pdf

MigrationGuideWorkFlow1.png Initial Setup
  • Published migration guide pulled directly from master XML files
  • Sequestered applications compiling correctly
MigrationGuideWorkFlow2.png Topic Branch
  • Standard git workflow
MigrationGuideWorkFlow3.png Local Changes
  • Standard git workflow
MigrationGuideWorkFlow4.png Migration Guide XML
  • Before pushing topic to Gerrit, must create a unique XML document that documents changes to API
  • XML documents will live in the source tree in a new directory
MigrationGuideWorkFlow5.png Gerrit Review
  • Standard Gerrit review process
  • Make any necessary changes
MigrationGuideWorkFlow6.png Finalize Migration Guide XML
  • Before review can be completed, the XML file must be revised to accurately reflect API changes
MigrationGuideWorkFlow7.png Merge to master
  • Merge the topic branch to master in the normal manner using stage
  • Once change is merged into master, the published migration guide will automatically update
  • Wait for nightly Sequestered Applications builds
MigrationGuideWorkFlow8.png Applications Fail
MigrationGuideWorkFlow9.png Create Applications Topic Branch
  • Checkout current version of sequestered applications
MigrationGuideWorkFlow10.png Fix Broken Applications
  • Make necessary changes to fix compilation errors for the applications
MigrationGuideWorkFlow11.png Add Migration Guide Links
  • When committing changes to sequestered applications, developer will be asked for ID of Migration Guide Page
  • Changes will be automatically linked to published migration guide page
Retrieved from "https://public.kitware.com/Wiki/index.php?title=ITK_Release_4/Users_Migration_Guide/Developer_Migration_Guide_Workflow&oldid=33594"