Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Re: Postgres tracking - the pgtrack project
Date: Mon, 4 Sep 2006 13:35:42 +0200
Message-ID: <6BCB9D8A16AC4241919521715F4D8BCEA3561B@algol.sollentuna.se>
In-Reply-To: <200609021602.k82G2qu29775@momjian.us>
Thread-Topic: [HACKERS] Postgres tracking - the pgtrack project
Thread-Index: AcbOrEd+E/ysJJPsQbChXWugt6GYSwBacgnw
References: <621fdf7c380b797f32c1ac0f7bccffd4@biglumber.com>
	<200609021602.k82G2qu29775@momjian.us>
From: "Magnus Hagander" <mha@sollentuna.net>
To: "Bruce Momjian" <bruce@momjian.us>,
	"Greg Sabino Mullane" <greg@turnstep.com>
Cc: <pgsql-hackers@postgresql.org>

> 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.=20

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

//Magnus