[blog] Kinetic release. #110

Merged
merged 1 commit into from Dec 16, 2016

Conversation

Projects
None yet
3 participants
@130s
Member

130s commented Nov 28, 2016

  • We should wait to merge this until Kinetic will be public synced (same as #96)
  • I'm not entirely sure the accuracy of each sentence for new features. Also not sure if this cover all changes that are worth noted.
+Update on ROS Indigo
+========================
+
+Contributors are working hard towards a new binary release into Indigo as well. Our loosely enforced backport policy is as follows. That said, Kinetic is recommended if you'd like to utilize the result of newest development:

This comment has been minimized.

@130s

130s Nov 28, 2016

Member

Also I'm not sure if the following bullet points are correct, and this is the right place for them to be mentioned.

@130s

130s Nov 28, 2016

Member

Also I'm not sure if the following bullet points are correct, and this is the right place for them to be mentioned.

This comment has been minimized.

@v4hn

v4hn Nov 28, 2016

Member

@davetcoleman probably agrees.
I don't see the need to reduce indigo support given that numerous robots out in the wild will still run indigo next year's christmas. How about:

  • Future research will primarily target Kinetic. ABI-compatible changes can be released into previous ROS distros too.

I'd propose to drop the point about bug-fixes. Bug-fixes should always be merged and released into all supported distributions.

@v4hn

v4hn Nov 28, 2016

Member

@davetcoleman probably agrees.
I don't see the need to reduce indigo support given that numerous robots out in the wild will still run indigo next year's christmas. How about:

  • Future research will primarily target Kinetic. ABI-compatible changes can be released into previous ROS distros too.

I'd propose to drop the point about bug-fixes. Bug-fixes should always be merged and released into all supported distributions.

This comment has been minimized.

@v4hn

Nice! Some fussy criticism inline.

+MoveIt! finally made it to the latest ROS LTS (Long Term Support) version [Kinetic](http://wiki.ros.org/kinetic)!
+From now onward, Kinetic is and will be the ROS version that comes with the newest capabilities and bug fixes for MoveIt!.
+
+First thing to note is that from Kinetic C++11 is fully enforced for MoveIt!, which means you can NOT build its source branch ([kinetic-devel](https://github.com/ros-planning/moveit/tree/kinetic-devel)) on the computers where the previous ROS distros run.

This comment has been minimized.

@v4hn

v4hn Nov 28, 2016

Member

This is not correct. I have MoveIt "kinetic-devel" running on an Indigo system on one of my machines.
It just means that

  1. you need a compiler that understands -std=c++11 (true virtually everywhere)

  2. All modules that include MoveIt headers have to be compiled with c++11 too.

  3. you might need the kinetic-version of some dependencies, but this has nothing to do with C++11, but with us being too busy to support the indigo interfaces of our dependencies too.

I'd propose:

[...] which means you HAVE to build all packages that include MoveIt headers with support for C++11.

@v4hn

v4hn Nov 28, 2016

Member

This is not correct. I have MoveIt "kinetic-devel" running on an Indigo system on one of my machines.
It just means that

  1. you need a compiler that understands -std=c++11 (true virtually everywhere)

  2. All modules that include MoveIt headers have to be compiled with c++11 too.

  3. you might need the kinetic-version of some dependencies, but this has nothing to do with C++11, but with us being too busy to support the indigo interfaces of our dependencies too.

I'd propose:

[...] which means you HAVE to build all packages that include MoveIt headers with support for C++11.

This comment has been minimized.

+
+- [MoveGroup's default capabilities are now added by default](https://github.com/ros-planning/moveit/pull/359).
+- [New benchmarking using PlanningArena](https://github.com/ros-planning/moveit/pull/228)
+- [Fix falsely called grasp service](https://github.com/ros-planning/moveit/pull/328)

This comment has been minimized.

@v4hn

v4hn Nov 28, 2016

Member

"falsely called" is not true. It served a purpose in indigo and before. We moved the functionality to MoveGroupInterface::planGraspAndPick.
I'd propose

separate Pick request without Grasps from Grasp Planning request

@v4hn

v4hn Nov 28, 2016

Member

"falsely called" is not true. It served a purpose in indigo and before. We moved the functionality to MoveGroupInterface::planGraspAndPick.
I'd propose

separate Pick request without Grasps from Grasp Planning request

+Update on ROS Indigo
+========================
+
+Contributors are working hard towards a new binary release into Indigo as well. Our loosely enforced backport policy is as follows. That said, Kinetic is recommended if you'd like to utilize the result of newest development:

This comment has been minimized.

@v4hn

v4hn Nov 28, 2016

Member

@davetcoleman probably agrees.
I don't see the need to reduce indigo support given that numerous robots out in the wild will still run indigo next year's christmas. How about:

  • Future research will primarily target Kinetic. ABI-compatible changes can be released into previous ROS distros too.

I'd propose to drop the point about bug-fixes. Bug-fixes should always be merged and released into all supported distributions.

@v4hn

v4hn Nov 28, 2016

Member

@davetcoleman probably agrees.
I don't see the need to reduce indigo support given that numerous robots out in the wild will still run indigo next year's christmas. How about:

  • Future research will primarily target Kinetic. ABI-compatible changes can be released into previous ROS distros too.

I'd propose to drop the point about bug-fixes. Bug-fixes should always be merged and released into all supported distributions.

+title: MoveIt! officially released into ROS Kinetic
+media_type: image
+media_link: http://wiki.ros.org/kinetic?action=AttachFile&do=get&target=kinetic.png
+description: If you're running your robot packages with ROS Kinetic, and/or if you want to try the newest MoveIt!, start at moveit.ros.org/install

This comment has been minimized.

@davetcoleman

davetcoleman Nov 29, 2016

Member

This is the description that will appear on the side bar of every page - I think it should mostly just be a copy of the first sentence in the actual blog post... people who are already on the website do not need a link to the install page.

@davetcoleman

davetcoleman Nov 29, 2016

Member

This is the description that will appear on the side bar of every page - I think it should mostly just be a copy of the first sentence in the actual blog post... people who are already on the website do not need a link to the install page.

+- ROS
+---
+
+MoveIt! finally made it to the latest ROS LTS (Long Term Support) version [Kinetic](http://wiki.ros.org/kinetic)!

This comment has been minimized.

@davetcoleman

davetcoleman Nov 29, 2016

Member

Sounds negative - how about "We are happy to announce MoveIt! is now released into ROS Kinetic LTS (Long Term Support)"

@davetcoleman

davetcoleman Nov 29, 2016

Member

Sounds negative - how about "We are happy to announce MoveIt! is now released into ROS Kinetic LTS (Long Term Support)"

+MoveIt! finally made it to the latest ROS LTS (Long Term Support) version [Kinetic](http://wiki.ros.org/kinetic)!
+From now onward, Kinetic is and will be the ROS version that comes with the newest capabilities and bug fixes for MoveIt!.
+
+First thing to note is that from Kinetic C++11 is fully enforced for MoveIt!, which means you can NOT build its source branch ([kinetic-devel](https://github.com/ros-planning/moveit/tree/kinetic-devel)) on the computers where the previous ROS distros run.

This comment has been minimized.

+
+- [Trajectory safety validation before execution](https://github.com/ros-planning/moveit/pull/63) (Kinetic onward only)
+- New planners in [OMPL](http://ompl.kavrakilab.org/) are now available from MoveIt! (geometric::{FMT, BFMT, PDST, STRIDE, BiTRRT, LBTRRT, BiEST, ProjEST, LazyPRM, LazyPRMstar, SPARS, SPARStwo}) ([see PR for detail](https://github.com/ros-planning/moveit/pull/338))
+

This comment has been minimized.

@davetcoleman

davetcoleman Nov 29, 2016

Member

why a line break?

@davetcoleman

davetcoleman Nov 29, 2016

Member

why a line break?

+Update on ROS Indigo
+========================
+
+Contributors are working hard towards a new binary release into Indigo as well. Our loosely enforced backport policy is as follows. That said, Kinetic is recommended if you'd like to utilize the result of newest development:

This comment has been minimized.

@130s

This comment has been minimized.

Show comment
Hide comment
@130s

130s Dec 6, 2016

Member

Thanks, all comments should be now addressed.

Member

130s commented Dec 6, 2016

Thanks, all comments should be now addressed.

@davetcoleman

This comment has been minimized.

Show comment
Hide comment

@davetcoleman davetcoleman merged commit 1b32e06 into ros-planning:gh-pages Dec 16, 2016

1 check failed

continuous-integration/travis-ci/pr The Travis CI build failed
Details

@130s 130s deleted the 130s:blog/kinetic_1strelease2 branch Jan 4, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment