AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2014.11.19 22:38 "[Tiff] libtiff release pending?", by Bob Friesenhahn
2014.11.19 22:48 "Re: [Tiff] libtiff release pending?", by Lee Howard
2014.11.19 23:09 "Re: [Tiff] libtiff release pending?", by Bob Friesenhahn
2014.11.19 23:07 "Re: [Tiff] libtiff release pending?", by Even Rouault
2014.11.19 23:14 "Re: [Tiff] libtiff release pending?", by Bob Friesenhahn
2014.11.19 23:23 "Re: [Tiff] libtiff release pending?", by Even Rouault
2014.11.19 23:34 "Re: [Tiff] libtiff release pending?", by Bob Friesenhahn
2014.11.19 23:40 "Re: [Tiff] libtiff release pending?", by Even Rouault
2014.11.19 23:59 "Re: [Tiff] libtiff release pending?", by Bob Friesenhahn
2014.12.06 18:29 "Re: [Tiff] libtiff test suite fails GCC Address Sanitizer", by Even Rouault

2014.11.19 23:09 "Re: [Tiff] libtiff release pending?", by Bob Friesenhahn

Libtiff CVS code works for me but perhaps there is something which absolutely should be fixed before a release.

It would be good for interested parties to verify that the code in libtiff CVS is worthy of a release. The code is worthy of a release if it is no worse than the previous release.

What's wrong with the traditional release process (cut code, beta, release candidate, etc.)?

Libtiff is believed to be in a stable state. It should not require the sort of release process required for experimental or possibly unstable code.

It would seem a simple and straight-forward method to call the community to make an active effort in vetting the code for release.

Interested developers should be able to use CVS to retrieve the code.

It has been observed that release candidates are rarely downloaded and tested.

The release candidates would consume shared library versioning numbers such that the "final" release would have numeric gaps from the previous "final" release.

Lastly, libtiff releases take several hours of work. Most of the work is associated with producing the release documentation. The procedure is well documented in the 'HOWTO-RELEASE' file.

Bob
--
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/