Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
>> Alvaro Herrera wrote:
>>> This is even better than our archives due to the problem that the
>>> archives don't have links to messages crossing month boundaries. Have
>>> you noticed that if you go to the archives, some discussions appe
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Alvaro Herrera wrote:
>> This is even better than our archives due to the problem that the
>> archives don't have links to messages crossing month boundaries. Have
>> you noticed that if you go to the archives, some discussions appear
>> truncated at a p
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Alvaro Herrera wrote:
>> This is even better than our archives due to the problem that the
>> archives don't have links to messages crossing month boundaries. Have
>> you noticed that if you go to the archives, some discussions appear
>> truncated at a p
On Wed, May 16, 2007 at 10:46:50AM -0400, Alvaro Herrera wrote:
> > > I am not sure. We will have to investigate more the capabilities of the
> > > bug tracking system we intend to use. In the worst case one could add
> > > the URL for the archived message copy; second worst would be bouncing
> >
Alvaro Herrera wrote:
> > > I am not sure. We will have to investigate more the capabilities of the
> > > bug tracking system we intend to use. In the worst case one could add
> > > the URL for the archived message copy; second worst would be bouncing
> > > (hopefully not forward) the interesting
Bruce Momjian wrote:
> Alvaro Herrera wrote:
> > Bruce Momjian wrote:
> > > Alvaro Herrera wrote:
> > > > Bruce Momjian wrote:
> > > > > Alvaro Herrera wrote:
> > > >
> > > > > > In Debian's bug tracking system, when the bug is created (which is
> > > > > > done
> > > > > > by sending an email to
Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > Alvaro Herrera wrote:
> > > Bruce Momjian wrote:
> > > > Alvaro Herrera wrote:
> > >
> > > > > In Debian's bug tracking system, when the bug is created (which is
> > > > > done
> > > > > by sending an email to a certain address) it gets a number, a
Bruce Momjian wrote:
> Alvaro Herrera wrote:
> > Bruce Momjian wrote:
> > > Alvaro Herrera wrote:
> >
> > > > In Debian's bug tracking system, when the bug is created (which is done
> > > > by sending an email to a certain address) it gets a number, and the
> > > > email is distributed to certain
On Tue, May 15, 2007 at 01:18:42PM -0400, Bruce Momjian wrote:
> > In Debian's bug tracking system, when the bug is created (which is done
> > by sending an email to a certain address) it gets a number, and the
> > email is distributed to certain lists. People can then reply to that
> > mail, and
Joshua D. Drake wrote:
> Bruce Momjian wrote:
>
> >> In Debian's bug tracking system, when the bug is created (which is done
> >> by sending an email to a certain address) it gets a number, and the
> >> email is distributed to certain lists. People can then reply to that
> >> mail, and send messa
Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > Alvaro Herrera wrote:
>
> > > In Debian's bug tracking system, when the bug is created (which is done
> > > by sending an email to a certain address) it gets a number, and the
> > > email is distributed to certain lists. People can then reply to th
Bruce Momjian wrote:
In Debian's bug tracking system, when the bug is created (which is done
by sending an email to a certain address) it gets a number, and the
email is distributed to certain lists. People can then reply to that
mail, and send messages to [EMAIL PROTECTED] and it gets tracked
Bruce Momjian wrote:
> Alvaro Herrera wrote:
> > In Debian's bug tracking system, when the bug is created (which is done
> > by sending an email to a certain address) it gets a number, and the
> > email is distributed to certain lists. People can then reply to that
> > mail, and send messages to
Alvaro Herrera wrote:
> Joshua D. Drake wrote:
>
> > >Also, if I want to discuss renaming something or cleaning up some code,
> > >do we create a tracker item for that or do we have a developer email
> > >list to discuss such issues?
> >
> > In the most conformist sense yes, but I can tell you t
Joshua D. Drake wrote:
> >Also, if I want to discuss renaming something or cleaning up some code,
> >do we create a tracker item for that or do we have a developer email
> >list to discuss such issues?
>
> In the most conformist sense yes, but I can tell you that generally
> isn't how CMD does
Bruce Momjian wrote:
To follow up on this, if you look at how TODO items are created, they
often come out of discussion threads, and sometimes more than one idea
comes from a discussion thread. If we moved to a trackers system, how
would we handle that?
We have the discussion on list, if it w
To follow up on this, if you look at how TODO items are created, they
often come out of discussion threads, and sometimes more than one idea
comes from a discussion thread. If we moved to a trackers system, how
would we handle that?
Also, if I want to discuss renaming something or cleaning up so
To follow up on Andrew's idea of tracking things back to the TODO or bug
number:
We could have a universal developer number, something like PGD#23432 as
a PostgreSQL Developer number. We could assign them for submissions to
the bugs list, where we already assign a number. I could easily add
the
Jim Nasby wrote:
> On May 6, 2007, at 8:18 AM, Andrew Dunstan wrote:
> > Oh, the answer to Bruce's question about when to create a feature
> > item? You could well do it at the time when today you create a TODO
> > item. However, we might even do better. For example, we might well
> > add fea
Jim Nasby wrote:
> On May 6, 2007, at 8:18 AM, Andrew Dunstan wrote:
> > Oh, the answer to Bruce's question about when to create a feature
> > item? You could well do it at the time when today you create a TODO
> > item. However, we might even do better. For example, we might well
> > add fea
Jim,
I am sympathetic to the issues you and Andrew are describing (I
understand Bruce's stream analogy, but I think Andrew is right that
from the user's point of view, it's not usable). But I am not
convinced that users voting on desired features will get us the
users' desired features. The fe
Hi,
guess I missed hackers on my initial reply. So I am re-sending the reply
I send to Joshua based on the reply I send to him in regards to a
hackers@ posting.
Read below.
regards,
Lukas
Joshua D. Drake wrote:
That being said, it seems obvious that so far PostgreSQL has been
mainly dr
Jim Nasby wrote:
On May 8, 2007, at 9:50 AM, Andrew Sullivan wrote:
On Mon, May 07, 2007 at 07:36:55AM -0500, Jim Nasby wrote:
Instead, if all feature requests are tracked then users can vote on
what's most important to them.
I am sympathetic to the issues you and Andrew are describing (I
und
On May 8, 2007, at 9:50 AM, Andrew Sullivan wrote:
On Mon, May 07, 2007 at 07:36:55AM -0500, Jim Nasby wrote:
Instead, if all feature requests are tracked then users can vote on
what's most important to them.
I am sympathetic to the issues you and Andrew are describing (I
understand Bruce's st
Andrew Sullivan wrote:
On Mon, May 07, 2007 at 07:36:55AM -0500, Jim Nasby wrote:
Instead, if all feature requests are tracked then users can vote on
what's most important to them.
I am sympathetic to the issues you and Andrew are describing (I
understand Bruce's stream analogy, bu
On Mon, May 07, 2007 at 07:36:55AM -0500, Jim Nasby wrote:
> Instead, if all feature requests are tracked then users can vote on
> what's most important to them.
I am sympathetic to the issues you and Andrew are describing (I
understand Bruce's stream analogy, but I think Andrew is right that
f
On May 6, 2007, at 8:18 AM, Andrew Dunstan wrote:
Oh, the answer to Bruce's question about when to create a feature
item? You could well do it at the time when today you create a TODO
item. However, we might even do better. For example, we might well
add feature requests that are denied. Tha
Dave Page wrote:
Bruce Momjian wrote:
The idea of the patch number in the subject line works with that
streaming model because it merely marks streams so they can be grouped.
The defining event that marks the stream is a post to the patches list.
We already number posts to the bugs list, so in
Bruce Momjian wrote:
The idea of the patch number in the subject line works with that
streaming model because it merely marks streams so they can be grouped.
The defining event that marks the stream is a post to the patches list.
We already number posts to the bugs list, so in a way we could impr
29 matches
Mail list logo
