[Freeciv-Dev] limitations of the bug tracker (was Re: Re: Improved game starting version 5 (ready?))

[Jason Short <vze2zq63@xxxxxxxxxxx>]

Petr Baudis wrote:

> Dear diary, on Sat, Jan 05, 2002 at 08:08:38PM CET, I got a letter, where
> Daniel L Speyer <dspeyer@xxxxxxxxxxx> told me, that...
> > On Sat, 5 Jan 2002, Jason Short wrote:
> > > Daniel L Speyer wrote:

> > > You *are* supposed to reply to bugs@freeciv, that allows the reply to be
> > > listed as a followup in the bug report.  But you need to make sure the
> > > message subject has the PR# in it so that bugs@freeciv can link it
> > > correctly.
> > Huh?
> >
> > I'm confused now.
> >
> > If the bugs listserve handles replies correctly, then why doesn't it pick
> > them up in CC's?  What exactly are the bad- and good-case scenarios here?
> >
> > BTW: is there a good way to get my PR#?  I assume it's somewhere on the web
> > interface, which I generally don't use -- do I need to?
> >
> > Sorry to cause additional trouble,
> Basically - when you reply to both freeciv-dev and bugs, it's a problem, as the
> mail will get duplicated and the original post will cause troubles ;-) - see my
> post before. It should be just enough to post everything only to bugs, and if
> it accidentally won't get forwarded, bounce it here manually.
Well, it's not *quite* that bad.  There are two problems here:

- When you send mail to both freeciv-dev and bugs@freeciv, it'll get 
duplicated on the list twice since bugs@freeciv automatically forwards 
it.  This is annoying, but only minorly so.
- When a bug is _initially_ submitted by sending it to both freeciv-dev 
and bugs@freeciv, the bug tracker will automatically append the PR# to 
the subject but freeciv-dev will not.  If people then reply to the wrong 
e-mail (the freeciv-dev one), the bug tracker will have no way of 
knowing the PR# and will just open a new bug.  This is more annoying.
I think the solution in both cases is just to send mail only to 
bugs@freeciv, until and unless we can confirm that it fails to forward 
messages.  But especially do this when you first submit a patch, as that 
will avoid the second (larger) problem as well.
jason