Content-Type: text/plain;
  charset="iso-8859-1"
From: Robert Treat <xzilla@users.sourceforge.net>
To: Tom Lane <tgl@sss.pgh.pa.us>, Lamar Owen <lamar.owen@wgcr.org>
Subject: Re: [HACKERS] SAP and MySQL ... [and Benchmark]
Date: Fri, 13 Jun 2003 23:54:22 -0400
User-Agent: KMail/1.4.2
Cc: Justin Clift <justin@postgresql.org>,
	Bruce Momjian <pgman@candle.pha.pa.us>, jim@nasby.net,
	"pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
References: <200306111624.h5BGOHe06484@candle.pha.pa.us>
	<200306131210.58564.lamar.owen@wgcr.org>
	<5786.1055563582@sss.pgh.pa.us>
In-Reply-To: <5786.1055563582@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200306132354.22606.xzilla@users.sourceforge.net>

On Saturday 14 June 2003 12:06 am, Tom Lane wrote:
> Lamar Owen <lamar.owen@wgcr.org> writes:
> > Getting the Linux, FreeBSD, and other geek news sites their press relea=
se
> > is just as important, but, that's a different audience who needs a
> > different press release.  ZDNet and its ilk could get the mainstream
> > release, with only a link to the homepage.  The geek news gets a meatier
> > press release, with links to the home page, downloads, and release note=
s.
> >  And Hackers gets the release notes.  One size does not fit all.
>
> ISTM Lamar's struck the nail pretty square on the head here.  We have
> several easily-identifiable audiences for release announcements.  We
> have to provide each audience with the material they want.
>

The current plan for the next major release is to write up a general press=
=20
release to be distributed to -announce and to the list o' press contacts.=
=20=20
It'll also go up on the various websites. However it *won't* be sent to the=
=20
-hackers list.  This worked well the last time (save the hackers part) and =
I=20
don't think anyone has brought up a reason to change it.

> I believe the current core team ("technical core" if you like that
> phrase) understands what sort of info the pgsql-hackers audience wants.
> I'm very happy to defer to someone else's judgement on how to present
> the same info to non-hacker audiences.
>
> Seems like the next problem is to figure out exactly who gets the last
> say in those decisions.  I made a lot of sweeping statements yesterday
> about earning one's respect by track record ... but I'm not sure what
> we do in the short run before anyone's established track records ...
>

we can sort that one out with whoever shows up on -advocacy.

Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL