Re: Postgres tracking - the pgtrack project

> Right now, the release notes show a list of all the significant
> items in each release, but it isn't available until the release,
> and it isn't complete (because it would be unreadable by ordinary
> users). And there is no tracking of individual items in progress
> except by individual developers. Magnus, for example, tracks Win32
> items, and Tom tracks backend stuff. I track whatever no one else
> tracks.

Well, I *try*. I find myself not managing quite as well as I'd like ;-)
So I for one would definitely appreciate a tool that would help with
that - provided that the tool fits the development model, not the other
way around.

(most other things seems to have been said already this time around, so
I won't repeat arguments others have made)

//Magnus