Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id B0374474E61 for ; Sat, 7 Dec 2002 22:03:47 -0500 (EST) Received: from bast.unixathome.org (bast.unixathome.org [66.11.174.150]) by postgresql.org (Postfix) with ESMTP id D1436474E53 for ; Sat, 7 Dec 2002 22:03:45 -0500 (EST) Received: from wocker (wocker.unixathome.org [192.168.0.99]) by bast.unixathome.org (Postfix) with ESMTP id 4734B3F4F for ; Sat, 7 Dec 2002 22:03:48 -0500 (EST) From: "Dan Langille" To: pgsql-hackers@postgresql.org Date: Sat, 07 Dec 2002 22:03:48 -0500 MIME-Version: 1.0 Subject: Let's create a release team Message-ID: <3DF27044.17951.1306494D@localhost> X-mailer: Pegasus Mail for Windows (v4.02a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200212/447 X-Sequence-Number: 32902 Hi folks, Let's create a release team. This strategy is one well established in other projects and in industry. For lack of a better starting reference, let me suggest http://www.freebsd.org/releng/charter.html as a starting point for consideration. See also http://www.freebsd.org/releng/index.html. This will also lighten the load on the core team allowing them to focus on development and such. cheers -- Dan Langille : http://www.langille.org/