2011.01.04 22:10 "Re: [Tiff] libtiff 4.0 stable? [was: Regression in libtiff 4.0 CVS when creating a JPEG RGB contig]", by Edward Lam
On 1/4/2011 2:47 PM, Lee Howard wrote:
My broader opinion is that our development team is far too small to warrant more than one code branch and that it's really the distributions that provide a meaningful implementation of "stable".
What about a radical idea like just calling libtiff 4.0 "stable" and split for a 4.1 development branch? It's been about 6 months now since Bob released beta 6 and I haven't seen anyone reporting on this mailing list about 4.0 issues until now (for the patch committed last month).
My fear is that we're adding destabilizing commits into libtiff 4.0 and thus make that much harder for us to do a "stable" 4.0 release. If we never treat libtiff 4.0 as "stable", then it will never cease to be moving target. IMHO, we need a "code freeze" for libtiff 4.0 and aim a for a public release say in 6(?) months from now. Are we even doing any real active development on libtiff 4.0? And if we are, shouldn't we be doing in a 4.1 branch?