Skip to content

Is it possible to restructure the Changelog so it's parser friendly? #775

@luzpaz

Description

@luzpaz

Currently the changelog is challenging to parse, specific versions have multiple entries:

sipp/CHANGES.md

Lines 1 to 11 in 464cf74

BREAKING(!) changes in 3.7.3
============================
- Remove support for variables in PCAP filenames, originally introduced in 3.7.0. See #673
Bugs fixed in 3.7.3
===================
- Recovered `-mp` and `[auto_media_port]` to maintain backwards compatibility (by Orgad Shaneh)
- Fix crash when using PCAP play with more than one call (by Pete O'Neill)
- Fix pager on macOS by trying less and more too (by Walter Doekes)


sipp/CHANGES.md

Lines 25 to 31 in 464cf74

Features added in 3.7.0
===========================
- RTPstream can now handle .wav files with a WAV header (by Orgad Shaneh)
Bugs fixed in 3.7.0
=======================


Would it be possible to consider the approach offered in https://keepachangelog.com/ ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions