<div dir="ltr">Sorry about the formatting, sending again:<br><br>Hi Everyone,<br><br>This email is to give an update on the ROS Hydro development.<br><br>In perparation for Hydro there has been lots of activity preparing the infrastructure for the new release [1]. There also has been significant patch releases for Groovy happening [4]. Two major requirements for the Hydro fork were the upgrades to bloom and the development of a REP for 3rdparty package releases which are being finished up [5] [6].<br>
<br>= Updated Hydro Schedule =<br><br>As we are now ready to fork the rosdisto for Hydro development we need to review the Hydro development cycle. We will not be able to catch up to the standard release cycle.<br><br>New Schedule Goals:<br>
<br>- March 5th: Hydro Fork<br>- April 2nd: Hydro Alpha<br> The first version of all packages are released into Hydro.<br>- April 25th: Hydro Beta<br> All major changes have been completed for stable packages. <br>
- May 22nd: Hydro Medusa Release<br><br><br>This means that in the next 4 weeks we hope that all released packages can be released into Hydro to form the Alpha Release on April 2nd. There will be 3 more weeks for upgrades before the Beta release on April 25th.<br>
<br>If you are a maintainer please watch for when it will be appropriate to make your first release into Hydro.<br><br>= Ongoing REPs =<br><br>Already there has been quite a bit of activity developing REPs for the Hydro cycle with discussions ongoing for REPs in ros-users, ros-sig-drivers, and ros-sig-buildsystem and the pull requests in the rep repository [3]. I encourage everyone to watch for REP discussions and consider joining them. <br>
<br>The REPs under review can be found at these locations:<br>- 132 Incorporation of Changelogs into Package Source Tree <a href="https://github.com/ros-infrastructure/rep/blob/master/rep-0132.rst">https://github.com/ros-infrastructure/rep/blob/master/rep-0132.rst</a><br>
- 133 Separation of build environment and source tree tools <a href="https://github.com/tkruse/rep/tree/repwstool">https://github.com/tkruse/rep/tree/repwstool</a><br>- 134 catkin_make_isolated for non-standard catkin packages <a href="https://github.com/tkruse/rep/blob/repisolated/rep-0134.rst">https://github.com/tkruse/rep/blob/repisolated/rep-0134.rst</a><br>
- 135 Driver Namespace Practices <a href="https://github.com/chadrockey/rep/blob/namespace/rep-0135.rst">https://github.com/chadrockey/rep/blob/namespace/rep-0135.rst</a><br>- 136 Releasing Third Party, Non catkin Packages <a href="https://github.com/ros-infrastructure/rep/blob/release_third_party/rep-0136.rst">https://github.com/ros-infrastructure/rep/blob/release_third_party/rep-0136.rst</a><br>
- 137 ROS distribution files <a href="https://github.com/po1/rep/blob/rep137/rep-0137.rst">https://github.com/po1/rep/blob/rep137/rep-0137.rst</a><br>- 138 LaserScan Common Topics, Parameters, and Diagnostic Keys <a href="https://github.com/chadrockey/rep/blob/laserscanner/rep-0138.rst">https://github.com/chadrockey/rep/blob/laserscanner/rep-0138.rst</a><br>
<br>They all have pull requests pointing to their discussions at [3].<br><br>= Outstanding Issues =<br><br>One major change in Ubuntu which will effect Hydro is that In Raring Ringtail (13.04) Ubuntu will switch to use Python 3 by default. This will require a large audit of the Python codebase to test for compatability. There's an issue open to keep track of this at the rosdistro level [7]. We plan to follow Ubuntu's recommendation which is to make scripts Python 2.7+ and Python 3.3+ compatible. For more information on what is required see the Ubuntu Python 3 wiki page [8].<br>
<br><br>= Maintainer Status =<br><br>One of the initiatives we plan for Hydro is to keep more up to date maintainer information for packages. This is covered in draft REP 137 [2]. There are a large number of released packages which over time the original authors have moved to new situations where they do not have the ability to maintain their packages. Historically many of these packages were picked up and carried forward by a few individuals. However this approach is not sustainable. <br>
<br>To keep the quality of ROS packages as high as possible we will be looking for new maintainers to distribute the burdon throughout the community. We will ask that all packages released into Hydro have clear maintenance status. <br>
One of the great strengths of the ROS community is the breadth and number of members in the community. With small contributions for many of the members the burden can be easily carried. Please keep this in mind and consider stepping up to maintain a package which is flagged as needing a maintainer in the future. There will be more communications about this going forward. <br>
<br>= Electric Buildfarm =<br><br>As we bring up the buildfarm to support Hydro we will be retiring the electric jobs on the farm. We cannot maintain the infrastructure for more than 3 rosdistros simultaneously. This will keep 2 active rosdistros (Fuerte and Groovy) and one in development(Hydro). The downloads will continue to be available. <br>
<br>Tully<br><br><br>[1] <a href="https://github.com/ros/rosdistro/issues?milestone=5&page=1&state=closed">https://github.com/ros/rosdistro/issues?milestone=5&page=1&state=closed</a><br>[2] <a href="https://github.com/ros-infrastructure/rep/pull/27">https://github.com/ros-infrastructure/rep/pull/27</a><br>
[3] <a href="https://github.com/ros-infrastructure/rep">https://github.com/ros-infrastructure/rep</a><br>[4] <a href="https://code.ros.org/lurker/attach/3@20130304.103724.ea382def.attach">https://code.ros.org/lurker/attach/3@20130304.103724.ea382def.attach</a><br>
[5] <a href="http://www.ros.org/news/2013/02/bloom-version-030.html">http://www.ros.org/news/2013/02/bloom-version-030.html</a><br>[6] <a href="https://github.com/ros-infrastructure/rep/pull/23">https://github.com/ros-infrastructure/rep/pull/23</a><br>
[7] <a href="https://github.com/ros/rosdistro/issues/506">https://github.com/ros/rosdistro/issues/506</a><br>[8] <a href="https://wiki.ubuntu.com/Python/3">https://wiki.ubuntu.com/Python/3</a><br><br><br><br>On Mon, Mar 4, 2013 at 12:17 PM, Tully Foote <<a href="mailto:tfoote@osrfoundation.org">tfoote@osrfoundation.org</a>> wrote:<br>
><br>><br>> Hi Everyone,<br>> This email is to give an update on the ROS Hydro development.<br>> In preparation for Hydro there has been lots of activity preparing the infrastructure for the new release [1]. There also has been significant patch releases for Groovy happening [4]. Two major requirements for the Hydro fork were the upgrades to bloom and the development of a REP for 3rdparty package releases which are being finished up [5] [6].<br>
> = Updated Hydro Schedule =<br>> As we are now ready to fork the rosdisto for Hydro development we need to review the Hydro development cycle. We will not be able to catch up to the standard release cycle.<br>> New Schedule Goals:<br>
> - March 5th: Hydro Fork- April 2nd: Hydro AlphaThe first version of all packages are released into Hydro. - April 25th: Hydro BetaAll major changes have been completed for stable packages. - May 22nd: Hydro Medusa Release<br>
><br>> This means that in the next 4 weeks we hope that all released packages can be released into Hydro to form the Alpha Release on April 2nd. There will be 3 more weeks for upgrades before the Beta release on April 25th.<br>
> If you are a maintainer please watch for when it will be appropriate to make your first release into Hydro.<br>> = Ongoing REPs =<br>> Already there has been quite a bit of activity developing REPs for the Hydro cycle with discussions ongoing for REPs in ros-users, ros-sig-drivers, and ros-sig-buildsystem and the pull requests in the rep repository [3]. I encourage everyone to watch for REP discussions and consider joining them. <br>
> The REPs under review can be found at these locations: - 132 Incorporation of Changelogs into Package Source Tree <a href="https://github.com/ros-infrastructure/rep/blob/master/rep-0132.rst-">https://github.com/ros-infrastructure/rep/blob/master/rep-0132.rst-</a> 133 Separation of build environment and source tree tools <a href="https://github.com/tkruse/rep/tree/repwstool">https://github.com/tkruse/rep/tree/repwstool</a> - 134 catkin_make_isolated for non-standard catkin packages <a href="https://github.com/tkruse/rep/blob/repisolated/rep-0134.rst-">https://github.com/tkruse/rep/blob/repisolated/rep-0134.rst-</a> 135 Driver Namespace Practices <a href="https://github.com/chadrockey/rep/blob/namespace/rep-0135.rst-">https://github.com/chadrockey/rep/blob/namespace/rep-0135.rst-</a> 136 Releasing Third Party, Non catkin Packages <a href="https://github.com/ros-infrastructure/rep/blob/release_third_party/rep-0136.rst-">https://github.com/ros-infrastructure/rep/blob/release_third_party/rep-0136.rst-</a> 137 ROS distribution files <a href="https://github.com/po1/rep/blob/rep137/rep-0137.rst-">https://github.com/po1/rep/blob/rep137/rep-0137.rst-</a> 138 LaserScan Common Topics, Parameters, and Diagnostic Keys <a href="https://github.com/chadrockey/rep/blob/laserscanner/rep-0138.rst">https://github.com/chadrockey/rep/blob/laserscanner/rep-0138.rst</a> They all have pull requests pointing to their discussions at [3].<br>
> = Outstanding Issues =<br>> One major change in Ubuntu which will effect Hydro is that In Raring Ringtail (13.04) Ubuntu will switch to use Python 3 by default. This will require a large audit of the Python codebase to test for compatibility There's an issue open to keep track of this at the rosdistro level [7]. We plan to follow Ubuntu's recommendation which is to make scripts Python 2.7+ and Python 3.3+ compatible. For more information on what is required see the Ubuntu Python 3 wiki page [8].<br>
><br>> = Maintainer Status =<br>> One of the initiatives we plan for Hydro is to keep more up to date maintainer information for packages. This is covered in draft REP 137 [2]. There are a large number of released packages which over time the original authors have moved to new situations where they do not have the ability to maintain their packages. Historically many of these packages were picked up and carried forward by a few individuals. However this approach is not sustainable. <br>
> To keep the quality of ROS packages as high as possible we will be looking for new maintainers to distribute the burden throughout the community. We will ask that all packages released into Hydro have clear maintenance status. One of the great strengths of the ROS community is the breadth and number of members in the community. With small contributions for many of the members the burden can be easily carried. Please keep this in mind and consider stepping up to maintain a package which is flagged as needing a maintainer in the future. There will be more communications about this going forward. <br>
> = Electric Buildfarm =<br>> As we bring up the buildfarm to support Hydro we will be retiring the electric jobs on the farm. We cannot maintain the infrastructure for more than 3 rosdistros simultaneously. This will keep 2 active rosdistros (Fuerte and Groovy) and one in development(Hydro). The downloads will continue to be available. <br>
> Tully<br>><br>> [1] <a href="https://github.com/ros/rosdistro/issues?milestone=5&page=1&state=closed[2]">https://github.com/ros/rosdistro/issues?milestone=5&page=1&state=closed[2]</a> <a href="https://github.com/ros-infrastructure/rep/pull/27[3]">https://github.com/ros-infrastructure/rep/pull/27[3]</a> <a href="https://github.com/ros-infrastructure/rep[4]">https://github.com/ros-infrastructure/rep[4]</a> <a href="https://code.ros.org/lurker/attach/3@20130304.103724.ea382def.attach[5]">https://code.ros.org/lurker/attach/3@20130304.103724.ea382def.attach[5]</a> <a href="http://www.ros.org/news/2013/02/bloom-version-030.html[6]">http://www.ros.org/news/2013/02/bloom-version-030.html[6]</a> <a href="https://github.com/ros-infrastructure/rep/pull/23[7]">https://github.com/ros-infrastructure/rep/pull/23[7]</a> <a href="https://github.com/ros/rosdistro/issues/506[8]">https://github.com/ros/rosdistro/issues/506[8]</a> <a href="https://wiki.ubuntu.com/Python/3">https://wiki.ubuntu.com/Python/3</a><br>
><br></div>