Christopher Browne wrote:
> >> 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.
The problem comes with someone starting to work on something, then
giving up, but if you record it, people think they are still working on
it.
What happens now is that someone says they want to work on X, and the
community tells them that Y might be working on it, and Y gives us a
status.
-- Bruce Momjian bruce@momjian.us EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +