public inbox for [email protected]  

help / color / mirror / Atom feed

From: Selena Deckelmann <[email protected]>
To: Tom Lane <[email protected]>
Cc: Brendan Jurd <[email protected]>
Cc: Alvaro Herrera <[email protected]>
Cc: Stefan Kaltenbrunner <[email protected]>
Cc: PostgreSQL www <[email protected]>
Cc: [email protected]
Subject: Re: [DOCS] the sad state of our FAQs
Date: Sat, 7 Mar 2009 14:52:19 -0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On Mar 7, 2009, at 2:33 PM, Tom Lane <[email protected]> wrote:

> Brendan Jurd <[email protected]> writes:
>> Although to be frank I think the value of per-version FAQs is  
>> dubious.
>> I would be totally okay with seeing the back-branch FAQs abandoned in
>> favour of the One FAQ (to rule them all, etc).
>
> I think it might well be true though that it'd be better to have one  
> FAQ
> with answers that say something like "Before version x.y, do this ...
> in x.y and later, do that ...".  That approach makes sure that people
> know that they are reading version-specific advice; whereas the  
> separate
> FAQs approach makes it pretty easy for people to fail to notice that
> they are reading advice that's inappropriate for their version.

Another approach would be to tag each FAQ with what version it was  
created for and what version it is deprecated for. (pretty much what  
Brenden suggested, but slightly less overhead than listing all  
versions the FAQ applies to)

Then we could do cool things like generate the version specific FAQs  
programmatically and not ever worry about removing them.

-Selena

view thread (29+ 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], [email protected]
  Subject: Re: [DOCS] the sad state of our FAQs
  In-Reply-To: <[email protected]>

* 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