Skip to content

Automating Changelog Generation #246

@mjcarroll

Description

@mjcarroll

There is a proposal to change the policy around how we create changelogs for ignition packages. The largest difference is that the changelogs will be updated at the time of release, rather than when a feature is merged ( the current procedure).

If we are doing this, there may be an opportunity to generate a changelog, much like how bloom does. This would be a reasonable reference for how bloom accomplishes this: https://github.com/ros-infrastructure/catkin_pkg/blob/master/src/catkin_pkg/changelog_generator.py

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions