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 BB29DD1C9BC; Tue, 18 Nov 2003 04:18:22 +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 41194-08; Tue, 18 Nov 2003 00:17:51 -0400 (AST) Received: from lerami.lerctr.org (lerami.lerctr.org [207.158.72.11]) by svr1.postgresql.org (Postfix) with ESMTP id 98172D1B50C; Tue, 18 Nov 2003 00:08:06 -0400 (AST) Received: from lerlaptop.lerctr.org (lerlaptop.lerctr.org [207.158.72.14]) (authenticated bits=0) by lerami.lerctr.org (8.12.10/8.12.10/20030923) with ESMTP id hAI47vv4027845; Mon, 17 Nov 2003 22:07:57 -0600 (CST) Date: Mon, 17 Nov 2003 22:07:54 -0600 From: Larry Rosenman To: Peter Eisentraut , Neil Conway Cc: "Matthew T. O'Connor" , "Marc G. Fournier" , Christopher Kings-Lynne , PostgreSQL Development Subject: Re: Release cycle length Message-ID: <3050000.1069128474@lerlaptop.lerctr.org> In-Reply-To: References: X-Mailer: Mulberry/3.1.0 (Linux/x86) X-PGP-Info: All other keys are old/dead. X-PGP-Key: 0x3c49bdd6 X-PGP-Fingerprint: D0D1 3C11 F42F 6B29 FA67 6BF3 AD13 4685 3C49 BDD6 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========1423F2E970293475750A==========" X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/933 X-Sequence-Number: 47221 --==========1423F2E970293475750A========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On Tuesday, November 18, 2003 04:43:12 +0100 Peter Eisentraut=20 wrote: > Neil Conway writes: > >> That said, I'm not really sure how we can make better use of the beta >> period. One obvious improvement would be making the beta announcements >> more visible: the obscurity of the beta process on www.postgresql.org >> for 7.4 was pretty ridiculous. Does anyone else have a suggestion on >> what we can do to produce a more reliable .0 release in less time? > > Here are a couple of ideas: > > 0. As you say, make it known to the public. Have people test their > in-development applications using a beta. > > 1. Start platform testing on day 1 of beta. Last minute fixes for AIX or > UnixWare are really becoming old jokes. The only reason we had last minute stuff for UnixWare this time was the=20 timing of PG's release and the UP3 release from SCO. I try to test stuff fairly frequently, and this time I didn't know when,=20 exactly, SCO would make the release of the updated compiler. LER --=20 Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: ler@lerctr.org US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 --==========1423F2E970293475750A========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/uZscrRNGhTxJvdYRAmo4AJ9cstCRKnJVLdb8yWS20Kdcj04lJQCfUzo5 V98ETna+rBS0vzqh716bv4M= =+q0x -----END PGP SIGNATURE----- --==========1423F2E970293475750A==========--