Re: [HACKERS] New idea for patch tracking

2007-05-07 Thread Zdenek Kotala
Jim Nasby wrote: People have suggested different trackers that have varying amounts of email capability, but I don't think any of them have had the full capability that we'd need. At best they might accept comments on a bug/issue via email, but to work for the community they'd need to go

Re: [HACKERS] New idea for patch tracking

2007-05-07 Thread Jim Nasby
On May 7, 2007, at 7:47 AM, Zdenek Kotala wrote: Jim Nasby wrote: And you describe current processes based on email communication. But if we setup some tracker some process will be changed. I think first step is determine what we really want and after we can discuss how to reach it. If

Re: [HACKERS] New idea for patch tracking

2007-05-06 Thread Jim Nasby
On May 5, 2007, at 11:40 AM, Dave Page wrote: snip tracker outline Barring a few trivial details, that sounds almost identical to what I proposed. Well, Andrew says everyone he talks to doesn't want it. They want a more comprehensive solution that goes from bug to patch. I don't recall

Re: [HACKERS] New idea for patch tracking

2007-05-05 Thread Dave Page
--- Original Message --- From: Bruce Momjian [EMAIL PROTECTED] To: PostgreSQL-development pgsql-hackers@postgresql.org Sent: 05/05/07, 03:00:25 Subject: [HACKERS] New idea for patch tracking As for #3, again, I don't want us to take on a burdensome patch tracking process that is

Re: [HACKERS] New idea for patch tracking

2007-05-05 Thread Bruce Momjian
Dave Page wrote: --- Original Message --- From: Bruce Momjian [EMAIL PROTECTED] To: PostgreSQL-development pgsql-hackers@postgresql.org Sent: 05/05/07, 03:00:25 Subject: [HACKERS] New idea for patch tracking As for #3, again, I don't want us to take on a burdensome patch

Re: [HACKERS] New idea for patch tracking

2007-05-05 Thread Stefan Kaltenbrunner
Bruce Momjian wrote: Dave Page wrote: --- Original Message --- From: Bruce Momjian [EMAIL PROTECTED] To: PostgreSQL-development pgsql-hackers@postgresql.org Sent: 05/05/07, 03:00:25 Subject: [HACKERS] New idea for patch tracking As for #3, again, I don't want us to take on a

Re: [HACKERS] New idea for patch tracking

2007-05-05 Thread Bruce Momjian
Stefan Kaltenbrunner wrote: Bruce Momjian wrote: Dave Page wrote: --- Original Message --- From: Bruce Momjian [EMAIL PROTECTED] To: PostgreSQL-development pgsql-hackers@postgresql.org Sent: 05/05/07, 03:00:25 Subject: [HACKERS] New idea for patch tracking As for #3,

Re: [HACKERS] New idea for patch tracking

2007-05-05 Thread Stefan Kaltenbrunner
Bruce Momjian wrote: Stefan Kaltenbrunner wrote: Bruce Momjian wrote: Dave Page wrote: --- Original Message --- From: Bruce Momjian [EMAIL PROTECTED] To: PostgreSQL-development pgsql-hackers@postgresql.org Sent: 05/05/07, 03:00:25 Subject: [HACKERS] New idea for patch tracking As

Re: [HACKERS] New idea for patch tracking

2007-05-05 Thread Bruce Momjian
Stefan Kaltenbrunner wrote: Bruce Momjian wrote: Stefan Kaltenbrunner wrote: Bruce Momjian wrote: Dave Page wrote: --- Original Message --- From: Bruce Momjian [EMAIL PROTECTED] To: PostgreSQL-development pgsql-hackers@postgresql.org Sent: 05/05/07, 03:00:25 Subject:

Re: [HACKERS] New idea for patch tracking

2007-05-05 Thread Andrew Dunstan
Bruce Momjian wrote: Dave Page wrote: Barring a few trivial details, that sounds almost identical to what I proposed. Well, Andrew says everyone he talks to doesn't want it. They want a more comprehensive solution that goes from bug to patch. Dave can speak for his own views, but I think

Re: [HACKERS] New idea for patch tracking

2007-05-05 Thread Stefan Kaltenbrunner
Bruce Momjian wrote: Stefan Kaltenbrunner wrote: Bruce Momjian wrote: Stefan Kaltenbrunner wrote: Bruce Momjian wrote: Dave Page wrote: --- Original Message --- From: Bruce Momjian [EMAIL PROTECTED] To: PostgreSQL-development pgsql-hackers@postgresql.org Sent: 05/05/07, 03:00:25

Re: [HACKERS] New idea for patch tracking

2007-05-05 Thread Zdenek Kotala
I would like to add one point: Bruce Momjian wrote: Patch committers check several things before applying a patch: 1) Follows the SQL standard or community agreed-upon behavior 2) Style merges seamlessly into the surrounding code 3) Written as simply and efficiently as possible 4) Uses

Re: [HACKERS] New idea for patch tracking

2007-05-05 Thread Bruce Momjian
OK, item modified to: liPasses all regression tests, and if needed, adds new ones/li --- Zdenek Kotala wrote: I would like to add one point: Bruce Momjian wrote: Patch committers check several

Re: [HACKERS] New idea for patch tracking

2007-05-05 Thread Dave Page
--- Original Message --- From: Bruce Momjian [EMAIL PROTECTED] To: Dave Page [EMAIL PROTECTED] Sent: 05/05/07, 11:06:37 Subject: Re: [HACKERS] New idea for patch tracking snip tracker outline Barring a few trivial details, that sounds almost identical to what I proposed

Re: [HACKERS] New idea for patch tracking

2007-05-04 Thread Andrew Dunstan
Bruce Momjian wrote: I have already responded to all the email comments. Here is my idea of moving forward. There are basically three interrelated issues: 1) bug tracking 2) getting more people to review complex patches 3) patch tracking I am not going to go into #1, except to say

Re: [HACKERS] New idea for patch tracking

2007-05-04 Thread Bruce Momjian
Andrew Dunstan wrote: I will say publicly what I have said to others privately. Forgive me if I'm a bit blunter than usual. I do not see any value in this at all. What we need to track are problems to be solved, be they bugs or features, not particular patches. Tracking patches simply comes