Re: Managing the community information stream

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, and the
> > > > > email is distributed to certain lists. People can then reply to that
> > > > > mail, and send messages to 12345@bugs.debian.org and it gets tracked in
> > > > > the bug, and you can see all those messages in the bug report. I
> > > > > ass-ume that BZ 3.0 does something similar.
> > > >
> > > > But often a TODO item has multiple threads containing details (often
> > > > months apart), and it isn't obvious at the time the thread is started
> > > > that this will happen. Note the number of TODO items that now have
> > > > multiple URLs. How is that handled?
> > >
> > > Just add the bug address to CC and reply to it, just like when you reply
> > > to say "added to TODO", only that you don't need to manually go and
> > > modify the TODO file by hand. The bug tracking system puts that mail
> > > into the bug report. Subsequent followups keep the bug address in CC
> > > and thus the whole discussion is saved in the bug report.
> >
> > Right, but you are adding the bug addresss at the end of the email
> > thread. How do you point to the email you want to reference?
>
> 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 messages to the bug address.

Sounds like what I do with the TODO list now.

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

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 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 12345@bugs.debian.org and it gets tracked in
> > > > > > the bug, and you can see all those messages in the bug report. I
> > > > > > ass-ume that BZ 3.0 does something similar.
> > > > >
> > > > > But often a TODO item has multiple threads containing details (often
> > > > > months apart), and it isn't obvious at the time the thread is started
> > > > > that this will happen. Note the number of TODO items that now have
> > > > > multiple URLs. How is that handled?
> > > >
> > > > Just add the bug address to CC and reply to it, just like when you reply
> > > > to say "added to TODO", only that you don't need to manually go and
> > > > modify the TODO file by hand. The bug tracking system puts that mail
> > > > into the bug report. Subsequent followups keep the bug address in CC
> > > > and thus the whole discussion is saved in the bug report.
> > >
> > > Right, but you are adding the bug addresss at the end of the email
> > > thread. How do you point to the email you want to reference?
> >
> > 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 messages to the bug address.
>
> Sounds like what I do with the TODO list now.

Except that this is the *worst case* with the bug tracker, whereas for
the TODO list it is not only the worst case, it is also the best case
and the only case at all.

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

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 messages to the bug address.
> >
> > Sounds like what I do with the TODO list now.
>
> Except that this is the *worst case* with the bug tracker, whereas for
> the TODO list it is not only the worst case, it is also the best case
> and the only case at all.

And it requires no additional work to ignore threads.

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

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
> > > (hopefully not forward) the interesting messages to the bug address.
> >
> > Sounds like what I do with the TODO list now.
>
> Except that this is the *worst case* with the bug tracker, whereas for
> the TODO list it is not only the worst case, it is also the best case
> and the only case at all.

And any number of people can manage it (just like the wiki).
--
Jim Nasby decibel@decibel.org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Bruce Momjian <bruce@momjian.us> 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 point, but you can go to the archive for the next month
>> and it continues there? I find that artifact somewhat annoying. The
>> bug report would continue receiving the CC'ed mails, so it would record
>> them all in a single place.

> Not crossing month boundaries is super-annoying.

Indeed, but that should be fixed. I can't imagine that one
presumably-fixable deficiency is grounds for changing our entire
discussion infrastructure. Or do you think we will find something
else that has no deficiencies of its own?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

Bruce Momjian <bruce@momjian.us> 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 point, but you can go to the archive for the next month
>> and it continues there? I find that artifact somewhat annoying. The
>> bug report would continue receiving the CC'ed mails, so it would record
>> them all in a single place.

> Not crossing month boundaries is super-annoying.

Indeed, but that should be fixed. I can't imagine that one
presumably-fixable deficiency is grounds for changing our entire
discussion infrastructure. Or do you think we will find something
else that has no deficiencies of its own?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> 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 point, but you can go to the archive for the next month
>>> and it continues there? I find that artifact somewhat annoying. The
>>> bug report would continue receiving the CC'ed mails, so it would record
>>> them all in a single place.
>
>> Not crossing month boundaries is super-annoying.
>
> Indeed, but that should be fixed. I can't imagine that one
> presumably-fixable deficiency is grounds for changing our entire
> discussion infrastructure. Or do you think we will find something
> else that has no deficiencies of its own?

Very much agreed, however, changing how it's done might open up ways to
change other things for the better - things we can't do now. But getting
rid of that annoying thing alone does not change anything else, or
require changing of anything else.

//Magnus

---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate