Re: Open Items/Release (was [HACKERS]: Shouldn't pg_settings.enumvals...)

On Tue, 7 Oct 2008, Tom Lane wrote:

> Greg Smith <gsmith@gregsmith.com> writes:
>> I was trying to avoid creating a new page just for open-items.
>
> I'm not sure why not ...

The reason I ask about stuff like this is to cut down the sheer number of 
links that need to go on the high-level pages.  Besides that just being 
general good practice, it took quite a bit of shuffling to get 
http://wiki.postgresql.org/wiki/Development_information and the pages 
below it to be organized usefully.  That page keeps getting trivial 
content added to it, and it's already time for another round of trimming 
that out so it's just the important stuff there at that top level of the 
developer section.

> The open-items list has been a major part of managing every previous
> release cycle, and I'm sure it still will be when it's on the wiki

Fine; that clearly deserves its own page then and I'll hang myself on the 
first hook there to get the ball rolling.  Only reason I double-checked is 
that I didn't want to see another created then ignored because it's not 
relevant anymore page like the Wishlist.  If you're sure that's still the 
right way to organize this, you got it.  I'll select some pages to evict 
from their too prominant place to make space for it.

P.S. on this general topic: the growth in use of the CommitFest pages has 
been interesting:

CommitFest 2008-03 (1,829 views)
CommitFest 2008-05 (4,103 views)
CommitFest 2008-07 (5,715 views)
CommitFest 2008-09 (6,048 views)

The 2008-11 one is already up to 1,276 views.

--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD