vkd3d: Add a changelog for all the released versions of vkd3d.
It will soon need an update, but do people at least like the idea?
Merge request reports
Activity
added 5 commits
-
9f2722f1...f866fb95 - 4 commits from branch
wine:master
- dd652314 - Add a changelog for all the released versions of vkd3d.
-
9f2722f1...f866fb95 - 4 commits from branch
added 1 commit
- 22a07cc8 - Add a changelog for all the released versions of vkd3d.
I agree that the change log can be handy for people that want to know when a feature was implemented or when they want to update vkd3d many versions at the same time.
I would rename it to CHANGELOG for consistency with the other files ANNOUNCE, AUTHORS, COPYING, LICENSE, INSTALL, README, etc...
Also, a little bit against markdown conventions, maybe we can format the titles for each version like we do in the README:
=============================== version titles can go like this ===============================
so it is easier to parse as plain text.
I would rename it to CHANGELOG for consistency with the other files ANNOUNCE, AUTHORS, COPYING, LICENSE, INSTALL, README, etc...
Well, the convention is for change logs to be called "ChangeLog" and for them to have a fairly specific format. (Wine used to have one; it was dropped a while ago in commit 84e8f7944be5bb53c8b5f1ff93cadcd0bba2acfe.)
Well, the convention is for change logs to be called "ChangeLog" and for them to have a fairly specific format.
I suppose the format you mean is the GNU one, as in https://www.gnu.org/prep/standards/html_node/Style-of-Change-Logs.html#Style-of-Change-Logs?
Is it important to you that we follow that? I don't find it particularly valuable today. Markdown is more common than that format today, and it correspond to the format we're already using for
ANNOUNCE
, removing the need for writing the same text in two different styles at each release.
Well, the convention is for change logs to be called "ChangeLog" and for them to have a fairly specific format.
I suppose the format you mean is the GNU one, as in https://www.gnu.org/prep/standards/html_node/Style-of-Change-Logs.html#Style-of-Change-Logs?
Is it important to you that we follow that? I don't find it particularly valuable today. Markdown is more common than that format today, and it correspond to the format we're already using for
ANNOUNCE
, removing the need for writing the same text in two different styles at each release.Not particularly; that was mostly in response to Francisco's suggestion to rename the file to CHANGELOG.
added 169 commits
-
22a07cc8...ddfa94fd - 168 commits from branch
wine:master
- 24460728 - Add a changelog for all the released versions of vkd3d.
-
22a07cc8...ddfa94fd - 168 commits from branch