Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
luzpaz opened this issue Jan 30, 2025 · 0 comments
Open

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

luzpaz opened this issue Jan 30, 2025 · 0 comments

Comments

@luzpaz
Copy link
Contributor

luzpaz commented Jan 30, 2025

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/ ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant