From: | Neil Conway <neilc(at)samurai(dot)com> |
---|---|
To: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Release cycle length |
Date: | 2003-11-18 05:53:12 |
Message-ID: | 87k75ygr3r.fsf@mailbox.samurai.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-www |
"Marc G. Fournier" <scrappy(at)postgresql(dot)org> writes:
> On Tue, 18 Nov 2003, Peter Eisentraut wrote:
>
>> 0. As you say, make it known to the public. Have people test their
>> in-development applications using a beta.
>
> and how do you propose we do that? I think this is the hard part
(1) Make the beta more obvious on the website, as we've already
discussed
(2) Make a freshmeat.net release announcement for _each_ beta, RC, and
of course the final release (we totally missed this during 7.4).
There are probably other software release announcement sites we
could inform.
(3) Is it worth trying to get some technical press coverage for the
start of the beta process? I don't mean on PHB-oriented sites like
ComputerWorld or ZdNet where we need to do the work of getting a
press release prepared, but OSNews or Slashdot just need a link to
the release notes and the source tarballs.
Any other suggestions?
Perhaps we could add a list of this sort to src/tools/RELEASE_CHANGES?
-Neil
From | Date | Subject | |
---|---|---|---|
Next Message | Marc G. Fournier | 2003-11-18 06:00:56 | Re: Release cycle length |
Previous Message | Matthew T. O'Connor | 2003-11-18 05:52:59 | Re: [pgsql-advocacy] Not 7.5, but 8.0 ? |
From | Date | Subject | |
---|---|---|---|
Next Message | Marc G. Fournier | 2003-11-18 06:00:56 | Re: Release cycle length |
Previous Message | elein | 2003-11-18 05:03:41 | 7.4 official docs : Fonts? |