Re: Colons in wiki page titles, and commit fest page names

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Smith <gsmith(at)gregsmith(dot)com>
Cc: Brendan Jurd <direvus(at)gmail(dot)com>, pgsql-www(at)postgresql(dot)org
Subject: Re: Colons in wiki page titles, and commit fest page names
Date: 2008-04-22 14:51:42
Message-ID: 21357.1208875902@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

Greg Smith <gsmith(at)gregsmith(dot)com> writes:
> On Tue, 22 Apr 2008, Brendan Jurd wrote:
>> So, what naming scheme should we go with? I guess I would lean
>> towards "CommitFest YYYY-MM" for easy lexical sorting.

> I don't know. Maybe that is a good format. Maybe we should be naming
> them "8.4 CommitFest 1,2,3". This whole Year/Month format presumes a
> schedule that may or may not happen. For example: the next CommitFest is
> named "May 2008" right now. But what if it isn't then? Maybe some people
> end up on vacation and the whole thing slips a month. If the page was
> named "CommitFest 8.4-2" instead that problem goes away (but lexical
> sorting falls apart circa 10.0-1).

Well, naming them after version numbers is doomed to fail even sooner
than that --- what happens when we decide that, say, 8.5 is going to be
called 9.0 instead? Those sorts of decisions have always been made at
the ends of release cycles, so you'd be stuck with retroactively
renaming the pages.

I think the year/month naming idea is fine, at least for as far ahead
as we can see at the moment. There's no intention of allowing the
commit fests to slip.

> ... If it's not clearly impacting how people work, forget about it
> for now.

Agreed.

regards, tom lane

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Tom Lane 2008-04-22 16:40:42 Re: CommitFest Wiki page annoyance
Previous Message Alvaro Herrera 2008-04-22 14:21:28 Re: CommitFest Wiki page annoyance