<br>Hi Steve,<br><br>You bring up very good questions,<br>let me comment below:<br><br><br><div class="gmail_quote">On Fri, Jul 16, 2010 at 9:51 PM, Steve M. Robbins <span dir="ltr"><<a href="mailto:steve@sumost.ca">steve@sumost.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On Thu, Jul 15, 2010 at 09:46:15AM -0400, Luis Ibanez wrote:<br>
<br>
> Please share with us your impression on how<br>
> the current transition plan may impact your use<br>
> of ITK.<br>
<br>
</div>I really applaud the use of Reference Applications and producing<br>
detailed Migration reports. You have quite a large set of Reference<br>
Applications listed. Have you any idea how much of ITK they<br>
collectively cover?<br>
<br></blockquote><div><br><br>We don't have application coverage information yet.<br><br>This will be very enlightening, we will finally see hard<br>numbers on what are the most used part of the toolkit.<br><br>Feel free to propose other applications to include in the<br>
list.<br><br>BTW: <br>We are still looking for tools that will help us organize <br>all this information in a systematic way. <br><br>We will appreciate any suggestions...<br><br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Is there any more detail on what new functionality each topic branch<br>
will contain and how they will interact to produce the final ITK?<br></blockquote><div><br><br>The current suggested Topic Branches are loosely cut<br>based on the larger topics that ITKv4 contractors have<br>proposed. However, we anticipate that a large number<br>
of related branches will derive from the larger topic<br>branches.<br><br>We are relying on Git flexibility for creating and merging<br>branches on a daily basis.<br><br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The diagram in the transition plan suggests that five groups will<br>
be operating in parallel, each on their own copy of ITK, output to<br>
"Gerrit Code Reviews". Is the idea to publish completed code from<br>
each branch into the ITKv4 Master for integration testing?<br>
<br></blockquote><div><br><br>Yes, all the repositories will be publishing into the Master.<br><br>In between, all the repositories will be public, to allow<br>the larger ITK community to help review the progress<br>of ITKv4 and steer its course.<br>
<br><br>We need to work more on the labeling of things, but in <br>principle there will be an ITK Git repository at Kitware <br>that will host the "published" version of ITKv4 in its <br>"master" branch.<br>
<br>Its "next" branch will be the integration branch and will <br>be heavily tested in the Dashboard.<br><br>Topic branches will also be tested in the Dashboard by <br>using a "test-on-demand" service (that we will implement<br>
soon based on CDash & CTest). Once green in a set of<br>"required" platforms (most likely including Visual Studio<br>9 & 10, Gcc 4.3 & 4.4 in Linux and Mac OS), the code<br>will be passed to Gerrit for code review. The code may<br>
go back and forth between reviewers and authors in <br>Gerrit, and once it get to satisfy ITK standards, its will<br>be pushed into the "next" branch of the published repository.<br><br><br>The move from "next" to "master" will be done in <br>
short iteration releases (three weeks each, maybe...)<br><br><br>There are still many details to be figure out, <br><br>so, <br>Please point out any flaws or inconsistencies<br>that you may find in the Transition Plan.<br>
<br><br>We better learn about them earlier :-)<br><br><br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Thanks,<br>
<font color="#888888">-Steve<br>
</font><br>-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.10 (GNU/Linux)<br>
<br>
iD8DBQFMQQyc0i2bPSHbMcURAmJNAKChXu+rqTvXXSuLYFsW3+ehICfKrgCeKx6q<br>
97wTSYs3LoeFjtPg96UZ/tM=<br>
=UPAi<br>
-----END PGP SIGNATURE-----<br>
<br></blockquote></div><br>