Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id B3AC09FBB89 for ; Wed, 8 Aug 2007 15:16:38 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 42164-06-3 for ; Wed, 8 Aug 2007 15:16:32 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.185]) by postgresql.org (Postfix) with ESMTP id 44DCB9FBC6F for ; Wed, 8 Aug 2007 15:16:34 -0300 (ADT) Received: by rv-out-0910.google.com with SMTP id f1so178046rvb for ; Wed, 08 Aug 2007 11:16:33 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=R7hshJROrH1MPjs6lmysJwePdNei8G3VNMNclpTwVAc/ho4Tx1Bf2niFz47lL6LNApHghp8X+WY7lBKuMkYGlm9eADifLeYq1LH8MbviN6fRDIMQmttK/XE0MUXeVe8mSY+5m3e9lX3rP/P0Ra8gkTiG1eGEY42rYcBX16lDHZQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=bS3Z1Ldt9bs4VHvLqx0GPVguoXDcMJZkAjO0I2FmNddbAFpSbdJAKoqsO6kiETGx3W3xhz9T1cyxTJIZ2/OIKc6h1cABDSkqBH9Jmye5OUOJPiTfa+41hIkxQ07qFYoYEqXvTQlQXuV/0iOrho8hChodHrGPJlAfOoyYPKeSSFQ= Received: by 10.141.155.5 with SMTP id h5mr250119rvo.1186596992885; Wed, 08 Aug 2007 11:16:32 -0700 (PDT) Received: by 10.141.77.17 with HTTP; Wed, 8 Aug 2007 11:16:32 -0700 (PDT) Message-ID: <219951fd0708081116v5c761346yc68d72b04ae9ee1d@mail.gmail.com> Date: Wed, 8 Aug 2007 14:16:32 -0400 From: "Mike Ellsworth" To: pgsql-advocacy@postgresql.org Subject: Re: EnterpriseDB Postgres In-Reply-To: <46B9FA88.8000809@commandprompt.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1887_1133439.1186596992826" References: <200708081736.26564.peter_e@gmx.net> <51494DB187D98F4C88DBEBF1F5F6D423022518CA@edb06.mail01.enterprisedb.com> <200708081836.44990.peter_e@gmx.net> <46B9FA88.8000809@commandprompt.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/159 X-Sequence-Number: 11729 ------=_Part_1887_1133439.1186596992826 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 8/8/07, Joshua D. Drake wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Peter Eisentraut wrote: > > Am Mittwoch, 8. August 2007 18:11 schrieb Derek Rodner: > >> While the wording of the press release is cause for concern in the > >> community because of "first-ever" and "professional grade", we need to > >> do this for marketing purposes. If we had said "EnterpriseDB releases > >> yet another PostgreSQL distribution" then no one would cover it. > > > > Well, at least you are admitting that you are not telling the truth. > > > > I will suggest, however, that knowingly wrong material should not be > posted on > > the postgresql.org web site any longer. > > How do we make that determination? > > Sincerely, > > Joshua D. Drake > I was under the impression that www scrutinizes all Press Releases prior to posting to the site. Not true? It would seem to make more sense to do so as issues such as this could be worked out privately. Presoak the laundry before hanging on the line. Otherwise, neighbors may gossip. ------=_Part_1887_1133439.1186596992826 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 8/8/07, Joshua D. Drake <jd@commandprompt.com> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Peter Eisentraut wrote:
> Am Mittwoch, 8. August 2007 18:11 schrieb Derek Rodner:
>> While the wording of the press release is cause for concern in the
>> community because of "first-ever" and "professional grade", we need to
>> do this for marketing purposes.  If we had said "EnterpriseDB releases
>> yet another PostgreSQL distribution" then no one would cover it.
>
> Well, at least you are admitting that you are not telling the truth.
>
> I will suggest, however, that knowingly wrong material should not be posted on
> the postgresql.org web site any longer.

How do we make that determination?

Sincerely,

Joshua D. Drake

I was under the impression that www scrutinizes all Press Releases prior to posting to the site.  Not true?

It would seem to make more sense to do so as issues such as this could be worked out privately. 
Presoak the laundry before hanging on the line.  Otherwise, neighbors may gossip.
------=_Part_1887_1133439.1186596992826--