jacro: 0.2.0-1 in 'rolling/distribution.yaml' [bloom]

[JafarAbdi]

Increasing version of package(s) in repository jacro to 0.2.0-1:

• upstream repository: https://github.com/JafarAbdi/jacro.git
• release repository: https://github.com/JafarAbdi/jacro-release.git
• distro file: rolling/distribution.yaml
• bloom version: 0.12.0
• previous version for package: null

jacro

* Replace minijinja with jinja2
* Contributors: JafarAbdi

[Yadunund]

New package review checklist

• At least one of the following must be present
  • Top level license file:
  • Per package license files:
• License is OSI-approved: BSD-3-Clause
• License correctly listed in package.xmls
• Public source repo: https://github.com/JafarAbdi/jacro.git
• Source repository contains ROS packages
• Each package meets REP-144 naming conventions

Left some comments to consider and will wait for secondary approval from @sloretz before we merge this.

[Yadunund]

Do you want to consider housing the release repo in the ros2-gbp org instead? The advantage there is that your package will automatically be available in the next ROS 2 distribution on release day.
https://docs.ros.org/en/rolling/How-To-Guides/Releasing/First-Time-Release.html#create-a-new-release-repository

[clalancette]

Actually, it is more than an advantage; for rolling, we require that the release repository be in the ros2-gbp organization.

[Yadunund]

Do you want to include a doc tag so that documentation is automatically generated for your package? The documentation will be accessible from your package page on index.ros.org.

[clalancette]

The release repository needs to be in the ros2-gbp organization for this to move forward.