On Fri, Feb 15, 2013 at 10:51 AM, Daniel Stonier <span dir="ltr"><<a href="mailto:d.stonier@gmail.com" target="_blank">d.stonier@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div><br></div><div>I recently spent quite a bit of time catkin bugfixing inbetween a successful pre-release and a successful release, so I thought I'd post some feedback.<br></div>
<div><br></div><div>Previously, one important part of pre-releasing was catching stack dependency bugs. Wet pre-releases on the other hand, let through alot of dependency bugs that are only found in the actual release. I believe the cause is due to the fact that the pre-release runs catkin on the whole stack, whereas the release works on individual packages. </div>
<div><br></div><div>In a pre-release a missing package dependency (e.g. you used geometry_msgs/Pose.h, but didn't include geometry_msgs in the package.xml) sometimes gets installed by another unrelated package in the stack which, just by chance, also happened to use it and did include it in the package.xml correctly... and no error results. On the build farm, where it builds packages independantly, you get a fail.</div>
<div><br></div><div>These fails also happen in other ways - e.g. a missing find_package(catkin REQUIRED ...) in just one package in the stack also gets past pre-release.</div>
<div><br></div><div>I know that once you're familiar with the development process, these problems are not so common. In this case, however, I had someone new trying on the catkin release process, and the 12-24 hr delay ping-ponging back and forth between trying a release, bugfixing it and trying again meant broken packages for a considerable period of time.</div>
<div><br></div><div>Also as a result - it rather feels that the pre-release isn't doing much more for me than a compile check that I can do on my own machine.</div></div></blockquote><div><br></div><div>Didn't you forget to mentioned:</div>
<div>"I hate Catkin!"?</div><div>;-)</div><div><br></div><div>Marcus</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><br>
</div><div>Regards,</div>
<div>Daniel</div><div><div>
</div></div>
</div>
<br>_______________________________________________<br>
Ros-release mailing list<br>
<a href="mailto:Ros-release@code.ros.org">Ros-release@code.ros.org</a><br>
<a href="https://code.ros.org/mailman/listinfo/ros-release" target="_blank">https://code.ros.org/mailman/listinfo/ros-release</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><font size="1">Marcus Liebhardt <br>Control Engineer<br>Yujin Robot<font size="1"><br></font></font><font size="1"><span lang="ko">주소</span></font><font size="1">: </font><font size="1"><span lang="ko-Hang">대한민국 </span></font><font size="1">서울시 금천구 가산동 345-30 남성프라자 #601, 153-023.<br>
</font><font size="1">Address: Door </font><font size="1">#601, Namsung-Plaza, 345-30 Gasan-dong, Guemcheon-gu, Seoul, 153-023, Republic of Korea<br>Website: <a href="http://www.yujinrobot.com/" style="color:rgb(0,0,0)" target="_blank">http://www.yujinrobot.com</a><br>
Email: <a href="mailto:marcus.liebhardt@yujinrobot.com" style="color:rgb(0,0,0)" target="_blank">marcus.liebhardt@yujinrobot.com</a><br>Phone: +82-70-46577073</font>