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 we
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
bey
On May 5, 2007, at 11:40 AM, 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.
I don't recall him saying that, tho
> --- 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
>
> >
> >
> > Barring a few trivial details, tha
OK, item modified to:
Passes all regression tests, and if needed, adds new
ones
---
Zdenek Kotala wrote:
> I would like to add one point:
>
> Bruce Momjian wrote:
>
> >
> > Patch committers check several
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 th
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
>>> Sent: 05/0
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 thin
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
> > Sent: 05/05/07, 03:00:25
> > S
Bruce Momjian wrote:
> Stefan Kaltenbrunner wrote:
>> Bruce Momjian wrote:
>>> Dave Page wrote:
> --- Original Message ---
> From: Bruce Momjian <[EMAIL PROTECTED]>
> To: PostgreSQL-development
> Sent: 05/05/07, 03:00:25
> Subject: [HACKERS] New idea for patch tracking
Stefan Kaltenbrunner wrote:
> Bruce Momjian wrote:
> > Dave Page wrote:
> >>
> >>> --- Original Message ---
> >>> From: Bruce Momjian <[EMAIL PROTECTED]>
> >>> To: PostgreSQL-development
> >>> Sent: 05/05/07, 03:00:25
> >>> Subject: [HACKERS] New idea for patch tracking
> >>>
> >>> As for
Bruce Momjian wrote:
> Dave Page wrote:
>>
>>> --- Original Message ---
>>> From: Bruce Momjian <[EMAIL PROTECTED]>
>>> To: PostgreSQL-development
>>> 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 burdenso
Dave Page wrote:
>
>
> > --- Original Message ---
> > From: Bruce Momjian <[EMAIL PROTECTED]>
> > To: PostgreSQL-development
> > 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
>
> --- Original Message ---
> From: Bruce Momjian <[EMAIL PROTECTED]>
> To: PostgreSQL-development
> 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 more effort than i
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 co
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 that
16 matches
Mail list logo