vision_visp repository

Repository Summary

Checkout URI https://github.com/lagadic/vision_visp.git
VCS Type git
VCS Version lunar-devel
Last Updated 2017-10-31
Dev Status MAINTAINED
Released RELEASED

README

ViSP stack for ROS

GPL-2

vision_visp provides ViSP algorithms as ROS components. ViSP is the Visual Servoing Platform and ROS a robotics middleware.

These packages are released under the GPL-2 license.

Components documentation is hosted on the ros.org wiki.

Support is provided through ROS Answers .

Which branch should I use?

Branches come in two flavors:

  • development branch,
  • release branch

Package for each ROS release is maintained on separate branches. I.e. lunar-devel is the Lunar Loggerhead development branch whereas lunar is the Lunar Loggerhead release branch.

master means the next ROS release.

If you are a user you should use a release branch as they contain stable and tested versions of the packages. If you are a developper you must provide new patches against master. You may also provide version-specific bug fix again older releases.

  • Never implement new features in old branches (i.e. not master). These Pull Requests will not be accepted. If you provide a bug fix then you may ask for it to be backported. ABI/API breakage prevent patches from being backported.
  • The only action allowed in release branches is merging the development branch in the current branch.

Warning: the Fuerte branches still rely on the legacy rosbuild build system. We recommend you to update to a newer ROS release. Only minimum maintained will be done for this release.

Additional development guidelines are provided in CONTRIBUTING.md.

Build Status

This stack supports the following ROS releases:

  • Hydro
  • Groovy
  • Fuerte
  • Indigo
  • Jade
  • Kinetic
  • Lunar

The master branch holds the development that will be available in the next ROS release.

ROS Release Development Branch Release Branch
Master Build Status N/A
Lunar Build Status Build Status
Kinetic Build Status Build Status
Jade Build Status Build Status
Indigo Build Status Build Status
Hydro Build Status Build Status
Groovy Build Status Build Status
Fuerte Build Status Build Status

Repository Summary

Checkout URI https://github.com/lagadic/vision_visp.git
VCS Type git
VCS Version kinetic-devel
Last Updated 2017-02-17
Dev Status MAINTAINED
Released RELEASED

README

ViSP stack for ROS

GPL-2

vision_visp provides ViSP algorithms as ROS components. ViSP is the Visual Servoing Platform and ROS a robotics middleware.

These packages are released under the GPL-2 license.

Components documentation is hosted on the ros.org wiki.

Support is provided through ROS Answers .

Which branch should I use?

Branches come in two flavors:

  • development branch,
  • release branch

Package for each ROS release is maintained on separate branches. I.e. kinetic-devel is the Kinetic Kade development branch whereas kinetic is the Kinetic Kame release branch.

master means the next ROS release.

If you are a user you should use a release branch as they contain stable and tested versions of the packages. If you are a developper you must provide new patches against master. You may also provide version-specific bug fix again older releases.

  • Never implement new features in old branches (i.e. not master). These Pull Requests will not be accepted. If you provide a bug fix then you may ask for it to be backported. ABI/API breakage prevent patches from being backported.
  • The only action allowed in release branches is merging the development branch in the current branch.

Warning: the Fuerte branches still rely on the legacy rosbuild build system. We recommend you to update to a newer ROS release. Only minimum maintained will be done for this release.

Additional development guidelines are provided in CONTRIBUTING.md.

Build Status

This stack supports the following ROS releases:

  • Hydro
  • Groovy
  • Fuerte
  • Indigo
  • Jade
  • Kinetic

The master branch holds the development that will be available in the next ROS release.

ROS Release Development Branch Release Branch
Master Build Status N/A
Kinetic Build Status Build Status
Jade Build Status Build Status
Indigo Build Status Build Status
Hydro Build Status Build Status
Groovy Build Status Build Status
Fuerte Build Status Build Status

Repository Summary

Checkout URI https://github.com/lagadic/vision_visp.git
VCS Type git
VCS Version indigo-devel
Last Updated 2017-02-17
Dev Status MAINTAINED
Released RELEASED

README

ViSP stack for ROS

GPL-2

vision_visp provides ViSP algorithms as ROS components. ViSP is the Visual Servoing Platform and ROS a robotics middleware.

These packages are released under the GPL-2 license.

Components documentation is hosted on the ros.org wiki.

Support is provided through ROS Answers .

Which branch should I use?

Branches come in two flavors:

  • development branch,
  • release branch

Package for each ROS release is maintained on separate branches. I.e. indigo-devel is the Indigo development branch whereas indigo is the Indigo release branch.

master means the next ROS release.

If you are a user you should use a release branch as they contain stable and tested versions of the packages. If you are a developper you must provide new patches against master. You may also provide version-specific bug fix again older releases.

  • Never implement new features in old branches (i.e. not master). These Pull Requests will not be accepted. If you provide a bug fix then you may ask for it to be backported. ABI/API breakage prevent patches from being backported.
  • The only action allowed in release branches is merging the development branch in the current branch.

Warning: the Fuerte branches still rely on the legacy rosbuild build system. We recommend you to update to a newer ROS release. Only minimum maintained will be done for this release.

Additional development guidelines are provided in CONTRIBUTING.md.

Build Status

This stack supports the following ROS releases:

  • Hydro
  • Groovy
  • Fuerte
  • Indigo

The master branch holds the development that will be available in the next ROS release.

ROS Release Development Branch Release Branch
Master Build Status N/A
Indigo Build Status Build Status
Hydro Build Status Build Status
Groovy Build Status Build Status
Fuerte Build Status Build Status

Repository Summary

Checkout URI https://github.com/lagadic/vision_visp.git
VCS Type git
VCS Version jade-devel
Last Updated 2017-02-17
Dev Status MAINTAINED
Released RELEASED

README

ViSP stack for ROS

GPL-2

vision_visp provides ViSP algorithms as ROS components. ViSP is the Visual Servoing Platform and ROS a robotics middleware.

These packages are released under the GPL-2 license.

Components documentation is hosted on the ros.org wiki.

Support is provided through ROS Answers .

Which branch should I use?

Branches come in two flavors:

  • development branch,
  • release branch

Package for each ROS release is maintained on separate branches. I.e. jade-devel is the Jade development branch whereas jade is the Jade release branch.

master means the next ROS release.

If you are a user you should use a release branch as they contain stable and tested versions of the packages. If you are a developper you must provide new patches against master. You may also provide version-specific bug fix again older releases.

  • Never implement new features in old branches (i.e. not master). These Pull Requests will not be accepted. If you provide a bug fix then you may ask for it to be backported. ABI/API breakage prevent patches from being backported.
  • The only action allowed in release branches is merging the development branch in the current branch.

Warning: the Fuerte branches still rely on the legacy rosbuild build system. We recommend you to update to a newer ROS release. Only minimum maintained will be done for this release.

Additional development guidelines are provided in CONTRIBUTING.md.

Build Status

This stack supports the following ROS releases:

  • Hydro
  • Groovy
  • Fuerte
  • Indigo
  • Jade

The master branch holds the development that will be available in the next ROS release.

ROS Release Development Branch Release Branch
Master Build Status N/A
Jade Build Status Build Status
Indigo Build Status Build Status
Hydro Build Status Build Status
Groovy Build Status Build Status
Fuerte Build Status Build Status

Repository Summary

Checkout URI https://github.com/lagadic/vision_visp.git
VCS Type git
VCS Version hydro-devel
Last Updated 2015-11-03
Dev Status MAINTAINED
Released RELEASED

README

ViSP stack for ROS

GPL-2

vision_visp provides ViSP algorithms as ROS components. ViSP is the Visual Servoing Platform and ROS a robotics middleware.

These packages are released under the GPL-2 license.

Components documentation is hosted on the ros.org wiki.

Support is provided through ROS Answers .

Which branch should I use?

Branches come in two flavors:

  • development branch,
  • release branch

Package for each ROS release is maintained on separate branches. I.e. hydro-devel is the Hydro development branch whereas hydro is the hydro release branch.

master means the next ROS release.

If you are a user you should use a release branch as they contain stable and tested versions of the packages. If you are a developper you must provide new patches against master. You may also provide version-specific bug fix again older releases.

  • Never implement new features in old branches (i.e. not master). These Pull Requests will not be accepted. If you provide a bug fix then you may ask for it to be backported. ABI/API breakage prevent patches from being backported.
  • The only action allowed in release branches is merging the development branch in the current branch.

Warning: the Fuerte branches still rely on the legacy rosbuild build system. We recommend you to update to a newer ROS release. Only minimum maintained will be done for this release.

Additional development guidelines are provided in CONTRIBUTING.md.

Build Status

This stack supports the following ROS releases:

  • Hydro
  • Groovy
  • Fuerte
  • Indigo

The master branch holds the development that will be available in the next ROS release.

ROS Release Development Branch Development branch (ros.org) Release Branch Documentation (ros.org)
Master Build Status N/A N/A N/A
Indigo Build Status Build Status Build Status Build Status
Hydro Build Status Build Status Build Status Build Status
Groovy Build Status Build Status Build Status Build Status
Fuerte Build Status N/A Build Status N/A