public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Greg Smith <[email protected]>
Cc: Stefan Kaltenbrunner <[email protected]>
Cc: PostgreSQL www <[email protected]>
Subject: Re: Roadmap web page
Date: Wed, 11 Jun 2008 10:55:33 -0400 (EDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Greg Smith wrote:
> On Fri, 30 May 2008, Bruce Momjian wrote:
>
> > Stefan Kaltenbrunner wrote:
> >> Bruce Momjian wrote:
> >>> Do we need to update the URLs on the roadmap page to point to the wiki
> >>> instead?
> >>>
> >>> http://www.postgresql.org/developer/roadmap
> >>
> >> what urls and what wording would you think is appropriate - we could
> >> either link to
> >> http://wiki.postgresql.org/wiki/PostgreSQL_8.4_Development_Plan or
> >> include that exact information on the website - or what else do you have
> >> in mind ?
> >
> > I would like us to use consistent URLs based on ISO dates rather than
> > month names, and have a fixed URL that points to the most recent
> > commit-fest, and then link to that from the web site.
>
> So basically what you want here is for CommitFest:July to become
> CommitFest:2008-07? That's pretty reasonable and some ideas in this area
> were already tossed around.
Yes.
> There's already a http://wiki.postgresql.org/wiki/CommitFest redirect that
> is being kept current.
Good.
> I still think the developer/roadmap page should include a link to a
> higher-level view than the CommitFest level. Linking to specific versions
> is a maintenance headache to be avoided though; a link to
> http://wiki.postgresql.org/wiki/Development_information would be
> sufficient I think, that's a highly visible page that should always be
> kept up to date.
Agreed. I was thinking of using the ISO date because it makes sorting
pages in order easier and clearer.
--
Bruce Momjian <[email protected]> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
view thread (9+ 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]
Subject: Re: Roadmap web page
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