ros / rosdistro Goto Github PK

We need to create the variants/equivilant meta packages people are used to installing. And a REP should define what the core ones are.

This will allow us to see the status of packages in the different repos.

I.e. rospkg.rospack.depends-on provides no dependencies for wet packages which breaks rqt_dep.

A high level document which calls out any changes required of the user for core packages when moving from fuerte to groovy. This should be used in #262

$ aptitude search ros-groovy | grep variant

shows no results

We've gotten lazy about adding license headers at the top of files.

Remind maintainers to fix warnings in package.xml, setup.py, etc.

We've patched a bunch of sutff. I'd like to make sure we've capture them all.

from @dirk-thomas
catkinpkg
rospkg
catkin
genpy
rospack
ros
ros_comm

@wjwwood you have a list too?

This should probably be done as part of the indexing steps to allow for audits and better knowledge when considering changing keys.

ros/ros_comm/issues/19
ros/ros_comm/issues/20

We need a tool to find the dependencies of wet packages and resolve them for the current operating system.

The way I see it we can either:

• Get a minimal Xylem implementation
• Or modify rosdep to handle wet packages/catkin workspaces

I think modifying rosdep to support this is the easiest way forward.

This would fit nicely into an RSS feed.

As Dirk and I outlined on his whiteboard. This should provide the clean build and runtime dependencies.

The packages should be message_generators and message_runtime.

Create groovy branch, make an announcement, update doc in Wiki to mention new flow with "rolling release" instead of "unstable" and ditch unstable

To minimize the rqt dependency list to only those needed by the user we will need to split rqt up.

for example we might have the following groups:

rqt_core
rqt_pr2
rqt_rviz
etc

The ros wiki pages for the iri-ros-pkg repository (added to rosdistro in merge #220) are not being generated. See http://www.ros.org/wiki/iri_core as an example.

We deliver our software via subversion using https. The certificate signature is not valid for the standard authorities so it could be a problem with the SSL acceptation.

Thanks.

This is a follow on to #195. The tool currently works on precise, but not lucid so it can't be deployed on the buildfarm at the moment. This will track getting the script output into a publicly viewable location, and being regularly updated by the buildfarm.

vision_opencv.rosinstall points to uri: https://github.com/wg-perception/vision_opencv.git but this is wrong. It should point to uri: https://github.com/ros-perception/vision_opencv.git. Just change the wg- to ros-.

pr2_empty_worlds.launch should come up and operate for us to consider the beta ready.

The release repo needs to be updated to include rosdep rules for the dry groovy stacks. And then the sourcedeb generation needs to be run so that it can be regenerated for quantal.

We need to make sure that empty values can be supported in the rosdistro file.
E.g.: python-argparse is a dependency on lucis but not precise (as it is included in Python), so we should do something like:
lucid: python-argparse
precise: ''

As discussed on the mailing list.

to avoid confusion during the beta

Zev is looking at this.

These tests should be reliable to use for the users.

The following pages needs an update: http://www.ros.org/wiki/Tickets

Ready for external users to make releases

Everything in the ros trac should be moved to github.

from code.ros.org:
ROS svn repos should be moved to github
ros trac
rx

from kforge:
Geometry
rospack

http://packages.ros.org/cgi-bin/gen_rosinstall.py?rosdistro=electric&variant=desktop-full&overlay=yes
-> []
same for diamondback

http://packages.ros.org/cgi-bin/gen_rosinstall.py?rosdistro=fuerte&variant=desktop-full&overlay=yes
-> [{'other': {'local-name': '/opt/ros/fuerte/share/ros'}}, ...
localname should just be ros

This is going to go out after the beta, but should be soon after.

This will parse and format check the files.

The recent changes introducing message_generation and message_runtime lack documentation.
i expect the following to be created:

• The two new packages should get at least README files on github.
• update any wiki ROS tutorial still referring to genmsg
• update any wiki catkin tutorial still referring to genmsg
• update static catkin documentation
• change catkinize script
• change catkin_create_pkg scripts
• reference new packages in genmsg documentation
• explain the change to the community and whether it has an impact on dry packages

Generate ,rosinstall files for variants based on distro.yaml (depends on ros-infrastructure/bloom#9).

For the announcement and groovy page.

The roscpp tutorials should be verified as operational on groovy: http://www.ros.org/wiki/roscpp/Tutorials

Two people should sign off as tested before closing.

It will parse check the files and make sure they're all parseable and are structured appropriately.

So you don't manually have to compute the other part.

We don't usually use them internally they need to be tested.

Everything in variants should be doing this. Especially desktop.

http://www.ros.org/wiki/rospy/Tutorials

Two people should sign off as tested before closing.

python.yaml has key:
python_qt_bindings

Based on a grep of the ros source this should be:
python_qt_binding

I don't have time to create a patch. Sorry.

Everything should be in ros-gbp.