2019.11.03 18:13 "[Tiff] libtiff, breaking with release traditions", by Bob Friesenhahn
I am currently working toward producing the next libtiff release, which we will call 4.1.0.
It has been a long tradition to include a per-release HTML file which has manually transcribed the changes from ChangeLog into HTML syntax. Since libtiff switched to CVS to Git, the ChangeLog file is no longer manually maintained, but may be (and will be) generated from Git history using a tool. I am finding the text of the Git history to be inadequate and the many changes lead to lots of menial work for me, and little value for the users.
Since Git is on-line and useful, I plan to simply include links to the Git change history for top directories. For example, changes related to libtiff utilities may be found at "https://gitlab.com/libtiff/libtiff/commits/master/tools" and changes to the libtiff library may be found at "https://gitlab.com/libtiff/libtiff/commits/master/libtiff". What could be easier than that?
Only significant changes which should be brought to the user's attention will get additional text in the per-release HTML file.
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt