X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id AA87530DCBF for ; Tue, 10 Jun 2003 23:20:26 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 62751-05 for ; Tue, 10 Jun 2003 20:20:16 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id A2C2730DBB3 for ; Tue, 10 Jun 2003 20:20:15 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h5ANKCU6006367; Tue, 10 Jun 2003 19:20:12 -0400 (EDT) To: Bruce Momjian Cc: PostgreSQL-development Subject: Re: Feature freeze date In-reply-to: <200306101925.h5AJPd418238@candle.pha.pa.us> References: <200306101925.h5AJPd418238@candle.pha.pa.us> Comments: In-reply-to Bruce Momjian message dated "Tue, 10 Jun 2003 15:25:39 -0400" Date: Tue, 10 Jun 2003 19:20:12 -0400 Message-ID: <6366.1055287212@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200306/229 X-Sequence-Number: 39536 Bruce Momjian writes: > We are 5 days away from the feature freeze date, but with the almost > week of downtime we have had, I don't think we can stick to that date. > Do we choose July 1 as feature freeze and July 15 as beta, or push beta > start to Auguest 1? I don't think a week of partial downtime justifies a month's slip. The July 1/15 schedule seems like it might be a good plan though. I know I'm not going to be done editing error messages by June 15 ... Any other thoughts out there? regards, tom lane