rmw: 7.7.0-1 in 'rolling/distribution.yaml' [bloom]

[ahcorde]

Increasing version of package(s) in repository rmw to 7.7.0-1:

• upstream repository: https://github.com/ros2/rmw.git
• release repository: https://github.com/ros2-gbp/rmw-release.git
• distro file: rolling/distribution.yaml
• bloom version: 0.12.0
• previous version for package: 7.6.0-1

rmw

* get_zero_initialized_xxx functions return zero initialized structure. (#380 <https://github.com/ros2/rmw/issues/380>)
  * get_zero_initialized_xxx functions return zero initialized structure.
  * introduce RMW_EVENT_TYPE_MAX in rmw_event_type_t.
  * add a comment and more tests for rmw_event_type.
  ---------
* Contributors: Tomoya Fujita

rmw_implementation_cmake

• No changes

rmw_security_common

* Added rmw_security_common (#388 <https://github.com/ros2/rmw/issues/388>)
* Contributors: Alejandro Hernández Cordero

[github-actions]

Thanks for sending a pull request to ROS distro!

This is an automated tool that helps check your pull request for correctness.
This tool checks a number of attributes associated with your ROS package and generates a report that helps our reviewers merge your pull request in a timely fashion. Here are a few things to consider when sending adding or updating a package to ROS Distro.
ROS Distro includes a very helpful CONTRIBUTING.md file that we recommend reading if it is your first time submitting a package.
Please also read the ROS Distro review guidelines which summarizes this release process.

ROS Distro Considerations

• ROS Distributions are created using REP-134 Standards Track as a guide.
• Your package name should comply to REP-144 ROS Package Naming
• Your package must build for all platforms and architectures on the ROS buildfarm. See REP-2000 ROS Releases and Supported Platforms for all supported platforms for your ROS Distro.
• Your package must contain an OSI approved license. Your package.xml file must also include that license in a machine readable format. See REP-149 Package Manifest Format Three Specification for additional details.
• A publicly available, open source, repository for your ROS package.
• While not required, we recommend that you create an account for ROS Discourse and subscribe to the appropriate release topic.
• If you would like, you may join our Discord Server and ask questions in the #infra-help channel.

Package Considerations

Having your package included in a ROS Distro is a badge of quality, and we recommend that package developers strive to create packages of the highest quality. We recommend package developers review the following resources before submitting their package.

• REP-2004 Package Quality Declaration-- The ROS 2 TSC has created a quality rating system for ROS packages. These ratings should serve as a guide for package developers. We recommend package developers achieve a quality level of three or higher.
• Documentation -- it is recommended that ROS packages include an extensive README.md file, and API level documentation using the Sphinx documentation system.
• Maintainer Responsibilities -- the ROS 2 documentation includes a guide to ROS package maintainer responsibilities that summarizes your responsibilities as an open source maintainer. While we do not enforce these requirements on package maintainers they should be considered best practices.
• We recommend that your package should strive to conform to the ROS 2 Developer Guide and the ROS 2 Style Guide.

Need Help?

Please post your questions to Robotics Stack Exchange or refer to the #infra-help channel on our Discord server.

---

For changes related to yamllint:

• ✅ All new lines of YAML pass linter checks

[Yadunund]

@ahcorde I would have expected to see a major version bump given that we added a new package. Let's align on how we bump versions of core packages for Rolling in the next PMC meeting!

[MichaelOrlov]

• In general, I would agree with @Yadunund about major version bump when adding a new package.
  However, we usually bump major versions when making API/ABI-breaking changes. Adding a new package and a new API usually does not break API/ABI compatibility.
• Therefore merging this PR as is.