Return-Path: <tiff-bounces@lists.maptools.org>
X-Original-To: info@awaresystems.be
Delivered-To: info@awaresystems.be
Received: from mx-m.b-one.net (mx-m.one.com [91.198.169.60])
	by mail9.b-one.net (Postfix) with ESMTP id A435940080A
	for <info@awaresystems.be>; Mon, 22 Feb 2010 22:59:33 +0100 (CET)
Received: by mx-m.b-one.net (Postfix, from userid 106)
	id 9534D11C50F2; Mon, 22 Feb 2010 22:59:33 +0100 (CET)
X-Virus-Scanned: by one.com
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=0 required=4 tests=[none]
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4
Received: from lists.maptools.org (lists.maptools.org [65.39.174.144]) by
 mx-m.b-one.net (Postfix) with ESMTP id D3E0711C50F0 for
 <info@awaresystems.be>; Mon, 22 Feb 2010 22:59:23 +0100 (CET)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by
 lists.maptools.org (Postfix) with ESMTP id 6D8D31D3D4538; Mon, 22 Feb 2010
 16:58:50 -0500 (EST)
Received: from mail.sidefx.com (mail.sidefx.com [38.99.137.163]) by
 lists.maptools.org (Postfix) with ESMTP id 5D3A71D3D4430 for
 <tiff@lists.maptools.org>; Mon, 22 Feb 2010 16:34:48 -0500 (EST)
Message-ID: <4B82F86F.70909@sidefx.com>
Date: Mon, 22 Feb 2010 16:34:39 -0500
From: Edward Lam <edward@sidefx.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
References: <alpine.GSO.2.01.0911041214530.19531@freddy.simplesystems.org>
 <4B829A95.1070204@sidefx.com> <op.u8ja9b0mqw3wu1@titan>
 <4B82A57C.9030002@pobox.com> <4B82A962.6040504@howardsilvan.com>
 <4B82AD87.8080300@pobox.com> <4B82C2B4.4010409@howardsilvan.com>
 <4B82CD05.50608@pobox.com> <4B82DDE2.1020407@howardsilvan.com>
 <4B82E1C8.2090008@pobox.com>
 <alpine.GSO.2.01.1002221430410.25017@freddy.simplesystems.org>
In-Reply-To: <alpine.GSO.2.01.1002221430410.25017@freddy.simplesystems.org>
Cc: Tiff List <tiff@lists.maptools.org>
Subject: Re: [Tiff] Libtiff 4.0.0beta5 Released
X-BeenThere: tiff@lists.maptools.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TIFF and libtiff discussion <tiff.lists.maptools.org>
List-Unsubscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
 <mailto:tiff-request@lists.maptools.org?subject=unsubscribe>
List-Archive: <http://lists.maptools.org/mailman/private/tiff>
List-Post: <mailto:tiff@lists.maptools.org>
List-Help: <mailto:tiff-request@lists.maptools.org?subject=help>
List-Subscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
 <mailto:tiff-request@lists.maptools.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org

Bob Friesenhahn wrote:
> I don't see a real difference between release candidates or betas. 
> Betas are all release candidates.

Release candidates tend to make more sense with commercial software. In 
absence of that, I'll go with it as "We will not fix anything in a 
release candidate unless it is a crash that will impact most people". I 
guess that presumes that you also thought of a beta as "we will still 
add patches that people believe should be added before release". :)

With that definition, I'd agree with Lee that we should just move to a 
"release candidate". We've gone through 5 betas already and it's 
unlikely that someone new will come along and test a beta6 if they 
haven't already tested the betas. The added bonus of changing the name 
to "release candidate" is that it gives yet another signal that "Ok, 
we're *actually* going to release this time." :)

Cheers,
-Edward

_______________________________________________
Tiff mailing list: Tiff@lists.maptools.org
http://lists.maptools.org/mailman/listinfo/tiff
http://www.remotesensing.org/libtiff/
