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.
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.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
