This document is a declaration of software quality for the rmf_task_msgs
package, based on the guidelines in REP-2004.
The package rmf_task_msgs
claims to be in the Quality Level 3 category.
Below are the rationales, notes, and caveats for this claim, organized by each requirement listed in the Package Requirements for Quality Level 3 in REP-2004.
rmf_task_msgs
uses semver
according to the recommendation for ROS Core packages in the ROS 2 Developer Guide.
rmf_task_msgs
is at a stable version, i.e. >= 1.0.0
.
The current version can be found in its package.xml, and its change history can be found in its CHANGELOG.
All message definition files located the msg
directory are considered part of the public API.
rmf_task_msgs
will not break public API within a released ROS distribution, i.e. no major releases once the ROS distribution is released.
rmf_task_msgs
will not break public ABI within a major version number.
rmf_task_msgs
follows the recommended guidelines for ROS Core packages in the ROS 2 Developer Guide.
rmf_task_msgs
requires that all changes occur through a pull request.
rmf_task_msgs
uses DCO as its confirmation of contributor origin policy. More information can be found in CONTRIBUTING.
All pull requests must have at least 1 peer review.
All pull requests must pass CI on all platforms supported by RMF.
All pull requests must resolve related documentation changes before merging.
rmf_task_msgs
has basic comments in the message definition files, but no list of messages or usage guide is provided.
New messages require their own documentation in order to be added.
rmf_task_msgs
has embedded API documentation, but it is not currently hosted.
The license for rmf_task_msgs
is Apache 2.0, the type is declared in the package.xml manifest file, and a full copy of the license is in the repository level LICENSE file.
There are no source files that are currently copyrighted in this package so files are not checked for abbreviated license statements.
There are no copyrighted source files in this package.
This quality declaration is linked in the README file.
This quality declaration has not been externally peer-reviewed and is not registered on any Level 3 lists.
rmf_task_msgs
is a package providing strictly message definitions and therefore does not require associated tests.
rmf_task_msgs
is a package providing strictly message definitions and therefore does not require associated tests.
rmf_task_msgs
is a package providing strictly message definitions and therefore has no coverage requirements.
rmf_task_msgs
is a package providing strictly message definitions and therefore has no performance requirements.
rmf_task_msgs
does not use the standard linters and static analysis tools for its generated C++ and Python code to ensure it follows the ROS 2 Developer Guide.
rmf_task_msgs
has the following runtime ROS dependencies, which are at or above Quality Level 3:
It has several "buildtool" dependencies, which do not affect the resulting quality of the package, because they do not contribute to the public library API.
rmf_task_msgs
does not have any optional direct runtime ROS dependencies.
rmf_task_msgs
does not have any runtime non-ROS dependencies.
As a pure message definitions package, rmf_task_msgs
supports all of the tier 1 platforms as described in REP-2000, but does not currently test each change against all of them.
This package conforms to the Vulnerability Disclosure Policy in REP-2006.