ITK Release 4/What Developers Must Do To Contribute to the Users Migration Guide: Difference between revisions

From KitwarePublic
Jump to navigationJump to search
Line 52: Line 52:
{| border="1"
{| border="1"
|-
|-
|[[File:]]
| [[File:MigrationGuideWorkFlow1.png]]
|Blank
|Blank
|-
|-
|[[File:]]
| [[File:MigrationGuideWorkFlow2.png]]
|Blank
|-
| [[File:MigrationGuideWorkFlow3.png]]
|Blank
|-
| [[File:MigrationGuideWorkFlow4.png]]
|Blank
|-
| [[File:MigrationGuideWorkFlow5.png]]
|Blank
|-
| [[File:MigrationGuideWorkFlow6.png]]
|Blank
|-
| [[File:MigrationGuideWorkFlow7.png]]
|Blank
|-
| [[File:MigrationGuideWorkFlow8.png]]
|Blank
|-
| [[File:MigrationGuideWorkFlow9.png]]
|Blank
|-
| [[File:MigrationGuideWorkFlow10.png]]
|Blank
|-
| [[File:MigrationGuideWorkFlow11.png]]
|Blank
|-
| [[File:MigrationGuideWorkFlow12.png]]
|Blank
|Blank
|}
|}

Revision as of 20:48, 13 October 2010

< Users Migration Guide

Overview

What Information Must Be Captured

  • Git hash of the ITKv4 commit that changed the API
  • Migration guide page describing the justification for the change
  • Git hash of the Sequestered Applications commit that fixed the app to build with the new API

Proposed Procedures

General Ideas

  • Gerrit review checklist
    • Step that asks "Does this patch change the API"
    • If so, have the changes been documented in the migration guide
    • Only accept if documented
  • Documentation should include:
    • Names of files that change API
    • English explanation of changes
    • Code example of conversion from old API to new API
  • Some parts of documentation could be auto-generated
    • Extract English explanation from git commit
    • Find conversion examples in diff of tests
    • Names of files generated from git commits as well
  • Some sort of interface where automatic guesses for each migration component are auto-generated and developer can make changes to auto-generated results.
    • Maybe an addition to gerrit (how much gerrit editing can we do?)
    • If not, some sort of html form that is auto-populated from git and can be changed manually


Specific Proposals

  • Git commit messages
    • If changes api, commit message must start with API - ...
    • API changes must include sections:
      • RATIONAL: english explanation of what the change is and why it was made
      • Possibly include OLD and NEW sections for sample code
  • Gerrit post-review
    • Once change is fully reviewed and ready to be committed to master, developer must make a post to phpBB with full commit details
    • Forum post could be automatically populated by pulling in commit messages and/or review discussion from gerrit
    • Would then need to be manually edited by developer before final merge to master allowed

Workflow

MigrationGuideWorkFlow1.png Blank
MigrationGuideWorkFlow2.png Blank
MigrationGuideWorkFlow3.png Blank
MigrationGuideWorkFlow4.png Blank
MigrationGuideWorkFlow5.png Blank
MigrationGuideWorkFlow6.png Blank
MigrationGuideWorkFlow7.png Blank
MigrationGuideWorkFlow8.png Blank
MigrationGuideWorkFlow9.png Blank
MigrationGuideWorkFlow10.png Blank
MigrationGuideWorkFlow11.png Blank
MigrationGuideWorkFlow12.png Blank
Retrieved from "https://public.kitware.com/Wiki/index.php?title=ITK_Release_4/What_Developers_Must_Do_To_Contribute_to_the_Users_Migration_Guide&oldid=32350"