Re: [HACKERS] On status data and summaries

Andrew Sullivan wrote: > On Thu, Oct 12, 2006 at 05:26:02PM -0400, Bruce Momjian wrote: > > What I think people wanted was something like that, but maintained > > during the development cycle, so they would know what features our being > > worked on, and by whom. > > I'd be happy to work on that.

Re: [HACKERS] On status data and summaries

On Thu, Oct 12, 2006 at 05:26:02PM -0400, Bruce Momjian wrote: > What I think people wanted was something like that, but maintained > during the development cycle, so they would know what features our being > worked on, and by whom. I'd be happy to work on that. > One great thing about the list I

Re: [HACKERS] On status data and summaries

Andrew Sullivan wrote: > On Thu, Oct 12, 2006 at 01:56:37PM -0500, Jim C. Nasby wrote: > > *ahem* nudge people to update the status of what they're working on once > > a month. > > Well, though, remember that the point of this was supposed to be to > make things easier for the developers, who are

Re: [HACKERS] On status data and summaries

On Thu, Oct 12, 2006 at 01:56:37PM -0500, Jim C. Nasby wrote: > *ahem* nudge people to update the status of what they're working on once > a month. Well, though, remember that the point of this was supposed to be to make things easier for the developers, who are already spending (it would seem) to

Re: [HACKERS] On status data and summaries

On Thu, Oct 12, 2006 at 01:53:27PM -0400, Andrew Sullivan wrote: > On Thu, Oct 12, 2006 at 10:20:43AM -0400, Bruce Momjian wrote: > > use a wiki to track open development items, with some status, like I did > > for the open items list for 8.2. I usually only do that during feature > > freeze, but

Re: [HACKERS] On status data and summaries

On Thu, Oct 12, 2006 at 10:20:43AM -0400, Bruce Momjian wrote: > use a wiki to track open development items, with some status, like I did > for the open items list for 8.2. I usually only do that during feature > freeze, but could expand it and open it up for others to edit. So do I understand th

Re: [HACKERS] On status data and summaries

Andrew Sullivan wrote: > On Wed, Oct 11, 2006 at 06:26:50PM -0400, Bruce Momjian wrote: > > > > Funny, sounds like what I usually do. I welcome the assistance. > > Well, yes, that was my impression too. The complaint in the thread > that started all this, as I understood it, was that there were

Re: [HACKERS] On status data and summaries

Jim C. Nasby wrote: > On Thu, Oct 12, 2006 at 07:14:36AM -0400, Andrew Sullivan wrote: > > On Wed, Oct 11, 2006 at 06:26:50PM -0400, Bruce Momjian wrote: > > > > > > Funny, sounds like what I usually do. I welcome the assistance. > > > > Well, yes, that was my impression too. The complaint in t

Re: [HACKERS] On status data and summaries

On Thu, Oct 12, 2006 at 07:14:36AM -0400, Andrew Sullivan wrote: > On Wed, Oct 11, 2006 at 06:26:50PM -0400, Bruce Momjian wrote: > > > > Funny, sounds like what I usually do. I welcome the assistance. > > Well, yes, that was my impression too. The complaint in the thread > that started all thi

Re: [HACKERS] On status data and summaries

On Wed, Oct 11, 2006 at 06:26:50PM -0400, Bruce Momjian wrote: > > Funny, sounds like what I usually do. I welcome the assistance. Well, yes, that was my impression too. The complaint in the thread that started all this, as I understood it, was that there were big, hairy features that tended to

Re: [HACKERS] On status data and summaries

Funny, sounds like what I usually do. I welcome the assistance. --- Andrew Sullivan wrote: > Hello, > > In a possible moment of insanity, in > > > > I

Re: [HACKERS] On status data and summaries

On Wed, Oct 11, 2006 at 04:27:41PM -0400, Andrew Sullivan wrote: > Hello, > > In a possible moment of insanity, in > > > > I volunteered to try to help solve a problem Tom Lane noted: "The > hard part of this problem is finding

[HACKERS] On status data and summaries

Hello, In a possible moment of insanity, in I volunteered to try to help solve a problem Tom Lane noted: "The hard part of this problem is finding a convenient way to capture status data out of the community's conversations."