<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Nov 12, 2013 at 3:38 PM, Jack O'Quin <span dir="ltr"><<a href="mailto:jack.oquin@gmail.com" target="_blank">jack.oquin@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">
<div class="im">On Tue, Nov 12, 2013 at 1:15 AM, Daniel Stonier <span dir="ltr"><<a href="mailto:d.stonier@gmail.com" target="_blank">d.stonier@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">
<div>On 12 November 2013 14:43, Dirk Thomas <span dir="ltr"><<a href="mailto:dthomas@osrfoundation.org" target="_blank">dthomas@osrfoundation.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">On 11.11.2013 19:07, Daniel Stonier wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div>
<br>
On 12 November 2013 06:41, Dirk Thomas <<a href="mailto:dthomas@osrfoundation.org" target="_blank">dthomas@osrfoundation.org</a> <mailto:<a href="mailto:dthomas@osrfoundation.org" target="_blank">dthomas@osrfoundation.<u></u>org</a>>> wrote:<br>
<br>
The wiki page was simply pretty outdated.<br>
I have updated the ROS/Roadmap wiki page with current information:<br></div>
<a href="http://wiki.ros.org/ROS/__Roadmap" target="_blank">http://wiki.ros.org/ROS/__<u></u>Roadmap</a> <<a href="http://wiki.ros.org/ROS/Roadmap" target="_blank">http://wiki.ros.org/ROS/<u></u>Roadmap</a>><div>
<br>
<br>
Please feel free to discuss any further information which would be useful on that page.<br>
</div></blockquote>
<br></blockquote><div><br></div></div><div>Ok, perhaps some better wording is needed.</div><div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
I don't understand what that sentence is supposed to mean:<br>
"Hydro and Indigo will be staggered across Quantal, Raring and Saucy"<br>
Can you please clarify, Daniel?<br></blockquote><div> </div></div><div>"Hydro and Indigo will be staggered across Quantal, Raring and Saucy" - just a reflection of the graph above illustrating hydro/quantal, hydro/raring, indigo/saucy.<br>
</div><div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Regarding the "planning your development" section:<br>
if we do release Indigo as a kind of LTS version of ROS I would strongly disagree to first-time release any disruptive changes into that version and than aim for stabilizing them later...<span><font color="#888888"><br>
</font></span></blockquote><div><br></div></div><div>Note: I didn't intend with the statement on the wiki page to infer a first time release on Indigo/Trusty. First time release would be on Indigo/Saucy as a beta release.<br>
</div><div><br></div><div>I thought I had heard Tully talking similar to what I outlined there. It certainly is the way we are planning to move over the next year or so. If it's not a general consensus, then certainly lets remove it. To clarify, we need to look at targeting some fairly major release points with disruptive changes. These disruptive changes have to go in somewhere, so for us, the best approach would seem to be:</div>
<div><ul><li>Develop on sources</li><li>Beta release debs on Indigo/Saucy - this is a short term release, so edge users only who are great for feedback.</li><li>Officially release debs on Indigo/LTS Trusty - we've acommodated many bugfixes hopefully and at this point we'd point our software on our more official platforms. This though, is where most new users would see the software.<br>
</li></ul></div></div></div></div></blockquote></div></div></div></div></blockquote><div>For clarification here, there will be only one Indigo release. It will have had more soak time in Saucy as Saucy will have been released and is fully stabilized but there won't be a 2nd release of Indigo with Trusty. </div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<div class="im"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<div><ul><li>
</li><li>Avoid any further disruptive changes on J-Turtle/LTS Trusty - gives the software and users time to enjoy and stabilise.</li></ul></div><div>Catkin went through a fairly similar process - it was beta released in fuerte (which would be like an early groovy with the longer timespans now), officially released in groovy on precise, and then hydro saw it really settle in. Having groovy/hydro on precise, gave a fairly constant environment to see that through.<br>
</div><div><br></div><div>Of course, this isn't a must do, but is this a recommendation that folks agree with and think would be useful?</div></div></div></div></blockquote><div><br></div></div><div>Yes.</div><div><br>
</div>
<div>Disruptive changes are always problematic. But, we need to spend more effort planning for smoother transitions.</div><div><br></div><div>With releases coming farther apart, I expect them all to create noticeable disruption. To deal with that, I'd like the build farm to start generating Indigo packages soon. We can release the plethora of Python 3 fixes there, leaving Hydro stable. The long beta cycle will give actively supported packages an opportunity to deal with the changes.</div>
</div></div></div></blockquote><div><br></div><div>We have started testing our toolchain on the first alpha releases of trusty. We hope to have them up shortly. </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<div><br></div><div>+1 to updating REP-0003 for Indigo.</div></div></div></div></blockquote><div><br></div><div>Pull request submitted. Please comment here: <a href="https://github.com/ros-infrastructure/rep/pull/64">https://github.com/ros-infrastructure/rep/pull/64</a></div>
<div><br></div><div>Tully</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">
<div class="gmail_extra"><span class=""><font color="#888888">-- <br> joq
</font></span></div></div>
<br>_______________________________________________<br>
ros-users mailing list<br>
<a href="mailto:ros-users@code.ros.org">ros-users@code.ros.org</a><br>
<a href="http://lists.ros.org/mailman/listinfo/ros-users" target="_blank">http://lists.ros.org/mailman/listinfo/ros-users</a><br>
<br></blockquote></div><br></div></div>