public inbox for [email protected]  

help / color / mirror / Atom feed

From: Magnus Hagander <[email protected]>
To: Andrew Dunstan <[email protected]>
Cc: PostgreSQL WWW Mailing List <[email protected]>
Subject: Re: almost hidden placement of release support policy
Date: Mon, 11 Feb 2013 21:12:09 +0100
Message-ID: <CABUevEyMU2t5efGKMoEjVmUOUiXTURj2zqogbM1+5nHAfQ8Ptg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-www>

On Mon, Feb 4, 2013 at 5:30 PM, Andrew Dunstan <[email protected]> wrote:
>
> Web Team,
>
> I just went looking for the release maintenance policy on the web site. I
> eventually found it by a very circuitous route, but really this needs to be
> much more prominent. I'd suggest it needs its own page rather than being on
> the end of the Versioning Policy page. At the very least the Page should be
> renamed to reflect that it also covers release maintenance, and the submenu
> on the support page needs to reflect that. Frankly, though, I think it
> should be its own page and probably have a front page shortcut as well.

I agree it's pretty well hidden and could be done bette.r

I'm not sure "release maintenance policy" is all that much better a
name than "Versioning policy" :)

But, assuming we keep the current page as versioning policy, and add a
separate page that just has the EOL dates on it (I assume that's what
you're asking for, right?), what should we call that? I don't like
"release maintenance policy" since that part really isn't a policy,
but right now I'm drawing a blank for good names for such a page...

-- 
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/


-- 
Sent via pgsql-www mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-www

view thread (2+ messages)

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]
  Subject: Re: almost hidden placement of release support policy
  In-Reply-To: <CABUevEyMU2t5efGKMoEjVmUOUiXTURj2zqogbM1+5nHAfQ8Ptg@mail.gmail.com>

* 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