<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Matt,<div><br></div><div>Forgive me for not knowing but, why is keeping the minor release schedule important?</div><div><br></div><div>In my view spending time to fix things that are not working to give the community that we are improving stability is important. Many discussion on patch releases vs minor releases, boil down to give the impression of stability or innovation. </div><div><br></div><div>From my personal usage, I would like a stable release version of ITKv4 installed on some systems for some scientists to use. I don't think that 4.2 is it yet. And unfortunately its not uncommon, for a release to contain a couple of bug that require a patch or two. In some situation stability is good. While when I want the latest features I frequently can pick a specific commit near master, that is suitable.</div><div><br></div><div>Additionally, I don't think that both can really be done in the next 60 days, so I suggested just doing the patch.</div><div><br></div><div>Brad</div><div><br></div><div><br><div><div>On Jul 23, 2012, at 11:25 AM, Matt McCormick wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Hi Brad,<br><br>I think the performance issues and WrapITK issues are important enough<br>to justify a patch release. However, why substitute a minor release<br>that has other feature improvements? Keeping the minor release<br>schedule regular is important.<br><br>My 2 cents,<br>Matt<br><br>On Mon, Jul 23, 2012 at 1:55 PM, Bradley Lowekamp<br><<a href="mailto:blowekamp@mail.nih.gov">blowekamp@mail.nih.gov</a>> wrote:<br><blockquote type="cite">Hello,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I have been considering what is being discussed to be done between now and<br></blockquote><blockquote type="cite">September, when currently the 4.3 release is scheduled, along with the<br></blockquote><blockquote type="cite">resources that I am aware that are available to contribute and add new<br></blockquote><blockquote type="cite">features to ITK. I would like to propose that we change the scheduled<br></blockquote><blockquote type="cite">release in september to only a patch release of 4.2.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">The fix for the performance regression that Kent and myself have worked on<br></blockquote><blockquote type="cite">in quite significant and there is still work to be done there to try to<br></blockquote><blockquote type="cite">whittle the maximum number of GetInput calls down further. Additionally,<br></blockquote><blockquote type="cite">there are some WrapITK issues I have encountered when I instantiate more<br></blockquote><blockquote type="cite">pixel types. And there is the important patch that has been contributed by a<br></blockquote><blockquote type="cite">use to get WrapITK working with VS10. So I think there is some significant<br></blockquote><blockquote type="cite">fixes that would justify a 4.2.1 patch release.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">This would not disrupt those working on the forward progress of the master<br></blockquote><blockquote type="cite">branch either. Those patches intended to be merged into the release can<br></blockquote><blockquote type="cite">through the normal gerrit process. The only difference would be that should<br></blockquote><blockquote type="cite">be based on the release branch and not the master branch, and SHOULD NOT be<br></blockquote><blockquote type="cite">rebased before they are merged into master.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Thanks for sharing you thoughts on this issue.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Brad<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">========================================================<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Bradley Lowekamp<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Medical Science and Computing for<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Office of High Performance Computing and Communications<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">National Library of Medicine<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><a href="mailto:blowekamp@mail.nih.gov">blowekamp@mail.nih.gov</a><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">Powered by <a href="http://www.kitware.com">www.kitware.com</a><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Visit other Kitware open-source projects at<br></blockquote><blockquote type="cite"><a href="http://www.kitware.com/opensource/opensource.html">http://www.kitware.com/opensource/opensource.html</a><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Kitware offers ITK Training Courses, for more information visit:<br></blockquote><blockquote type="cite"><a href="http://kitware.com/products/protraining.php">http://kitware.com/products/protraining.php</a><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Please keep messages on-topic and check the ITK FAQ at:<br></blockquote><blockquote type="cite"><a href="http://www.itk.org/Wiki/ITK_FAQ">http://www.itk.org/Wiki/ITK_FAQ</a><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Follow this link to subscribe/unsubscribe:<br></blockquote><blockquote type="cite"><a href="http://www.itk.org/mailman/listinfo/insight-developers">http://www.itk.org/mailman/listinfo/insight-developers</a><br></blockquote><blockquote type="cite"><br></blockquote></div></blockquote></div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; -webkit-text-decorations-in-effect: none; text-indent: 0px; -webkit-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; -webkit-text-decorations-in-effect: none; text-indent: 0px; -webkit-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><p style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; ">========================================================</font></p><p style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; ">Bradley Lowekamp<span class="Apple-converted-space"> </span><span class="Apple-converted-space"> </span></font></p><p style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; ">Medical Science and Computing for</font></p><p style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; ">Office of High Performance Computing and Communications</font></p><p style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; ">National Library of Medicine<span class="Apple-converted-space"> </span></font></p><p style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; "><a href="mailto:blowekamp@mail.nih.gov">blowekamp@mail.nih.gov</a></font></p><br class="Apple-interchange-newline"></span></div></span></span><br class="Apple-interchange-newline">
</div>
<br></div></body></html>