Обсуждение: Open Items/Release (was [HACKERS]: Shouldn't pg_settings.enumvals...)

Поиск
Список
Период
Сортировка

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

От
Greg Smith
Дата:
On Tue, 7 Oct 2008, Alvaro Herrera wrote:

> Greg Smith wrote:
>> http://wiki.postgresql.org/wiki/Todo:WishlistFor84
>
> No, "open items" is a list of tasks that must be completed before
> release, not a wishlist.

Moving this to a more appropriate list as not to bore all the hackers with 
wiki minutia.

After a bit of research I realized the original Wishlist page and format, 
which was quite active circa late 8.3, isn't really relevant anymore.  I 
just streamlined it to the parts that still make sense, which is just the 
initial proposals (few of them actually executed anyway).

I was trying to avoid creating a new page just for open-items.  On the 
original developer's wiki, there was an expansion of special-purpose pages 
for single tasks related to 8.3 that were really kind of confusing by the 
end.  I cleaned up a lot of that and would prefer not to go through that 
again.

With that in mind, here's what I think makes sense:

-Rename "ToDo:WishlistFor84" to "Proposed 8.4 Projects" since that's what 
it really ended up being.  While not strictly necessary, it suggests how a 
page like that should be named when the next release cycle starts, and 
that old page title needs to get rid of the old ToDo: baggage anyway.

-Create a "PostgreSQL 8.4.0 Development Archive" that all the no longer 
active pages can start moving to.  The goal will be that ultimately it 
will have *every* 8.4 page on it, as the main "Development Information" 
page moves to tracking the next version.  Push the page above 
(Wishlist->Proposed) and GSoC pages onto there as initial no longer 
mainstream content.

-Create a new "PostgreSQL 8.4 Release" page that tracks that process. 
Populate it right now with the "Open Items" list.  That gives a place to 
put other final release-oriented notes at, since the CommitFest pages are 
no longer going to be the place everything interesting is happening at.

I'm not sure whether that's the right title for the last page, part of why 
I didn't just do all of the above already.  But I think it's more 
appropriate to create a page addressing the 8.4 release checklist, with 
the coding "Open Items" just being the first section there, rather then 
creating a page for every individual task.  Maybe that's a better 
name--"PostgreSQL 8.4 Checklist"?

Anyway, just wanted to start kicking around ideas for how to usefully 
organize the end of the release cycle on the Wiki, which includes a bit of 
thinking about how that will smoothly transition to the next release.

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


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

От
Tom Lane
Дата:
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 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
rather than posted to -hackers every so often.  I don't think it's a
good idea to make it share a page with some unspecified set of other
stuff.
        regards, tom lane


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

От
Greg Smith
Дата:
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