2015.06.13 06:10 "Re: [Tiff] Libtiff 4.0.4 release soon", by Lee Howard
I've committed the mentioned contributed patches to the repository. The source builds afterwards, and the few tests I ran passed.
A quick review of Bugzilla shows 89 open bugs, and at least a few of them have patches available on the reports. I will try to review these this weekend and make some commits where possible. Others can feel welcome to assist in this effort.
I am unlikely to make the time to go through distributions' patches and see if there is anything there worth upstreaming. So if someone is ambitious... :-D
On 06/11/2015 09:43 AM, Lee Howard wrote:
On 06/11/2015 08:46 AM, Bob Friesenhahn wrote:
There will be a libtiff 4.0.4 release within the next week or two. I encourage interested parties to check out libtiff from CVS (see instructions at http://www.remotesensing.org/libtiff/) and verify that no problems have been added since the previous release (which is from September 22, 2012).
On 2014-05-21 Eduardo Robles Elvira sent a few patches to the mailing list. While he admitted that at least one of the patches was intended for their own use (and apparently was provided merely to point-out some problem) I see no evidence that his other patches were addressed.
Also on 2014-05-21 Antti S. Lankila provided a patch on Bug 2078 which does not seem to be addressed.
On 2015-01-25 Yuriy M. Kaminskiy provided a patch to the mailing list which does not seem to be addressed.
On 2015-05-08 Andy Cave provided an explanation to the mailing list for a patch (which I've now created and sent to the list) which does not seem to be addressed.
I haven't tested any of those patches, but my sentiment is that's what "beta" release-cycle periods (like this one) are for.
Have the open tickets in Bugzilla been reviewed to see if any have provided patches?
Have the libtiff packages at major distributions (e.g. Fedora, Debian, Gentoo) been reviewed to see if any are using patches that should have been upstreamed but weren't?
I have made a cursory test of current libtiff CVS using HylaFAX+, and it worked fine, but I have not been extremely thorough, and HylaFAX is not an extremely thorough test of libtiff.