X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id DFCB7D1B584; Tue, 18 Nov 2003 02:25:10 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 05215-09; Mon, 17 Nov 2003 22:24:43 -0400 (AST) Received: from ganymede.hub.org (u46n208.hfx.eastlink.ca [24.222.46.208]) by svr1.postgresql.org (Postfix) with ESMTP id 92B0DD1B52D; Mon, 17 Nov 2003 22:24:39 -0400 (AST) Received: by ganymede.hub.org (Postfix, from userid 1000) id CEE2835FD6; Mon, 17 Nov 2003 22:22:12 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id CDF79342A1; Mon, 17 Nov 2003 22:22:12 -0400 (AST) Date: Mon, 17 Nov 2003 22:22:12 -0400 (AST) From: "Marc G. Fournier" X-X-Sender: scrappy@ganymede.hub.org To: Christopher Kings-Lynne Cc: "Marc G. Fournier" , Peter Eisentraut , PostgreSQL Development Subject: Re: Release cycle length In-Reply-To: <3FB97A5B.5010102@familyhealth.com.au> Message-ID: <20031117221338.R731@ganymede.hub.org> References: <20031117204606.W731@ganymede.hub.org> <3FB97A5B.5010102@familyhealth.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/913 X-Sequence-Number: 47201 On Tue, 18 Nov 2003, Christopher Kings-Lynne wrote: > > Everyone on -hackers should have been aware of it, as its always > > discussed at the end of the previous release cycle ... and I don't think > > we've hit a release cycle yet that has actually stayed in the 4 month > > period :( Someone is always 'just sitting on something that is almost > > done' at the end that pushes it further then originally planned ... > > I think that the core just need to be tough on it, that's all. > > If we have pre-published target dates, then everyone knows if they can > get their code in or not for that date. Right now, I believe we are looking at an April 1st beta, and a May 1st related ... those are, as always, *tentative* dates that will become more fine-tuned as those dates become nearer ... April 1st, or 4 mos from last release, tends to be what we aim for with all releases ... as everyone knows, we don't necessarily acheive it, but ... Actually, historically, it looks like we've always been close to 12 months between releases ... 7.0->7.1: ~11mos, 7.1->7.2: ~10mos, 7.2->7.3: ~9 mos, and 7.3->7.4: ~12mos ... so, on average, we're dealing with an ~10mos release cycle for the past 3 years ... svr1# ls -l */postgresql-7.?.tar.gz -rw-rw-r-- 1 pgsql pgsql 9173732 May 9 2000 v7.0/postgresql-7.0.tar.gz -rw-r--r-- 1 pgsql pgsql 8088678 Apr 13 2001 v7.1/postgresql-7.1.tar.gz -rw-r--r-- 1 pgsql pgsql 9180168 Feb 4 2002 v7.2/postgresql-7.2.tar.gz -rw-r--r-- 1 pgsql pgsql 11059455 Nov 27 2002 v7.3/postgresql-7.3.tar.gz -rw-r--r-- 1 pgsql pgsql 12311256 Nov 16 17:57 v7.4/postgresql-7.4.tar.gz