[GRASS5] Dealing with old bug reports: new GRASS 6 bugtracker?

Bernhard Reiter bernhard at intevation.de
Thu Aug 11 06:38:56 EDT 2005

On Wed, Aug 10, 2005 at 10:57:34PM +0200, Maciek Sieczka wrote:
> From: "Bernhard Reiter" <bernhard at intevation.de>
> >If you wrote a reply, you can "take" the issue and then
> >a reply of the user will be directed to you and you do not miss it.
> Indeed. But if I went this way during the cleanup, I would have to "take" a
> lot of bugs, while only developers who really fix the bug should "take" them
> so they have full control on an issue. Besides, missunderstandings are be
> possible - I might be taken for a developer fixing the bug :DDD.
> A good solution for me would be simply to CC any message sent to
> grass-bugs at intevation.de to my address werchowyna at epf.pl temporarily, so I
> keep an eye on everything - those of my particular interest mainly. After
> all there is not that much traffic in the RT and I don't mind some extra
> spam. That'd be a workarond until you can craft neat, new bugtracker for
> Grass. Is my idea hard to implement?

Unfortunately: Probably yes.
I cannot say for sure until I have tried.

> One remark more. I noticed that a "reply" from the RT interface sent as a
> "guest" is sent *only* to the RT itself and the bug owner, while the
> requestor doesn't get a copy. Only when I "reply" as a registered user
> "msieczka" both requestor and owner are CC'ed. Why the difference? I think a
> reply from a guest should be taken same as from a registerd user, you never
> know who has an idea.

No idea, this might be simply a bug or has a meaning.

> I still think that CC'ing grass5 list all the messages to
> grass-bugs at intevation.de by default is a good idea. 

If this is what most people want, I will try to make it happen.
It will be the same implementation effort than above.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.osgeo.org/pipermail/grass-dev/attachments/20050811/0607cb77/attachment.bin

More information about the grass-dev mailing list