| Summary: | Changelog not available | ||
|---|---|---|---|
| Product: | LibreOffice Online | Reporter: | Michiel Janssens <michiel> |
| Component: | LibreOffice | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED NOTOURBUG | ||
| Severity: | normal | CC: | aron.budea, samuel.mehrbrodt, timar74, xiscofauli |
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
|
Description
Michiel Janssens
2018-03-15 19:45:24 UTC
@Andras, One for you ? I don't think I will work on this. It is not supported by LibreOffice build system. List of changes is available in our version control system, for example: https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=cp-5.3-36..cp-5.3-43 Hi Andreas, the list you mention can be read and understood by a developer. However a sysadmin or just a home user using your CODE packages just would like to see the major highlights of the expected changes, f.e. CVE fixes, bug fixes or feature updates. That is worded nicely here: https://www.debian.org/doc/debian-policy/#document-ch-source "Changes in the Debian version of the package should be briefly explained in this file" And apparently the file that covers it: https://www.debian.org/doc/debian-policy/#s-changelogs I'm not a linux packager but I suppose that in debian/ubuntu, the changelogs will likely never be an automated task of a build system, rather a manual task for the maintainer releasing a package update. Let's confirm this, it'd be nice to figure out a way to semi-automate this and the format and whatnot upstream. For the last few releases, there always was a "Online" section in the release notes: https://wiki.documentfoundation.org/ReleaseNotes/6.3#Online https://wiki.documentfoundation.org/ReleaseNotes/6.2#Online https://wiki.documentfoundation.org/ReleaseNotes/6.1#Online That should be enough from TDF side. Adding changelog to specific packages is up to the packager :) |