Release Plan

Topic

When/what versions to release, do we want documentation officially put somewhere already?

Current Resolution

  • Indigo Igloo, starting with 0.7.x. Core scheduler sources should eventually drop into github::rocon_concert.

  • Implementations of different scheduling algorithms could be anywhere though.

Discussion Thread

  • (Jack) Are you planning to release rocon_msgs-0.6.3 any time soon?

  • (Jack) How do you feel about changing the rosdoc/hydro/doc.yaml links to use the hydro-devel branch, so new updates appear on the ROS wiki?

    • (Daniel) Wasn't planning on re-releasing hydro, but rather wait for igloo. It's moving too fast and is disruptive right now - for users (incl. turtlebot users) and us too w.r.t. providing support.

    • (Jack) OK. In that case the hydro-devel branch name is rather confusing. But, we can probably start documenting an Indigo release on the wiki fairly soon without confusing existing Hydro users.

    • (Jack) I suggest the work not be closely tied to a specific ROS distro. The new Concert version should work on both Indigo and Hydro. Piyush and the other BWI people at UTexas will need to install it on Hydro for quite a while.

    • (Jack) Personally, I favor always doing new work in a master branch, documenting which ROS distros those sources currently support. There is no implied promise to actually release on all of them.

Wiki: rocon_concert/Reviews/simple_scheduler API proposal_API_Review/Release Plan (last edited 2013-11-29 17:12:07 by JackOQuin)