Re: 8.2 features status - Mailing list pgsql-hackers

From Christopher Browne
Subject Re: 8.2 features status
Date
Msg-id 87ac6fulu8.fsf@wolfe.cbbrowne.com
Whole thread Raw
In response to Re: 8.2 features status  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: 8.2 features status
List pgsql-hackers
A long time ago, in a galaxy far, far away, bruce@momjian.us (Bruce Momjian) wrote:
> Joshua D. Drake wrote:
>> >>
>> >> For example:
>> >>
>> >> Make postmater and postgres options distinct so the postmaster -o 
>> >> option is no longer needed | PeterE | Confirmed for 8.2 | 07/20/06
>> > 
>> > 
>> > We could do that, but once an item is done I don't see the point in
>> > having the date and person's name.  You are right that is clearly a
>> > different purpose from the TODO list, and if someone wants to track
>> > that, it might help things.
>> 
>> The idea of the above is not to track when it is done. THe "confirmed" 
>> is to track that development is taking place and that we have confirmed 
>> from the developer that they think it will be done for 8.2.
>
> Oh, "confirmed" confused me.  Maybe "anticipated" or "planned" for 8.2.
>
>> It is something that in theory would update throughout the cycle 3 or 4 
>> times. You could even have:
>> 
>> Make postmater and postgres options distinct so the postmaster -o
>> option is no longer needed | PeterE | Confirmed for 8.2 | 04/20/06
>> 
>> 
>> Make postmater and postgres options distinct so the postmaster -o
>> option is no longer needed | PeterE | Trouble encountered | 06/20/06
>> 
>> Make postmater and postgres options distinct so the postmaster -o
>> option is no longer needed | PeterE | Asks for help | 08/20/06
>> 
>> Make postmater and postgres options distinct so the postmaster -o
>> option is no longer needed | Alvaro | Confirmed | 09/20/06
>> 
>> Notice the sequence of events. I am not saying the specific statuses are 
>> the way to go but it would give a simple way to keep tabs on things 
>> without having to create a whole new ball of yarn.
>
> Interesting idea.  If people willing to state they will complete items
> for the next release, I can add this to the TODO list, and just remove
> it once the item is in CVS.

Is it forcibly necessary to have that commitment in order for this to
be of some use?

It seems to me that this would be a reasonably useful way of tracking
the progress of TODO items irrespective of any particular commitment
to completion in sync with a version.
-- 
(reverse (concatenate 'string "moc.liamg" "@" "enworbbc"))
http://linuxdatabases.info/info/languages.html
When aiming for the common denominator, be prepared for the occasional
division by zero.


pgsql-hackers by date:

Previous
From: alfranio correia junior
Date:
Subject: Re: standard interfaces for replication providers
Next
From: Bruce Momjian
Date:
Subject: Re: 8.2 features status