Hi Marcus, ROS has been around for more than 5 years now and we've developed a great user base and it has proven to be a successful platform. There are many things that people like about ROS, but we know that there are many areas for improvement. ROS 2.0 is an abstract name for developing the next generation of ROS. Over the years we have learned many areas where ROS could be improved and there are many tools which exist today that did not exist when ROS was originally created. It's more of a process of reviewing and improving elements of the ecosystem. The first part of this was our review and overhaul of the build system to enable us to do more powerful things at the library level. We've spent the last several months upgrading the infrastructure to leverage the strengths of the new build system. The next stage we planning to review and develop the communications libraries in ROS. Here's a link to a presentation which Dirk and I put together a few months ago: https://docs.google.com/presentation/d/1ScMOC7Gr4OY-j6XP5dPWfVsvdGBgaeWjHdXOd_JsTfc/edit?usp=sharing It's a long process and we're in the very early stages of planning and exploration. One of our biggest steps right now is to develop a process by which we can coordinate the community in productive manner. Our first step will be to gather use cases from the community to be able to derive design requirements. If you or anyone is interested in participating please be on the lookout for more postings on this mailing list. Tully On Fri, Apr 26, 2013 at 12:15 AM, Thibault Kruse wrote: > No, Fuerte was 1.8, Groovy is 1.9 (Changed the even-odd cycle), Hydro > should be 1.10 (not 2.0). > See http://code.ros.org/lurker/attach/3@20130104.210053.794d21eb.attach > Feel free to update the wiki. > > I believe the only "official" communication about ROS2.0 was by Ken when > he handed over work: > http://comments.gmane.org/gmane.science.robotics.ros.user/16100 > I have not seen other official communications of plans or roadmaps so far. > > > > > > On 26.04.2013 03:00, Marcus Liebhardt wrote: > > On Fri, Apr 26, 2013 at 9:39 AM, Marcus Liebhardt < > marcus.liebhardt@yujinrobot.com> wrote: > >> Hello everyone! >> >> My latest finding of the term "ROS 2.0" in OSRF's GSoC description [1], >> made me looking for its actual meaning, since I have no idea what it stands >> for. I don't even know, which version we are using now, e.g. Groovy = 1.X? >> > > My colleague just pointed me at this interesting list: > http://www.ros.org/wiki/ROS/ChangeList > Looks like we either are already using 2.0 or got stuck at 1.8 with Fuerte. > > Marcus > > > >> Unfortunately, a quick Google search didn't bring up much. >> >> So what is ROS 2.0 exactly? Are there any detailed plans for it yet? >> When will it be released? What will it include (e.g. NextGen Comms)? Ah, so >> many questions ... :-) >> >> Since answering these might start of some discussions, I thought it's >> better to ask here on ROS users. In case I am wrong and there is a clear >> answer, I am happy to re-ask it on ROS Answers and port the answer there. >> >> Cheers, >> Marcus >> >> [1] >> http://wiki.osrfoundation.org/gsoc13#Develop_new_Parameter_API_for_C.2B-.2B-_ROS_client >> >> -- >> Marcus Liebhardt >> Control Engineer >> Yujin Robot >> 주소: 대한민국 서울시 금천구 가산동 345-30 남성프라자 #601, 153-023. >> Address: Door #601, Namsung-Plaza, 345-30 Gasan-dong, Guemcheon-gu, >> Seoul, 153-023, Republic of Korea >> Website: http://www.yujinrobot.com >> Email: marcus.liebhardt@yujinrobot.com >> Phone: +82-70-46577073 >> > > > > -- > Marcus Liebhardt > Control Engineer > Yujin Robot > 주소: 대한민국 서울시 금천구 가산동 345-30 남성프라자 #601, 153-023. > Address: Door #601, Namsung-Plaza, 345-30 Gasan-dong, Guemcheon-gu, > Seoul, 153-023, Republic of Korea > Website: http://www.yujinrobot.com > Email: marcus.liebhardt@yujinrobot.com > Phone: +82-70-46577073 > > > _______________________________________________ > ros-users mailing listros-users@code.ros.orghttps://code.ros.org/mailman/listinfo/ros-users > > > > _______________________________________________ > ros-users mailing list > ros-users@code.ros.org > https://code.ros.org/mailman/listinfo/ros-users > >