public inbox for [email protected]
help / color / mirror / Atom feedFrom: Dave Page <[email protected]>
To: Michael Glaesemann <[email protected]>
To: Neil Conway <[email protected]>
Cc: Magnus Hagander <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: PostgreSQL WWW Mailing List <[email protected]>
Subject: Re: On-line docs for PG 8.1 need updating
Date: Mon, 7 Nov 2005 08:37:58 -0000
Message-ID: <E7F85A1B5FF8D44C8A1AF6885BC9A0E4CC3969@ratbert.vale-housing.co.uk> (raw)
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Michael
> Glaesemann
> Sent: 07 November 2005 02:04
> To: Neil Conway
> Cc: Magnus Hagander; Tom Lane; Dave Page; PostgreSQL WWW Mailing List
> Subject: Re: [pgsql-www] On-line docs for PG 8.1 need updating
>
>
> On Nov 7, 2005, at 6:46 , Neil Conway wrote:
>
> > On Sun, 2005-06-11 at 22:37 +0100, Magnus Hagander wrote:
> >> That's intentional, it's scheduled to go up along with the press
> >> release
> >> and related info once the release is done.
> >
> > What is the reasoning for this? IMHO for future releases it
> would be a
> > better idea to make the beta documentation a part of the main
> > website's
> > list of documentation at about the same time the first beta is
> > released.
> > That would make the documentation easier to find and would also
> > encourage more people to use the beta.
>
> I agree with your points. One reservation I have is that
> people might
> be more likely to run a beta in a production environment.
> Nowadays it
> seems increasingly common for projects to release betas for
> widespread circulation. I don't know if this is something
> that should
> be encouraged for PostgreSQL. I'd hate to see people get a bad
> impression of PostgreSQL because a beta screws up their data.
> Putting
> it on the top page might lend it more credibility and lead people to
> trust it in environments they shouldn't--even though PostgreSQL
> hackers are very clear that beta should not be used in production.
>
> I'd guess these things are better discussed on -advocacy.
Probably not - It's me that does the job, and if you discuss it there it
won't make any difference as I won't see it :-)
Regards, Dave.
view thread (8+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: On-line docs for PG 8.1 need updating
In-Reply-To: <E7F85A1B5FF8D44C8A1AF6885BC9A0E4CC3969@ratbert.vale-housing.co.uk>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox