https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22890 --- Comment #14 from Julian Maurice <julian.maurice@biblibre.com> --- (In reply to Martin Renvoize from comment #12)
I still think maintaining this inside Bugzilla and pulling it into a changelog.md file for each release is the way to go... I'd maintain it in a file with every commit/patchset if we were only supporting one definitive version/branch of Koha but as we're continually supporting at least 3 versions in parallel I think ensuring it's properly chronological would be difficult in commits..
An example would be with almost any bug.. it's is the rmaints decision whether the bug is a required backport and as such the RM doesn't know at the time of his/her push what version this bug is going to appear in.. as such they would put it under their version, and when the rmaints backported the rm would then need to forward port a second patch to get move the change down the changelog to get the chronology right again.
I don't think the forward port would be needed. Each stable branch would have its own changelog. For instance, if you are on 19.11.x Changelog would contain: # Unreleased - bugfix X - ... # 19.11.01 - bugfix Y - ... #19.11.00 <release notes of major version> And on master you would have # Unreleased - bugfix X - bugfix Y - ... # 19.11.00 <release notes of major version> I think it would be confusing to have bugfixes referenced twice or more in the same file (once for master, once for stable, once for oldstable, ...). Stable branches live their own life and I think it's ok if only them contain the changes for minor releases. -- You are receiving this mail because: You are watching all bug changes.