Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 1AD386378F9 for ; Tue, 17 Mar 2009 15:56:08 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 94161-01-10 for ; Tue, 17 Mar 2009 15:56:01 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by mail.postgresql.org (Postfix) with ESMTP id E3582636909 for ; Tue, 17 Mar 2009 15:51:04 -0300 (ADT) Received: from perhan.alvh.no-ip.org (200-126-101-194.bk7-dsl.surnet.cl [200.126.101.194]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id n2HIvi1i017250 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 17 Mar 2009 11:57:46 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 1DF8E47CDF; Tue, 17 Mar 2009 14:50:58 -0400 (CLT) Date: Tue, 17 Mar 2009 14:50:58 -0400 From: Alvaro Herrera To: Robert Treat Cc: Josh Berkus , pgsql-www@postgresql.org Subject: Re: Bad news approval Message-ID: <20090317185058.GI4202@alvh.no-ip.org> References: <49BD7159.6070709@agliodbs.com> <200903170029.26717.xzilla@users.sourceforge.net> <200903170903.31902.josh@agliodbs.com> <200903171429.04204.xzilla@users.sourceforge.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200903171429.04204.xzilla@users.sourceforge.net> User-Agent: Mutt/1.5.18 (2008-05-17) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Tue, 17 Mar 2009 11:57:47 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200903/114 X-Sequence-Number: 16768 Robert Treat wrote: > On Tuesday 17 March 2009 12:03:31 Josh Berkus wrote: > > Robert, > > > > > That was my bad. For some reason I thought we had an exception for > > > products that are introducing PostgreSQL support into thier products. I > > > guess that isn't the case? > > > > Yeah, but not betas. Look at it this way; if we're only allowing them one > > announcement per 6 months, then their final release will get no > > announcement. > > Well, this assumes the final release is within 6 months of the beta > announcement, which is probably true, though GMail is still in beta. I guess > assuming a priori knowledge of the product release cycle should be done in > favor of increasing the beta pool to help ensure solid support upon release. Actually this makes a lot of sense. Surely we'd like top-notch Postgres support on proprietary products, right? What about changing the policy to admit one beta announcement and one final release, even if they are closer than 6 months apart? -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.